Open
Conversation
dasha-uwu
reviewed
Mar 12, 2026
Member
There was a problem hiding this comment.
why should we do this? the spec doesn't say to. in fact it says the opposite:
It MUST apply the events implied by the request in the following order:
...
Events set by the preset. Currently these are them.room.join_rules,m.room.history_visibility, andm.room.guest_accessstate events.
it doesn't say we should or just can skip the events. synapse is wrong here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
in the synapse room.py line 1690
it says that: only
guest_can_join == true, it will create and returnguest_accessevent.in the past tuwunel
create.rsline 246 : it will create and returnguest_accessanyway.