Clients cannot ignore edits

This commit is contained in:
Richard van der Hoff 2023-02-28 14:24:30 +00:00
parent 97b7544f2c
commit 05d1779d1f

View file

@ -259,17 +259,9 @@ difficult, and servers should no longer make this replacement.
#### Client behaviour #### Client behaviour
Clients can often ignore `m.replace` events, because any events returned Since the server will not replace the content of any edited events, clients
by the server to the client will be updated by the server to account for should take note of any replacement events they receive, and apply the
subsequent edits. replacement whenever possible and appropriate.
However, clients should apply the replacement themselves when the server is
unable to do so. This happens in the following situations:
* The client has already received and stored the original event before the
message edit event arrives.
* The original event (and hence its replacement) are encrypted.
Client authors are reminded to take note of the requirements for [Validity of Client authors are reminded to take note of the requirements for [Validity of
replacement events](#validity-of-replacement-events), and to ignore any replacement events](#validity-of-replacement-events), and to ignore any