-
Notifications
You must be signed in to change notification settings - Fork 416
MSC4367: via routes in the published room directory #4367
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Johannes Marbach <[email protected]>
af8d2b4 to
5d43468
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation requirements:
- Server that returns
viain both APIs, and passes it through in the C-S API when querying a remote server - Client that uses the returned
viafor/joincalls
| To begin with, it is unclear whether the endpoints for listing a server's directory may return rooms | ||
| that the server is not joined to. Additionally, there is no recommendation on what `via` parameter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This first sentence of this paragraph is not addressed by the proposal either, maybe it should? Like stating that the spec should be updated to say that the room directory can include rooms that the server is not joined to. Otherwise it's hard to see a reason for adding the via parameter.
Also I couldn't see a use case for this at first, until I read this thread, so maybe it should be added as an example as a justification for this proposal?
Rendered
Fixes: matrix-org/matrix-spec#1375