not yet, but we are waiting for somebody to go deep into it. nostr:npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamlskcsghjm9c and I tried a kind:30053 for DNS records many months ago. The goal back then would be to not have a relay list with domain names, but a relay list with pubkeys that in turn point to IPs. Maybe he is still offering that event for his relays. We just never really went for it.
Only DNS can mildly slow down Nostr at this point. And that is a short amount of slowing down. People could edit their relays and go on. In that case yes, having a Nostr Naming System would be cool to have as a fallback option. Then enough fallbacks later, it could be default.. .
nostr:note1n480q2mva32hkdqd8xm3vl0d630luz8850smt87tp46w7fm4vnjquqnaqs
I don't want to spoil the fun, but IP adresses are much bigger problem.
We can easily replace root zone; we can't do much about the IANA. Other then fork it, create separate "VLANS" or something.
federated? multiple, bridged? connected with (long range) radio, local wifis? opensource satellites? 🤔
That'd be great infrastructure for a national/international decentralized meshnet that anyone could spin up a diy node and join.
ipv6 is the way
