<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: the Washington Post talks to bloggers</title>
	<atom:link href="http://www.manifestdensity.net/2007/01/09/the-washington-post-talks-to-bloggers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.manifestdensity.net/2007/01/09/the-washington-post-talks-to-bloggers/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 13 Mar 2010 19:07:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: chrisafer</title>
		<link>http://www.manifestdensity.net/2007/01/09/the-washington-post-talks-to-bloggers/comment-page-1/#comment-280</link>
		<dc:creator>chrisafer</dc:creator>
		<pubDate>Wed, 10 Jan 2007 22:10:40 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1:8888/?p=91#comment-280</guid>
		<description>It seems I left before all the good stuff happened.  Three hours was a long time, though.
</description>
		<content:encoded><![CDATA[<p>It seems I left before all the good stuff happened.  Three hours was a long time, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kris</title>
		<link>http://www.manifestdensity.net/2007/01/09/the-washington-post-talks-to-bloggers/comment-page-1/#comment-279</link>
		<dc:creator>kris</dc:creator>
		<pubDate>Wed, 10 Jan 2007 15:25:04 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1:8888/?p=91#comment-279</guid>
		<description>My major concern coming out of last night&#039;s meeting is that there won&#039;t be adequate screening of sites up front (a full-time responsibility for anyone, as I&#039;m sure we can attest) and the blogroll will become crammed, overwhelming and basically useless.  I have seen it happen with multiple organizations and it ruins an otherwise well-intentioned endeavor.
</description>
		<content:encoded><![CDATA[<p>My major concern coming out of last night&#8217;s meeting is that there won&#8217;t be adequate screening of sites up front (a full-time responsibility for anyone, as I&#8217;m sure we can attest) and the blogroll will become crammed, overwhelming and basically useless.  I have seen it happen with multiple organizations and it ruins an otherwise well-intentioned endeavor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://www.manifestdensity.net/2007/01/09/the-washington-post-talks-to-bloggers/comment-page-1/#comment-278</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Wed, 10 Jan 2007 05:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1:8888/?p=91#comment-278</guid>
		<description>I think you&#039;re right about this when it comes to links.  But they&#039;re doing more than that -- on the front page of the directory they&#039;ll be featuring excerpts from recent posts.  That&#039;s what was in the mock-up, anyway.
</description>
		<content:encoded><![CDATA[<p>I think you&#8217;re right about this when it comes to links.  But they&#8217;re doing more than that &#8212; on the front page of the directory they&#8217;ll be featuring excerpts from recent posts.  That&#8217;s what was in the mock-up, anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://www.manifestdensity.net/2007/01/09/the-washington-post-talks-to-bloggers/comment-page-1/#comment-277</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Wed, 10 Jan 2007 05:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1:8888/?p=91#comment-277</guid>
		<description>At the risk of a stretched analogy, I liken the linking of blogs to the publishing of letters to the editor. You acknowledge a person and some of that person&#039;s information.
If one were to look up a &lt;i&gt;WaPo&lt;/i&gt; letter writer in the phone book, call that person, and end up berated with profanities, that was an exchange based on the decision to seek further contact (or in the case of blogs, to click through).
I&#039;m sure their lawyers can figure out how to say all this in a coherent way that would pass muster in any court and be as amenably OK-able as any Terms and Conditions.
</description>
		<content:encoded><![CDATA[<p>At the risk of a stretched analogy, I liken the linking of blogs to the publishing of letters to the editor. You acknowledge a person and some of that person&#8217;s information.<br />
If one were to look up a <i>WaPo</i> letter writer in the phone book, call that person, and end up berated with profanities, that was an exchange based on the decision to seek further contact (or in the case of blogs, to click through).<br />
I&#8217;m sure their lawyers can figure out how to say all this in a coherent way that would pass muster in any court and be as amenably OK-able as any Terms and Conditions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://www.manifestdensity.net/2007/01/09/the-washington-post-talks-to-bloggers/comment-page-1/#comment-276</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Wed, 10 Jan 2007 05:17:48 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1:8888/?p=91#comment-276</guid>
		<description>They acknowledged that issue, but didn&#039;t really explain how they were going to deal with it.  They said &quot;we want to automate this as much as possible&quot; (paraphrasing, of course).  So I don&#039;t know -- I would imagine that they&#039;ll filter out bad words, but I&#039;m not sure what they can do about libelous content and obscene photos unless they&#039;ve got a human editor checking everything.
</description>
		<content:encoded><![CDATA[<p>They acknowledged that issue, but didn&#8217;t really explain how they were going to deal with it.  They said &#8220;we want to automate this as much as possible&#8221; (paraphrasing, of course).  So I don&#8217;t know &#8212; I would imagine that they&#8217;ll filter out bad words, but I&#8217;m not sure what they can do about libelous content and obscene photos unless they&#8217;ve got a human editor checking everything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: makenzie</title>
		<link>http://www.manifestdensity.net/2007/01/09/the-washington-post-talks-to-bloggers/comment-page-1/#comment-275</link>
		<dc:creator>makenzie</dc:creator>
		<pubDate>Wed, 10 Jan 2007 03:33:32 +0000</pubDate>
		<guid isPermaLink="false">http://127.0.0.1:8888/?p=91#comment-275</guid>
		<description>Here&#039;s what I don&#039;t get -- how are they going to deal w/ &quot;not for public consumption&quot; blog entries?  i.e., bad words, racy pictures, super-inflamed opinions?  I just don&#039;t see how the freedom of expression allowed with blogs on all fronts jives with a public newspaper -- and its editoral restrictions.  Was that discussed at all?
</description>
		<content:encoded><![CDATA[<p>Here&#8217;s what I don&#8217;t get &#8212; how are they going to deal w/ &#8220;not for public consumption&#8221; blog entries?  i.e., bad words, racy pictures, super-inflamed opinions?  I just don&#8217;t see how the freedom of expression allowed with blogs on all fronts jives with a public newspaper &#8212; and its editoral restrictions.  Was that discussed at all?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
