-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Join a room by "Internal room ID" #19722
Comments
A room ID is not routable, so cannot be used reliably for joining. #2925 being the reference issue on that So a Room ID on its own isn't enough over federation, you also need a list of |
Thanks, I had no idea it wasn't routable. Looking at https://matrix.org/docs/spec/client_server/r0.6.1#post-matrix-client-r0-join-roomidoralias, I guess this is about the case where all users from the initial homeserver left the room, or where that homeserver itself is no longer available, right ? Maybe at the GUI level, we could just try to find the room anyway, from the homserver in the link, and see if we find anything ? I mean when a user see that |
Nope, the server at the end of the room ID is never used. Only the local server and the ones specified in the ?via= are used. That would be a spec/synapse thing |
Ok, this explains why |
Hum… May I ask why this issue is closed ? Do you want me to open another one with I find it hard to understand that inside the same application, the command line works while the GUI doesn't :/ |
Your use case
What would you like to do?
I would like to be able to join a room from its Internal room ID, eg.
!ehXvUhWNASUkSLvAGP:matrix.org
Why would you like to do it?
Because if someone ask me to join a room and provide this ID, I would like to enter in that room.
How would you like to achieve it?
From the main interface to join a room: the "Find a room..." text input in the "Explore rooms" menu.
Have you considered any alternatives?
/join !ehXvUhWNASUkSLvAGP:matrix.org
Both work, but this doesn't feel very user friendly for a newcomer
Additional context
No response
The text was updated successfully, but these errors were encountered: