docs(backup): record how Dropbox and Google app status differ - #135
Merged
Conversation
Dropbox development status is fine indefinitely — a development app behaves identically to production and token lifetime is NOT affected by app status. The only limits are on how many accounts link it, so there is nothing to do until we grow. Nuance worth knowing first: the 50th linked user starts a two-week clock to obtain production approval, after which *new* links freeze (already-linked users keep working); development caps at 500. Google is not the equivalent and the same word means something different: an app in Testing publishing status issues refresh tokens that expire after 7 days, which is fatal to a monthly job and fails silently. Publishing to Production stays a functional prerequisite for phase 2, not a growth cap to defer — though drive.file being non-sensitive means no security assessment. Recorded because generalising the Dropbox rule to Google is the mistake most likely to cause a silent outage here: Dropbox status limits how many users, Google status limits how long tokens live. 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.
A doc-only correction to
docs/plan-cloud-backups.md.Dropbox development status is fine indefinitely. A development-status app behaves identically to a production one, and token lifetime is not affected by app status — the only limits are on how many accounts may link it. Nothing to do until we grow.
The nuance worth knowing before we get there: linking the 50th user starts a two-week clock to apply for and receive production approval. Miss it and the app's ability to link additional users freezes; already-linked users keep working. So it isn't "apply whenever after 50", it's "apply within two weeks of 50". Development caps at 500 linked users regardless.
Google is not the equivalent, and that's the point of writing this down. An app in Testing publishing status issues refresh tokens that expire after 7 days — fatal to a monthly job, and it fails silently: every connection dies between runs. Publishing to Production remains a functional prerequisite for Phase 2 rather than a growth cap to defer. (
drive.filebeing non-sensitive still means no security assessment.)Dropbox status limits how many users; Google status limits how long tokens live. Only the second can break a working feature, and generalising the first to the second is the mistake most likely to cause a silent outage here.
https://claude.ai/code/session_01XBNGwWrPih2Xgu6MVrcd6R