I personally wish torrent search engines stop using DNS systems (at least centralized ones) and HTTP servers. What they could do instead is use the DHT feeds id

I personally wish torrent search engines stop using DNS systems (at least centralized ones) and HTTP servers. What they could do instead is use the DHT feeds idea [1]; share their feed URI (a hash of a public key) which is a mutable DHT key, and have that point to a .torrent of their whole crawled database - I doubt their magnet_link -> description database is larger than a few dozen megs. When new torrents need to be updated, the DHT key is mutable and they can point to a new torrent - users will then just get the new stuff. Idea is laid out here: https://github.com/bittorrent/bittorrent.org/issues/19#issue-110508430 https://github.com/bittorrent/bittorrent.org/issues/19#issue... Sure it's more complex than typing somesite.com in your address bar, but it's not that much more complicated. 1. http://libtorrent.org/dht_rss.html http://libtorrent.org/dht_rss.html