feat: flag to redact all user messages upon deactivation #778

Open
opened 2025-04-20 12:13:00 +00:00 by nex · 2 comments
Owner

perhaps -r/--redact, mutually exclusive with -n?

perhaps `-r`/`--redact`, mutually exclusive with `-n`?
Author
Owner

May also want to include a reason in the bulk redactions, something like "redacted by server operator". Could be re-used for the #748 bulk-redact endpoint, which also means that you can't determine with 100% certainty that the account was deactivated (if we care about that)

May also want to include a reason in the bulk redactions, something like "redacted by server operator". Could be re-used for the #748 bulk-redact endpoint, which also means that you can't determine with 100% certainty that the account was deactivated (if we care about that)
nex added this to the 0.6.0 milestone 2025-06-18 16:38:39 +00:00
Author
Owner

Building off of 872's changes, we should:

  • Issue redactions for all events where the sender is still joined to the room, and has permission to send the redaction
  • Attempt to puppet another user's account in the same room to issue the redactions, if they have permission to
  • Internally redact those events, so if we're asked for them over backfill, we serve them in their redacted form, even if the redactions failed.
Building off of 872's changes, we should: * Issue redactions for all events where the sender is still joined to the room, and has permission to send the redaction * Attempt to puppet another user's account in the same room to issue the redactions, if they have permission to * Internally redact those events, so if we're asked for them over backfill, we serve them in their redacted form, even if the redactions failed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: continuwuation/continuwuity#778
No description provided.