# Can we automatically combat Sea-lioning

**URL:** https://meta.discourse.org/t/can-we-automatically-combat-sea-lioning/112258
**Category:** Community Building
**Created:** [March 21, 2019, 3:11pm UTC](https://meta.discourse.org/t/can-we-automatically-combat-sea-lioning/112258 "2019-03-21T15:11:36Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [March 22, 2019, 6:24am UTC](https://meta.discourse.org/t/can-we-automatically-combat-sea-lioning/112258/5 "2019-03-22T06:24:52Z")

</div>

Yes, the “slow mode” referenced is the right idea in these cases. Better to follow up there.

> [@Post Rate Limit Trigger for a topic that's heating up](https://meta.discourse.org/t/post-rate-limit-trigger-for-a-topic-thats-heating-up/98294/22):
>
> 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. [image] 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 a…

I do think @falco’s idea of how to automatically trigger this based on topic velocity is solid. The only thing I’d add is once velocity gets high enough, you probably need to _temporarily prevent new users from posting_ as well – otherwise people could circumvent the speed posting checks by creating new burner accounts.

(I think a massive influx of new posters is also kind of a problem in those scenarios, even if those new posters are well-intentioned.)

---

_[View the full topic](https://meta.discourse.org/t/can-we-automatically-combat-sea-lioning/112258)._
