Fix inconsistencies regarding redacted_because
Signed-off-by: Benjamin Saunders <ben.e.saunders@gmail.com>
This commit is contained in:
parent
69b1827b10
commit
cade909e25
5 changed files with 16 additions and 6 deletions
|
@ -970,9 +970,10 @@ one of the following event types:
|
|||
``kick``, ``redact``, ``state_default``, ``users``, ``users_default``.
|
||||
- ``m.room.aliases`` allows key ``aliases``
|
||||
|
||||
The redaction event should be added under the key ``redacted_because``. When a
|
||||
client receives a redaction event it should change the redacted event
|
||||
in the same way a server does.
|
||||
The server should add the event causing the redaction to the ``unsigned``
|
||||
property of the redacted event, under the ``redacted_because`` key. When a
|
||||
client receives a redaction event it should change the redacted event in the
|
||||
same way a server does.
|
||||
|
||||
Events
|
||||
++++++
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue