Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update spec links
  • Loading branch information
turt2live committed May 24, 2023
commit cd9c01266061d5ca5877cf4db5b9d44b5264c81d
4 changes: 2 additions & 2 deletions proposals/3821-update-redaction-rules-again.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Update redaction rules, again

The current [redaction algorithm](https://spec.matrix.org/v1.2/rooms/v9/#redactions) are
The current [redaction algorithm](https://spec.matrix.org/v1.6/rooms/v9/#redactions) are
still missing some key fields, even after [MSC2176](https://github.com/matrix-org/matrix-spec-proposals/pull/2176)
attempted to fix some of the obvious cases. This MSC aims to fix more fields.

Expand All @@ -12,7 +12,7 @@ before this proposal as MSC2176 contains a lot of backing context.
In a new room version due to redactions affecting event hashes, we:

* `m.room.member` events additionally preserve part of `third_party_invite` under `content`, if present:
* Spec: https://spec.matrix.org/v1.2/client-server-api/#mroommember
* Spec: https://spec.matrix.org/v1.6/client-server-api/#mroommember
* Under `third_party_invite`, `signed` is preserved. Rationale being that the `signed` block is required
for the server to validate the event, however excess fields and `display_name` are not as important.
Clients which are trying to represent a redacted `m.room.member` event with `third_party_invite` should
Expand Down