You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 @bob:company.com and their password in right now and click Sign in without manually changing the homeserver. That would mean they just sent their username and password to the default server. I’m sure matrix.org isn’t intentionally collecting that but it still doesn’t mean it is a good idea to have these plaintext passwords being sent to the wrong server.
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: