Permalinks cannot be routed by room ID, and aliases are not permanent. #355
Labels
A-Client-Server
Issues affecting the CS API
feature
Suggestion for a significant extension which needs considerable consideration
Comments
turt2live
added
the
feature
|
It seems like element-hq/element-web#2925 has been closed, so we can probably close this one too? |
|
|
|
Ok, can you update the description to be clearer about what the actual problem is, rather than just referring to a closed issue? |
|
done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original bug: element-hq/element-web#2925
Room IDs have a server component for namespacing, but there's no guarantee that the server is still a participant in the room. This makes room IDs canonical for the room, but without a routing component they are impossible to resolve unless you're already part of the room. Aliases meanwhile do have routing through the included server name (leading to further queries about resident servers), but can change which room ID they point to easily.
We patched over the routability issues for room IDs by adding
?via=parameters to permalinks, though this still has a chance to include servers which are no longer present when the link is clicked. Ideally, the room ID itself is routable to a resident server able to join the room.There are no currently known solutions to this - MSCs are required.
The text was updated successfully, but these errors were encountered: