<?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: We  Cannot  Have Too Much Information</title>
	<atom:link href="http://blog.contextdiscovery.com/information-overload/we-cannot-have-too-much-information/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.contextdiscovery.com/information-overload/we-cannot-have-too-much-information/</link>
	<description>Context matters...to better understand information context is needed</description>
	<lastBuildDate>Fri, 13 Aug 2010 12:34:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: gerry</title>
		<link>http://blog.contextdiscovery.com/information-overload/we-cannot-have-too-much-information/comment-page-1/#comment-4149</link>
		<dc:creator>gerry</dc:creator>
		<pubDate>Fri, 13 Aug 2010 12:34:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.contextdiscovery.com/?p=97#comment-4149</guid>
		<description>Hi,

Interesting post. Makes absolute sense. I wondered if you have had similar thoughts in the context of social networks, such as Twitter, where information is streamed in real-time i.e. there is no retrieval per se but contextually based and rendered in a non-linear way such as a &quot;workspace&quot;? Typically, these linear streams are those that I choose to receive but, because timelines are rendered in a linear way, become increasingly difficult and tedious to manage. So, in the event of an increased rate of flow of information, organic or otherwise, there  is a directly proportional difficulty and frustration in managing it.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Interesting post. Makes absolute sense. I wondered if you have had similar thoughts in the context of social networks, such as Twitter, where information is streamed in real-time i.e. there is no retrieval per se but contextually based and rendered in a non-linear way such as a &#8220;workspace&#8221;? Typically, these linear streams are those that I choose to receive but, because timelines are rendered in a linear way, become increasingly difficult and tedious to manage. So, in the event of an increased rate of flow of information, organic or otherwise, there  is a directly proportional difficulty and frustration in managing it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

