15

When I encounter a post in the first-posts or late-answers queue and flag it as spam or rude/abusive, and then hit I’m done, it is dequeued.

This leads to the absurd situation that when I want the post to be deleted as quickly as possible, the best course of action is to flag it and then hit Skip. This is obviously counter-intuitive and nothing we can expect reviewers to know. (It also means, that reviewing badges incentivise sub-optimal actions.)

I thus suggest that:

  • Posts flagged spam or rude/abusive in the first-posts or late-answers queue do not get dequeued (unless that flag deletes the post).
  • Those posts are prioritised in all review queues (in which they already are).

(Of course, the flagged posts should enter the moderator queue as they did before.)

This request is similar, but apparently about a significantly different, old review system.

  • Spam flag should send it to the moderator's queue, as far as I know. So it's "dequeued" from one place, but enqueued in other. – ShaWiz May 8 '16 at 12:28
  • @ShadowWizard: Sure, but it can also be destroyed by regular users, if only enough get to see it before a moderator is bothered. – Wrzlprmft May 8 '16 at 12:31
  • Still, I don't feel it's very elegant to keep spam where it doesn't belong. – ShaWiz May 8 '16 at 12:33
  • 11
    @ShadowWizard: How does spam not belong in front of reviewers? It’s one of the reason why those review queues exists in the first place. The help text for the late-answers queue even says: “Watch for […] spam.” If anything, it’s dequeueing those posts that keeps spam where it doesn’t belong: on the site. – Wrzlprmft May 8 '16 at 12:38
4

The purpose of the First Posts queue

The only users who can actively delete anything from that queue are moderators, and that's simply because it doesn't make sense for them to flag something for themselves or go out of their way to perform an action they should be able to perform wherever they see the post. It's not built to be a deletion queue.

The queue exists as a quality check mechanism. These are the first posts coming in to our site from these users, and it's helpful to have a set of eyes say "looks good" or "this could use some attention." All you're doing there is raising a signal fire when something looks off, so that it can be pushed in front of someone else's eyes to be fixed, depending on what the issue was.

Flagging as spam achieves that goal. Spam and offensive flags go directly to the top of the moderator flag queue, regardless of age or how many flags are on the post. They always go straight to the top, because they're important. They also generally get handled pretty quickly once they're at the top of that queue. Quickly enough that I rarely ever see them sitting there.

Some history on spam/offensive flags

Long ago, these flags used to appear in the 10k flags queue as well. But a massive problem arose here in that putting a post in front of a bunch of users with any sort of "spam" label on it almost always resulted in that post being deleted as spam - even if it shouldn't have been. Eventually spam and offensive flags got removed from the 10k flag queue and only shown to moderators.

We don't want a similar thing to happen in review. We already have a problem of users who see that message and just automatically flag it as spam. I've even seen some of them ask about it on Meta - why it was there, and why the system wanted them to flag it. While the message was meant to be an eye-opener and make you look at the post twice, it does have some harmful side-effects on occasion. But by simply raising a flag and letting the moderators handle it, we're limiting the damage to just a bad flag on a post that wasn't quite spam, rather than a post that erroneously got deleted, locked, potentially cost a user 100 reputation, and probably triggered an IP hobble.

In contrast, the worst thing that happens if a post gets deleted as not an answer is that the post gets deleted.

Not everyone cares as much as you

There's a large combination of factors out there for why we don't want regular users "reviewing" spam/offensive flags - people who don't understand when to use the flags, people who just plain get confused, etc. But above all, there are sometimes people who just don't care - the robo-reviewers, the people who just like flagging things for badges, etc.

Moderators care. If they didn't care, they wouldn't be moderators much longer. And it takes quite a bit of care to handle these flags correctly, given that they have some pretty detrimental effects to the user when they are deemed valid and the post is deleted, not all of which the moderators can undo (if it triggers an IP block, they have to get staff involved).

I'm not saying your request is being declined - I'm saying that we'd be very, very reluctant to make a change such as this, because we've seen what effect that label can have on a user's ability to handle posts effectively and fairly, and because they tend to get handled quickly enough that the additional complications to the system are not needed.


Keep in mind as well that any user who encounters posts like this through natural use of the site can still flag directly on the post. You want it deleted quickly, but it only needs to be deleted quickly if there are a lot of users looking at it. But if there are a lot of users looking at it, then it's already more likely to attract a lot more flags in a short time from those looking at it. If no one is looking at it, then there's not exactly a rush to get it removed, because no one is seeing it anyways.

  • 3
    Much of this answer seems to hinge on the observed effects of sending posts marked as spam past multiple reviewers... but the FP (and LA) queues do not have such a marking in most cases. Users can't see flags, certainly, and the "this post may be spam" warning is shown only when the software is uncertain about automated blocking. Caution about the effects of prejudged, focused attention is certainly warranted, but in cases where it really isn't prejudged... I'm not sure it's such a bad thing. – Nathan Tuggy May 8 '16 at 21:18
  • 1
    @NathanTuggy Sure, that's a big reason for it and the warning does raise that issue, but the other part is this is still fairly unnecessary. Y'all are asking for a change to deal with something that already gets handled well, and could potentially lead to things getting handled incorrectly. I'm not seeing the benefit. – animuson May 8 '16 at 21:20
  • 2
    It gets handled well on SO. Not so on smaller sites. – John Dvorak May 9 '16 at 17:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .