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.
matrix-spec/content
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.)
2 years ago
..
client-server-api Distinguish 'client' from 'federation' events (#3658) 2 years ago
rooms Update documentation style & fix room version heading order (#3683) 2 years ago
_index.md Move room version spec to `/rooms` (#3423) 3 years ago
appendices.md Revert fix to appendices 2 years ago
application-service-api.md Decorate Matrix version on appservice login 3 years ago
changelog.md v1.1 changelog 3 years ago
identity-service-api.md typoes (#3680) 2 years ago
proposals.md s/master/main/g otherwise we link to stale content 2 years ago
push-gateway-api.md Update content to call the new template for HTTP APIs 3 years ago
server-server-api.md Room versions 8 and 9: Restricted rooms (#3387) 2 years ago