Closed
Bug 1719392
Opened 3 years ago
Closed 2 years ago
Increase TTL of client and tab records
Categories
(Firefox :: Sync, enhancement)
Firefox
Sync
Tracking
()
RESOLVED
FIXED
105 Branch
Tracking | Status | |
---|---|---|
firefox105 | --- | fixed |
People
(Reporter: markh, Assigned: charlie)
References
Details
Attachments
(1 file)
Over in bug 1718545, a user lost their tabs because they went looking for them after ~8 weeks, but we TTL them at 3 weeks - even though the device still appeared as connected to the account itself. However, desktop actually hides "stale" devices - ie, devices that are no longer connected to FxA - so the primary reason for this short TTL (avoid dupe devices etc) doesn't really apply.
I don't see a good reason not to set these records with a TTL of (say) 6 months, or even longer.
(Note that SyncedTabs.jsm appears to not filter stale clients - maybe it does - someone should spend more than the 30 seconds I took to make sure. If we make this change we should also make it in the rust components so everyone is consistent)
Updated•3 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → chumphreys
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•2 years ago
|
||
Pushed by chumphreys@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e9b5a67453d0 update CLIENTS_TTL to be 180 days instead of 21 r=markh
Comment 4•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox105:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•