3 ms·
Well, 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,
by diggan 3y ago
Well, 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.
- diggan 3y agoSure, ideally that'd be the case. But today that kind of isn't feasible as discovering and providing content is slow, but hopefully it gets better in the future with changes like this and more. But what I wrote is how you can solve the issue today.
- stavros 3y agoThat's kind of a shame, the appeal of a public, peer-to-peer, content-addressable network was very high to me personally, because of its relative uniqueness. For a personal network, IPFS becomes just another technology I could deploy, out of many options.
- diggan 3y agoYeah, definitely I feel the same about the public parts, but I still find the public-but-private network part of it useful in itself. Both have use cases, but currently the public one just isn't feasible to use :/