-
Couldn't load subscription status.
- Fork 414
MSC4343: Making mass redactions use a new event type #4343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation requirements:
- Like MSC4084, an unstable implementation in a new room version
| In order to not break old clients | ||
| completely, servers should still add a `redacts` string containing one of the | ||
| redacted event IDs to the top level of `m.room.redaction` events in *newer* | ||
| room versions when serving such events over the Client-Server API. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't seem to add up - if there's a new event type then the redacting client won't even send an m.room.redaction event. Unless the homeserver is to synthesise an m.room.redaction event, there's nowhere to add the redacts string; and if it's to synthesise the event, it should be spelled out here.
Rendered
Disclosure: I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published as a Trust & Safety team member allocated in full to the Foundation.