Skip to content

Conversation

@Johennes
Copy link
Contributor

@Johennes Johennes commented Oct 14, 2025

@Johennes Johennes changed the title MSCXXXX: via routes in the published room directory MSC4367: via routes in the published room directory Oct 14, 2025
@Johennes Johennes force-pushed the johannes/public-rooms-via branch from af8d2b4 to 5d43468 Compare October 14, 2025 12:08
@Johennes Johennes marked this pull request as ready for review October 14, 2025 12:09
@tulir tulir added proposal A matrix spec change proposal s2s Server-to-Server API (federation) client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Oct 14, 2025
Copy link
Member

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 via in both APIs, and passes it through in the C-S API when querying a remote server
  • Client that uses the returned via for /join calls

Comment on lines +8 to +9
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
Copy link
Contributor

@zecakeh zecakeh Nov 6, 2025

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client-server Client-Server API hacktoberfest-accepted kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal s2s Server-to-Server API (federation)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

room directory does not make it clear how to find a resident server

4 participants