Replies: 2 comments
-
Bruh, now, what’s left to us? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Mention rate limit and global message limit would be good, since Discord can be proactive, compared to the reactivity of bots. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
AutoMod allows pre-moderation, however it can be extended into a more general policies system to allow even more detailed moderation possibilities.
Proposal
I propose a few policies that would complement existing moderation tools.
Channel rate limit across users
Per-user rate limit, i.e. slow mode is useful to ease up a bit of a moderation load, but it does not necessarily make whole discussion slower-paced. Channel rate limit across users, on the other hand, would be useful to slow whole discussion, and force a more IM-like or more forum-like discussion by altering the pace of the discussion. It is generally known that slower discussions have more thoroughly thought-out messages posted, compared to rate-unlimited channels.
Fan-out and rate limiting of mentions (thanks @Andre601)
Guild admins should be able to limit how many mentions can be used per posted message, and users should similarly be able to limit how often they can be notified when they get mentioned, and how often they can be mentioned per user.
Channel-specific attachment policies
Guild admins should be able to restrict the ability to upload attachments, beyond a simple "upload new files" permission. The proposed policy item involves:
Shadow bans
Auto-moderation policies should have a possible remedy of applying policies in a stealth, also known as shadow ban, fashion.
Minimum membership duration condition
Guild admins should be able to impose membership duration (intended to survive past leave&rejoin, membership duration of an individual user pre-leave not accessible to any user other than the member, just emit an event when the user acquires the condition to access the channel) conditions, in addition to roles.
Pre-scheduled changes to guild settings
Guild admins should be able to schedule certain changes (roles, auto-moderation, attachment policies, MFA conditions) to a certain time, to allow synchronised changes (bots currently cannot do that, as they can only apply most changes one by one).
Bot permission preconditions
Guild owners should be able to impose certain pre-conditions to bots, in terms of required or prohibited approvals (I am thinking of privileged intents and privileged OAuth scope approvals). For example, one may want a certain bot to be auto-kicked when they gain an ability to read messages (guild messages' content intent). The alternative can be per-guild intent masking of bots, but that would be more expensive than auto-kicking a bot once it gains approval to a certain intent.
Scope
Applies to humans and bots alike.
45 votes ·
Beta Was this translation helpful? Give feedback.
All reactions