-
Notifications
You must be signed in to change notification settings - Fork 186
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
/directory/room leaks all involved homeservers #17298
Comments
Hmm. The response being returned is as per the spec: https://spec.matrix.org/v1.11/client-server-api/#get_matrixclientv3directoryroomroomalias As for being able to join the room (space) using the resolved alias from that request, I tried joining the space you mentioned with the room ID returned (!pvOfSyfiUOIEBrZDWF:matrix.org) using element desktop and it worked without issue. |
I wasn't suggesting synapse isn't respecting the spec. The spec doesn't mention the maximum number of servers to return or their ordering (one way or another) so I'm trying to acertaing if this is inentional, a mistake, a miss or something else. If you agree that this is indeed a problem I can go ahead and write the MSC As for joining, I don't know what Element Web is doing but the plain request is always failing for me, see the details
|
Description
348
servers which presumably is all of them.This is not only a privacy concern but also wasteful. If the client tries to use them to join the room it will fail and the client can't trim the list because no ordering is specified.
(joining jellyfin fails in this case with
<html><body><h1>400 Bad request</h1>\nYour browser sent an invalid request.\n</body></html>\n
, which is probably another problem in itself)Steps to reproduce
Access https://matrix-client.matrix.org/_matrix/client/v3/directory/room/%23jellyfinorg:matrix.org
Homeserver
matrix.org
Synapse Version
server_version: "1.109.0rc1 (b=matrix-org-hotfixes,40975b3098,dirty)"
Installation Method
Other (please mention below)
Database
Workers
Single process
Platform
Configuration
Relevant log output
Anything else that would be useful to know?
The text was updated successfully, but these errors were encountered: