I think Mike's answer misses the mark because people don't read instructions. The issue with adding a little phrase to the end of the existing text is that the people doing this regularly already have this behavior ingrained, and probably won't re-read the instructions. This means it will prevent the growth of these flags, but not solve the existing issue.
In an older version of the flagging system, flags were handled by two main queues. The diamond moderators, obviously, could see and act on flags at will; that's one of the main jobs of being a diamond moderator. However, users with sufficiently high (10,000) reputation could also see many sorts of flags, but had only a lesser ability to act on them.
When you select "Invalid flag" in the flag dialog, you are essentially invalidating a flag raised from another user, not raising a new flag. Then, as far as I recall from the last time I handled a disputed flag as moderator, moderators cannot mark as helpful a disputed flag; they can only dismiss it without giving a reason.
The "Invalid flag" option was ...
Figured it out. It happened only when the user hit the flags tab via the /tools route, since it was the last /tools tab he had open.
Fixed in next build that rolls out (before that happens you can simply work around by clicking visiting /tools/flagged). Watch for build rev 2014.1.9.1836 on meta and 2014.1.9.1287 on sites.
10K users can access this screen:
When clicking the marked button, we get:
That's what Shog meant. :)
Note that even 10K users doing this still have to wait until moderator handle the original flag, until then it will still be active like any other flag:
When the flag is handled, the status of both flags will be updated identically, based on ...
I had the same problem, and I have just found a solution!
The problem comes when you disable sending the referer header.
I have post Allow to flag as "invalid flag" without requiring referer header in order to fix this bug.
Meanwhile, you can enable referer header. On Firefox, just go to about:config and set
network.http.sendRefererHeader = 2
No, it is still there:
Do note the highly specific location of this option. You only get it in the 10K moderator tools page, Flags tab. Sounds to me like you are clicking the "flag" link under a plain post, available to anybody.
You feel this way because you think disputed means rejected. It does not. The three states are:
helpful. +1. Given to flags that moderators think are right.
declined. -1. Given to flags that moderators think are wrong.
disputed. 0. Given to all flags on a post that has an "invalid flags" flag, no matter whether any of the flags are right or wrong. See What ...
This is working as designed.
The flag resolution of "disputed" means that the flags were neither "helpful" nor "declined".
At the moment (November 2013) when we resolve a flag, all the flags have to be resolved the same way, so that if there are any incorrect flags we have to either reward the bad flag or punish the good flag. As it's more important to ...
This is a very good point. I've been tempted to flag eye-popping wrong answers as NAA's quite a few times. And the -1 reputation gives the impression of doing something bad, rather than spending points doing useful moderation.
I also like the ideas of the other answers, but the comments indicate a few problems. So, I suggest the following solution, that ...
Not impossible, per say. I believe there's still a bug where if a moderator agrees with the original flag and deletes the post, all the flags get dismissed as helpful (even though in that cade yours should be declined).
This all boils down to the fact that moderators cannot dismiss flags for different reasons. It's unfair to mark an "invalid flags " flag as ...
I encountered this message (i.e. "You don't have the permission to use this type of flag") today on Stack Overflow.
Apparently the cause was that, between the time I opened the flag dialog and selected the flag, a dupe-hammer was thrown on the question.