4 ms·

The DHT had a big upgrade. Nodes detect their own connectivity status and configure themselves accordingly so that they are not a burden to the network when the

The DHT had a big upgrade. Nodes detect their own connectivity status and configure themselves accordingly so that they are not a burden to the network when they cannot be contacted. This has improved DHT lookups significantly, along with publishing, IPNS etc. I know it is possible to run a public IPFS gateway on 1VCPU+2GB of RAM without issues (+ nginx). So much for the need for a "really powerful computer". In fact, it is more difficult to configure IPFS to take advantage of a really powerful computer than doing it for a low-spec machine (defaults are very conservative). An IPFS peer does not drop connections to peers you have manually connected to. Bitswap (the data interchange protocol) has overhead, true, but to say it is the slowest or that things are stuck for days is a big exaggeration. The author complains about databases on IPFS but I'm not sure about what exactly. Pubsub is a very good way to notify changes to content and it works at scale (see Filecoin). In fact, IPNS also works over pubsub, not only DHT. The author also bashes on "IPFS has used different kinds of hashing algorithms" which is a lie as it always used sha256 by default. A CID obtained 5 years ago works today. In fact, the default options to add content are exactly the same (256KB-blocks, CIDv0, balanced-DAG). In any case, no content-address has ever been broken on upgrade. I'm not sure about the obsession about "flirtation with Ethereum". I would seem the author hates "the Ethereum hoax" and prefers Bitcoin. shrug. In the end, p2p is pretty difficult and IPFS solves many things only to find new issues as the network heavily grows, which is frustrating, but IPFS is nevertheless in constant evolution and improvement.

kova12 5y ago
I don't know if that helps really. All you do in your comment is reiterate the issues and opine that they are not that bad. But they were bad enough for those several times when I tried to use ipfs for my projects, and I am not a noob. There isn't any way some average user would get a value from this project. I think a lot comes down to misrepresentation. When your product doesn't work, make it clear that it's a pre-alpha. When I see version 5.0 released, I expect to see something not just workable, but also mature and stable.
- hecturchi 5y ago
  Latest version of go-ipfs is v0.11.0, not v5.0. In any case, IPFS is not a "product", it is a number of protocols and layers sometimes used together and sometimes not (libp2p, ipld, kad-dht, gossipsub, bitswap, graphsync...). And all of them are in production and sucessfully used, but they also have different levels of maturity and evolve as we have the need and capacity. The fact that the state is not the final "interplanetary distributed rainbow that replaces the web as we know it" doesn't mean it is completely broken either.

kova12 5y ago

I don't know if that helps really. All you do in your comment is reiterate the issues and opine that they are not that bad. But they were bad enough for those several times when I tried to use ipfs for my projects, and I am not a noob. There isn't any way some average user would get a value from this project. I think a lot comes down to misrepresentation. When your product doesn't work, make it clear that it's a pre-alpha. When I see version 5.0 released, I expect to see something not just workable, but also mature and stable.

hecturchi 5y ago
Latest version of go-ipfs is v0.11.0, not v5.0. In any case, IPFS is not a "product", it is a number of protocols and layers sometimes used together and sometimes not (libp2p, ipld, kad-dht, gossipsub, bitswap, graphsync...). And all of them are in production and sucessfully used, but they also have different levels of maturity and evolve as we have the need and capacity. The fact that the state is not the final "interplanetary distributed rainbow that replaces the web as we know it" doesn't mean it is completely broken either.