Hacker News Reader

Comment by algo_trader | Hacker News Reader

Also, is this suitable for publishing an RSS-like feed which out polluting the world with a new torrent for each atom?

It depends. You an either have your mutable torrent point to the head of a liked list like this:

    head
    |
    |- post.txt
    +- prev.torrent

    prev
    |
    |- post.txt
    +- prev.torrent

You get the idea. With the not yet widely-supported BitTorrent v2, you can just add files to a new torrent and seeders of the old torrent will seed the files that are also in the new torrent too.

What are the challenges slowing the v2 deployment? Client uptake?

My reading of the situation is that for 99.99% of data currently transferred by Bittorrent, v1 works just fine. And for many use cases, the ability to do something like change an already created torrent would actually be detrimental. It's not that v2 is actively bad, it's just that it's designed for a different audience than currently uses Bittorrent, and will take time for that new audience to find it.

Yes and no - DMT (https://github.com/lmatteis/dmt) is implemented into this so you can use a single hash in the DHT for the 'site', but that will be updated to point to a new torrent infohash on every update.

Reply on news.ycombinator.com