docs: document cloud backups everywhere; defer phases 3 and 4 - #137
Merged
Conversation
Phases 0-2 shipped and are verified against both real providers, but the feature was only described in /help and the CHANGELOG. README, the FAQ and the comparison page had zero mention of it. - README: cloud backups added to "Own your data" — both providers, the minimum-scope guarantee, streaming, and never deleting anything. - /faq: new "Can it back up to my own Dropbox or Google Drive automatically?" answering the questions that actually matter when you send records to a third party — what we can and can't see, what happens on disconnect, that nothing is ever deleted, and how you find out when a run fails. The export answer now points at it instead of telling people to remember to take a ZIP. - /compare: the "what you leave with" and "if it shuts down" cells now reflect that the archive can already be sitting in the user's own cloud, plus a new "Automatic offsite copy" axis rated honestly across all six approaches. - /help: corrected a real inaccuracy. It gave one path shape for both providers; Dropbox's app folder already roots the path, so only Drive nests under MyTailLog/. Verified against the actual uploads. Phases 3 (S3-compatible) and 4 (two-phase resumable) deferred, with the conditions that would revive them. Phase 4 was always gated on "only if telemetry shows archives near the ceiling" — it now exists and says no: largest real archive is 70 MB against a 400 MB guard, ~22 s against a 300 s budget. Deferred on evidence rather than on a guess, which is what the size guard and byte logging were added to make possible. Claude-Session: https://claude.ai/code/session_01XBNGwWrPih2Xgu6MVrcd6R
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phases 0–2 shipped and are verified against both real providers, but the feature was only described in
/helpand the CHANGELOG. README, the FAQ and the comparison page had zero mention of it.Documentation
/faq— a new "Can it back up to my own Dropbox or Google Drive automatically?", answering the questions that actually matter when you send records to a third party: what we can and can't see (and that it's enforced by the permission requested, not promised), what happens on disconnect, that nothing is ever deleted, and how you find out when a run fails. The export answer now points at it rather than telling people to remember to take a ZIP./compare— "what you leave with" and "if it shuts down" now reflect that the archive can already be sitting in the user's own cloud, plus a new "Automatic offsite copy" axis rated honestly across all six approaches (paper loses to a hangar fire; a spreadsheet only wins if it's in a synced folder; an ops platform gives you their backups, not a copy you hold)./help— corrected a real inaccuracy. It gave one path shape for both providers. Dropbox's App folder already roots the path, so only Drive nests underMyTailLog/. Verified against the actual uploads:/MyTailLog/N9363V/2026-08-03-N9363V.zip/n9363v/2026-08-02-n9363v.zipPhases 3 and 4 deferred
Recorded in
docs/plan-cloud-backups.mdwith the conditions that would revive them, rather than deleted.Phase 4 (two-phase resumable) was always gated on "only if phase-1 telemetry shows real archives near the ceiling". That telemetry now exists and says no: the largest real archive is 70 MB against a 400 MB size guard, uploading in ~22 s against a 300 s budget — roughly 5× headroom on size, 13× on time. Revisit if
backup_run.bytesstarts showing archives past ~250 MB, or if anyskipped_too_largerows appear.Phase 3 (S3-compatible) would mainly serve self-hosters; Dropbox and Drive cover where GA owners actually keep files, and connecting both already gives redundancy across two companies.
These were the two most expensive items left on the plan, and both are deferred on evidence rather than on a guess — which is exactly what the size guard and the byte logging were added to make possible.
415/415 unit tests, typecheck, lint and build clean.
https://claude.ai/code/session_01XBNGwWrPih2Xgu6MVrcd6R