> But the solution needs to be multi-pronged. How do we make web content that can last and be maintained for at least 10 years? I've a boring solution to add t

> But the solution needs to be multi-pronged. How do we make web content that can last and be maintained for at least 10 years? I've a boring solution to add to this list to address hosting. It's boring, dependable, and sadly no one will likely ever use it: Encourage users to download your web pages. The skeuomorphic label of "bookmark" really doesn't fulfil it's metaphor. Books don't change when you insert bookmarks, you can keep them around for decades, fingerprints, underlines and all - revisit them later in life and no external dependencies beyond keeping a roof over them will affect those properties. The nature of the web as hosted on remote servers is a moving target, "bookmarks" are merely links on a clock waiting to be broken, it's inevitable. Making lean downloadable front end content is not hard (for the vast majority of content), but unpopular, convincing authors to do it is hard. Harder still is convincing a society spoiled by the convenience of search engines to embraces such an antiquated idea: downloading content for the value of some guaranteed, localised permanence. Perhaps the best chance we have outside of more radical "IPFS" ideas, to extend the existing web, might be to simply build this into the browser, probably a plug-in at first - something that changes bookmark into bookcase. Browsers can already sort of "save" a web page, they just need to do it in a scalable way to try to accommodate the way most web pages are not built in a self contained manner. e.g back it with a content addressed file system or database. At which point it's feasible to turn this into a simple button without taking up 20MB for every page.