-
Notifications
You must be signed in to change notification settings - Fork 378
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
MSC3585: Allow the base event to be omitted from /federation/v1/event_auth
response
#3585
Conversation
/federation/v1/event_auth
response/federation/v1/event_auth
response
Co-authored-by: Stuart Mumford <stuart@cadair.com>
[MSC3585](matrix-org/matrix-spec-proposals#3585) says this is a thing we can do.
I think this is a no-brainer. @mscbot fcp merge |
Team member @mscbot has proposed to merge this. The next step is review by the rest of the tagged people: Concerns:
Once at least 75% of reviewers approve (and there are no outstanding concerns), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for information about what commands tagged team members can give me. |
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.
Looks sensible. The fact that conduit already does this seems like a reasonable indication that it won't cause the world to explode.
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.
otherwise lgtm
@mscbot concern Check Dendrite compatibility |
@mscbot resolve Check Dendrite compatibility |
SIGH. It turns out that synapse actually already does what this MSC proposes. The code is misleading, but the functionality is correct. The whole premise of this MSC is that the /de-facto/ spec, based on what Synapse does, is that I also think that #3583 has clarified the written spec sufficiently: it is clear that the auth chain of an event does not include that event itself. So no further changes are needed to the spec imho. Meanwhile, @kegsay has been actually writing tests to verify behaviour (matrix-org/complement#280) (thank you). |
Rendered
Implementation: Conduit already does this. See also synapse PR.
Preview: https://pr3585--matrix-org-previews.netlify.app