16

Is there a way to estimate amount of posts in queue that aren't eligible for vote expiration, that is have only flags?

I'd like to understand how many posts are guaranteed to eventually leave the queue due to votes being expired and how many are going to stay there for arbitrary long time, until someone casts a vote.

For the sake of completeness, it would be interesting to also estimate how many posts in queue have only migration flags, which are guaranteed to be "aged away" in 60 days.

Improve this question
4
  • To know how many will leave the queue we'd also need to know how many with votes have enough views for close vote aging
    – Richard Tingle
    Commented Nov 14, 2013 at 7:24
  • @RichardTingle I am rather interested to find out how many are guaranteed to stay there irrespectively of aging ("forever", until flag is dismissed by a vote)
    – gnat
    Commented Nov 14, 2013 at 7:28
  • upper estimate for posts eligible for vote expiration is count of questions that are open and have close vote(s). It isn't accurate though, since it contains posts pulled off the queue by Leave Open votes
    – gnat
    Commented Nov 15, 2013 at 7:02
  • 1
    @gnat I know this close vote queue size issue troubles you a lot. Maybe you'll find my question interesting?
    – Shai
    Commented Nov 20, 2013 at 15:54

1 Answer 1

Reset to default
11
+50

There are currently 12,533 review tasks in the close review queue that are there only because of flags. If we applied the same aging rules to these flags that we apply to close votes, 4,895 of them would age away today.

Of these, 207 are migration flags. For comparison purposes, there are 2285 tasks based on migration votes.

In total, 116,958 review tasks have been created in response to flags, and 48,651 such tasks have been completed (the remainder were made ineligible due to deletion, closing from outside the queue, aging, etc.)

For Matt: in the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed. Note that since more than one flag can be raised for a single post, these numbers do not correspond directly to either posts or review tasks (that is, they're not directly comparable to the numbers above).

Improve this answer
5
  • 1
    Have you got any figures on how accurate the flags are? I.e how many of them result in the question actually being closed?
    – Matt
    Commented Nov 21, 2013 at 22:24
  • 2
    See edit, @Matt
    – Shog9
    Commented Nov 21, 2013 at 22:30
  • 4
    Interesting... pretty accurate flagging from the < 3000 rep people.
    – Matt
    Commented Nov 21, 2013 at 22:54
  • I suspect that those people who are most interested in flagging questions for closure are the ones more likely to give a crap about how things work out @Matt. Therefore, they are (probably) more likely to get it right... Anecdotally I don't notice that as much on low quality flags but closure isn't as much of a surprise.
    – ben is uǝq backwards
    Commented Nov 21, 2013 at 23:44
  • @Shog9 - In your Regarding the SOCVQ post you mention that there are 11K items left in the queue of the original 57K. I guess they must all have <100 views. Can you say how many of those have >1 vote? (There's so much discussion on this it's hard to find the data.) I'm thinking of proposing that the <100-view long tail items be closed by default after some time or views, and go in the reopen queue instead, rather than just dropping out after 100 views.
    – martin clayton
    Commented Dec 7, 2013 at 13:33

You must log in to answer this question.

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