This came up recently, where a user had taken the time to look at the link on a post and realized that the post wasn't just off-topic, it was actually half-decently-disguised spam. So he flagged it as spam, and an overworked mod declined it, giving the questioner the benefit of the doubt. And we probably want mods to be giving the questioner the benefit of the doubt.

We also want to get rid of spam ASAP, and make the lives of mods easier. I'd like to suggest a feature the mod in question mused might be useful: An optional textbox where you can add a note saying why you think it's spam, so the mod can see it easily. In this case, the helpful user who went the extra mile could have written "Site linked doesn't relate at all to the question, instead solicits BitCoins" or similar.

One can leave a comment on the question, but:

  1. People sometimes leave...unhelpful...comments on spam questions, and we don't want mods to have to take the time to read through them hoping for something useful

  2. It allows the user flagging the spam to do so and say why without calling attention to themselves publicly

Update: We may well want this for all flags, but in particular I had reason to want it for an NAA flag, so I've posted this other feature request for it.

  • 61
  • 10
    Additional support for this idea: meta.stackoverflow.com/a/288085/19679 Commented Mar 16, 2015 at 18:28
  • 1
    This would help. Although I've had a spam flag declined when the OP, an unregistered uses, had a link at the bottom of their post saying "come to me for SEO" (unrelated to the question). Something like that, I'm not grown-up enough to be able to look at the (later) deleted answer. On the other hand, I still have a custom flag outstanding on a self-promotion/borderline spam. So, it won't be perfect (we make mistakes), but it will be useful. If we get the feature, would the advice be to use it, unless absolutely blatantly 100% obvious? Commented Mar 16, 2015 at 21:54
  • 27
    I want this for all flags. In particular not-an-answer often requires an additional explanation. Commented Mar 17, 2015 at 12:47
  • 3
    Isn't this what the "other" flag is for? It already has a text box to describe the reason.
    – TylerH
    Commented Mar 17, 2015 at 13:34
  • 14
    @TylerH: No, "other" doesn't have the same automation associated with it, nor does it appear in the same places for mods to look at. Commented Mar 17, 2015 at 13:36
  • 3
    How can it be made clear that a mod will often not read this text, as the processing of spam flags is mostly automated. E.g. don't include anything other then explaining the spam flag. Commented Mar 17, 2015 at 15:04
  • @IanRingrose, as far as I know/have found, mods get it on their dashboard first after 1 flag and only after 6+ flags is it handled automatically. For making it clear that it should only be explaining the reason for the spam flag, perhaps just have placeholder text displaying when the user is presented the input, something like "(Optional) Provide specific details of why this post is spam".
    – Turnerj
    Commented Mar 17, 2015 at 22:29
  • 2
    @CodesInChaos NAA goes to LQP, so I usually just leave a comment on the post for the reviewers (and presumably the mods will look at it if they handle it manually). So if we're going to add optional explanation, it needs to show up in LQP too. Commented Mar 17, 2015 at 22:32
  • 1
    Being able to explain yourself couldn't be a bad thing in any circumstance.
    – Chris
    Commented Mar 18, 2015 at 3:50
  • 1
    @Ian Ringrose: The system could implement this by way of creating both a spam flag and a custom flag. Custom flags will remain pending on posts even after they are auto-deleted by spam flags. Commented Mar 18, 2015 at 3:56
  • 1
    @Duncan every meta is monitored by SE employees (even the little ones) and they all are appropriate for system-wide support.
    – corsiKa
    Commented Mar 18, 2015 at 19:57
  • @corsiKa: That's useful to know. Commented Mar 18, 2015 at 20:04
  • 3
    Being able to add in custom text to a spam flag would be useful for when a user has information promoting their product and their profile but fail to disclose that when they post an answer. This would give the ability to let the moderator handling the flag to check the users profile or other source as needed.
    – Joe W
    Commented Sep 21, 2015 at 15:21
  • 2

2 Answers 2


The more general case came up recently: We should always be able to include explanation with moderator flags, even if they're not a custom situation. I think Shog's answer applies here too. If it's not clear that a post is spam, you might want to use a custom flag instead of the simple spam flag. The downside, of course, is that you aren't contributing to 6 flags required for the community to delete spam automatically.

The catch here is that it's hard to know beforehand that your spam flag will be misunderstood. If you were a 100% certain the moderator wouldn't see how this is spam, you would always leave a custom flag. If you were certain the spamminess was obvious, you'd never bother. So how likely are spam flags to be wrongly declined?

All-time on Stack Overflow, the statistics are:

N Name
221606 Helpful
17027 Declined
9309 Disputed
860 Self Clear

(For those who, like me, get confused about what a disputed spam flag is, it means the post was rolled back or undeleted and a moderator dismissed the flag. I've also excluded Smokey's autoflags.)

So if every declined spam flag represented a misunderstanding, there would only be a 7% chance adding a message would help. But I'm pretty sure that most of the declined spam flags are the result of flaggers not understanding the purpose of the flag. It seems like the cases where a custom comment on a spam flag would be useful are vanishingly small.

Another question suggested that not providing an explanation wastes moderator time. If this were a problem for them, we'd certainly heard about it. But there's an even better reason to recommend subtle spam should be flagged 'in need of moderator intervention': human task switching. Spam flags are usually quite easy to clear as it's generally random crap unrelated to the site's topic. (For examples, check out the autoflag logs.) Self-promotion spam is a very different beast. Often it's not malicious, but just a little unclear on what the rules are. Most spam users can be deleted without thought, but people who talk about their own stuff should be contacted by a moderator more often than not.

In other words, we talk about spam to mean two very different things:

  1. Mindless attempts to plant links somewhere (anywhere!) on the internet.
  2. Calculated attempts to answer questions with subtle advertisements.

Despite the shared name, these are very different problems with different remediations. So they should be flagged differently.

It occurs to me that we can estimate how many spam flags would benefit from having comments by looking at a sampling of posts that received a declined spam flag:

  1. https://stackoverflow.com/questions/50298996/c-program-linked-data-structure-for-sparse-matrices (Image link I guess?)
  2. HTTP ERROR 500 given when adding php script to website login/register feature (Links to own site, but it's not worth spamming yet as it's just a shell. Also, OP disclosed their affiliation.)
  3. https://stackoverflow.com/questions/50296064/been-hacked-phone-has-been-cloned-i-dont-know-how-to-speak-up-to-your-standards (Email?)
  4. Create multiselect lookup in salesforce using apex (Deleted since it's just a link to a GitHub repository. Might be spam, I suppose, but only one of the 7(!) flags was of the spam variety.)
  5. https://stackoverflow.com/questions/50287073/getting-error-code-504-when-trying-to-update-facebook-via-play-store (Of the 8(!) flags, only one is for spam. No link or anything.)
  6. https://stackoverflow.com/questions/50287135/the-localhost4200-is-not-working (Image? IDK.)
  7. https://stackoverflow.com/questions/50286711/zoomable-user-interface-in-python (No link or any reason for the spam flag.)
  8. https://stackoverflow.com/questions/50284382/page-navigation-buttons (Link to blog, supposedly. But the domain is not registered.)
  9. https://stackoverflow.com/questions/50283654/rtsp-command-for-move-head-of-cctv-using-java-jdk-1-8 (IP address in the code?)
  10. what can change extension .txt to .HTML files with ruby (I got nothing.)

So of the ten most recent rejected spam flags, maaaaaybe 2 (#4 and #8) are plausibly self-promotion and none are the typical fake designer handbag type. Personally, I'd decline all ten flags. My guess is some of them are mis-clicks and the rest are misunderstanding how flags work here.

  • 10
    How many custom flags are there currently that could have been spam flags if spam flags had an explanation box? Commented Aug 15, 2015 at 13:41
  • Agree with @JohnDvorak . What is the worst, no-one has access to the figures to prove anything with them. Commented May 10, 2018 at 0:47
  • According to meta.stackoverflow.com/questions/367645/… (10k needed) and meta.stackoverflow.com/questions/367645/… , a large portion of spam flags come as a result of automated actions by "SmokeDetector" (even though they seem to be double-checked by people), so the figures as they are are skewed, and the conclusion about the percentage is wrong! Commented May 10, 2018 at 13:32
  • @ivan_pozdeev: This answer is a little out of date. When it was written, I don't think SmokeDetector even existed. Commented May 10, 2018 at 22:46
  • @JonEricson Well, Shog9 has closed my feature request as a duplicate of this. If this Q&A is outdated, my request is not a duplicate because the changed circumstances have made the justifications here no longer apply. Commented there to this effect and VTRed. Commented May 11, 2018 at 1:17
  • If your previous all-time data had 5% rejection and the current one has 7%, that means if you only take recent data, the percent will be even higher. Comparing your two results, the percentage for the last 2.5 years is 11.4% and ~10.4k posts. Commented May 11, 2018 at 12:37
  • 1
    @ivan_pozdeev: That surprised me too. So I took a small sampling of recent posts that have declined spam flags. It looks like we can blame flagger error not lack of information for all 10. Commented May 11, 2018 at 22:20
  • 1
    There's another benefit to custom mod flagging... The mods will always see it, even if the post is deleted. If the post gets deleted as something other than spam - say being VLQ - it may need to be spam deleted to actually trigger the spam penalties.
    – Catija
    Commented May 11, 2018 at 22:24
  • The "two types of spam" model sounds like a workable compromise. The flag note will need to be updated though. Commented May 11, 2018 at 23:52
  • Cases like this would be much easier to handle if we could include a comment on the spam flag. Most of the time, no mod has to be bothered with it, since if other community members also flag it as spam, it's gone. If it's subtle enough a mod has to be bothered with it, they'll see the comment. Commented Sep 9, 2021 at 16:32
  • @T.J.Crowder: Not sure what's wrong with a custom flag in this case. The end result is that a moderator would need to investigate and decide if a warning/suspension is in order. Spam flags are tuned for really obvious spam (fake handbags and such). Why make that flag less useful for the majority of cases when there's alternative tool already in place? Commented Sep 10, 2021 at 4:14
  • @JonEricson - In what way does an optional comment field make spam flags less useful? What's wrong with a custom flag is that it doesn't handle the spam automatically if other users also realize what it is, avoiding bothering the mods unnecessarily. Commented Sep 10, 2021 at 5:52

(Disclaimer: this post is obsolete now that @JonEricson updated his to address the issue.)

According to Spam flag declined on link from Founder & CTO, dozens of similar posts (10k needed to see the answer1) and @gparyani's comments in the same Q&A, a large portion of spam flags come from a source other than general SE users – as automated detections by the "SmokeDetector" software, allegedly double-checked by its volunteers. Naturally, they all come without evidence.

So the observed percentage doesn't reflect the UX of SE users, and @JonEricson's proof that these are "rare cases" is wrong.

Since no-one has access to the data, we cannot adjust the figures ourselves accordingly and (dis)prove anything with the results.

1Won't provide a screenshot: the author deleted the post shortly, so I suspect that they felt they disclosed too much. So it makes sense to limit exposure to 10k users who can see it anyway.

  • I could re-run the query with automated flags excluded, but it's unlikely to change the results much. Even if cases like the one you cited were more common now, it would still pay to use a "in need of moderator intervention" flag to explain the problem. In those more subtle cases, it's likely a moderator will need to contact the user anyway. Commented May 11, 2018 at 1:47
  • 1
    @JonEricson That wouldn't hurt in the least, especially if you mention what time period the data is for -- so one can get an idea if your upper bound of 5% and a few thousand posts is good or bad. I challenged your reasoning regardless of that though. Commented May 11, 2018 at 2:14
  • I'd say gparyani's MSO answer is a honest one. Furthermore, Charcoal is not some company. It's a voluntary organization that helps SE fight off spam. I changed your wording a bit to prevent it from diverting the meaning to the wrong side. Commented May 11, 2018 at 3:14
  • 2
    @ivan_pozdeev: I updated my answer. The new data suggests spam flags are more often rejected now than they were when I wrote that answer. (Smoky autoflags account for ~10k flag on SO.) I also added an argument that comments on spam flags are a bad idea even if this is a common problem. Commented May 11, 2018 at 6:26
  • 1
    I deleted the answer because other Charcoal participants wanted me to do so. (FYI I'm gparyani on Stack Overflow.) Commented May 13, 2018 at 22:15
  • @JonEricson It might be useful to re-run the query with only flags that were handled by moderators, excluding those that were automatically deleted upon receiving six flags from normal users. Commented Jul 5, 2018 at 3:20

You must log in to answer this question.

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