view the rest of the comments
datahoarder
Who are we?
We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.
We are one. We are legion. And we're trying really hard not to forget.
-- 5-4-3-2-1-bang from this thread
https://ipfs.tech/
I think this is the main technology behind that and it is open source... I heard something about it years ago too. I've similarly never used it and am curious now that you mention it if anyone has. I'm unsure how to actually "use" ipfs and/or what tools might use it.
I'm kind of inclined to believe it doesn't work (or doesn't work well) otherwise it probably would be a bigger deal by now and there would be a lot to show off on the ipfs website.
Edit: It looks like this provides S3 compatible storage to IPFS. However, it seems more expensive than B2... So I'm not really sure why one would use it. You'd think IPFS would be attempting to undercut traditional providers.
Note: every file on Ipfs is unencrypted and semi-public unless you encrypt before upload.
Should be standard operating procedure anyway...
Is a local ipfs cluster perhaps the best way here, or does that also connect itself to the global ipfs? https://docs.ipfs.tech/install/server-infrastructure/#features