You'll have to offer children in sacrifice to the gods of DNS.
nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 thinking aloud but is there a way, if we bought and created the .npub tld that we could set up a wildcard domain registrar with some kind of dns redirect so that whenever someone pumped in any random npub string it would show as an http link and open their Nostr client, similar to the way clicking any other link opens a browser? The thought is that this would make it much easier to share npubs, could just drop a ".npub" at the end of the string and then—if this method is possible—the TLD server would handle the rest? What does it take to get apps to recognize TLDs as hyperlinks? Is there a protocol for this or does it have to be added manually by the developers?
Discussion
So exploring more it looks like the objective with the TLD is to achieve something called "Universal Acceptance" and the cost for this apparently is child sacrifice? 😑
FWIW, in all seriousness, I'm spitballing ideas because I think a lot of us agree there needs to be more effort in the community to deal with onboarding and adoption. There is a danger that we're invoking a Field of Dreams mythology around nostr—whereas the possibility this platform disappears into irrelevance is still pretty significant. Crossing the chasm is going to take intentional and concerted effort.