This is very nit picky. The entire web works by severs “seeding” data to the client, so by your logic you can’t “put stuff” on the web. The difference with torrents and IPFS is you can have multiple servers seeding the same content, and not be dependent on any one.
I’m not making any predictions about how long Z library stays up, but the illegal seeding of movies and tv shows has remained very strong until today.
IPFS is actually worse to put stuff in than the web or torrents, in my experience.
Last time I tried it, the ipfs service used its own storage scheme. Meaning it's not like pointing Apache at a directory. You take your stuff, and upload it into ipfsd first, and it puts that data into its storage system.
So to do this from scratch (not mirroring somebody else's content) needs a minimum of >62TB -- 31TB of content, which ipfsd will then package into 31TB more + overhead in its storage area.
And of course if you're doing this, you're expecting other people to mirror this stuff, so count on hundreds of terabytes of traffic.
So this is easily ~$3K in hard disks alone, plus the NAS/server hardware, plus traffic, plus the willingness to risk the FBI coming and grabbing all of it.
I have entire sites hosted for free this way, whereas other hosts like vercel and netlify will charge you for traffic. you can just put your big assets on ipfs+filecoin pins and have unlimited traffic. the ipfs CDNs help with performance.
IPFS is a caching or distributing layer, not a persistent storage. There are some attempts to make a storage that backs IPFS by Filecoin team (Filecoin and IPFS teams have a lot of overlap.)
Yes, but there are people who claim that IPFS is uncensorable or permanent. I saw that a lot from NFT salespeople who were claiming you’d own something forever with no further payments needed, or even that a copyright claim couldn’t take it down.
tinalumfoil|3 years ago
I’m not making any predictions about how long Z library stays up, but the illegal seeding of movies and tv shows has remained very strong until today.
dale_glass|3 years ago
Last time I tried it, the ipfs service used its own storage scheme. Meaning it's not like pointing Apache at a directory. You take your stuff, and upload it into ipfsd first, and it puts that data into its storage system.
So to do this from scratch (not mirroring somebody else's content) needs a minimum of >62TB -- 31TB of content, which ipfsd will then package into 31TB more + overhead in its storage area.
And of course if you're doing this, you're expecting other people to mirror this stuff, so count on hundreds of terabytes of traffic.
So this is easily ~$3K in hard disks alone, plus the NAS/server hardware, plus traffic, plus the willingness to risk the FBI coming and grabbing all of it.
typingmonkey|3 years ago
tshaddox|3 years ago
blooalien|3 years ago
This is a very good argument for primarily using ipfs to host high quality content that people will want to preserve long-term…
yieldcrv|3 years ago
there is a free service that does this for you till like 5 gigabits, it pins with filecoin
https://web3.storage/pricing/
I have entire sites hosted for free this way, whereas other hosts like vercel and netlify will charge you for traffic. you can just put your big assets on ipfs+filecoin pins and have unlimited traffic. the ipfs CDNs help with performance.
miohtama|3 years ago
miohtama|3 years ago
Xeoncross|3 years ago
acdha|3 years ago