brugeman on Nostr: I am long time fascinated by mainline DHT, and it's cool you are experimenting with ...

I am long time fascinated by mainline DHT, and it's cool you are experimenting with it. Can we talk about browser js not being able to access DHT directly? User needs to set a custom dns server, which is quite a barrier, and is the middleman that can censor or be censored, is that right?

We could have a custom relay that could query dht for user's outbox relays and fetch requested events from there, acting as dht bridge for web apps. But then it's no different from existing indexer relays that clients hardcode for discovery.

We could also have a custom dns server resolving npubs to their outbox relay. But again users won't change their dns settings.

I go back and forth on this and still don't see what is fundamentally solved by this use of dht, at least for the web. Am I missing something?