Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
A bunch of open-source projects would like to use v2 torrents, but because Transmission is so popular and has zero support, 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 effort is surprisingly high; they've never allowed empty dict keys in bencoding). I think either they either don't know or don't care that their market share makes them an adoption blocker.
I have a love-hate affair with Transmission; it's simple, the UI is very clean...but the performance is terrible. Downloading a torrent at ~15MB/sec should not nearly max out a 4th generation i7 processor.
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://stackoverflow.com/a/65299426/2700296
2. https://github.com/webtorrent/magnet-uri/pull/43#issuecommen...
BiglyBT was the first Torrent client with v2 support
[1] https://torrentfreak.com/biglybt-is-the-first-torrent-client...
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.
Not really true - v0.20 of PicoTorrent [1] was released the same day as libtorrent released support for v2 torrents. I think this predates BiglyBT 2.5 with v2 [2] support with about two weeks.
[1] https://github.com/picotorrent/picotorrent/releases/tag/v0.2...
So as far as I understand the protocol this is the principle behind Zeronet (https://zeronet.io/)