6 ms·
Is IPFS working these days? I was very excited about it eight years ago, to the point where I made one of the first IPFS pinning services, but lost all my inter
by stavros 3y ago
Is IPFS working these days? I was very excited about it eight years ago, to the point where I made one of the first IPFS pinning services, but lost all my interest. IPFS is a great idea, but the implementation basically doesn't work, and it certainly doesn't work to the point where people can be running the node locally.
It used to have tons of problems discovering content from other nodes on the network unless it was directly connected to them, and it broke often. It also didn't seem like Protocol Labs worked on any of these problems at all, focusing on launching a cryptocurrency instead.
Has it changed now?
- Borg3 3y agoWell said. I too was looking at IPFS few times, but hardly could find a place to use it. Im a big fan of distributed storage or self hosting, but IPFS is far too static for anything usefull, except maybe archives of import static blobs.
- diggan 3y agoWhat exactly are you unable to build with IPFS that requires it to be even more dynamic than what it is? I've found it flexible enough for most use cases I've had in mind, as long as you're flexible on how they architecture should look.
- Borg3 3y agoThats the point. I cant kinda wrap myself into it. I cant see it anything more that distributed object storage. So, calling it a future web is kinda exaggeration imo. Not sure. I host very simple web pages myself, and yet they are pretty dynamic on output. Can you point me to some interesting projects that utilize IPFS?
- 2color 3y agoSee https://awesome.ipfs.tech/ https://awesome.ipfs.tech/ and https://ecosystem.ipfs.tech/ https://ecosystem.ipfs.tech/ for some projects using IPFS
- Borg3 3y agoThx. Seems im too old fashioned or sth.. Most projects are out of scope. Some are interesting, and some are weird, like IPFS chat or Push to talk. I think I will stick to my good old web for now :)
- diggan 3y agoWell, I guess it depends on your use-case. As a general and public discovery / providing / downloading network, it's been kind of overloaded for the last years, and it finally seems like Protocol Labs is putting some efforts to solving some of the most biting issues. In this case, it's about the process of adding content to the network. It was neigh impossible to add large directories/files as your connections got overloaded with provide messages. This seems to batch things up and parallelize better, so should at least make it easier to add content and subsequently find it for the peers who want to. But, the implementation still works very well when you're doing your own networks, which I think is a much better use of the protocol anyways. So when building a application with IPFS, you're using your own network only composed of nodes that are actually relevant to your application, instead of connecting to the public DHT. Unless your scale is really big, it'll work a lot better than using the already huge public DHT.
- 9dev 3y agoI hope the irony of a protocol called „Interplanetary file system“ being more suitable for local usage isn’t lost on people :)
- diggan 3y agoI hope you don't believe I wrote something about that IPFS is only suitable for local usage. You can have your own remote network, spanning whatever nodes/computers/servers you want, remote or otherwise :)
- _factor 3y agoFunny enough. Interplanetary refers to the ability to know a file created on earth would still hash to the same value if an alien created it on Alpha Centauri. You could both work independently and combine your databases and the distance wouldn’t matter. That’s seems pretty local to me.
- londons_explore 3y agoI think it would be better to fix the public network than to split the network into millions of local networks... The public design today still allows actual file transfers to be local over your local network - it is only metadata that goes over the public internet.
- theK 3y agoI also was very active in the early IPFS days. I think two points really atributted to your experience 1. Success: IPFS got tons of usage early on so scaling the software (which back then was mostly a prototype) was challenging, especially with Bennett's BDFL initial stance. 2. The need to codify an incentives market which then lead to the creation of filecoin took a lot of effort and setting up a trustworthy org around that one and ipfs got even more challenging So Yes, working with IPFS was not plain sailing (and still isn't) but it seems that by now the two projects have been set up to start iterating again and I see a lot of great work happening on both fronts so it looks lika a promising future here. Source: I have worked and am still working with both IPFS and Filecoin as part of my business
- noman-land 3y agoCan you say a bit about using it for your business? Curious how people are using IPFS in the real world.
- theK 3y agoApart from the obvious web3 stuff there are some interesting usecases for classical enterprise software. Caveat, my experience is limited to clusters below 100 nodes. You can run your private IPFS DHT if you want and the protocol has some cool load shedding features. There is also IPFS cluster which adds data availability features to your IPFS deployments. When we tried private IPFS networks the cluster project was relatively early and we found that managing DA in the application that owns the data ended up being more straight forward so we didn't use that but I've heard good things lately. If you don't need to enforce access management across your internal data calls it can be an interesting alternative to stuff like minio or ceph. YMMV but my experience was that, running a private IPFS cluster can be easier and much more flexible than running a similarly scaled minio or ceph deployment. It can be seen as a shift left like DevOps is. Instead of having each internal app on your project depend on a Data team that manages Ceph or another data storage and access technology you run (most of) it yourself.
- zubairq 3y agoI’m actually using it for sharing enterprise components so that a document saved in one company can be sent to another company and the document loads content from IPFS. All this without needing a central server
- KirillPanov 3y agoIPFS is propped up by AI companies. When it becomes clear that their models were trained on library genesis, they are betting that "but our web crawler stumbled into it through cloudflare's gateway" will be a good enough excuse to keep them out of prison. This is basically the only thing IPFS offers that Bittorrent doesn't.
- j_maffe 3y ago> This is basically the only thing IPFS offers that Bittorrent doesn't. Now that's simply just untrue. The main difference from Bittorrent is that it relies on Content ID, not torrent links. IPFS is used by many organizations and individuals more than just AI companies.
- yieldcrv 3y agoIt works great for my use case Since you havent looked, people are using Protocol Lab’s crypto version of IPFS to pin on IPFS Filecoin+IPFS is far more free than any of the IPFS SaaS pinning services and it has decent replication too I serve over CDNs, of which there are many, and they cache well enough. I use it to stay on Vercel and Netlify’s free tiers for my static assets, so my sites can have huge spikes in traffic but my static assets are not loaded from them. Its free on free, big use case for exploratory projects https://web3.storage https://web3.storage does that filecoin+ipfs pinning
- yiannisbot 3y agoWe've been doing quite extensive measurements over several parts of the architecture, which you can find here: https://probelab.io/ https://probelab.io/ Still lots to optimise, but wouldn't say it's unusable. In fact, performance is pretty good for a decentralised P2P network.
- simonw 3y agoI mostly lost interest in it when I learned that it's possible for a file published to IPFS to simply blink out of existence one day in the future (if no one is left pinning it). At that point I'd rather stick something in an S3 bucket and pay for it myself.
- stavros 3y agoI didn't mind that too much, because IPFS is strictly better than S3 in that regard. IPFS isn't meant to make it so that you don't need to host your own files, but rather that I can seamlessly host your files too. In that regard, it's much more available than any HTTP server.
- detaro 3y agoa file on S3 will simply blink out of existence too one day if you stop paying for one specific someone to "pin" it, so I don't think this point makes that much sense without further context?
- simonw 3y agoI care about making things available to other people. My initial attraction to IPFS was that it looked like it could help me do that - but then I learned that just publishing a file to IPFS doesn't permanently solve that problem for me. It solves caching/distribution, but it doesn't solve make-this-thing-available. I've been using and paying for S3 for this purpose for 15+ years. I was hoping IPFS could offer a better alternative, but I don't think it does. I might consider IPFS in the future if I need to distribute a prohibitively large file and my target audience are the kind of people who can access IPFS.
- Karrot_Kream 3y agoThe Cloudflare gateway works pretty well for this honestly. You can send an HTTP request yourself to the Cloudflare gateway after pinning a file and Cloudflare will generally have it available.
- kkielhofner 3y agoI have a similar take with slightly more recent experience. When it came down to it the resource requirements for an IPFS node were pretty insane relative to the "value" provided and by many takes it still basically didn't "work". I understand it's not the same thing at all but in the days of running a web server on nearly anything than can handle many thousands of requests/sec an IPFS node running on the beefiest hardware we could throw at it ate tremendous amounts of system resources and bandwidth for double digit requests per second, and even then it would frequently time out and/or get into various unrecoverable states necessitating a service restart. We had to run a cluster of them and watch IPFS nearly melt the hardware... We tried every IPFS implementation available and ended up having to use the "least worst" while also adding a lot of instrumentation, health checks, etc around it just to keep it up and running in some kind of consistent, usable fashion.
- aftbit 3y agoI briefly ran an IPFS node, I believe working towards the same project that you are discussing. It ate my home network: drove my packet loss into the 10% range and somehow convinced my core switch (a Brocade ICX6610) to send all traffic to every port. When I saw every port on my upstairs switch blinking like crazy and tcpdump showed traffic intended for a downstairs server arriving at my upstairs workstation, I pulled the plug and told free he was on his own.
- kkielhofner 3y agoThis was for an internal project, but yeah your experience sounds about right.
- omginternets 3y agoI'm quietly using it in a side-project of mine that is intended to provide a cloud-esque environment to a permissioned p2p compute cluster. In my case, it's basically providing S3-like functionality, which works rather nicely in a datacenter environment.
- evbogue 3y agoI don't mind pinning, but back in the day I was having issues using IPFS to transfer small files between devices. I admit I haven't investigated to see if the problems were ever resolved. I've been watching https://github.com/ipfs/helia https://github.com/ipfs/helia which is going to replace https://github.com/ipfs/js-ipfs https://github.com/ipfs/js-ipfs and hoping they can get an IPFS node working in the browser.
- b_fiive 3y agoDepends on how you define working :). I'm a 6+ year vet of the IPFS ecosystem, we work on iroh these days, which I think addresses many core issues with the protocol design: https://iroh.computer https://iroh.computer The biggest challenges still unaddressed are twofold imho: 1. The network is very forgetful. Stuff you added 24 hours ago is likely gone unless you've taken specific steps to keep it up. This is hard because all CIDs in IPFS have equal weight, which makes it very hard to cache intelligently. 2. The implicit promise that IPFS will resolve _any_ of the 86-100k new CIDs it sees daily in "normal internet" times, (sub-second TTFB). This doesn't work in practice, because mapping content addresses to location-based providers who are under high churn is, well, very hard. Both of these problems are "content routing" problems, which is the core of "get me stuff from this hash, I don't care where" interface IPFS offers. It's hard. With iroh we just don't make that promise at all right now.
- stavros 3y agoI hope you succeed!
- anacrolix 3y agoIPFS has ruined the public perception of what a content addressable network could be. Now when you mention CAD, people think IPFS and freak out about bad performance and flakiness. It's a real shame because we already have a fantastically reliable CAD and DHT in BitTorrent, and it's trivial to build on top of that to create excellent experiences.