4

I flagged an answer on Assertion fails after using memcpy() as "not an answer" because I felt it should have been a comment. The answer had been posted by a 10k+ user, and shortly after I flagged it the flag status changed to "disputed".

I assume the answerer disputed the flag themselves; I think that 10k+ users should not be able to dispute flags on their own content.

(In truth I suspect my own answer would have been better as a comment as well, but I only thought of that once I'd posted it, and I couldn't see any way for me to convert my own answer to a comment!)

Improve this question
4
  • ...I couldn't see any way for me to convert my own answer to a comment. Delete or flag for deletion and repost as comment.
    – Time Traveling Bobby
    Sep 27, 2011 at 9:40
  • Are we talking about the two answers of Ernest? If yes, about which one? Both sound like valid answers to me, though, not the best...but the question isn't the best either.
    – Time Traveling Bobby
    Sep 27, 2011 at 9:42
  • 4
    What makes you think that the owner of the post was the one that disputed the flag? There are other 10ks that can see the flags too you know.
    – Jeff Mercado
    Sep 27, 2011 at 9:42
  • @Padded Cell: It was the earlier answer Ernest posted, about the order of parameters of memcpy().
    – Vicky
    Sep 27, 2011 at 9:46

1 Answer 1

Reset to default
18

10k users cannot see flags for their own posts. What happened is that other users who thought what posted as answer was really an answer voted your flag to be invalid.

Improve this answer
2
  • 1
    "10k users cannot see flags for their own posts." - OK, that answers the question. Thank you.
    – Vicky
    Sep 27, 2011 at 9:47
  • 4
    Actually, it was 3 other users (not the person who posted) who voted to disagree with the flag /cc @Vicky
    – Marc Gravell
    Sep 27, 2011 at 10:01

You must log in to answer this question.

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