-
Notifications
You must be signed in to change notification settings - Fork 379
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2174 from matrix-org/rav/proposals/move_redacts_key
MSC2174: Move the `redacts` key to a sane place
- Loading branch information
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# MSC2174: move the `redacts` property to `content` | ||
|
||
[`m.room.redaction`](https://matrix.org/docs/spec/client_server/r0.5.0#m-room-redaction) | ||
events currently have an *event-level* property `redacts` which gives the event | ||
ID of the event being redacted. | ||
|
||
The presence of this field at the event level, rather than under the `content` | ||
key, is anomalous. This MSC proposes that, in a future room version, the | ||
`redacts` property be moved under the `content` key. | ||
|
||
For backwards-compatibility with *older* clients, servers should add a `redacts` | ||
property to the top level of `m.room.redaction` events in *newer* room versions | ||
when serving such events over the Client-Server API. | ||
|
||
For improved compatibility with *newer* clients, servers should add a `redacts` | ||
property to the `content` of `m.room.redaction` events in *older* room versions | ||
when serving such events over the Client-Server API. |