s/should/must for redaction algorithm
This feels like it was a mistake some time ago considering the redaction algorithm is used in very strict algorithms like event signing.
This commit is contained in:
parent
0300a3cab4
commit
be35311559
1 changed files with 2 additions and 2 deletions
|
@ -31,7 +31,7 @@ implementation.
|
||||||
Redactions
|
Redactions
|
||||||
~~~~~~~~~~
|
~~~~~~~~~~
|
||||||
|
|
||||||
Upon receipt of a redaction event, the server should strip off any keys not in
|
Upon receipt of a redaction event, the server must strip off any keys not in
|
||||||
the following list:
|
the following list:
|
||||||
|
|
||||||
- ``event_id``
|
- ``event_id``
|
||||||
|
@ -54,7 +54,7 @@ the following list:
|
||||||
Some of the keys, such as ``hashes``, will appear on the federation-formatted
|
Some of the keys, such as ``hashes``, will appear on the federation-formatted
|
||||||
event and therefore the client may not be aware of them.
|
event and therefore the client may not be aware of them.
|
||||||
|
|
||||||
The content object should also be stripped of all keys, unless it is one of
|
The content object must also be stripped of all keys, unless it is one of
|
||||||
one of the following event types:
|
one of the following event types:
|
||||||
|
|
||||||
- ``m.room.member`` allows key ``membership``.
|
- ``m.room.member`` allows key ``membership``.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue