Comment by toomuchtodo

Comment by toomuchtodo 2 days ago

IPFS [1] requires a gateway unfortunately (whether remote or running locally). If you can use content idents that are supported by web primitives, you get the distributed nature without IPFS scaffolding required. Content is versioned by hash, although I haven't looked to see if mutable torrents [2] [3] are used in this implementation. Searching via distributed hash tables for torrent metadata, cryptographically signed by the publisher, remains as a requirement imho.

Bittorrent, in my experience, "just works," whether you're relying on a torrent server or a magnet link to join a swarm and retrieve data. So, this is an interesting experiment in the IPFS, torrent, filecoin distributed content space.

[1] https://ipfs.tech/

[2] https://news.ycombinator.com/item?id=29920271

[3] https://www.bittorrent.org/beps/bep_0046.html

amelius a day ago

You don't hear much these days about IPFS, but I can remember one big problem with it was illegal content and how to deal with it.

Reply View 1 reply

grumbel 20 hours ago

It's worse than just illegal content. Copyright doesn't allow you to redistribute anything without the permission of the copyright holder. IPFS however has no means to track the author or the license of content.
That means even distributing a piece of perfectly legal Open Source becomes illegal. Unlike a tarball or even a torrent where you can bundle content and license, IPFS allows addressing individual files or blocks, thus stripping the license from the content, which most licenses forbid. This does not even require an intentional action on the user, but happens automatically by partial content landing in your cache.

Reply View | 0 replies