meta.stackexchange.com/questions/149869/…

Looking into this...

Also related: How to know which questions should be closed, a reprise and my somewhat-tangential (but just posted) Modernize the close vote aging logic

New users tend to like clicking things. A good way to teach them how to use the site is to put lots of things they can click in their way, and then explain what they just did after they've clicked. This guidance has to be automated though; we learned that lesson after the ill-fated "kill a support person button" incident.

That queue is considered the most urgent - edits often make the difference between a problematic post and a great one.

Eventually, @Mateo. BTW, this kicked in finally and should've cleaned up the backlog here.

That one had an upvote until the voter was deleted yesterday, and didn't get a downvote until a week ago, @bain.

No, because that post had a score of 1 until 8 days ago, @bain.

That'd be clever, but we're not doing that - we're just looking at the score. Or we would be looking at the score if these scripts were running at all

Ref: meta.stackoverflow.com/questions/258718/…

i.sstatic.net/Gb5rC.png - askubuntu.com/help/bounty - i.sstatic.net/kHTBp.png