Thanks! At the moment we’re focused on archiving rather than read-later workflows, but this is great feedback. I’ve already added it to the feature requests list.
I maintain an open-source project called Linkwarden and this exact discussion is one of the reasons why it exists, teams needed a way to preserve referenced URLs reliably without having to depend on external services.
It stores webpages in multiple formats (HTML snapshot, screenshot, PDF snapshot, and a fully dedicated reader view) so you’re not relying on a single fragile archive method.
There’s both a hosted cloud plan [1] which directly supports the project, and a fully self-hosted option [2], depending on how much control you need over storage and retention.
If you review the project’s history, you’ll notice that Linkwarden was started well before the vibe-coding hype, and even before the existence of ChatGPT.
Sad to see Pocket shutting down. For anyone seeking alternatives, I've been working on Linkwarden[1], an open-source bookmark manager that hit HN's front page twice[2][3]. Plenty of other great alternatives out there too, such as Raindrop (not fully open-source), Karakeep, and Wallabag.
Also, there's an official Linkwarden mobile app in development, aiming to support most (if not all) of Pocket's key features :)
So there are different ways it archives a webpage.
It currently stores the full webpages as a single html file, a screenshot, a pdf, a read-it-later view.
Aside from that, you can also send the webpages to the Wayback Machine to take a snapshot.
To archive pages behind a login or paywall, you can use the browser extension, which captures an image of the webpage in the browser and sends it to the server.