13

There are three types of flags moderators get to deal with--standard flags (low quality, other), spam/offensive flags, and comment flags.

Within the moderator dashboard, we can see who has submitted a standard flag. However, we do not see who has submitted an offensive/spam flag nor a comment flag.

Is there a reason for this? If not, I'd like to be able to see the name of the user who has submitted a flag, no matter what type.


For those scoffers who scoffed at me:

http://i.stack.imgur.com/0RgBo.png

Now, how should I handle this situation? I could guess at who did this, but it would only be a guess. Scoffers suck.

35

George's concern - and my concern, raised in a couple of places, elsewhere over the years - are still valid... Seeing who raises a flag stands a good chance of prejudicing the moderator handling that flag, particularly in sensitive situations involving personality clashes.

This isn't a theoretical concern. It has happened, and in some cases it has caused problems to escalate far beyond what was necessary.

However... There is practical value in having this information in a great many cases, and I've come around to the belief that this value outweighs its cost.

  • For spam and offensive flags, that value primarily takes the form of avoiding abuse: these flags are useful, but very dangerous if abused.
  • For comment flags, the value is context: knowing how the flagger relates to the conversation is often helpful in understanding why their flag is valid.

Some examples of how this context can come into play with comment flags:

  • when a person deletes their half of a conversation and flags the other half as "no longer needed", this signals to the moderator that the conversation is concluded
  • when a comment is intended only as a temporary signal to an author ("thanks" / "I've edited your post"), knowing that the author has flagged the comment signals to the moderator that the comment has indeed served its purpose
  • when a comment intended to provide helpful guidance is flagged as rude by its recipient, this signals to the moderator that the comment fell on deaf ears, and is perhaps doing more harm than good
  • in the case of "in need of moderator intervention" flags, inexperienced flaggers occasionally assume that moderators are aware of their relationship to the thread, and write explanations that are difficult to interpret without that information.

Why this matters now

In the past, we've usually treated this as a training issue: moderators and flaggers can learn to better communicate with one another. However, it's become apparent that an awful lot of people don't even know that they can flag comments - this is a serious problem, as it leads to precisely the sort of escalation we'd like to avoid! To remedy this, we've made some minor UI tweaks last week, and now we're preparing to enable new users to flag comments on their own posts. Combined, these changes will open the door to a lot more flags from a lot more people: we're gonna have to make handling them easier.

Changes

As a first step toward accomplishing this, we've enabled flagger visibility and timestamps for all comment flags. The timestamp thing probably sounds pretty obscure, but... Along with the name of the flagger, we previously also obscured the time at which the flag was raised in much of the moderator UI: that made it unnecessarily difficult to determine when, for example, a flag on a comment followed an edit to the post. Combined, I'm hoping these two small changes partially compensate for the additional work that moderators will soon be faced with.

Cautions

Moderators, please do not use this information to discourage people from flagging comments, unless those flags are overtly frivolous or abusive. In particular, be wary of chiding flaggers for flagging comments that are part of an argument they are / were engaged in: even when such flags are petty, they're infinitely preferable to re-enagaging and escalating an unproductive argument!

As always, if you aren't sure that you can interpret flags fairly, leave them to another moderator to handle.

12

I fear that doing this might lead to, "Oh, so-and-so said it, so I can just tune him out." or "I don't like how he flags things, so if I see him flag something, I'll just ignore it or mark it 'unhelpful'".

It comes down to this:

The content of the flag is what matters, not who said it.

  • 7
    And why are standard flags not anonymous? – slhck Oct 19 '11 at 13:11
  • 1
    You'd have to ask @Jeff Atwood et. al., that. If it were me, all of those would be made anonymous to moderators, and there'd be an automated system that would not allow the bad spam/offensive flaggers to even flag something as spam/offensive unless their flag weight improved substantially in other areas. – George Stocker Oct 19 '11 at 13:16
  • 4
    As the worst, most hated moderator on all SE, I can assure you that moderators don't stoop as low as you suggest (I don't, therefore noone else will). I see it being used more to resolve issues with people revenge-flagging users for spam and never ending cycles of "rude/offensive (dismissed) rude/offensive (dismissed)" comment flags. – Won't Oct 19 '11 at 13:28
  • @Won'tಠ_ಠ It sounds like that should be an automated thing, if it happens that often. – George Stocker Oct 19 '11 at 13:47
  • 4
    Mod flags aren't anonymized because they say things like "please migrate to X, I'm the OP", or "I've gotten a lot of downvotes, can you check my account for suspicious activity" -- things where the mod needs to know who flagged it. I don't know why mods would need to see who spam flagged a post though – Michael Mrozek Oct 19 '11 at 14:12
  • @MichaelMrozek Perhaps so that we can take action if someone is abusing spam flags (which does happen). – Rand al'Thor Jul 27 '18 at 13:46

You must log in to answer this question.

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