<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: The future, cont&#8217;d</title>
	<atom:link href="http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/</link>
	<description>Same old blog, brand new place</description>
	<lastBuildDate>Fri, 04 Dec 2009 20:29:45 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Luis Villa&#8217;s Blog / one solution to the data permanence problem</title>
		<link>http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/comment-page-1/#comment-55</link>
		<dc:creator>Luis Villa&#8217;s Blog / one solution to the data permanence problem</dc:creator>
		<pubDate>Sun, 05 Aug 2007 17:28:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/docsearls/2007/08/03/the-future-contd/#comment-55</guid>
		<description>[...] you guarantee that your data is always available so that you can take it and go elsewhere with it? Doc Searls has one solution to the problem: Since I’m a Berkman fellow at Harvard, and the blogs here are well-supported, and they’ll [...]</description>
		<content:encoded><![CDATA[<p>[...] you guarantee that your data is always available so that you can take it and go elsewhere with it? Doc Searls has one solution to the problem: Since I’m a Berkman fellow at Harvard, and the blogs here are well-supported, and they’ll [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Thompson</title>
		<link>http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/comment-page-1/#comment-54</link>
		<dc:creator>Jim Thompson</dc:creator>
		<pubDate>Sun, 05 Aug 2007 13:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/docsearls/2007/08/03/the-future-contd/#comment-54</guid>
		<description>doc.searls.com now redirects here</description>
		<content:encoded><![CDATA[<p>nbsp;<a href="http://doc.searls.com" title="http://doc.searls. " target="_blank">doc.searls.com</a> now redirects here</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Leyden</title>
		<link>http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/comment-page-1/#comment-46</link>
		<dc:creator>Andrew Leyden</dc:creator>
		<pubDate>Sun, 05 Aug 2007 13:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/docsearls/2007/08/03/the-future-contd/#comment-46</guid>
		<description>Hi Doc,

I think it would be simple to have the old blog just read and post an RSS feed from the new blog.</description>
		<content:encoded><![CDATA[<p>Hi Doc,</p>
<p>I think it would be simple to have the old blog just read and post an RSS feed from the new blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sabadashus</title>
		<link>http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/comment-page-1/#comment-41</link>
		<dc:creator>sabadashus</dc:creator>
		<pubDate>Fri, 03 Aug 2007 23:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/docsearls/2007/08/03/the-future-contd/#comment-41</guid>
		<description>Nice demonstration of wisdom, tying in with Harvard. It&#039;s history, it&#039;s (some of) the future. Good move. 


saba-us</description>
		<content:encoded><![CDATA[<p>Nice demonstration of wisdom, tying in with Harvard. It&#8217;s history, it&#8217;s (some of) the future. Good move. </p>
<p>saba-us</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doc Searls</title>
		<link>http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/comment-page-1/#comment-37</link>
		<dc:creator>Doc Searls</dc:creator>
		<pubDate>Fri, 03 Aug 2007 16:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/docsearls/2007/08/03/the-future-contd/#comment-37</guid>
		<description>Thanks. That&#039;s high on the list of things I&#039;ll need to do when I get back on track after the current detour.</description>
		<content:encoded><![CDATA[<p>Thanks. That&#8217;s high on the list of things I&#8217;ll need to do when I get back on track after the current detour.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Winer</title>
		<link>http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/comment-page-1/#comment-35</link>
		<dc:creator>Dave Winer</dc:creator>
		<pubDate>Fri, 03 Aug 2007 11:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/docsearls/2007/08/03/the-future-contd/#comment-35</guid>
		<description>Doc, I&#039;d be surprised if the Berkman system people couldn&#039;t handle you mapping blog.searls.com or soemthing like that, to this blog.</description>
		<content:encoded><![CDATA[<p>Doc, I&#8217;d be surprised if the Berkman system people couldn&#8217;t handle you mapping&nbsp;<a href="http://blog.searls.com" title="http://blog.searls. " target="_blank">blog.searls.com</a> or soemthing like that, to this blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mic Edwards</title>
		<link>http://blogs.law.harvard.edu/doc/2007/08/03/the-future-contd/comment-page-1/#comment-34</link>
		<dc:creator>Mic Edwards</dc:creator>
		<pubDate>Fri, 03 Aug 2007 11:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/docsearls/2007/08/03/the-future-contd/#comment-34</guid>
		<description>My recommendation is that you use your own domain and turn off comments.

Whatever you choose, keep an archive your posts somewhere safe offline from your hosts.</description>
		<content:encoded><![CDATA[<p>My recommendation is that you use your own domain and turn off comments.</p>
<p>Whatever you choose, keep an archive your posts somewhere safe offline from your hosts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
