3 ms·

I am probably missing something then, but as far as I can tell most of the value proposition of ipfs is the single universal dht. if you remove or fragment it n

by somat 3y ago

I am probably missing something then, but as far as I can tell most of the value proposition of ipfs is the single universal dht. if you remove or fragment it now all you have is basically a worse bittorrent. Most of the interesting things I want to do with ipfs involve the dht, any sort of file transfer is usually a secondary concern.

diggan 3y ago
> I am probably missing something then Yes :) There can be multiple implementations using the same specification and still be compatible. For example, the new "facelift" they talk about in the submission article would be a new implementation, but still compatible with the old one, as they would (publicly) mostly have the same interface, so they can still talk. There are many IPFS and libp2p implementations already, and they mostly aim first to be compatible with each other, so even if they work differently inside, they can communicate. Similarly as with BitTorrent where many clients implement the same specification and can therefore exchange data still, just like TCP or basically any protocol.