What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 150 Stack Exchange communities.

Currently, when users are putting a custom flag on a post, there is a chance that this flag will be dismissed before a moderator could see it.

For example, if it was a close flag, and the question got closed, all flags about the question are getting removed. Including custom ones. This was reported already earlier, from what I see in similar questions.

The same happens when someone wants to report a spam user, and writes a comment in the flag, about it. If enough people are flagging the post as the basic "it is spam", the answer will get auto-deleted, as well as the flag. This means that it's possible that the moderator will not even see such report of a spammer account, and it makes it harder to actually find them, after, and prevent them from posting new advertisements.

So the request is: is it possible to make it so that custom flags can only be dismissed by moderators?

This would prevent the loss of information that would be given by a user.

share|improve this question
Huh, I just kind of assumed these never got auto-dismissed – Ben Brocka Aug 9 '12 at 13:10
For those who don't know, Gnoupi has been a former SU mod and above issue was discussed and verified by other mods in the Root Access chat room. – Tom Wijsman Aug 9 '12 at 13:13
See also this question which was closed as duplicate of the other one. – kiamlaluno Aug 9 '12 at 13:26
Thanks for the duplicate, haven't found it earlier. Though seriously, how many times does it need to be reported, for someone from the SE team to actually answer something? @JeffAtwood, come back! – Gnoupi Aug 9 '12 at 13:27
The most annoying case of this I've ever seen was a user with only one question in a delete/undelete war. In some cases it is the right action though (e.g. you comment on an NAA saying "you should make this an edit to your question, not a answer" and flag saying "should be converted to edit") – Flexo Aug 9 '12 at 13:37
stackoverflow.com/posts/10930859/revisions is an example of this auto-dismissal behaviour being harmful. (Even without seeing the timing of flags there it's fairly easy to see what happened) – Flexo Aug 9 '12 at 14:14
@Flexo - now that's a nice trainwreck – Gnoupi Aug 9 '12 at 14:19
@Gnoupi Are you sure you want Jeff to come back? Remember, his standard response was [status-declined]... – Yannis Aug 9 '12 at 19:17
@YannisRizos - Actually, it was status-bydesign. But still, at least it was an answer. Let's try another way: JeffAtwood, JeffAtwood, JeffAtwood! – Gnoupi Aug 9 '12 at 21:09
current design obscures an information needed for moderators to evaluate issues with flagged posts, as discussed here - "According to the record, I declined that flag, but I never even saw it..." – gnat Nov 2 '12 at 7:47
@animuson: Did this just get fixed?? Agh. – Nathan Tuggy Oct 8 at 22:38
@NathanTuggy This has been fixed for years, the question just never got updated. Custom flags can never be dismissed by non-moderator action. – animuson Oct 8 at 22:39
@animuson: Good to hear. – Nathan Tuggy Oct 8 at 22:39

1 Answer 1

I support this.

Since the reason for the flag is customized by a human, it doesn't make sense for the flag to be dismissed by a machine, since only a human can determine the purpose of the flag and whether or not corrective action is needed.

share|improve this answer
While we are at it, I'd like for questions with multiple flags for me to decline specific flags and accept specific flags, since there are times that posts have contradictory flags. – George Stocker Aug 10 '12 at 3:34

You must log in to answer this question.

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