Skip to content
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

[Story] Redaction recommendation for m.policy.rule.user. #10

Open
Gnuxie opened this issue Jan 31, 2024 · 0 comments
Open

[Story] Redaction recommendation for m.policy.rule.user. #10

Gnuxie opened this issue Jan 31, 2024 · 0 comments
Labels
outdated The story or task needs to consider more recent work

Comments

@Gnuxie
Copy link
Member

Gnuxie commented Jan 31, 2024

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.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.

Issues

Dependencies

Total Pain

20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
outdated The story or task needs to consider more recent work
Projects
Status: No status
Development

No branches or pull requests

1 participant