Link rot and 'back it up' as a founder-side habit
"If you love a website, back it up" got agreement from people watching their bookmarks decay. One lamented that buthowdoitknow.com, a visual CPU emulator, went offline. Another said they used wget over the summer to save favorite blogs. The Hacker Times project (an NYT-style HN front page) sparked the adjacent wish for a daily or weekly curated paper, and a commenter noted that because it depends on ChatGPT it is blocked in places like Hong Kong.
The pattern: people are realizing the web they relied on is not durable, and that building on a third-party service (a domain, an API, a model) inherits that fragility. The Hacker Times reachability note shows it concretely: your dependency's geography becomes your product's geography.
This is a small thread, but it echoes bigger infrastructure worries in the wider stream, like Docker pulls failing in Spain during La Liga matches because of Cloudflare blocks.
So what?
Archive what you depend on (docs, data, key references), and check your product's reachability in markets you care about. Give users an export path, because your own site will be someone's lost bookmark someday.