<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel>
	<title>MetaFilter posts tagged with blogback</title>
	<link>http://www.metafilter.com/tags/blogback</link>
	<description>Posts tagged with 'blogback' at MetaFilter.</description>
	<pubDate>Thu, 20 Dec 2001 22:56:44 -0800</pubDate> <lastBuildDate>Thu, 20 Dec 2001 22:56:44 -0800</lastBuildDate>

	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>
	<item>
		<title></title>
		<link>http://www.metafilter.com/13292/</link>
		<description>&lt;a href="http://www.tecknik.net/blogback/"&gt;BlogBack&lt;/a&gt; RIP, November 16th. &lt;a href=&quot;http://www.snorland.com/&quot;&gt;SnorComments&lt;/a&gt;: RIP, about a week later, due to a massive migration of BlogBack&apos;s deserting rats. With the blogging community reaching critical mass, is it possible for a remotely-hosted comments service to survive the bandwidth bludgeoning?  </description>
		<guid isPermaLink="false">tag:metafilter.com,2001:site.13292</guid>
		<pubDate>Thu, 20 Dec 2001 22:56:44 -0800</pubDate>
		<category>blogback</category>
		<category>blogging</category>
		<category>blogs</category>
		<category>dotcom</category>
		<dc:creator>tweebiscuit</dc:creator>
	</item>
      
	</channel>
</rss>


