News for hackers. Stuff that matters.
Re:Why is printing “B” dramatically slower than printing “#”? by sanderjd on Monday February 24, 2014 @08:44PM (#7294659)
Your analogy is bad because it would be very hard to ignore Rodney Dangerfield in your bedroom, but it is very easy to ignore these sorts of questions. At worst it sits there and nobody comes up with an answer. We aren't running out of bits.
Re:Why is printing “B” dramatically slower than printing “#”? by MaulingMonkey on Tuesday February 25, 2014 @12:04AM (#7295735)
It's easy to ignore singular questions like this. It's harder to ignore such questions when they compose 99% of the content source you're interested in, without ignoring the entire source - including the 1% of signal you care about. We are certainly running out of mental bandwidth all the time, even if you aren't counting them as bits.

This sort of community moderation exists in an attempt to proactively ensure a high signal to noise ratio (SNR), by discouraging noise. While it's an entirely valid stance to say they're overreacting and that the ratio is fine, that there's no slippery slope, etc., here's another viewpoint:

I don't read from the raw Stack Overflow firehose of posts. It doesn't even have a 1% SNR to me. Higher SNR sources (searches, specific links from my communities) will occasionally take me there, but as a primary source of information I don't even think of consulting it. I took a stab at participating in one of the far more niche subtopics - gamedev, relevant to me both professionally and unprofessionally - and still found it didn't have a high enough SNR to hold my interest beyond gathering a few hundred internet points. I found myself ignoring the majority of these sorts of questions, and quickly progressed to the natural conclusion of ignoring the site entirely.

And that's fine: Not everything is for everyone. But there are presumably those who still participate in the site directly who would prefer to remain doing so, yet find the SNR low enough to be pushing their own tolerances.

Re:Why is printing “B” dramatically slower than printing “#”? by sanderjd on Tuesday February 25, 2014 @11:29AM (#7298534)
Thanks, this is a great response. I see the problem now. The SNR is plenty high enough for my use case of searching for content and following links, but to ensure that a high number of the links that I follow have good answers, it's important to keep the SNR reasonably high for those who are looking through the firehose for things to answer. Makes sense.
Re:Why is printing “B” dramatically slower than printing “#”? by euank on Monday February 24, 2014 @10:25PM (#7295202)
We aren't "running out of bits", but we have a highly limited amount of time and screen real-estate.

The reason it was marked as such was so that other people didn't waste time on an unreproducible problem until it was fixed to be reproducible.

At worst, it sits there and wastes many people's time, thus getting in the way of actually reproducible questions getting seen and answered.

Note, that this is not regarding this one question, but thousands - certainly there are a large number of items selected for moderator action.

Re:Why is printing “B” dramatically slower than printing “#”? by jules on Tuesday February 25, 2014 @08:19AM (#7297403)
And yet...the answer was found without this "required information".
Re:Why is printing “B” dramatically slower than printing “#”? by dionidium on Monday February 24, 2014 @09:54PM (#7295042)
Real-world analogies don't always work on virtual problems, even when they seem to on the surface. Unfortunately, this seems to be the standard way to respond [0].

[0] https://news.ycombinator.com/item?id=4273324