Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-26 21:14:09 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse source
This commit is contained in:
Richard van der Hoff 2022-09-01 15:38:17 +01:00 committed by GitHub
parent e5a3df3706
commit 563a1832a8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/client-server-api/_index.md
View file

@ -1938,14 +1938,14 @@ parent event, for example.
{{% /boxes/note %}}
To allow the server to aggregate and find child events for a parent, the `m.relates_to`
key of an event MUST be included in the cleartext (unencrypted) part of the event. It cannot be
key of an event MUST be included in the plaintext copy of the event. It cannot be
exclusively recorded in the encrypted payload as the server cannot decrypt the event
for processing.
{{% boxes/warning %}}
If an encrypted event contains an `m.relates_to` in its payload, it should be
ignored and instead favour the cleartext `m.relates_to` copy (including when there
is no cleartext copy). This is to ensure the client's behaviour matches the server's
ignored and instead favour the plaintext `m.relates_to` copy (including when there
is no plaintext copy). This is to ensure the client's behaviour matches the server's
capability to handle relationships.
{{% /boxes/warning %}}

4
content/client-server-api/modules/event_replacements.md
View file

@ -41,9 +41,9 @@ replacement events.
an event's content property, such as `formatted_body` (see [`m.room.message`
`msgtypes`](#mroommessage-msgtypes)).
#### Validity of message edit events
#### Validity of replacement events
There are a number of requirements on message edit events, which must be satisfied for the replacement to be considered valid:
There are a number of requirements on replacement events, which must be satisfied for the replacement to be considered valid:
* As with all event relationships, the original event and replacement event
must have the same `room_id` (i.e. you cannot send an event in