Dynamic slowmode

(#3541) Feature Open: Under consideration channels messaging

Current problem

So basically if a community suddently spikes in activity because an announcement pinging everyone was just made or something similar moderators will suddently have a lot more work to do so they will usually raise the time between messages in the slowmode and that can be tedious each time and if it doesn't get reset to it's original value it can be frustrating for users when activity dials down again, unless you use a third party bot to do it automatically

Proposed change

What i'm proposing is a per channel option that can be enabled so that slowmode can automatically be set to certain values based on that channel's activity (for example based on how many messages per minute/second get sent)

Platform

macOS, Windows, Linux, Web, Android, iOS, API, Self-hosting

Additional information

Many big communities on discord already do this using a third party bot so it would be nice to have this entirely in platform without needing any third party tools

1 comment

Sign in with Fluxer to comment and vote.
Comment by NanbanJim
I had written this feature request in an email back in May; reproducing here for consideration. Feature Request: Progressive Slowmode This Feature Request centers on a Progressive Slowmode, but also suggests @user-specific slowmode settings. FR uses standard <required> and [optional] notation. Usage: /slowmode [/progressive] <#channel|@user [#channel|all]> [timer] /slowmode <#channel> [timer] mutes all users in the specified <#channel> for [timer] seconds after they send a message, 60s default if unspecified. /slowmode <@user> [#channel] [timer] mutes an individual <@user> in a specified [#channel] (or [all] channels) for [timer] seconds after they send a message, 60s default. The /progressive switch doubles the [timer] value for each message sent by a user before their [timer] has expired. Due to the cascading effects, the /progressive switch also has a default [timer] of 6s. These options SHOULD (RFC2119) also be options in a channel's settings. Use Cases: Extremely high volume channels, spammy users, administrative convenience, desire for quality over quantity, argument cooldown, etc. Examples: In 2 scenarios on Discord, enforcing Progressive Slowmode by hand has taken the wind out of a disruptive argument's sails. In 1 of those scenarios, 1 user used the time to write wall-o-text, which caused the other side to realize how utterly stupid arguing over the topic was. Enforcing Progressive Slowmode by hand would not have been possible had I not been infuriated by the persistent arguments between these users in the past (different sets of users in each scenario). Admins with any experience can envision or recall scenarios where a user, due to any number of issues (giddiness, anger, inebriation, youth, etc), is rapidly sending (or receiving) a disruptive amount of messages in short order.