<?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: OLED nanotechnology displays</title>
	<atom:link href="http://www.foresight.org/nanodot/?feed=rss2&#038;p=1632" rel="self" type="application/rss+xml" />
	<link>http://www.foresight.org/nanodot/?p=1632</link>
	<description>examining transformative technology</description>
	<lastBuildDate>Wed, 03 Apr 2013 18:23:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Anonymous Coward</title>
		<link>http://www.foresight.org/nanodot/?p=1632#comment-4617</link>
		<dc:creator>Anonymous Coward</dc:creator>
		<pubDate>Wed, 27 Oct 2004 20:33:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=1632#comment-4617</guid>
		<description>&lt;p&gt;&lt;strong&gt;Re:Redunant!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I thoughts show true understanding of storage technology. Thank you&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p><strong>Re:Redunant!</strong></p>
<p>I thoughts show true understanding of storage technology. Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chemisor</title>
		<link>http://www.foresight.org/nanodot/?p=1632#comment-4616</link>
		<dc:creator>Chemisor</dc:creator>
		<pubDate>Mon, 25 Oct 2004 23:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=1632#comment-4616</guid>
		<description>&lt;p&gt;&lt;strong&gt;Redunant!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If you have 10 terabytes of space, it is easy to implement 3-way redunancy and have software periodically check all three copies for consistency, rewriting damaged portions to clean areas. If each copy is stored in a different area of the disk, the data thus encoded becomes nearly indestructible.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p><strong>Redunant!</strong></p>
<p>If you have 10 terabytes of space, it is easy to implement 3-way redunancy and have software periodically check all three copies for consistency, rewriting damaged portions to clean areas. If each copy is stored in a different area of the disk, the data thus encoded becomes nearly indestructible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Metzen</title>
		<link>http://www.foresight.org/nanodot/?p=1632#comment-4615</link>
		<dc:creator>Metzen</dc:creator>
		<pubDate>Mon, 25 Oct 2004 17:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=1632#comment-4615</guid>
		<description>&lt;p&gt;&lt;strong&gt;Fragile?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The linked story talks about a 1.8 inch disk that could hold 10 terabyts of information and is read optically. Could a small scratch result in 50 GB of data loss? At such high data density, even a speck of dust could pose problems that even parity error correction couldn&#039;t correct.&lt;br /&gt;
&lt;br /&gt;
It&#039;s fun to dream about nonetheless.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p><strong>Fragile?</strong></p>
<p>The linked story talks about a 1.8 inch disk that could hold 10 terabyts of information and is read optically. Could a small scratch result in 50 GB of data loss? At such high data density, even a speck of dust could pose problems that even parity error correction couldn&#39;t correct.</p>
<p>It&#39;s fun to dream about nonetheless.</p>
]]></content:encoded>
	</item>
</channel>
</rss>