Live data from Hacker News

BitTorrent v2 (2020)

blog.libtorrent.org

61–70 of 155 posts

Re: BitTorrent v2 (2020)

#61
post #4

Earlier quoted context omitted.

i do love that it immediately goes into yet another crypto bashing comment chain while not realising that a crypto company owns bittorrent: https://torrentfreak.com/bittorrent-inc-confirms-acquisition... and that after the creator of bittorrent left he created his own cryptocurrency: https://en.m.wikipedia.org/wiki/Chia_(cryptocurrency)

Reading through the wikipedia page for Chia > The Chia Network was founded in 2017 by American computer programmer Bram Cohen, the author of the BitTorrent protocol.[4] In China stockpiling ahead of the May 2021 launch led to shortages and an increase in the price of hard disk drives (HDD) and solid-state drives (SSD).[5] Shortages were also reported in Vietnam.[6] Phison, a Taiwanese electronics manufacturing compan…

And it wasn't completely original, as Burst (now Signum) was a cryptocurrency using storage space for mining back in 2014.

Re: BitTorrent v2 (2020)

#62
Can someone explain how the Merkle-tree concept is useful? I didn't quite catch that part. On the one hand it is says:

> all you need is the root hash of the tree.

but on the other hand:

> the .torrent file must still contain these piece hashes

So what are we saving here? If a piece hash doesn't match the downloaded data, we re-download the piece.

Re: BitTorrent v2 (2020)

#63
post #38

Earlier quoted context omitted.

Ironically, the company that bought µTorrent was BitTorrent, Inc[1]. They're the geniuses also responsible for forking IPFS, renaming it to "BTFS", and not acknowledging IPFS as an upstream in any way[2]. 1. https://en.wikipedia.org/wiki/Rainberry,_Inc . 2. https://twitter.com/juanbenet/status/1250634833258143744

Wow, that's a bummer, had no idea the people behind the hollowing out and filling with shit of µTorrent include the actual creator of the protocol itself.

If it makes you feel any better about it, that tweet thread is from 2020, and the actual creator of the protocol itself hasn't worked there in a day to day capacity since 2017.[0]

[0]https://en.wikipedia.org/wiki/Bram_Cohen

Re: BitTorrent v2 (2020)

#64
post #38

Earlier quoted context omitted.

In the beginning I used µTorrent, until it got fucked by whatever company that bought it. It was easily the fastest and most resource-smart client I've ever used. After that I tried a bunch, Deluge, Transmission, Azure and plenty more, but only qBittorrent seems to be a suitable replacement (and is open source as well). Now it has BitTorrent V2 support too :) You should really give it a try.

Ironically, the company that bought µTorrent was BitTorrent, Inc[1]. They're the geniuses also responsible for forking IPFS, renaming it to "BTFS", and not acknowledging IPFS as an upstream in any way[2]. 1. https://en.wikipedia.org/wiki/Rainberry,_Inc . 2. https://twitter.com/juanbenet/status/1250634833258143744

BTFS is the product of an entirely different group of people than the ones who were responsible for the uTorrent purchase. BitTorrent Inc was itself bought by cryptocurrency company TRON in 2018. Few people who worked at BT Inc prior to the acquisition are still there, and AFAIK none of them ever worked on BTFS.

Re: BitTorrent v2 (2020)

#65
post #55

Earlier quoted context omitted.

It's from a DHT/BitTorrent crawler that runs around downloading all the torrent metadata it can find I've been running for ages.

Do you make visualizations of the traffic?

Some different views. For instance, to give some sense of a scale for the 250 or so v2 torrents seen every day is, here's a view of the total number of torrents it discovers each day [1]. (Or, more properly, this is the number of torrents it gathered complete metadata and validated against the infohash each day).

One of these days I should find somewhere to put all these bits of metadata I've been downloading.

[1] https://imgur.com/a/8pWhjxD

Re: BitTorrent v2 (2020)

#66
post #57
post #47

Earlier quoted context omitted.

Why are there always people linking to previous discussions then? Including dang himself...

They were doing it for you because you didn't know about that button. But now that you do, they will stop doing it.

Wouldn't it be easier to create an automated comment for everyone else?

Re: BitTorrent v2 (2020)

#67
post #54

Earlier quoted context omitted.

It's from a DHT/BitTorrent crawler that runs around downloading all the torrent metadata it can find I've been running for ages.

cool. Did you write it yourself or are you using an open source project of some kind? Would be interested to run one of these myself.

I stumbled across a DHT crawler, and started running it. Over time I added random things to it, like IPv6 and the ability to download metadata. I was mostly interested in using it to learn how DHT worked both in theory and in practice, and for that, it did it's job.

The page for the crawler I started with is long gone, but this appears to be a reasonable copy on github:

https://github.com/zlzlovezl/simDHT-1

I'm sure you can find other copies, with features added. Looking around, it seems like quite a few people have taken this and made it their own over time.

It's far from perfect in this state, but a fun toy to play with. I will say, from a point of painful experience: The way this crawler works tends to make some of the various people that track such things think you're sharing pretty much all the things. If that's an issue where you live, don't run it from your home connection.

Re: BitTorrent v2 (2020)

#68
post #37
post #6

I assume this is being posted because qBittorrent recently released version 4.4 which includes libtorrent 2.x and therefore support for BitTorrent v2. Hopefully we'll start seeing hybrid torrents/magnets in trackers soon. Although these are mostly automated so I'm not sure how fast the tools will catchup. One thing I'd like qBittorrent and other torrent clients to do is to allow users to upgrade v1 torrents to hybrid…

Unless I'm mistaken, we'd need to settle on a "default" piece size[1] if we were to have automatic upgrading in a client. I learned recently[2] that there's no standard set by the protocol, so Client A might choose a 16KiB piece size, and Client B might take the same files and choose a 64KiB piece size, resulting in two different hashes (v1 or v2!) and thus two peer pools for the same file set. 1. https://stackoverfl…

I'm not sure if the the piece side continues to have bearing when the hashes are all in a Merkle tree on uniform 16k blocks.

"Enforcing these encodings also help make it more likely that two people creating a torrent from the same files, end up with the same info-hash and the same torrent."

In the discussion of backwards compatibility, it appears that v1 collections of identical content encoded with different piece sizes will all become the same v2 collection when upgraded.

Re: BitTorrent v2 (2020)

#69
post #47

Earlier quoted context omitted.

That’s what the “past” button does.

Why are there always people linking to previous discussions then? Including dang himself...

Well, it's certainly handy when using a mobile client that doesn't have a "Past" button, like Materialistic :)

Re: BitTorrent v2 (2020)

#70
post #38

Earlier quoted context omitted.

Ironically, the company that bought µTorrent was BitTorrent, Inc[1]. They're the geniuses also responsible for forking IPFS, renaming it to "BTFS", and not acknowledging IPFS as an upstream in any way[2]. 1. https://en.wikipedia.org/wiki/Rainberry,_Inc . 2. https://twitter.com/juanbenet/status/1250634833258143744

BTFS is the product of an entirely different group of people than the ones who were responsible for the uTorrent purchase. BitTorrent Inc was itself bought by cryptocurrency company TRON in 2018. Few people who worked at BT Inc prior to the acquisition are still there, and AFAIK none of them ever worked on BTFS.

Different team of people, all working in the same company, correct?
Post reply on HN