Implementation of unstable MSC4388 #19127
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an implementation of the rendezvous transport session part of MSC4388. This is part of the 2025 version of MSC4108
The implementation is independent of the existing experimental MSC4108 support in Synapse which is for the 2024 version.
Usage
It is configured using:
Where mode is one of:
off(default): feature is disabledauthenticated: enabled and requires an authenticated user to create a rendezvouspublic: enabled and no authentication is requiredImplementation notes
For future reference when implementing a final/non-experimental version:
Notes once the MSC is accepted
Once this MSC is accepted into the spec I would propose that the default mode in Synapse be
authenticated.The is a trade-off between capabilities across the modes:
authenticatedpublicFor Element clients the user flow impact would be as follows:
authenticatedpublicPull Request Checklist
EventStoretoEventWorkerStore.".code blocks.