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.

Reply to this note

Please Login to reply.

Discussion

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.

True, but that ship has long sailed; the user@domain making people think it's an email address is with us at least for another generation.

Fact is, other nomenclatures, like @user@domain are largely still up for grabs because no other protocol/platform has captured it the way email has.

This is largely a branding thing and not a protocol issue; technically speaking a URI scheme is more accurate, but that's a branding and usability disaster.

something simple and new would be cool. like n:

but pablo is right. it wouldnt make sense to anyone but nerds.