Here me out:
@nip05
how about we help differentiate nostr identifiers (NIP-05) from someone's email address
@ is the universally recognized character to refer to someone. I think Bluesky got this one right.
@pablo@f7z.io 👉 NIP-05
Thoughts? This will be important for the onboarding flow I have in mind and would love to hear what people think.
Repost for visibility 🙏
Seems fine
Good idea! Let’s do it! 🐶🐾🫡
This is the way.
yeah mastodon and fedi doing it the same
makes sense.
hate this
This is also how ActivityPub handles this
I like it as it is. One could say the same about lightning addresses. And how would you differentiate then the LN addresses from the Nostr ones?
The @ at the beggining looks very mastodon-ty.
that's also confusing and people and bots (like Brain Coinbase) have already been confused by it
Have to say that I like the current usermane@domain nip-05. And find the double @ as ugly as it is confusing…
Make nip 05 providers also email providers. I realize this adds a large burden for providers if they want to provide an email client, but they don't necessarily have to do that. I made my NIP 05 (hodlbod@coracle.social) into an email address with an MX record. NIP 05's could do that with users' existing providers.
Lots of sharp edges there, but I really think the right UX is to have the same name for both protocols.
At first this stood out to me, the username seemed to have no correlation to the username in Nostr.
This format might be better to not be confused as an email address:
domain.tld/@username
It could also be linked to an njump page that can open into a native application.
user@domain is specifying a user at a domain, it is not specifying any protocol. The fact that people see it and think it is an email address is unfortunate, because this format of specifying a user at a domain was not originally intended to be used exclusively by email.
An email address URI is "mailto:user@domain"
We could use a URI something like "nostr:nip05:user@domain". I don't like the verbosity though.
But I don't like @user@domain. There is no way to tell that this is a nostr thing at all. Could be a mastodon address. Could be a bluesky address. Might be an email address with a typo.
To add to that, using "nostr:nip05:user@domain" doesn't require any context. It says what it is.
Using "user@domain" requires context. You have to know external to the data that this is a nip05 address. In which case you already know that it is not an email address.
A user only confuses it with an email address if the context isn't obvious. And if the context isn't obvious, then the data should specify the context.
what about PabloF7z[&]f7z.io?
How about PabloF7z[&]f7z.io?
nostr:note1nudsl2skpjahg9q4ufh5u9927e4mutaxvh8fzfwn3em3fp298h9skukrs9
The double @ is what mastodon uses. Personally I think emails are losing their dominance and we should just use it as user @ server.
Yeah! Time to kick email's ass!
Totally agree.
Oh wow! I didn’t expect that response from you; you thinking that makes me think this is a non-issue and that I shouldn’t bother with this then.
Thanks!
Cc nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac
Overload the email operator. No worries.
To me Nostr represents the future. Kids in 5 years won't prob even remember what an email is. Gentlemen we must look ahead and think bolder. I think the format user@server is the way to go. Let Gen Zers wonder why this thing called "email" uses the same format as Nostr, they will barely use it anyway.
"A nostriches bikesheds nip05. Other nostriches show up in the thread to survey the bikeshed in an attempt to get developers to whitewash the fence. In accordance with federal law, the only solution is to rewrite everything in Rust with 'over 9000!' crate dependencies."
nostr:note1nudsl2skpjahg9q4ufh5u9927e4mutaxvh8fzfwn3em3fp298h9skukrs9
Nip-05 identifiers are overrated.
WoT ftw.
Different things entirely
Not really.
UX could chose between giving importance and trust to some "domain aliases" (aka NIP-05), or giving importance to the web of trust of someone.
You either trust some DNS and web admin, or you trust your follows contact lists.
Doing both is confusing for the user, imo.
Thinking in usernames is thinking in the ol' way of doing of the pre-nostr era.
🫂🫂
It’s not about trust, the “verification” part of NIP-05 is a nonstarter. It’s an identifier to locate a record.
Eg, my NIP-05 is f7z.io, far easier to remember and say aloud than my npub.
The nip-05 alias as an identifier to locate a record for the first time could have a pass, but just if treated as that, a tool for finding a user.
Still, several nostr clients mark NIP-05 identities as somehow"verified", confusing completely the user, and opening the door to several scam possibilities.
That's why it's about trust. NIP-05 usage in several nostr client right now seems to show 'trusted users' falsely.
Nah. Thatd start a push to do something for lightning addresses as well
