archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
release/v1.12
dbkr/msc4178
release/v1.11
tulir/msc4142
release/v1.10
travis/msc2702-msc2701
rav/ref_objects_in_params
dkasak/foldable-sidebar
travis/knock-join
release/v1.9
release/v1.8
anoa/update_docsy
anoa/nix_flake
dbkr/3077-multi-stream-voip
release/v1.7
dbkr/2746-reliable-voip
rav/links_for_object_defs
release/v1.6
release/v1.5
release/v1.4
anoa/invite_knock_room_state
release/v1.3
push_gateway/r0.1.0
r0.0.0
0.2.0
application_service/r0.1.0
application_service/r0.1.1
application_service/r0.1.2
client-server/0.3.0
client-server/r0.1.0
client-server/r0.2.0
client-server/r0.3.0
client_server/r0.4.0
client_server/r0.5.0
client_server/r0.6.0
client_server/r0.6.1
identity_service/r0.1.0
identity_service/r0.2.0
identity_service/r0.2.1
identity_service/r0.3.0
push_gateway/r0.1.1
r0.0.1
server_server/r0.1.0
server_server/r0.1.1
server_server/r0.1.2
server_server/r0.1.3
server_server/r0.1.4
v1.1
v1.10
v1.11
v1.12
v1.2
v1.3
v1.4
v1.5
v1.6
v1.7
v1.8
v1.9
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0e771c7b07'
${ noResults }
matrix-spec/api/server-server/definitions
History
Travis Ralston 42ae5c966a Clarify the limits of prev_events and auth_events 
Fixes https://github.com/matrix-org/matrix-doc/issues/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: 207b1737ee/synapse/handlers/federation.py (L1183-L1213)

... and Synapse's handling of the backfill endpoint is described here: 207b1737ee/synapse/handlers/federation.py (L829-L837)

This also includes a mention that https://github.com/matrix-org/matrix-doc/pull/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.
 		5 years ago
..
event-schemas remove unused schema defs 6 years ago
edu.yaml Remove unused origin and destination on EDUs 6 years ago
invite_event.yaml The event *format* changes, not the version 6 years ago
keys.yaml correct use of required annotation in json-schema 5 years ago
keys_query_response.yaml Improve the server key exchange portion of the s2s specification 6 years ago
pdu.yaml Clarifications and bug fixes in how v3 rooms work 6 years ago
pdu_v3.yaml Clarify the limits of prev_events and auth_events 5 years ago
pdu_v4.yaml Clarify the limits of prev_events and auth_events 5 years ago
security.yaml Define authorization requirements on federation swagger APIs 6 years ago
single_pdu_transaction.yaml Clarify how many PDUs are in a given transaction object 6 years ago
transaction.yaml The event *format* changes, not the version 6 years ago
unlimited_pdu_transaction.yaml Clarify how many PDUs are in a given transaction object 6 years ago
unsigned_pdu.yaml Add specification for room version 3: Event IDs as hashes 6 years ago
unsigned_pdu_base.yaml Clarify the limits of prev_events and auth_events 5 years ago