Is anyone still (or has anyone ever) used IPFS in production?
I’m not talking about technology demos such as Wikipedia-on-IPFS (which indeed worked and was impressive) but where IPFS is actually being relied on for some functionality.
Is anyone still (or has anyone ever) used IPFS in production?
I’m not talking about technology demos such as Wikipedia-on-IPFS (which indeed worked and was impressive) but where IPFS is actually being relied on for some functionality.
At meta, there was a project for delivering binaries of internally built libraries / binaries to dev laptops using a private ipfs network. This was live for at least some period of time.
https://swap.cow.fi uses it for order metadata registering iirc
Yeah.. IPFS is a bit disappointement. I was a bit exceited about it back in the day. Recently, I wanted to download sth large from archive.org, I used torrent (and my legacy torrent client) and it worked like a charm!
It seems pure HTTP tracker + Torrent is good enough.
It doesn't seem like it's popular to put old game ROMs on IPFS...? And that surprises me...
And why would you do that? As opposed to, say, distributing via BitTorrent or serving them using a good-old HTTP server?
edit: Not opposed to the idea, just curious what makes you pick IPFS over the existing alternatives.
NFT artwork, if you count that. Briefly checked, the ones that were traded for the most were using IPFS rather than HTTP. But I also don't trust that these aren't self-wash sales (easy given the "NF" part), also NFTs are dumb.
I don’t think NFTs (should) count: My first impressions of web3 by Moxie Marlinspike
https://moxie.org/2022/01/07/web3-first-impressions.html
I agree that purely in the dApp sense, NFTs never fully took off. The blockchain tech made it theoretically distributed, but the interest in NFTs died off way before that mattered, so we only ever saw effectively centralized versions of it.
I personally had no interest in seeing the decentralized one either, but there are people who collect digital things for some reason. In that case would've needed convergence on one JSON format at least for the 99% use case of still images, and agreement to put the heavy assets on IPFS instead of HTTP (it was a mix). Maybe axe some of the confusing features like editions.
It's funny because even in Piracy, IPFS has never really taken off and that's a massive use case.
It slowly was taking off—e.g. Library Genesis on IPFS[0]—but then IPFS introduced Bad Bits Denylist [1] which killed it on arrival.
[0] https://freeread.org/ipfs.html
[1] https://badbits.dwebops.pub/
Also public key lists like what Whatsapp now publishes