Skip to content
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{roomAlias} leaks all involved homeservers #2052

Open
stefanceriu opened this issue Jan 14, 2025 · 1 comment
Open

/directory/room{roomAlias} leaks all involved homeservers #2052

stefanceriu opened this issue Jan 14, 2025 · 1 comment
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@stefanceriu
Copy link
Member

Link to problem area:

https://spec.matrix.org/v1.11/client-server-api/#get_matrixclientv3directoryroomroomalias

Issue
What is wrong? How can we improve?

The spec for resolving room aliases to IDs doesn't specify any limits on the returned servers list resulting in strange occurences like ~400 servers (grew significantly since I raised the synapse issue) on #jellyfinorg:matrix.org for example.

I believe this is wasteful and a privacy concern and that the list should be perhaps artifically capped and maybe ordered by the size of the homeserver (number of active users?).

@stefanceriu stefanceriu added the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label Jan 14, 2025
@richvdh
Copy link
Member

richvdh commented Jan 14, 2025

vaguely related: #528

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

No branches or pull requests

2 participants