5 ms·
I like the IPNS idea. That would be useful even if it was just back-ported to bittorrent
by cowtools 4y ago
I like the IPNS idea. That would be useful even if it was just back-ported to bittorrent
- claudedopplr 4y agoI like the "immutability" of IPFS. Back in 2017 I tried it out and [Dat](https://www.datprotocol.com/ https://www.datprotocol.com/). Both IPNS and Dat seemed to break often (not finding the correct peer, which then lead to broken downloads). With IPFS, you know "it's just a hash of the content". That idea of content addressing is pretty powerful, and I'm starting to see it a lot more, particularly in the NixOS ecosystem. IPNS, on the other hand, seldom worked. The 24hr timeout made it unusable without an abstraction on top that kept it up to date. Dat had a similar problem, one of storing way too much historical data, and I could never be sure if the peers had the same version I las published. I think these are "theoretical problems". Content addressing is a great idea and it's reliable. Distributed hash tables are on the weaker technology spectrum. I'm rooting for IPFS to replace bittorrent, not IPNS/Hypercore, which I think will have serious scalability/security /privacy problems.
- easrng 4y agoIPNS sucks. It's very slow. BitTorrent already has an alternative[1] and it works somewhat better but doesn't have much client support yet. [1]: https://www.bittorrent.org/beps/bep_0046.html https://www.bittorrent.org/beps/bep_0046.html