Skip to content

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

MSC4367: via routes in the published room directory #4367

wants to merge 1 commit into from
+75 −0

Conversation

Johennes
Copy link
Contributor

@Johennes Johennes commented Oct 14, 2025 •
edited
Loading

@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
This was referenced Oct 14, 2025
Open
Open
@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
tulir
tulir reviewed Oct 14, 2025
View reviewed changes
proposals/4367-public-rooms-via.md
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

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implemented into Vona: https://foundry.fsky.io/vel/matrix-vona/src/branch/master/vona/globals/__init__.py#L258-L272

@github-project-automation github-project-automation bot moved this to Tracking for review in Spec Core Team Workflow Oct 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tulir tulir tulir left review comments

+1 more reviewer

@velikopter velikopter velikopter left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

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

Spec Core Team Workflow
Status: Tracking for review

Milestone

No milestone

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

@Johennes @tulir @velikopter @turt2live