docs-matrix-spec/content/rooms/fragments/v11-redactions.md at release

* Remove duplicate words.

* Add information on room version 11.

* Note some event changes.

* Newsfragment

* Fix-up event schema.

* Apply suggestions from code review

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

* Fix 'new in this version'.

* Clarify creator field.

* Fix-up event format & examples.

* Move the Redactions section to the client section.

* Reference the sender instead of the creator.

* More links

* Even more links.

* Fix order of headers.

* Fix typos.

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

* Clarify description of creator.

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

* Clean-up intro paragraphs for redactions.

* Clean-up examples and language.

* Review comments.

* FIx-up markup tags.

---------

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

2023-08-15 00:18:45 -06:00

1.1 KiB

Raw Permalink Blame History

Upon receipt of a redaction event, the server must strip off any keys not in the following list:

event_id
type
room_id
sender
state_key
content
hashes
signatures
depth
prev_events
auth_events
origin_server_ts

The content object must also be stripped of all keys, unless it is one of the following event types:

m.room.member allows keys membership, join_authorised_via_users_server. Additionally, it allows the signed key of the third_party_invite key.
m.room.create allows all keys.
m.room.join_rules allows keys join_rule, allow.
m.room.power_levels allows keys ban, events, events_default, invite, kick, redact, state_default, users, users_default.
m.room.history_visibility allows key history_visibility.
m.room.redaction allows key redacts.

1.1 KiB Raw Permalink Blame History

1.1 KiB

Raw Permalink Blame History