<?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: That Sound You Hear</title>
	<atom:link href="http://www.newsome.org/2007/04/that-sound-you-hear/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.newsome.org/2007/04/that-sound-you-hear/</link>
	<description>Kent Newsome on technology, music and life</description>
	<lastBuildDate>Sun, 05 Feb 2012 23:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ethan</title>
		<link>http://www.newsome.org/2007/04/that-sound-you-hear/comment-page-1/#comment-4017</link>
		<dc:creator>Ethan</dc:creator>
		<pubDate>Fri, 27 Apr 2007 03:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=3333#comment-4017</guid>
		<description>Hooray - an actual inline disclaimer! I hate it when people feel the need to disclaim something, and then bury it at the end of the post somewhere. Nobody asked me, but I believe disclaimers should immediately follow whatever needs to be disclaimed.Re: Point #4 that you expanded on, I&#039;m not seeing how Twitter makes for &quot;conversation&quot;. I haven&#039;t signed up and tried it on a smaller scale, but the Twitter site gives me the impression that it&#039;s a bunch of one-liners that don&#039;t necessarily equate to conversing. Though I am aware that people can mark their submissions as being directed at someone, such as a reply to an earlier one-liner.I dunno, it just strikes me as much more noise vs signal in a smaller package. From the outside looking in via your blog app.</description>
		<content:encoded><![CDATA[<p>Hooray &#8211; an actual inline disclaimer! I hate it when people feel the need to disclaim something, and then bury it at the end of the post somewhere. Nobody asked me, but I believe disclaimers should immediately follow whatever needs to be disclaimed.Re: Point #4 that you expanded on, I&#8217;m not seeing how Twitter makes for &#8220;conversation&#8221;. I haven&#8217;t signed up and tried it on a smaller scale, but the Twitter site gives me the impression that it&#8217;s a bunch of one-liners that don&#8217;t necessarily equate to conversing. Though I am aware that people can mark their submissions as being directed at someone, such as a reply to an earlier one-liner.I dunno, it just strikes me as much more noise vs signal in a smaller package. From the outside looking in via your blog app.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

