Nuh 🔻 on Nostr: A dns resolver can be (and most often is) literally your router, when your router ...
A dns resolver can be (and most often is) literally your router, when your router doesn't have the cache it asks ICANN who owns .com and then asks .com who owns nostr.com and then asks who owns nostr.com for the ip address.
The only hard coded part here is ICANN 13 root servers, and Pkarr entire thing is to replace these 13 servers with Mainline DHT and make public keys TLDs.
Nostr relays don't have neither the hierarchy of ICANN domains nor the fallback to Mainline so if you don't find the data you are looking for in your hardcoded relays, now there are NO Authoritative way to find the data, it becomes literally ad you said "your imagination" so if you fail to gather enough breadcrumbs to find that elusive data, we'll skill issue.
If that still doesn't sound as a significant and fundamental difference, then we lack the common foundations to reason about system design.
The only hard coded part here is ICANN 13 root servers, and Pkarr entire thing is to replace these 13 servers with Mainline DHT and make public keys TLDs.
Nostr relays don't have neither the hierarchy of ICANN domains nor the fallback to Mainline so if you don't find the data you are looking for in your hardcoded relays, now there are NO Authoritative way to find the data, it becomes literally ad you said "your imagination" so if you fail to gather enough breadcrumbs to find that elusive data, we'll skill issue.
If that still doesn't sound as a significant and fundamental difference, then we lack the common foundations to reason about system design.