So I was going through the First Posts review queue, and got trapped by a "honey pot" post after voting up an answer. Oops, this is embarrassing! Or so I thought, until further inspection:

Robo-reviewer caught in the act?

This actually looks like a decent answer, right? The answer makes reference to an external link, but it quotes the relevant part. Looking at the revision history, it turns out this answer was edited three days after it was originally posted. The original answer appears to have been edited and then deleted; the post was then copied and posted as a new answer, where it received 4 up-votes and was accepted.

The problem is, the honey-pot trap showed the fixed-up version of the post. I'm sure this wasn't intended; evidently some wires got crossed somewhere in the process.

  • 6
    It's a good post, but not a great one; it's been fixed up by a code copypasta, but without any further explanation of how the code works. Nevertheless, your observation is correct; the audit should have shown you the revision that was deleted.
    – user102937
    Dec 5, 2012 at 4:08
  • 2
    You are not the first to mention this: meta.stackexchange.com/questions/157604/… Dec 11, 2012 at 9:20
  • Please don't use that tag on actual bugs, @gnat.
    – Shog9
    Aug 14, 2013 at 19:03

1 Answer 1


We have tweaked the audit tasks to include posts that are much worse than what you see here. We will continue to review these to make sure they are obviously good selections for audit tasks.

  • 5
    What about showing them as they existed, before the edit, at the time the flag was cast? The root problem is that we're showing a flag state based on a previous version... Dec 11, 2012 at 20:26
  • 3
    One small part of the tweaks made to audit tasks is the exclusion of posts that have an edit. Dec 11, 2012 at 21:18

You must log in to answer this question.

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