Post Rate Limit Trigger for a topic that's heating up

In the meantime I suggest a staff member issue a timed close on any problem topics so it can “cool down”, where the topic automatically reopens after the number of hours you choose. Additionally, enough live community flags will cause a topic to enter a timed close as well, so you could encourage community members to flag this kind of disruptive behavior.

One thing I’m unclear on is when to automatically enter the “slow down” mode for a topic, and when to exit that mode. What should the thresholds be?

To be clear I fully support this approach and technique, but it takes some consideration to get the defaults right.


First of all, thanks so much for providing discourse and all of this for us - it’s definitely been a boon to our organization so far. Second, as a mod on this forum, I can say that ignoring specific users would be very welcome by members of the forum. I’m excited to see it being developed and on the release timeline, and like that it will flag multi-ignored users to staff. I’m curious to see how that works with threads and conversations that the user is involved with.

Timed closes is what we’ve been doing. It’s helped a lot to cool down topics, and to give us as mods a breather.

I’m not sure whether we need an “automatic slow down” mode as much as we need a trigger to indicate “this thread needs to slow down”. It’s fairly easy for us to know what threads will escalate, and we can’t - as Speck described - limit those threads from not happening or prevent them, so a simple toggle that we can activate would probably already help a lot (one that Trust Level 4 users could trigger too, would be really helpful).

Then I don’t know how possible it is to limit responses from the heaviest participants, as opposed to someone who hasn’t participated yet in the thread. That’s something we would also love to be able to tweak. Off the top of my head - something like “if the thread has had 10 posts in the last hour, and if this person has written 20% of the words in this thread, limit them to comment every 15 minutes”. It’d be a forced step back? Again, don’t know how feasible that is, but I feel like that kind of nuance would be nice.

And again, just a “slow down” toggle would go a long way to helping here I think. “if activated, default to slow down at one reply a minute”. With it being clear in the UI that this is a “slowed down” text.


I don’t think that’s precisely workable because I can imagine 6 people waiting to post and trying to get in on that minute allotment. But perhaps the per person slowdown can be dynamic to the number of words/posts being put up? If there’s a lot happening then the limit increases to match and vice versa. With a dynamic timer on the top of the compose box, people would be able to know how long they have to wait to get their reply in.

One of the major frustrations I have with the posting limits is that I don’t know when I’m about to hit it. Only finding out that I have to wait 45 seconds after I press the post button is jarring.

1 Like

Not sure about the automatic trigger, but looking from prior-art about how it would work:

  • Staff can trigger slow mode from the wrench menu.


  • New Site Settings:

    • Slow Mode Interval: Minimum time between posts from the same user in slow mode topics.
    • Min Trust to Slow Mode Immunity: Minimum Trust Level for Slow Mode Immunity.

Regarding automatic triggers, we could:

  • Check for posts rate in a topic during the last interval (day/hour, etc). Eg: If a topic has more than 50 posts an hour, or 100 topics per day, trigger slow mode for next 24h.

  • Not sure flags are correct here, the discussion is lawful, just too fast so it excludes most of community who aren’t online here right now from participating.


Given the “factional” issue you are seeing I am really not sure what we could do to improve this unless factions are properly defined.

If we say “only 1 post is allowed every 3 minutes, period”, then one faction can drown out the other faction by basically doing the ebay trick and always posting just as the limit is about to be hit.

If we say “only 1 post per user per N minutes” then the larger faction always wins, cause that faction will always get to post more than the small faction.

If we could rate limit to one post per faction then I guess this can work, but enforcing this with software sounds like a nightmare.

Honestly, I am not sure if simple rate limits can fix this problem. Freezing conversation temporarily to let people cool off is one approach that certainly works (and is already automatic in the case of flags). The other one I see with lots of merit is the ability to kick certain users off topics or even categories (while leaving them in the forum), eg: light weight bans. Technically this is achievable today by simply informing users that they must behave in a certain way or they will be booted.

Have you considered ramping up moderation in your forum, or maybe even simply ramping up TL4 user count?


The noisiest people on each side are by far the most aggressive, so having a rate limiter on the noisest folks on each side would be quite effective. It lets the more thoughtful people – on each side – have equal time to the noisiest folks. That’s a big deal.


Another product introduces the same slow mode we discuss here:


Oh, what a fantastic tool this would be for us. Generally our community gets along well, but there are times when things get so heated that they explode faster than we can deal with it. We don’t want to stop the conversation, just slow it down.

I’m not fussed about an automatic trigger for us (I can’t imagine trying to determine the defaults for that) but a toggle in the menu would be phenomenal.

I’d prefer this be something we can turn off for TL4s if necessary, but am fine with them having it generally. For our local representatives especially, being able to slow down conversations would be vital. I’ve seen a similar feature in action on Twitch and love it.


I also run a community about roleplaying games that could make good use of this feature.

Just to explain, discussions can end up being divided on factional lines, sometimes on cultural grounds. There is also a lot of questions-and-andswer kind of process going on, where it’s important that the beginner receives good, thoughtful and written out explanations. Sometimes even just for zeal and enthusiams of posters, discussion might go into an unproductive direction if the OP that asked the original question gets drowned out by tons of small messages.

We have some experience in other forums about the same topic where a “slow down” rule was enforced by the moderators, and it seemed to work well. I think this is something that seems natural that could be managed directly by the software, removing the need for moderator intervention (which always comes at a cost).

I subscribed to this topic so I get notified if there’s any updates on this; I really think this would make for a great feature.


This feature would be helpful even for our community :+1:

1 Like

Sorry if I keep pestering on this feature, but I would like to give a concrete example of how some sort of slow mode would highly benefit discussion in particular cases.

It’s all Italian language, sorry about that. My main concern in this discussion is not the content of the posts at all (it’s all rather fine and polite), but the fact that a few well-meaning overzealous users are posting too much, shutting down discussion for everyone else, and making the thread inaccessible to outsiders wanting to join in.

You can definitely see how temporary thread closure is not a good tool for this. It doesn’t solve the problem: overzealous users are still free to post as much as they want while the thread is open, while readers or more casual posters now might not intervene because of the thread being closed, and them not being available to post at the time of opening.

If we had the ability to limit discussion to one post per user per day, then everyone would get the chance to join in, and the topic post count would also not grow as much.


Believe me, I am a huge fan of this concept. It makes sense. It’s a question of having the time to do it!

In the meantime I’d recommend intervening with those specific users, but I hear you.


Yeah, that’s what we’re doing at the moment.

We’ve got something similar with a kid’s thread in our forum-- it’s the busiest thread on our forum, and is mostly populated with 14 and 15 year olds, lol. They have a tendency to spam the thread. Now, we are of course working on the users themselves, but these are young people who like to make sockpuppets. Thankfully they haven’t yet stumbled on the concept of changing IP addresses, but once they do it’s going to get harder to control.


We have a related issue, where we don’t want to prevent people making posts, but we want to delay making them visible to others.

We have a community of a few hundred people, of which a handful are online pretty much all the time. What tends to happen is that for a lot of new topics, those people (of whom I’m one), all pile in and reply very rapidly, and then keep replying to each other.

That means that by the time the less engaged people see the thread, it hardly seems worth commenting, because what they want to say has already been said, or the matter seems to have been settled (people say this explicitly).

This means we get less widespread participation and engagement than we would like. Often the thread is not time-critical, so a slower conversation involving more people would be much better.

It’s not that we don’t want replies from the engaged people, we just don’t want them to immediately dominate and swamp the thread. So what we would like is a way to mark some/all threads as delaying replies. In this state, people can reply, but their reply doesn’t become visible to others for a length of time.

That way the hectic back and forth won’t happen, and other people get to comment on the thread from a clean start.



In our case the problem is also that these few people jump onto EVERY forum topic. So lately we’ve been thinking of a per-day posts (including replies) limit for all users. A high limit that would only affect these few power users, and they could come back the next day in order to post more. And excluding subforums that are dedicated to quick-paced chatter.


Believe me, I am starting to become strongly in favor of this as a category level setting. Limit the number of replies you can make – so you can make them count rather than overwhelming people with excessive verbosity and infinite replies…


That would definitely be useful in some cases.

But I think there is a separate issue about the speed of replies, as opposed to the number.

I don’t want my most active users to be discouraged from posting. I don’t want them to have to jump through hoops to come back later, because that’s punishing them for being really valuable contributors.

I just want the visibility of their contributions to be delayed so that not every thread has immediate comments from the same few people within five minutes.

That puts off everyone else from replying, and therefore makes a broader, more involving discussion less likely.


A BIG :+1:
That’s exactly what I was thinking since a while reading this discussion.
IMHO, there would be a solution (albeit a slightly more complicated one) by forking a portion of the discussion (and/or some of the participants) into another topic (maybe a closed one, not sure) not appearing on the front page. This could be a solution to some problems raised here. Fork a particular point (“hot topic”) or group of users and try to force them to arrive to a conclusion, then maybe post a summary in the initial topic. There could be ways to automate this to trigger it automatically according to certain parameters (one concern raised being the time to be able to react).

There are not many solutions for UNREASONABLE users, though. And “slowing down” the discussion seems to appear to be the “best”, or maybe the “only” one. (Unless banning such users. But many also aren’t always unreasonable, so it’s not simple)


I am hugely in favor of many of the strategies being discussed here.