assembled some issues to track for activity. Size can balloon pretty quickly depending on what is backed up
- Estimate the required space · Issue #363 · seedvault-app/seedvault · GitHub
- Make the size of the last backup visible · Issue #362 · seedvault-app/seedvault · GitHub
- implement backup rotation / limits · Issue #559 · seedvault-app/seedvault · GitHub
(as of now, a follow up to 2. isn’t opened: “let the user set a specific backup count”)
I myself do include a Signals backup target directory. It’s one multi-gigabyte blob that isn’t friendly to incremental backup. Though there was a chunked PR in 2022 that was then acknowledged (but not merged) and I see “local archive export” from 2024 that feels to be still behind a feature flag not yet enabled.