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
..
.gitignore	Prepare the appservice spec for an r0 release	2018-08-27 18:04:08 -06:00
3658.clarification	Distinguish 'client' from 'federation' events (#3658)	2022-02-01 15:05:08 +00:00
3674.clarification	Changelogs for #3674	2022-01-26 11:00:30 +00:00
3675.clarification	Fix the response for `GET /_matrix/app/v1/thirdparty/protocol/{protocol}` (#3675)	2022-01-26 10:47:29 +00:00