clarification to MSC2675 (#3829)

because this is confusing enough without outright lies
pull/3832/head
Richard van der Hoff 2 years ago committed by GitHub
parent f6f3299b0d
commit 6f411413af
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -196,6 +196,10 @@ adds the related-to event in `original_event` property of the response.
This way the full history (e.g. also the first, original event) of the event This way the full history (e.g. also the first, original event) of the event
is obtained without further requests. See that MSC for further details. is obtained without further requests. See that MSC for further details.
* **Edited 2022-06-06**: This appears to be incorrect. MSC2676 contains
no reference to `original_event`, nor can I find any record of it ever
having done so.
### End to end encryption ### End to end encryption
Since the server has to be able to aggregate relation events, structural Since the server has to be able to aggregate relation events, structural
@ -317,4 +321,4 @@ While this MSC is not considered stable, the endpoints become:
None of the newly introduced identifiers should use a prefix though, as this MSC None of the newly introduced identifiers should use a prefix though, as this MSC
tries to document relation support already being used in tries to document relation support already being used in
the wider matrix ecosystem. the wider matrix ecosystem.

Loading…
Cancel
Save