8

Right now, this flag appears to be generated whenever three questions in a row are closed. It's even a bit extreme - if a user asks 10 questions and the first three ever asked are closed, it appears to get generated even though the 7 more recent questions are not closed.

  1. The age of the questions should be considered. It should look at a rolling window of user questions for raising the automatic flag. I don't really care if the user's first three questions on the site were closed if there are a number of other good questions. Perhaps only consider questions asked in the last year or maybe 3 consecutive from the last (n > 3 questions, I'm thinking n = 5 or n = 6 would be good) get closed.

  2. Consider user activity. If the user isn't active on the site, I'm not going to do anything other than dismiss. There's no need to notify someone who doesn't participate any more about their poor participation. If the user hasn't been active in some period of time (3 months? 4 months? 6 months?), don't raise the flag.

  3. Some closure types aren't necessarily bad. Duplicate questions should not raise the flag, although perhaps a large number of duplicate closures should raise a different auto flag. Migrations (especially with all the SE sites - I can't even keep track of them sometimes) also shouldn't count toward a closure flag, although perhaps a large number of migrations should again trigger a different flag case. For example, a unique flag after 3 migrations or a unique flag after 3 duplicates would be acceptable, but this should be a different flag than 3 closures for what generally amounts to low-quality questions.

2
  • I will say that in at least one case it's been helpful on duplicates. We had a user who asked several questions in a row that were all duplicates showing a supreme lack of thought and research effort.
    – wax eagle
    Jul 17, 2013 at 14:55
  • 2
    @waxeagle The duplicates are helpful, but they may or may not be "low quality". It could be a matter of not knowing what to search for, and someone knowing closing it rightfully as a duplicate. That's why it should still exist, but as a separate "duplicate monitor" for people who ask too many duplicates (either the same question multiple times or for people who routinely don't search for other questions before asking). Jul 17, 2013 at 14:57

0

You must log in to answer this question.