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.
Thread
Comment by NanbanJim