I'm working on something related to this right now, so it's worthwhile to pull the data. More on that in a bit, but first...
- 1380 questions asked here in the last 30 days, from
- 1219 distinct accounts, of which
- 1100 have/had accounts on Stack Overflow
- 184 of whom hit some kind of block on Stack Overflow during the past 60 days (this includes not just the quality-ban, but also spam blocks and 4 types of rate-limits).
From those 184 users...
- 227 questions were posted during the past 30 days.
- 152 were closed
- 135 were deleted
- 161 score < 0
- 62 received at least one answer
- 25 score > 0
- 771 questions were closed in total during the past 30 days,
- 636 were deleted,
- 728 score < 0,
- 523 were answered, and
- 323 score > 0
But... that's not the whole story. See, posting here in response to a block on Stack Overflow is a real desperation move - and there are less extreme tactics to try first. Like sockpuppets...
I grabbed the IP addresses associated with those 1380 posts and looked to see how many had been associated with blocked questions on Stack Overflow in the past 60 days. From those 255 IPs,
- 267 questions were posted here during the past 30 days,
- 168 of which were closed,
- 154 of which were deleted,
- 176 of which score < 0,
- 87 of which were answered, and
- 35 of which score > 0
Now, folks share IPs, and hop between networks. IP-based banning isn't a great long-term solution for anything... But if your goal is to slow down folks searching desperately for any text box into which they can type, then it ain't bad. Which is why we've been working on a system for temporarily classifying networks according to the number of bad posts coming from them. I took the currently-live data for this and compared it to the questions posted here during the past 2 days:
- 9 questions from potentially "bad" networks
- 4 of these closed
- 5 of these deleted
- 5 scoring < 0
- 2 answered
- 3 upvoted
Total stats for the same time period: 166,47,37,58,30,58.
Thus far, blocks on SO are a pretty weak predictor for quality. While there is a massive overlap between users on both sites, blocked users don't account for a very large chunk of the total here, and the false-positive rate is high.
Network-based tracking is even worse... But there's a caveat: we're only tracking networks with problematic posts on Stack Overflow right now, so all of those posts (and users) having issues on Programmers itself don't count. Right now, the network quality signal is used to feed Triage review on Stack Overflow... Potentially, turning on tracking for Programmers would allow it to do the same thing here, and save a considerable amount of time identifying these questions on both sites.