-
Notifications
You must be signed in to change notification settings - Fork 123
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
Support .well-known in the way the spec says #479
Comments
Interesting this is mentioned specifically in the spec (I hadn't noticed) as I would consider this more a UX choice up to the discretion of each client. Any particular reason you prefer this over the current way of entering the server? |
I believe the reason it’s in the spec is for security. If a user thinks “oh this client supports .well-known” they might go and type |
Ah, I see. Well, it would definitely make sense to change the homeserver if a people enter a user id with a server in the user field. |
Hydrogen has now implemented Element's newish style of doing .well-known which is great but that isn't how the spec says .well-known works. It would be good to support both methods.
The spec says .well-known works by having the user enter their full username (as in @user:server.com) and then the client sends the .well-known request to the server name that appears after the colon. https://spec.matrix.org/unstable/client-server-api/#well-known-uri
The text was updated successfully, but these errors were encountered: