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

"Notify" on list match #269

Closed
ShadowJonathan opened this issue Mar 30, 2022 · 5 comments
Closed

"Notify" on list match #269

ShadowJonathan opened this issue Mar 30, 2022 · 5 comments

Comments

@ShadowJonathan
Copy link
Contributor

Is your feature request related to a problem? Please describe.

I want to subscribe/follow a moderation list, but I do not fully trust or "vibe" with the moderators behind that list, as they could have a different/more strict CoC than my own community would have.

Describe the solution you'd like

Be able to subscribe to a list on a "notify" basis, that if there's a match, that match is presented in the management/moderation room, and a quick action on what to do with it. (Follow/ignore)

Additional context

Moderation lists are great, but the way they're used today can be a bother because (from what i understand) people are either actively following and applying moderation from every list, or not.

This is a middle ground, where moderation teams for "neighboring" communities are alerted to a moderation decision, and can look into it, or at least become aware of such an action, to pay close attention to the members/servers involved.

@ShadowJonathan ShadowJonathan changed the title "Notification" on list match "Notify" on list match Mar 30, 2022
@ShadowJonathan
Copy link
Contributor Author

Additionally; "Ignore" can be expanded to "ignore for this match" and "ignore for any match", the former will notify if a new Notify match appears in a different list, but the latter will ignore any further Notify match.

@Gnuxie
Copy link
Contributor

Gnuxie commented Mar 30, 2022

For context; Currently the only way watched lists are audited when changed by another user is with https://github.com/matrix-org/mjolnir/blob/main/src/Mjolnir.ts#L971

For bus factor: The problem goes a lot further than improving auditing, there's an entire domain to explore with regards to propagating bans beyond who you trust to be in the moderation room/adjacent communities. Another glaring thing to be careful about is the distinction between banning because a ban was recommended via a watched list and reaffirming that ban by republishing in your own list. Duplicating a published ban should really be done sparingly, as if you aren't banning someone firsthand, you'll want any unban to be propagated to you.

@ShadowJonathan
Copy link
Contributor Author

Sounds like some spec/schema changes need to occur then to signal that it's a manually-approved delegated ban, sourcing from a different list, instead of being from your own list.

@ShadowJonathan
Copy link
Contributor Author

Thinking about this while working with mjolnir, i think there's two subcategories here; match-notify and change-notify.

match-notify would notify of the rule's existence in the mod room when it comes into existence and matches existing users, or if a user were to join that then matches one of those rules.

change-notify would notify on changes in lists themselves.

Both would probably have quick-action buttons, like ✔️ and ❌, which'd allow mods to take quick actions on eying the rule. This'd make the rule probably to be added to a default list, with a reference to the original list/event where the rule originated from.

@turt2live
Copy link
Member

Duplicate of #68 and/or #18

@turt2live turt2live closed this as not planned Won't fix, can't repro, duplicate, stale Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants