Skip to content
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

Clarify OAuth identities #24

Closed
fluffy-critter opened this issue Jul 18, 2019 · 0 comments · Fixed by #66
Closed

Clarify OAuth identities #24

fluffy-critter opened this issue Jul 18, 2019 · 0 comments · Fixed by #66
Labels
enhancement New feature or request UX Relating to the end-user experience

Comments

@fluffy-critter
Copy link
Contributor

Technically an OAuth-based identity does not need a full user URL, it only requires providing the common domain name of the service (E.g. Mastodon.social, twitter.com, etc). It might be nice to signal that in some way, or to even make the standard UX just forward to the authority if the user clicks on the appropriate link for the service in the list (like linking to /login?me=http://twitter.com or whatever).

But it might be nice to just pretend that the full URL is important for the sake of consistency anyway. (But it might look like a bug if someone has two identities on a remote service and they want to specify one but the handler gives them another...)

@fluffy-critter fluffy-critter added enhancement New feature or request UX Relating to the end-user experience labels Jul 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request UX Relating to the end-user experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant