Support MSC4194 (Batch redaction of events by sender within a room) #872

New issue

Open

opened 2025-06-27 22:59:39 +00:00 by nex · 2 comments

nex commented

2025-06-27 22:59:39 +00:00

Owner

https://github.com/matrix-org/matrix-spec-proposals/pull/4194

Supporting this would allow Meowlnir to redact users more efficiently and will pave the way for other T&S tooling. Looks like it might also make us the first server implementation of that MSC, which could help push it into spec.

https://github.com/matrix-org/matrix-spec-proposals/pull/4194 Supporting this would allow Meowlnir to [redact users more efficiently](https://github.com/maunium/meowlnir/blob/eb3175fcc5bdbe0753bfb46d8343f9f5d2664b08/policyeval/execute.go#L229) and will pave the way for other T&S tooling. Looks like it might also make us the first server implementation of that MSC, which could help push it into spec.

nex added the

Database

Enhancement

Matrix/Administration

labels 2025-06-27 22:59:39 +00:00

nex commented

2025-06-28 00:25:11 +00:00

Author

Owner

Game plan:

new db index (mapping of event IDs to user IDs or vice versa or something) to speed up searching for events sent by a user, which will also help with implementing #778
admin command to "reindex" (i.e. clean up old, redundant entries, & retroactively index the database for users upgrading from before this has been implemented)
Actually supporting the endpoint

It's been noted that the likelyhood of supporting ordered redactions is improbable due to the additional complexity and expense (more database lookups required), but I doubt that's a requirement to comply with the MSC.

I have opened several requests for clarification on the MSC, preferrably those would be answered prior to implementation work starting.

Game plan: - new db index (mapping of event IDs to user IDs or vice versa or something) to speed up searching for events sent by a user, which will also help with implementing https://forgejo.ellis.link/continuwuation/continuwuity/issues/778 - admin command to "reindex" (i.e. clean up old, redundant entries, & retroactively index the database for users upgrading from before this has been implemented) - Actually supporting the endpoint It's been noted that the likelyhood of supporting ordered redactions is improbable due to the additional complexity and expense (more database lookups required), but I doubt that's a requirement to comply with the MSC. [I have opened several requests for clarification on the MSC](https://github.com/matrix-org/matrix-spec-proposals/pull/4194/files), preferrably those would be answered prior to implementation work starting.

nex changed title from ~~Support MSC4194~~ to Support MSC4194 (Batch redaction of events by sender within a room)

2025-06-28 00:28:28 +00:00

nex commented

2025-06-28 00:43:48 +00:00

Author

Owner

Should be noted in the relevant changelog that implementing this, while it won't break it, will disrupt cross-compatibility with conduwuit and other forks, unless they also pull in our changes or make similar compatible ones.

nex referenced this issue

2025-06-28 12:24:18 +00:00

Support for the client-side component of MSC4293: Redact on ban #874

nex added the

Matrix/MSC

label 2025-06-28 12:39:53 +00:00

nex referenced this issue

2025-06-29 12:26:14 +00:00

Support for the client-side component of MSC4293: Redact on ban #874