-
Notifications
You must be signed in to change notification settings - Fork 12
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
When someone uses an unroutable room ID ("Failed to join"), suggest using via server derived from the room ID #973
Comments
that's a better approach to help end-user. can I work on this? |
Anyone knows what "404" means. This is not client issue. You are going to offer to user spend his time. |
and I think most client won't be able to understand the routing / and all, so |
Rooms don't have a specific homeserver, they're shared amongst all servers which have users in the room. |
If this is a heuristic we want then it should be implemented in the spec and server rather than every client where it'll be inconsistent As for defaulting to matrix.org, leaking room IDs of private federations would be considered a privacy issue. |
Seems room |
@JeanPaulLucien this isn't a support room for specific rooms. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Problem
When someone uses an unroutable room ID, it currently just presents them with an error modal that looks like following and isn't helpful for knowing what's wrong or how to fix it:
Potential solution
We could instead suggest a best-guess
via
server derived from the room ID. Yes, this does mean parsing an opaque room ID (gasps) to give the guess, but the user still needs to do the correct thing in the end.This not only helps the user get where they want but also teaches them for next time.
We can even include
matrix.org
as a fallback as that is probably a great server to use as a shot in the dark for things to work out. We want to delight and teach people, not bury them caveats.Have you considered any alternatives?
Ideally, this via server assumption could just be automatic but I don't think this would hold up against decision makers with a strong room IDs are opaque strings opinions. And also doesn't teach people for a future where we can't assume.
Additional context
Related issues:
Mockup HTML/CSS
The text was updated successfully, but these errors were encountered: