<?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: Blogger snafu: emergency migration to Wordpress</title>
	<atom:link href="http://blog.forret.com/2006/03/blogger-snafu-emergency-migration-to-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.forret.com/2006/03/blogger-snafu-emergency-migration-to-wordpress/</link>
	<description>and I mean it</description>
	<lastBuildDate>Wed, 18 Nov 2009 21:45:03 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: blog.forret.com &#187; Blog Archive &#187; Migration to Wordpress: me vs Murphy</title>
		<link>http://blog.forret.com/2006/03/blogger-snafu-emergency-migration-to-wordpress/comment-page-1/#comment-449</link>
		<dc:creator>blog.forret.com &#187; Blog Archive &#187; Migration to Wordpress: me vs Murphy</dc:creator>
		<pubDate>Tue, 21 Mar 2006 05:51:50 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2006/03/09/blogger-snafu-emergency-migration-to-wordpress/#comment-449</guid>
		<description>[...] PROLOGUE: WHY BOTHER? I have been blogging since 2004 and have built blog.forret.com up to Google Pagerank 6 and Technorati rank 8000. For the non-bloggers amongst you: it&#8217;s an ego thing. I don&#8217;t want to start again from a PageRank 0, Technorati rank &#8734;. So that&#8217;s why I didn&#8217;t stop until I got it back.  SAGA 1: Blogger -&gt; Bluehost I started blogging in Feb 2004 through Blogger. I published my blog through FTP, first on www.forret.com, then on a subdomain blog.forret.com (on a shared hosting account of mine). I had already started my migration towards Wordpress from the moment I saw Wordpresss 2.0 supported import from Blogger. I had taken an account with Bluehost, that I already use for my Argentine Tango &#8216;tangopedia&#8217; wiki, my dutch poetry blog, my podcast feed validator &#8230; The main domain name is smoothouse.com, with a (Wordpress) blog on www.smoothouse.com/blog. This would turn out to be a crucial detail. I had installed a new Wordpress on peter.smoothouse.com, done the import from my Blogger account (posts + comments - really neat!), and was playing around with themes and plugins to see what I wanted. Then Google/Blogger made the unfortunate decision to mark my blog as a spamblog and consequently mess up my whole blog setup. I was throughly pissed of (not having been warned, my template gone &#8230;), so I decided to give them the finger and switch immediately. I &#8216;just&#8217; needed to convert my peter.smoothouse.com blog into a blog.forret.com. Then I discovered that Bluehost has limits to what it can do on DNS subdomain hosting: [...]</description>
		<content:encoded><![CDATA[<p>[...] PROLOGUE: WHY BOTHER? I have been blogging since 2004 and have built blog.forret.com up to Google Pagerank 6 and Technorati rank 8000. For the non-bloggers amongst you: it&#8217;s an ego thing. I don&#8217;t want to start again from a PageRank 0, Technorati rank &infin;. So that&#8217;s why I didn&#8217;t stop until I got it back.  SAGA 1: Blogger -&gt; Bluehost I started blogging in Feb 2004 through Blogger. I published my blog through FTP, first on <a href="http://www.forret.com" rel="nofollow">http://www.forret.com</a>, then on a subdomain blog.forret.com (on a shared hosting account of mine). I had already started my migration towards Wordpress from the moment I saw Wordpresss 2.0 supported import from Blogger. I had taken an account with Bluehost, that I already use for my Argentine Tango &#8216;tangopedia&#8217; wiki, my dutch poetry blog, my podcast feed validator &#8230; The main domain name is smoothouse.com, with a (Wordpress) blog on <a href="http://www.smoothouse.com/blog" rel="nofollow">http://www.smoothouse.com/blog</a>. This would turn out to be a crucial detail. I had installed a new Wordpress on peter.smoothouse.com, done the import from my Blogger account (posts + comments &#8211; really neat!), and was playing around with themes and plugins to see what I wanted. Then Google/Blogger made the unfortunate decision to mark my blog as a spamblog and consequently mess up my whole blog setup. I was throughly pissed of (not having been warned, my template gone &#8230;), so I decided to give them the finger and switch immediately. I &#8216;just&#8217; needed to convert my peter.smoothouse.com blog into a blog.forret.com. Then I discovered that Bluehost has limits to what it can do on DNS subdomain hosting: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shoob Corporate Blogging (FR)</title>
		<link>http://blog.forret.com/2006/03/blogger-snafu-emergency-migration-to-wordpress/comment-page-1/#comment-419</link>
		<dc:creator>Shoob Corporate Blogging (FR)</dc:creator>
		<pubDate>Sat, 11 Mar 2006 18:03:18 +0000</pubDate>
		<guid isPermaLink="false">http://peter.smoothouse.com/2006/03/09/blogger-snafu-emergency-migration-to-wordpress/#comment-419</guid>
		<description>&lt;strong&gt;La lutte de Blogger contre les splogs semble surprenante...&lt;/strong&gt;

Peter Forret nous raconte ses derniers déboires avec blogger le service de blogging de Google. Il utilisait ce service pour héberger le contenu de son blog mais publiait ses pages sur un espace disque avec son propre nom de domaine.......</description>
		<content:encoded><![CDATA[<p><strong>La lutte de Blogger contre les splogs semble surprenante&#8230;</strong></p>
<p>Peter Forret nous raconte ses derniers déboires avec blogger le service de blogging de Google. Il utilisait ce service pour héberger le contenu de son blog mais publiait ses pages sur un espace disque avec son propre nom de domaine&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.466 seconds -->
