Clarify m.room.redaction, remove duplicate entry

Signed-off-by: Aaron Raimist <aaron@raim.ist>
This commit is contained in:
Aaron Raimist 2020-10-10 12:59:42 -05:00
parent 62cfc8c472
commit 445b0a3a01
No known key found for this signature in database
GPG key ID: 37419210002890EF
2 changed files with 1 additions and 3 deletions

View file

@ -1,7 +1,7 @@
---
allOf:
- $ref: core-event-schema/room_event.yaml
description: 'Events can be redacted by either room or server admins. Redacting an event means that all keys not required by the protocol are stripped off, allowing admins to remove offensive or illegal content that may have been attached to any event. This cannot be undone, allowing server owners to physically delete the offending data. There is also a concept of a moderator hiding a message event, which can be undone, but cannot be applied to state events. The event that has been redacted is specified in the ``redacts`` event level key.'
description: 'Redacting an event means that all keys not required by the protocol are stripped off, allowing messages to be hidden or allowing admins to remove offensive or illegal content. Users may redact their own events, and any user with a power level greater than or equal to the redact power level of the room may redact events in that room. Redactions cannot be undone. The event that has been redacted is specified in the ``redacts`` event level key.'
properties:
content:
properties:

View file

@ -1551,8 +1551,6 @@ prefixed with ``m.``
{{m_room_power_levels_event}}
{{m_room_redaction_event}}
Historical events
+++++++++++++++++