Washington Post Shuts Off Blog Comments Indefinitely

Washington Post Shuts Off Blog Comments Indefinitely

I'm sorry, but this is just a stupid move. Here we have a newspaper with lots of resources, an online department that's making money, and as soon as the trolls show up, they shut the door on comments. Why not just have someone do something journalistic like act like a gatekeeper. Yeah, that's it. It's a mix of reader submitted content and newspaper editorial control! Brilliant. Heh. Ok, maybe not. I do wonder why it's not being done, though. Or is that something they're considering during their down time?

Edit to add: Fixed the first link and also wanted to mention the great Q&A at PressThink... I guess it was the right thing to do for the moment. You have to have the people, though...

From WaPo:

As of 4:15 p.m. ET today, we have shut off comments on this blog indefinitely.

At its inception, the purpose of this blog was to open a dialogue about this site, the events of the day, the journalism of The Washington Post Company and other related issues. Among the things that we knew would be part of that discussion would be the news and opinion coming from the pages of The Washington Post and washingtonpost.com. We knew a lot of that discussion would be critical in nature. And we were fine with that. Great journalism companies need feedback from readers to stay sharp.

But there are things that we said we would not allow, including personal attacks, the use of profanity and hate speech. Because a significant number of folks who have posted in this blog have refused to follow any of those relatively simple rules, we've decided not to allow comments for the time being. It's a shame that it's come to this. Transparency and reasoned debate are crucial parts of the Web culture, and it's a disappointment to us that we have not been able to maintain a civil conversation, especially about issues that people feel strongly (and differently) about.

We're not giving up on the concept of having a healthy public dialogue with our readers, but this experience shows that we need to think more carefully about how we do it. Any thoughtful feedback on that (or any other issue) is welcome, and you can send it to executive.editor@washingtonpost.com.

Thanks,
Jim Brady
Executive Editor, washingtonpost.com

UPDATE, 7 p.m.: As you might expect, we're getting a ton of e-mail on this, and while I can't answer those e-mails individually, I'll address the two main points being made, that 1) we're afraid of being criticized and, 2) that were no personal attacks, profanity or hate speech in any of the comments.

On the first point, washingtonpost.com has done an awful lot to be as transparent as possible. We've started a ton of blogs, we've linked out to bloggers who are writing (often negatively) about Post content and we've made journalists from The Post and post.com available to answer questions online on a daily basis. So I find it hard to make a case that we're unwilling to be criticized. What we're not willing to do is allow the comments area to turn into a place where it's OK to unleash vicious, name-calling attacks on anyone, whether they are Post reporters, public figures or other commenters. And that's exactly what was happening. That leads into the second complaint. The reason that people were not routinely seeing the problematic posts I mentioned were that we were trying to remove them as fast as we could in order to preserve the reasoned arguments many others were making. We removed hundreds of these posts over the past few days, and it was becoming a significant burden on us to try and keep the comments area free of profanity and name-calling. So we eventually chose to turn off comments until we can come up with a better way to handle situations like this, where we have a significant amount of people who refuse to abide by the rules we set out.

Hmm. It seems like they were trying to remove them.

Significant burden, though? I mean, come on. Why not look into Amazon's Mechanical Turk to vet the comments before they go live?

To say it was a significant burden to moderate the comments seems a bit ridiculous to me.

Am I being too hard on them?

I mean, yes, it is work people. Online isn't easy. It needs resources too.

(On a side note, wasn't there one quarter last year where WaPo made more online than they did in print?)

Also related: NYT, CBS Public Eye and E&P





Yeah, but ...

think: The reason why they profited more from online than print (and, by the way, I don't remember the Post doing that, but I know the Wall Street Journal did) is precisely because of the same strategies that caught them short in this instance. That is, not too many people.
'Oh, it's just a computer, all you gotta do is...' not hire more than a couple geeks and put a newsroom-type in charge.
The Post's staff may be a bit more fleshed out than that, but I'm willing to bet they didn't exactly duplicate newsroom staffing in the online department.
And I'm a little surprised at you, here. You know how big papers tend to react, institutionally, to such things. The story behind this is that someone upstairs saw something and overreacted. Brady is doing his best, even if he is forced to follow a prescribed strategy (as impossible as it is) and knows he can't make everybody happy.
And, remember, the Post is a paper with national exposure, so it gets national buckshot in such an instance.

you're right, of course...

it was the WSJ. and i have nothing against Brady in it, i guess. there was a time i had to follow orders that didn't make sense all the time.

the solution, though, is manhours - journalisthours - paying people to moderate/edit. there's no easy way around it, imho.

outing mentioned, though, the possibility of people having to pay to comment? no, the companies should be paying journalists to sift...

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options