dweb-archive

List of references https://en.wikipedia.org/wiki/Wayback_Machine https://blog.archive.org/2025/09/02/looking-back-on-preservi... https://archive.org/web/petabox.php https://en.wikipedia.org/wiki/PetaBox https://ipfs.tech/ https://github.com/internetarchive/dweb-archive https://en.wikipedia.org/wiki/Internet_Archive https://www.eweek.com/storage/making-web-memories-with-the-p... https://internetarchive.archiveteam.org/index.php/PetaBox https://blog.archive.org/2010/07/27/the-fourth-generation-pe... https://hackaday.com/2025/11/18/internet-archive-hits-one-tr... https://www.computerworld.com/article/1562759/the-internet-a... https://www.datacenterknowledge.com/business/internet-archiv... https://www.rootsimple.com/2023/08/inside-the-internet-archi... https://richmondsunsetnews.com/2017/03/11/internet-archive-p... https://en.wikipedia.org/wi

I spent a bit of time trying to find it just now but I swear I read a super long blog or comment or something by someone at archive.org where they concluded essentially that IPFS just "isn't ready" or wasn't feasible for their needs because it's super slow and they didn't see how that couldn't be the case when they consider the volume of transactions they need to do (they didn't see an optimization path). I wish I could find that article! edit: https://github.com/internetarchive/dweb-archive/blob/master/...

Which has a rather lengthy section explaining why it's currently a failed experiment: https://github.com/internetarchive/dweb-archive/blob/master/... (this doc is 5-6 years old though, and I'm not sure what may have changed since then) In my own (toy-scale) IPFS experiments a couple years ago it has been rather usable, but also the software has been utterly insane for operators and users, and if I were IA I would only consider it if I budgeted for a from-scratch rewrite (of the stuff in use). Nearly uncontrollable and unintrospectable and high resource use for no apparent reason.

Done. It is called IPFS. The IA already supports it. https://github.com/internetarchive/dweb-archive/blob/master/...

How does one contribute? In the article you linked: > there is no information on how users can get involved in the decentralized version of Archive.org and who the peers are that are distributing the content. The other link doesn't mention how people could help host data either. If there is a way, then it seems like more of a marketing issue if those willing are unaware or unable to figure out how. I can't find any actionable steps on how to contribute. edit - it seems the dweb version was a frontend for archive.org testing serving IA content over alternative protocols. It was never finished or expanded on unfortunately. Links to it are dead but here's the github repo https://github.com/internetarchive/dweb-archive

Its still an experiment to see what was possible with a big site, in today's browsers using some of the emerging tools (IPFS, WebTorrent, GUN). We only test on absolutely current releases of Chrome & Firefox. If you run into problems on the site, there is a feedback button, otherwise you can report directly on https://docs.google.com/forms/d/e/1FAIpQLSe7pXiSLrmeLoKvlDi2... or open an issue on https://github.com/internetarchive/dweb-archive/issues

If you run into problems, I'd love to know specific details - this is an experiment to see what was achievable with Dweb tools like IPFS, WebTorrent, Gun on browsers, with a big site like the Archive. It certainly pushes the edge of browsers - and does use the latest ES6 features without much attempt to support older browsers (unlike the production site at archive.org). We only currently test in the latest Chrome & Firefox, though it seems to work (mostly) on current Safari on iPad and iPhone and I heard its working on Android though I haven't seen it yet. If you can get on, there is a feedback button, if you can't feel free to go straight to the form at https://docs.google.com/forms/d/e/1FAIpQLSe7pXiSLrmeLoKvlDi2... or open an issue on https://github.com/internetarchive/dweb-archive/issues .