-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default username? #28
Comments
What's wrong with |
Nothing wrong.
it's not |
I have the same request.
@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:
Thoughts? |
@andrerfneves any further thoughts on this? |
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 |
@lukechilds what's next here |
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?
The text was updated successfully, but these errors were encountered: