Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

BitTorrent v2 (2020)

blog.libtorrent.org

Post reply on HN
Print view View original

41–50 of 155 posts

Re: BitTorrent v2 (2020)

#41

Post by banana_giraffe »

nodja wrote: 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…

The release of qBitorrent 4.4 has had an impressive impact. BitTorrent went from something like an average of 10 or so BitTorrent v2 hybrid torrents to 250 or so.

Granted, that's something like 0.4% of the new torrents made every day, but still, it's not a rounding error anymore.

[1] https://imgur.com/a/mPcEaT5

Re: BitTorrent v2 (2020)

#42

Post by muldvarp »

banana_giraffe wrote: post #41
nodja wrote: 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…

The release of qBitorrent 4.4 has had an impressive impact. BitTorrent went from something like an average of 10 or so BitTorrent v2 hybrid torrents to 250 or so. Granted, that's something like 0.4% of the new torrents made every day, but still, it's not a rounding error anymore. [1] https://imgur.com/a/mPcEaT5

Which tracker is this data from?

Re: BitTorrent v2 (2020)

#43

Post by moolcool »

BitTorrent slaps so hard as a protocol, and DHTs are absolutely brilliant. With all of the recent hype about decentralization with the rise of crypto, I'm surprised BitTorrent hasn't seen much hype or revitalization as well.

Re: BitTorrent v2 (2020)

#44

Post by banana_giraffe »

muldvarp wrote: post #42
banana_giraffe wrote: post #41

Earlier quoted context omitted.

The release of qBitorrent 4.4 has had an impressive impact. BitTorrent went from something like an average of 10 or so BitTorrent v2 hybrid torrents to 250 or so. Granted, that's something like 0.4% of the new torrents made every day, but still, it's not a rounding error anymore. [1] https://imgur.com/a/mPcEaT5

Which tracker is this data from?

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

Re: BitTorrent v2 (2020)

#45

Post by nodja »

xd1936 wrote: post #37
nodja wrote: 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…

If I read the article correctly in v2 each file will contain its own root hash, which is calculated by using 16KB "pieces", the piece size for the torrent creation is still used for data transmission between peers and integrity checks.

Re: BitTorrent v2 (2020)

#46

Post by RankingMember »

xd1936 wrote: post #38
capableweb wrote: post #35

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

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.

Re: BitTorrent v2 (2020)

#47

Post by hffftz »

digianarchist wrote: post #31
hffftz wrote: post #28

Earlier quoted context omitted.

It would help if HN would automatically link to previous discussions (next to the title?) if there are any... It seems wasteful having people do it manually

That’s what the “past” button does.

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

Re: BitTorrent v2 (2020)

#48

Post by gh02t »

capableweb wrote: post #35
KennyBlanken wrote: post #34

Earlier quoted context omitted.

A bunch of open-source projects would like to use v2 torrents, but because Transmission is so popular and has zero support for v2, nobody can use them. Transmission's dev team hasn't said a word on the matter, ever, in four years: https://github.com/transmission/transmission/issues/458 Elsewhere someone quipped: > That transmission bug is 4 years old and they've never announced plans to prioritize it (granted the eff…

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.

qBT also has a nice WebUI that has feature parity with the desktop version (or at least near enough that I don't miss anything), which is very useful. Other clients (e.g. Transmission) do too, but I like qBT the most here.

Re: BitTorrent v2 (2020)

#49

Post by guimplen »

marcan_42 wrote: post #21
elcomet wrote: post #16

Earlier quoted context omitted.

unlikely ? all methods are broken eventualy when compute becomes faster

This is not true. Modern cryptography is not breakable via brute force any more, nor will it ever be. You can prove that the amount of energy required assuming a thermodynamically ideal computer is more than will ever be available in our galaxy, with classical computing. Breaks of symmetric crypto or hashes that are practical require an actual cryptographic weakness, whose existence is not a given. Then there's quant…

AFAIK, this is more of a belief than a fact. I would be very curious if you would show me a rigorous proof that e.g. SHA256 requires like on the order of 2^256 of operations to find a preimage of a random 256-bit string.

Re: BitTorrent v2 (2020)

#50

Post by calpaterson »

KennyBlanken wrote: post #34
nodja wrote: 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…

A bunch of open-source projects would like to use v2 torrents, but because Transmission is so popular and has zero support for v2, nobody can use them. Transmission's dev team hasn't said a word on the matter, ever, in four years: https://github.com/transmission/transmission/issues/458 Elsewhere someone quipped: > That transmission bug is 4 years old and they've never announced plans to prioritize it (granted the eff…

> I think either they either don't know or don't care that their market share makes them an adoption blocker.

The truth seems to be that between 2014 and mid-2021 the "transmission dev team" was a single (probably part-time) maintainer:

https://github.com/transmission/transmission/graphs/contribu...

Post reply on HN