<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: &#8220;What happens in interaction between the parts is more important than the parts&#8221;</title>
	<atom:link href="http://www.jarche.com/2010/04/what-happens-in-interaction-between-the-parts-is-more-important-than-the-parts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jarche.com/2010/04/what-happens-in-interaction-between-the-parts-is-more-important-than-the-parts/</link>
	<description>Life in Perpetual Beta</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:59:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ben</title>
		<link>http://www.jarche.com/2010/04/what-happens-in-interaction-between-the-parts-is-more-important-than-the-parts/comment-page-1/#comment-198091</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Mon, 26 Apr 2010 13:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.jarche.com/?p=3876#comment-198091</guid>
		<description>If Twitter gains value by allowing people to include more content than can be contained by the 140-character limit, why are we accepting the 140-character limit to begin with?

If the constraint is good, why try to make an end-run around it? If it&#039;s not, why accept it to begin with?</description>
		<content:encoded><![CDATA[<p>If Twitter gains value by allowing people to include more content than can be contained by the 140-character limit, why are we accepting the 140-character limit to begin with?</p>
<p>If the constraint is good, why try to make an end-run around it? If it&#8217;s not, why accept it to begin with?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

