# Users Automatically Blocked by System

**URL:** https://meta.discourse.org/t/users-automatically-blocked-by-system/41579
**Category:** Support
**Created:** [March 25, 2016, 10:08pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579 "2016-03-25T22:08:26Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![Carson1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/carson1/32/51212_2.png) [@Carson1](https://meta.discourse.org/u/Carson1)
#### Post date: [March 25, 2016, 10:08pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/1 "2016-03-25T22:08:26Z")

</div>

I have noticed that the system automatically blocks some new users. These appear to be normal users who don’t have the same IP as anyone else and in most cases haven’t posted a single thing. Why are these users blocked?

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [March 25, 2016, 10:24pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/2 "2016-03-25T22:24:28Z")

</div>

Chances are they are either posting extremely fast, such as clicking reply, pasting something and hitting the reply button within 3 seconds (this is a site setting).

Or, they are getting picked up via the Needs Approval queue.

Also see

> [@User blocked for no apparent reason](https://meta.discourse.org/t/user-blocked-for-no-apparent-reason/41251):
>
> So…the other day (well, 14 days ago, but I forgot…) we noticed that a user on Stonehearth was blocked, and we can’t figure out why! For the Discourse devs, here is the PM where we discussed the randomly blocked user: [http://discourse.stonehearth.net/t/did-anyone-block-a-user-lately/20556?u=jomaxro](http://discourse.stonehearth.net/t/did-anyone-block-a-user-lately/20556?u=jomaxro) Both moderators (myself and @8bitcrab) and admins (@sdee and @brad) on the site checked the logs, and we confirmed on Slack that no-one initiated the block manually. No posts appeared for approval …

---

<div class="post-metadata">

### Author: ![Carson1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/carson1/32/51212_2.png) [@Carson1](https://meta.discourse.org/u/Carson1)
#### Post date: [March 25, 2016, 10:29pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/3 "2016-03-25T22:29:10Z")

</div>

If they get picked up by the needs approval queue does the system block them?

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [March 25, 2016, 10:29pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/4 "2016-03-25T22:29:32Z")

</div>

Yes, until the post gets approved or the user manually unblocked.

---

<div class="post-metadata">

### Author: ![Carson1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/carson1/32/51212_2.png) [@Carson1](https://meta.discourse.org/u/Carson1)
#### Post date: [March 25, 2016, 11:00pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/5 "2016-03-25T23:00:28Z")

</div>

Regarding the fast typer anti-spam mechanism, are users automatically blocked after they try to reply, or after they trip the mechanism, are they sent to the needs approval queue?

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [March 25, 2016, 11:04pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/6 "2016-03-25T23:04:15Z")

</div>

For fast typing, they are simply blocked (I think, I don’t think it goes to the approval queue, but I can’t promise that). I can’t say that I’ve ever come across that scenario in our instance (or at least I don’t think I have)

---

<div class="post-metadata">

### Author: ![Carson1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/carson1/32/51212_2.png) [@Carson1](https://meta.discourse.org/u/Carson1)
#### Post date: [March 25, 2016, 11:17pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/7 "2016-03-25T23:17:43Z")

</div>

That’s crazy! We should at least be notified.

---

<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 25, 2016, 11:50pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/8 "2016-03-25T23:50:13Z")

</div>

This is 100% totally incorrect.

Blocked posts by new users always come into the approval queue – how could you not see the approval queue?

What generally happens is, **mods decline the new user’s post for whatever reason and thus they stay in a blocked state**. What is the correct way to handle a new user where you have declined their first post, but somehow decided not to destroy their account as a spammer?

It’s indeterminate…

---

<div class="post-metadata">

### Author: ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [March 26, 2016, 12:25am UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/9 "2016-03-26T00:25:32Z")

</div>

> [@codinghorror](#):
>
> Blocked posts by new users always come into the approval queue – how could you not see the approval queue

I assumed there is more logic than typing speed to make posts show up in Needs Approval and there isn’t any way for me to know which of the logistical parts are what invoked the post to go to the queue. Maybe speed is the only factor, which would surprise me, considering the data I’ve seen hit the Post Approval queue.

I also mis-remembered the logging change that occurred recently that was entirely due to speed of reply and blocking users.

---

<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 26, 2016, 3:11am UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/10 "2016-03-26T03:11:18Z")

</div>

To be clear this is what a blocked user looks like, notice the “crossed out / no” symbol next to their name.

 ![](https://global.discourse-cdn.com/meta/original/3X/8/7/8759817abd269c00bda66a35df75af11619dec62.jpeg)

 ![](https://global.discourse-cdn.com/meta/original/3X/2/a/2a8552de1640f995935c96c1b822972f3ae18d56.jpeg)

Rejecting their post here will NOT unblock that user.. and blocked state is on,y really automated on **new users making their first posts** , a time when we evaluate the user’s posts closely for spammy characteristics.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 8, 2024, 12:45pm UTC](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/11 "2024-06-08T12:45:51Z")

</div>

This topic was automatically closed after 2996 days. New replies are no longer allowed.
