Bundle mlDHT plugin with Azureus by default
Azureus has a DHT implementation that is incompatible with the mainline DHT implementation that pretty much every other torrent client uses.
And while a plugin exists that solves this problem, it is not installed by default, and thus many users do not have it. This hurts both their their user experience(they cannot find approx. 80% of the peers via DHT) and the whole swarm's too(they cannot be found by ~80% of the peers via DHT).
Bundling the mlDHT plugin with new Azureus releases would solve these problems, and it should be very easy to do.
Anonymous
shared this idea
7 comments
-
dht
commented
i used Mainline DHT over years with IPv6 and ipv4. It gives you many more peers ! Because vuze only have around million. While Mainline DHT is 25x times bigger Peer pool. For compatiblity and fallback please bundle this for default user.
-
vuzeuser
commented
or we could have an option like
"only track torrents when Tracker is unavailable (torrent has no tracker or tracker is down) and when dht fails (no peers / seeds)"thanks
-
vuzeuser
commented
can we have the option:
"However, perform low resource tracking when online for swarm cross-population"
for the mainline dht plugin toothanks
-
vuzeuser
commented
as usual thanks very much
it seems to me, (but i'm no one) that utorret/bittorent (client) = bittorrent (protocol),
i have nothing against utorrent, but what they do becomes a standard, what other clients do is "garbage" (this word is excessive but i don't know english very well), and i don't like this.
so every client have to follow utorent, and for me this means less research and less improvement in the bittorent protocol (luckily there is vuze)regarding the Multi-Port Trackers plugin, should it be marked as deprecated ?
thanks
-
AdminVuze
(CEO / Founder, Vuze)
commented
Always a bit disappointing that they went and did their own DHT, but that's the way things go.
The multi-port tracker plugin is a bit of a strange beastie, it was originally created for some very specific tracker cases, long time ago, and I'd be surprised if it did anything useful with any 'modern' trackers these days...
-
vuzeuser
commented
from wikipedia (http://en.wikipedia.org/wiki/Mainline_DHT):
"Mainline DHT is the name given to the Kademlia-based Distributed Hash Table (DHT) used by BitTorrent clients to find peers via the BitTorrent protocol. The idea of utilizing a DHT for distributed tracking was first implemented in Azureus 2.3.0.0 (now known as Vuze), from which it gained significant popularity. BitTorrent, Inc. then incorporated a similar DHT into their client, called Mainline DHT and thus popularized the use of distributed tracking in the BitTorrent Protocol."
why did bittorrent inc. make its own implementation? :)
in this old thread (http://forum.utorrent.com/viewtopic.php?id=3387) you can read:
"Azureus's implementation is WAY better than Mainline's"
i don't know if things are different nowa nice off-topic article pro vuze:
Make the most of public torrents (speed/performance & security):
http://torrentfreaknews.blogspot.it/2013/03/make-most-of-public-torrents.htmland what do you think about the Multi-Port Trackers plugin (http://plugins.vuze.com/plugin_details.php?plugin=multi-ports).
could be it also bundled with vuzethanks
-
Filipe Augusto
commented
Agree with you! I think they need to see if the plugin have some incomptibility before releasing it by default.
Excellent Ideia, and thanks the creator of the plugin for giving us the opportunitie to access the MainlineDHT.
Visit the