Are you suggesting to put an extra @ in front of the nip-05? I’d guess people don’t do that cause it looks weird and takes up a little more space.
Earlier this month nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch released in app NIP05 creation. If you dont have one definitely check it out!
During the development we had a long debate about the display of NIP05’s in app. Presently Nostr defaults to making them appear like email addresses with [name] @ [domain].
This presents challenges in the UX of how people interact with these handles.
- some apps send people to the website host of the nip
- some apps treat the nip as an email address
- what happens when there’s actually an email address vs a NIP05
- nostr already supports an @ ux pattern for Npubs and by extension n profile which renders as @ display name
Is there a reason NIP05’s dont follow the same @ pattern? I’m curious what problem are we solving for users of Nostr with the current format?
#asknostr
Discussion
It’s more why is the @ in the middle in the first place? I’d like to understand the problem we’re solving so we build the best ux experience
You need some kind of delimiter between the name and the domain. My guess is we just made it like that cause nip-05s work in a similar way to lightning addresses and that’s how lightning addresses are formatted.
The problem nip-05 solves is giving users a human readable unique identifier on nostr. It’s easier to share a nip-05 than an npub.
It can also prove you have access to a domain. For example, if you’re well known and have a personal website and use that for a nip-05, then people will have more confidence that it’s actually you and not someone pretending to be you.