I think that this topic really needs to be revisited and considered - even if it were only added for users with a higher privilege or certain flagging weight. That, or possibly the addition of a new flag-status such as no longer applicable
(instead of declined
).
Misreading a question or answer, misclicking buttons (odd, but I can't rule that out), or flagging a blatantly wrong answer as "not an answer" and 30 seconds after it's flagged the poster updates it to have just enough date to make it relevant - these are all things that happen way more often than not and there they all count against you (if they're marked as declined
).
To add a supporting question to your question - specifically regarding my last note, flagging a wrong answer (which is normally someone's attempt to be "first post", or someone who doesn't have the comment
privilege yet): Why on earth can't we revoke a flag on an answer if it's been updated after we've flagged it?
For example, just yesterday I flagged an answer that was very obviously a question asking the OP for more information. Flagged as "not an answer", as it should have been. About 2 minutes later, the answer was updated with another question, but had a small block of code in it that was relevant to the OP's question - but still didn't answer the question. I looked and my flag was still there and I had no way to remove it. As assumed, it was declined
. I followed the answer for this question and posted a second flag marked as other
with an explanation that the answer was edited after my flag - hoping the moderator would balance out my score and mark my second flag as helpful - it was declined
. So, now I have two decline
ed flags for the same answer =[
Again, I 100% agree that there needs to be more control over the flags that we post. I would be in support for the ability to revoke/delete a flag before it's been reviewed by a moderator, or even the logic to apply flag not applicable
if the question/answer has been updated since it was flagged.