<?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: Backup pricing model?</title>
	<atom:link href="http://www.rogue-development.com/blog2/2009/01/backup-pricing-model/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rogue-development.com/blog2/2009/01/backup-pricing-model/</link>
	<description>Comments and thoughts on technology from Marc Hughes</description>
	<lastBuildDate>Mon, 30 Aug 2010 16:55:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben Throop</title>
		<link>http://www.rogue-development.com/blog2/2009/01/backup-pricing-model/comment-page-1/#comment-548</link>
		<dc:creator>Ben Throop</dc:creator>
		<pubDate>Fri, 06 Feb 2009 02:54:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.rogue-development.com/blog2/?p=274#comment-548</guid>
		<description>Not far off from the market for data recovery service right there, but it takes out the uncertainty, the time, shipping, etc. Now, there&#039;s no upfront cost for data recovery services... ie, the part where you store people&#039;s stuff... so that puts the risk on you.

The &quot;holding the data hostage&quot; part is the first thing I thought of when you described it. Somehow it feels a little bit dirty. Plus, you&#039;d be setting yourself up for a bad situation when someone would want their data but couldn&#039;t afford it. Not a fun customer service email thread there. :)</description>
		<content:encoded><![CDATA[<p>Not far off from the market for data recovery service right there, but it takes out the uncertainty, the time, shipping, etc. Now, there&#8217;s no upfront cost for data recovery services&#8230; ie, the part where you store people&#8217;s stuff&#8230; so that puts the risk on you.</p>
<p>The &#8220;holding the data hostage&#8221; part is the first thing I thought of when you described it. Somehow it feels a little bit dirty. Plus, you&#8217;d be setting yourself up for a bad situation when someone would want their data but couldn&#8217;t afford it. Not a fun customer service email thread there. <img src='http://www.rogue-development.com/blog2/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
