-
Notifications
You must be signed in to change notification settings - Fork 24
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
Expose complete user address #178
Comments
Yeah this is a good idea. I don’t know if it is a username so I think a different variable — federationuser or something like that. The portable unique identifier is the DID for the account. The username is a label that we’ve decided to make unique for compatibility / UX reasons. hmmm. I guess “boris@bmannconsulting.com” or “boris@fission.name” is the full federation user ID? |
I guess if Fission supported Webfinger then the app would probably initiate the process outside of webnative and have one of these on hand already. But until then, either one would would be useful. |
Perhaps related: if the username/address was encrypted rather than stored in plaintext, the recipient could assume it is the actual identity? Again with my funding system, I can tie things to |
Yes. Broadly speaking I think we'd follow Verified Credentials for this, which basically links data to an ID. |
Re: @bmann's comment:
perhaps
state.username
could present the domain portion as well. This would allow me to make my funding button work with webnative without hard-coding the domain.The text was updated successfully, but these errors were encountered: