With our recent interoperability with uTorrent and BitComet, DHT bootstraps faster than ever. Talking to one DHT-supporting peer usually is enough for DHT to begin working well.

However, this still leaves the scenario of a brand-new KTorrent user going onto a torrent with a down tracker...

uTorrent bootstraps against router.utorrent.com initially, while mainline doesn't use DHT as a fallback tracker (to my understanding). Bitcomet uses node://router.bitcomet.net:554/ as its initial node...

All 3 of them seed trackerless torrent files with their respective routers, and Bitcomet also picks 10 random nodes that it's connected to (I'm not sure about other clients)


So, either way, it'd be nice to have KTorrent be DHT ready out-of-the-box.

I don't think it's too great of an idea to ship with the above mentioned nodes out-of-the-box without asking first -- that's a great way to get KTorrent 2.1 off to a bad start in terms of reputation .

What does it take for us to have a router.ktorrent.org?

I share your enthusiasm

I'm not quite sure we'll manage to finish all this in time for 2.1 release. However, if everybody agrees I could take a look at this if I find the time before v2.1

As a backup mechanism, why not. If we don't know any nodes we could use these nodes to get access to the DHT network.