Those three (router.bittorrent.com, dht.transmissionbt.com, dht.libtorrent.org) are convenience helpers baked into popular clients.
The DHT spec allows any UDP host to act as a router node, and they already do (uTorrent, qBittorrent, Aria2, PicoTorrent, etc.)
does pubkey have a baked in router helper?
Uhh yeah this is my question too
To be clear, you can use ANY NODE and it will work. And there are gazillions of nodes. But you still need to get started somehow. I don't think anybody could design a better system. But yes it has baked in starting points. see DEFAULT_BOOTSTRAP_NODES
https://docs.rs/mainline/latest/src/mainline/rpc.rs.html
My point was only that this is censorable, that EVERYTHING is censorable in this sense, and that nostr is just as censorship-resistant in this sense. Not trying to say the DHT isn't good.... it is great.
My point was that if you don't have a node list, you can't get one without going to these "convenience nodes". Take down these nodes and new people who have no other way of finding a node can't get anywhere.
This is IMHO the same problem nostr has, except nostr has the problem right now because it has no "convenience nodes".
