6 commits

Author	SHA1	Message	Date
Kévin Commaille	d601884378	Clarify string formats of event endpoints and schemas ... Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>	2026-03-30 17:58:24 +02:00
Richard van der Hoff	96057638ce	Spec unsigned.membership property, per MSC4115 (#1847)	2024-06-10 12:17:27 +00:00
Kévin Commaille	adff3faa35	Make sure version in x-changedInMatrixVersion is a string (#1562)	2023-06-10 14:44:06 +03:00
Travis Ralston	6c6c602845	Clarify that refreshed access tokens don't invalidate the scope of txnid (#1236)	2022-09-26 14:39:43 -06:00
Travis Ralston	a91030f27b	Re-add paragraph about how some state keys are reserved (#1100) ... * Re-add paragraph about how some state keys are reserved Fixes https://github.com/matrix-org/matrix-spec/issues/1013 * changelog	2022-05-31 09:24:25 -06:00
Richard van der Hoff	36b02edfc2	Distinguish 'client' from 'federation' events (#3658) ... Fixes #3305 Fixes #3380 The idea here is to better distinguish between a 'raw' event (as we send over the wire), and the 'serialised' format, as sent in responses to the C-S api and in `PUT /_matrix/app/v1/transactions/{txnId}`. It's made more complicated by the fact that there are _two_ serialisation formats, one used by `/sync` and `/notifications`, and one by everything else (the difference being whether `room_id` is included). In an ideal world, we wouldn't repeat `SerialisedEvent` every time it's used, and instead just link to the first reference, but that's a job for another day. Another job for another day is to get rid of things like `sync_state_event.yaml` (which is now used only in one place, so should be inlined.)	2022-02-01 15:05:08 +00:00