Default username?

[Falci]

This "username @ domain" is great for 3rd-party services like zbd.gg or bitrefill, but they seems unnecessary for personal domains.

You end up with [email protected], [email protected] or [email protected].

Could we just use @mydomain.com in this case?

What do you think?

[andrerfneves]

What's wrong with [email protected] for example? The Lightning Address follows the Addr-Spec Specification RFC which is an internet standard and it requires a username portion followed by a domain portion with the @ sign in between.

https://datatracker.ietf.org/doc/html/rfc5322#section-3.4.1

[Falci]

Nothing wrong.

they seems unnecessary for personal domains.

it's not pay at falci.com it would be pay to falci.com

[lukechilds]

I have the same request.

What's wrong with [email protected] for example?

@andrerfneves One issue is that it's not a common identifier between platforms. e.g if I have [email protected] for Lightning Address and [email protected] for Nostr and then [email protected] for another services it makes discovery between services a bit clunky. I could of course use [email protected] for everything but it just seems kind of unnecessary.

One suggestion taking inspiration from NIP05 would be to have "_" reserved as a special default username.

so:

username@domain   >   https://<domain>/.well-known/<username>
@domain           >   https://<domain>/.well-known/_

Thoughts?

[lukechilds]

@andrerfneves any further thoughts on this?

[andrerfneves]

I've spoken to a lot of people about this and the unanimous feedback is that since this is something that wallets would need to implement themselves in order to work, and is a fully optional item, then it should be fine. I quite like what this can enable. I was hesitant at first because it adds additional overhead on the simplicity of the protocol, but seeing the ease of NIP05 aliases with support for both of these methods, I am convinced of its benefits.

cc @Falci

[andrerfneves]

@lukechilds what's next here