-
Notifications
You must be signed in to change notification settings - Fork 371
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
Reject events with superfluous auth_events entries #1594
Conversation
It's fine. A link would help though. Put in an anchor in the relevant place; s/described previously/described above/; make |
06ff696
to
080845a
Compare
I've added a link, though its not linking "above" as I couldn't figure out how to have a different link text? |
you can use a substitution, which involves wrapping with |
Fixes #2307 These restrictions are due to a Synapse change which never made it to the spec prior to the MSC process. This is therefore documenting an omission. Synapse's numbers are verified here: https://github.com/matrix-org/synapse/blob/207b1737ee0acd226359d59ce3b7f7d46111b1c8/synapse/handlers/federation.py#L1183-L1213 ... and Synapse's handling of the backfill endpoint is described here: https://github.com/matrix-org/synapse/blob/207b1737ee0acd226359d59ce3b7f7d46111b1c8/synapse/handlers/federation.py#L829-L837 This also includes a mention that #1594 should render the `auth_events` limitation unnecessary. No changes are required to the the "checks on receipt of a PDU" section of the server-server spec as it starts with "must be a valid event", to which an event is invalid if it contains too many prev or auth events.
Based on: #1591, #1592
Related: #1593
Its a bit annoying that this refers to an algorithm from a previous section, but I don't want to duplicate it. Thoughts on how to tidy this up?