>>/9771/
Here's those 3 files with "especially problematic filenames" (pic related, from ponibooru.org):
https://gateway.pinata.cloud/ipfs/QmVicNf5ZSQLbLvZQUx9G3UPjHcGL6G8TgAEicCm28VrfP
----
I remember that someone criticized me by saying something like this:
> This guy just takes a bunch of already-archived things and saves them to IPFS and Wayback Machine
This is not what I mainly do. And even if I did do that, then so what? And what do you mean by "already-archived"? Saved to web.archive.org Saved to archive.org/details Please realize that web.archive.org can exclude any website they want from being accessed. https://web.archive.org/web/2/http://kiwifarms.net still says "Sorry. \ This URL has been excluded from the Wayback Machine." Maybe in the future they will exclude youtube.com due to copyright laws or other stupid Internet laws. And the WARCs that web.archive.org are based on are not open access, and in 2024 you can no longer find the path to the warc for web.archive.org/[any url]. Data at https://archive.org/details/ (URL prefix is WBM-excluded) can be removed for any reason, like copyright, or if it isn't removed, IA higher-ups may make it loginwalled after consulting with troons.
A solution to this is independent data, such as via peer-to-peer systems like BitTorrent and IPFS, and many things exist in neither of those. We can put less focus on "relying on archive.org to archive things" and put more focus on "actually hosting/creating the archives ourselves and properly dealing with the data+software+hardware"; I bet many archive.org users are inexperienced with the latter.