<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Washington Post Still Not Getting It</title>
	<atom:link href="http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 09:08:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Leslie</title>
		<link>http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/#comment-38</link>
		<dc:creator>Leslie</dc:creator>
		<pubDate>Mon, 23 Jan 2006 20:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/#comment-38</guid>
		<description>Dan -- Thanks for the thoughtful commentary on the WaPo situation, which I referenced in my own blog post on the subject.  Just like the wikitorial problem at the LA Times last summer, this issue raises profound questions regarding the balance between editorial integrity and open dialog.  By closing down comments on the site all the Post did was shut down the conversation.  They missed an opportunity to turn critics into loyal readers.  Traditional media organizations need to realize that "the horse has left the barn".  This isn't just about editorial ... it's about survival.</description>
		<content:encoded><![CDATA[<p>Dan &#8212; Thanks for the thoughtful commentary on the WaPo situation, which I referenced in my own blog post on the subject.  Just like the wikitorial problem at the LA Times last summer, this issue raises profound questions regarding the balance between editorial integrity and open dialog.  By closing down comments on the site all the Post did was shut down the conversation.  They missed an opportunity to turn critics into loyal readers.  Traditional media organizations need to realize that &#8220;the horse has left the barn&#8221;.  This isn&#8217;t just about editorial &#8230; it&#8217;s about survival.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weblogsky</title>
		<link>http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/#comment-37</link>
		<dc:creator>Weblogsky</dc:creator>
		<pubDate>Mon, 23 Jan 2006 14:49:59 +0000</pubDate>
		<guid isPermaLink="false">http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/#comment-37</guid>
		<description>&lt;strong&gt;Dan Gillmor on Washington Post Comments...&lt;/strong&gt;

Dan Gillmor's been posting about the Washington Post's removal of comments capabiltiy from its blog. In his latest on the subject, Dan says that the Post failed to set up its comment system with sufficient due diligence. They allowed freeform......</description>
		<content:encoded><![CDATA[<p><strong>Dan Gillmor on Washington Post Comments&#8230;</strong></p>
<p>Dan Gillmor&#8217;s been posting about the Washington Post&#8217;s removal of comments capabiltiy from its blog. In his latest on the subject, Dan says that the Post failed to set up its comment system with sufficient due diligence. They allowed freeform&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jonl</title>
		<link>http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/#comment-36</link>
		<dc:creator>jonl</dc:creator>
		<pubDate>Mon, 23 Jan 2006 14:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/#comment-36</guid>
		<description>High volume comment sites, just like sites with forums, inevitably need some form of moderation or monitoring, but that need is mitigated somewhat by an authentication requirement. The need's still there, though, and often overlooked. My guess is that the Post didn't budget for comment moderation and didn't know where to find skilled moderators, so they backed off.  An authentication requirement and 8 hrs/day of moderation, along with a real commitment to interactivity, would solve their problem.</description>
		<content:encoded><![CDATA[<p>High volume comment sites, just like sites with forums, inevitably need some form of moderation or monitoring, but that need is mitigated somewhat by an authentication requirement. The need&#8217;s still there, though, and often overlooked. My guess is that the Post didn&#8217;t budget for comment moderation and didn&#8217;t know where to find skilled moderators, so they backed off.  An authentication requirement and 8 hrs/day of moderation, along with a real commitment to interactivity, would solve their problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig McGinty</title>
		<link>http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/#comment-35</link>
		<dc:creator>Craig McGinty</dc:creator>
		<pubDate>Mon, 23 Jan 2006 12:31:30 +0000</pubDate>
		<guid isPermaLink="false">http://citmedia.org/blog/2006/01/23/washington-post-still-not-getting-it/#comment-35</guid>
		<description>Would a newspaper be willing to print a letter which had no name or address?  Of course not.
So why be so slack in not asking people to leave some sort of reference to who they are?
It is as though the Washington Post didn't want comments to work so they could at least say 'well we tried, but look what happens'.</description>
		<content:encoded><![CDATA[<p>Would a newspaper be willing to print a letter which had no name or address?  Of course not.<br />
So why be so slack in not asking people to leave some sort of reference to who they are?<br />
It is as though the Washington Post didn&#8217;t want comments to work so they could at least say &#8216;well we tried, but look what happens&#8217;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
