Index
Practice
The operational half: what an export actually contains, where a sync silently stops, how to audit a collection for rot, and what a service owes its users when it closes.
Published 2026-08-06 · Status of facts checked 2026-08-06
If a service you use is closing, start with what a shutdown notice should tell you and then what survives an export. If nothing is closing and you simply have too many saved links, audit them for rot first — knowing what is already dead changes what is worth moving.
-
The accounts are closed: what happened to this community, and what a shutdown notice should tell you
This path served a registration form until about 2010; no accounts exist, no data is held, nothing will be restored, and the windows other services gave their users when they closed are the most useful thing this page can now show.
-
Pocket is gone and you have the CSV: what survives an import, field by field
Migration guides say the export is straightforward. The question that actually costs people their library is narrower: which fields the export contains at all, and which of those any given importer reads.
-
One Hundred Thousand: the Bookmark Sync Ceiling, and the Years It Went Undocumented
Chrome stops syncing bookmarks at one hundred thousand nodes — a number enforced by default since March 2023, declared in Chromium’s source, absent from Google’s support article as late as a capture of 2025-12-26, and attached to an error state that in one case clears on a thirty-day timer rather than on anything a reader does.
-
Auditing a link collection for rot: what to check, in what order
Checking whether saved links still work is not one job but four, and the standard advice — use the Wayback Machine — answers only the third of them.