Return to Answer

##Improve communication between flaggers and moderators, or, "what's obsolete about that?"##

Some sites are very chatty. And that means flags on comments. My biggest moderation time sink is comment flags, and, within that, obsolete flags. I don't know why it's obsolete -- was the post edited? Was the comment it replied to removed? Or is it not obsolete, but the guy arguing with that other guy is trying to remove comments he doesn't like?

Can we add more information to "no longer needed" flags? requests a little bit of tooling that would help flaggers tell moderators what the problem is, so we can handle the flags efficiently. We all have better things to do than to read through 20 comments and 6 revisions to figure out what the history is.

On one of my sites we've asked our users to mostly stop using the obsolete flag and use custom flags instead, but this only works for people who've seen the meta post and remember. Also, it means we're giving the opposite advice for comments ("please use custom flags if you have any doubts") as for posts ("please don't use custom flags if the built-in ones apply"). That's confusing for users who aren't SE fanatics keeping up on every detail ("wait, am I supposed to use 'other' or avoid it here?").

##Improve communication between flaggers and moderators, or, "what's obsolete about that?"##

Some sites are very chatty. And that means flags on comments. My biggest moderation time sink is comment flags, and, within that, obsolete flags. I don't know why it's obsolete -- was the post edited? Was the comment it replied to removed? Or is it not obsolete, but the guy arguing with that other guy is trying to remove comments he doesn't like?

Can we add more information to "no longer needed" flags? requests a little bit of tooling that would help flaggers tell moderators what the problem is, so we can handle the flags efficiently. We all have better things to do than to read through 20 comments and 6 revisions to figure out what the history is.

On one of my sites we've asked our users to mostly stop using the obsolete flag and use custom flags instead, but this only works for people who've seen the meta post and remember. Also, it means we're giving the opposite advice for comments ("please use custom flags if you have any doubts") as for posts ("please don't use custom flags if the built-in ones apply"). That's confusing for users who aren't SE fanatics keeping up on every detail ("wait, am I supposed to use 'other' or avoid it here?").

##Improve communication between flaggers and moderators, or, "what's obsolete about that?"##

Some sites are very chatty. And that means flags on comments. My biggest moderation time sink is comment flags, and, within that, obsolete flags. I don't know why it's obsolete -- was the post edited? Was the comment it replied to removed? Or is it not obsolete, but the guy arguing with that other guy is trying to remove comments he doesn't like?

Can we add more information to "no longer needed" flags? requests a little bit of tooling that would help flaggers tell moderators what the problem is, so we can handle the flags efficiently. We all have better things to do than to read through 20 comments and 6 revisions to figure out what the history is.

##Improve communication between flaggers and moderators, or, "what's obsolete about that?"##

Some sites are very chatty. And that means flags on comments. My biggest moderation time sink is comment flags, and, within that, obsolete flags. I don't know why it's obsolete -- was the post edited? Was the comment it replied to removed? Or is it not obsolete, but the guy arguing with that other guy is trying to remove comments he doesn't like?

Can we add more information to "no longer needed" flags? requests a little bit of tooling that would help flaggers tell moderators what the problem is, so we can handle the flags efficiently. We all have better things to do than to read through 20 comments and 6 revisions to figure out what the history is.

On one of my sites we've asked our users to mostly stop using the obsolete flag and use custom flags instead, but this only works for people who've seen the meta post and remember. Also, it means we're giving the opposite advice for comments ("please use custom flags if you have any doubts") as for posts ("please don't use custom flags if the built-in ones apply"). That's confusing for users who aren't SE fanatics keeping up on every detail ("wait, am I supposed to use 'other' or avoid it here?").

##Improve communication between flaggers and moderators, or, "what's obsolete about that?"##

Some sites are very chatty. And that means flags on comments. AMy biggest moderation time sink is comment flags, and, within that, obsolete flags. I don't know why it's obsolete -- was the post edited? Was the comment it replied to removed? Or is it not obsolete, but the guy arguing with that other guy is trying to remove comments he doesn't like?

Can we add more information to "no longer needed" flags? requests a little bit of tooling that would help flaggers tell moderators what the problem is, so we can handle the flags efficiently. We all have better things to do than to read through 20 comments and 6 revisions to figure out what the history is.

##Improve communication between flaggers and moderators, or, "what's obsolete about that?"##

Some sites are very chatty. And that means flags on comments. My biggest moderation time sink is comment flags, and, within that, obsolete flags. I don't know why it's obsolete -- was the post edited? Was the comment it replied to removed? Or is it not obsolete, but the guy arguing with that other guy is trying to remove comments he doesn't like?

Can we add more information to "no longer needed" flags? requests a little bit of tooling that would help flaggers tell moderators what the problem is, so we can handle the flags efficiently. We all have better things to do than to read through 20 comments and 6 revisions to figure out what the history is.