ipfs

Interested to hear thoughts from ipfs-heads.

Toying with a project idea for decentralising public domain media and documents to preserve and protect historical information.

However the data is so vast that renting space from ipfs services would be extortionate.

Is the sensible way forward to self-host on hardware?

There are a lot of projects working on this. eg Internet Archive is doing some IPFS/Filecoin experiments. 

IPFS gives you a permanent immutable content address. 

You’re going to want different techniques for long term, redundant persistent storage. 

Or lean into users: IPFS desktop on 1000s of home users.

Ironically as I was looking into it I noticed that archive.org had optional ipfs as well. It seems like they are beginning to move that direction (which is great to see).

My thoughts were to bring together a community that would all share and partake in the hosting, but my fear is it would be a money pit for everyone.

Web Tinkerer. DWeb. Open Source. Community. Just another one of the bees 🐝

The nice thing about IPFS is content addressing. Anyone can help keep content online. 

Lots of people are like “this free gateway is too slow for my production app”. Yeah you’re going to need to get good at hosting … or pay someone. 

Just like for a web2 service.

More turnkey home options are good too.