As a policy room curator, I can write detailed reasons for adding a user policy to a policy list without disrupting my consumer's tooling. Currently, I cannot do this because Draupnir uses a list of words configured in config.automaticallyRedactForReasons to determine if a policy targetting a user should result in redaction of that user's messages. This restricts me from being able to write any reasons other than those that are default in Draupnir because consumers of my list will not have their Draupnir redact messages from spam bots.
Acceptance Criteria
When a user is banned for spam, illegal, intolerable etc content, a policy is created with the recommendation to redact in addition to ban.
Draupnir can consume redaction policies, check the timeline for relevant events and then redact them.
Redaction policies can be issued distinct from bans via a command.
A decision has been made with justification as to whether a redaction policy needs to be linked to the ban policy for purposes of auditing, expiry review etc.
Description
As a policy room curator, I can write detailed reasons for adding a user policy to a policy list without disrupting my consumer's tooling. Currently, I cannot do this because Draupnir uses a list of words configured in
config.automaticallyRedactForReasonsto determine if a policy targetting a user should result in redaction of that user's messages. This restricts me from being able to write any reasons other than those that are default in Draupnir because consumers of my list will not have their Draupnir redact messages from spam bots.Acceptance Criteria
Issues
Dependencies
Total Pain
20