2 ms·
> You don't really "upload" anything to IPFS, ever, that's not how the protocol works. You "provide" something and then if someone requests it, you upload it di
by londons_explore 3y ago
> You don't really "upload" anything to IPFS, ever, that's not how the protocol works. You "provide" something and then if someone requests it, you upload it directly to them.
This model should be changed... I should be able to just send something to the network, having other users store it for me, and come fetch it back later.
The whole idea that I am constantly online 'pinning' files is a bad one. The whole idea that I must store the specific files I want to make available to others is also a bad one. The network protocol should mix file data beyond recognition, and the exact data on my hard drive should have little correlation to the data I specifically am sharing with others.
- diggan 3y agoThat particular thing is one of the fundamentals of the protocol. If you want something else, then IPFS really isn't what you're looking for. If that model is what expected from reading the landing page, then I guess the landing page doesn't clearly communicate how it works. What you're asking for is a bit like asking Bittorrent to suddenly change their model to a model where people can push data onto other nodes. If that is truly what you want, probably something like Freenet (https://en.wikipedia.org/wiki/Freenet https://en.wikipedia.org/wiki/Freenet) would be more suitable, as it's highly unlikely IPFS would change the protocol in such a major way.
- dale_glass 3y agoWhat you want then is the old Freenet. But that model also sucks. People have to contribute a pool of storage to the network, and data is spread through it by uploads and usage. It's extremely prone to losing data especially with big files, and it's low capacity because content needs a lot of duplication to actually be reliably retrievable. And if nobody wants it for long enough it'll fall off the network entirely.