<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The coming problem with the ASP-lock</title>
	<link>http://www.fredtrotter.com/2008/08/06/the-coming-problem-with-the-asp-lock/</link>
	<description>My life and thoughts, often about FOSS in medicine</description>
	<pubDate>Wed, 07 Jan 2009 11:08:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: jbartels</title>
		<link>http://www.fredtrotter.com/2008/08/06/the-coming-problem-with-the-asp-lock/#comment-1606</link>
		<dc:creator>jbartels</dc:creator>
		<pubDate>Wed, 06 Aug 2008 12:55:22 +0000</pubDate>
		<guid>http://www.fredtrotter.com/2008/08/06/the-coming-problem-with-the-asp-lock/#comment-1606</guid>
		<description>Fortunately, this isn't a new problem. It's coming up in a new context, but ever since the advent of free internet services that store something for you (email, files, forums, hosting...) the rule of thumb has been that you're getting something for nothing and therefore have no right to expect anything. Cover your own ass, do your own backups, and archive your content.

The problem then becomes "How do we store all this?". You've got to figure out how to extract your data (hopefully automatically, en masse, and regularly) from these services, store it, and then manage it as part of your normal backup process. Email and documents are a classic example, but how will GoogleHealth and HealthVault let you export your data?

As for the story, will something like strong authentication help resolve or prevent such lockouts?</description>
		<content:encoded><![CDATA[<p>Fortunately, this isn&#8217;t a new problem. It&#8217;s coming up in a new context, but ever since the advent of free internet services that store something for you (email, files, forums, hosting&#8230;) the rule of thumb has been that you&#8217;re getting something for nothing and therefore have no right to expect anything. Cover your own ass, do your own backups, and archive your content.</p>
<p>The problem then becomes &#8220;How do we store all this?&#8221;. You&#8217;ve got to figure out how to extract your data (hopefully automatically, en masse, and regularly) from these services, store it, and then manage it as part of your normal backup process. Email and documents are a classic example, but how will GoogleHealth and HealthVault let you export your data?</p>
<p>As for the story, will something like strong authentication help resolve or prevent such lockouts?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
