<?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"
	>
<channel>
	<title>Comments on: One reason why DRM has those pesky device limits: Not enough e-book lovers probably care YET</title>
	<atom:link href="http://www.teleread.org/blog/2008/05/25/one-reason-why-drm-has-those-pesky-device-limits-not-enough-e-book-lovers-care-yet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.org/blog/2008/05/25/one-reason-why-drm-has-those-pesky-device-limits-not-enough-e-book-lovers-care-yet/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<pubDate>Fri, 21 Nov 2008 08:18:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Christo</title>
		<link>http://www.teleread.org/blog/2008/05/25/one-reason-why-drm-has-those-pesky-device-limits-not-enough-e-book-lovers-care-yet/#comment-812425</link>
		<dc:creator>Christo</dc:creator>
		<pubDate>Mon, 26 May 2008 06:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/05/25/one-reason-why-drm-has-those-pesky-device-limits-not-enough-e-book-lovers-care-yet/#comment-812425</guid>
		<description>I often ran foul of Microsoft Reader's device limit, despite only ever having 1 PDA and 1 PC activated. The software kept deciding it needed to be reactivated. I don't know about Mobipocket, but anything that tries to detect a device uniquely is bound to fail and cause false lockouts, even if you are under their limits!</description>
		<content:encoded><![CDATA[<p>I often ran foul of Microsoft Reader&#8217;s device limit, despite only ever having 1 PDA and 1 PC activated. The software kept deciding it needed to be reactivated. I don&#8217;t know about Mobipocket, but anything that tries to detect a device uniquely is bound to fail and cause false lockouts, even if you are under their limits!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
