Users Automatically Blocked by System

AI-generated summary

Users are being automatically blocked by the system upon registration, raising concerns about the process. Carson1 questions why normal users are blocked without clear reasons. cpradio suggests possible causes: rapid posting (triggering anti-spam) or entry into the Needs Approval queue. Carson1 clarifies that blocked users are sent to the approval queue, and cpradio confirms they remain blocked until approved or manually unblocked. Carson1 asks whether fast typing leads to blocking or approval queue placement, and cpradio says blocked users are likely not sent to the queue. codinghorror corrects the misunderstanding, stating blocked posts always go to the approval queue and that mods must approve or reject them. He notes that rejecting a post does not unblock the user, and the block is typically automated for new users’ first posts. cpradio admits uncertainty about the exact triggers. codinghorror also shares images showing blocked users with a crossed-out symbol, emphasizing that the block is tied to initial post evaluation.

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?

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

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

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

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?

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)

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

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…

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.

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

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.