6

The quality score on that post is 75 out of a possible 100. The threshold for sending it straight into review is 70. Yeah, that's pretty useless. We're working on a better one, based on some analysis of the available data. It ain't perfect either, but it would've flagged that one right out of the gate. The new system isn't quite ready to go live yet ...


5

6 days later, five different users have hit the code formatting check (including the author of this deleted question, who tried to post it 12 times before finally getting the formatting almost right). In addition, two questions have been caught by the code ratio check: This one was later posted as later posted as: https://softwareengineering.stackexchange....


5

Please don't. It's implementation at Stack Overflow causes all manner of side effects, including "pr0blem," "Halp," and "Knapsack Issue." In addition, unlike many other behaviors, this one isn't overridable by moderators, so it's forced on people unconditionally. SE seems especially enamored of this "fix," so if you get it here, you'll get it permanently, ...


5

It didn't break. It was a warning, not a block. Since I'm tired of clarifying this, it is now a block. Expect to observe this circumvented in titles of the form, "THE NeXT PALINDROME".


4

After analyzing the data, I'm not convinced raising the sensitivity of the current filters will do much good on Programmers: The "quality" checks were designed for sites like Stack Overflow which attract a lot of short, very poorly written questions. Of the examples you gave, only 1 would currently be blocked on Stack Overflow - and that's with the recently-...


2

Since all three questions you cited as examples were posted by the same person, and were all heavily downvoted and deleted, it's likely that this user is question-banned, and the problem has already solved itself. The quality filters are not a panacea. All they do is look for textual patterns that are highly predictive of question failure. In that sense, ...


1

A workaround worth considering is posting links to these questions to CV chat room: okay, I plan to post here all the 'problem' and 'help' questions that will be dropped at us from now on. If you spot such a question before me, I would appreciate if you drop it here. SE team and moderators want us, the community, to handle these? all right, let's do it ...


1

A possible approach: Detection While it would be practically impossible to identify all these, some should be relatively easy to identify, including known keywords around the edges ("hello" etc near the top, "bye", "thanks", poster's username or full name near the bottom) or some likely to be unnecessary (I'm not sure I've seen many paragraph starting with ...


1

We should tighten up the quality filter if there is evidence it would help. I'd like some clarification of what Shog9 said, but it sounded to me like the algorithm they have isn't very predictive for this site. As soon as gnat finishes tuning his bayesian filter and submits the patch to SO we should do it. (Just kidding about the filter. As far as I know)...


Only top voted, non community-wiki answers of a minimum length are eligible