<?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: Migration from Blogger to Wordpress</title>
	<atom:link href="http://rutsum.com/migration-from-blogger-to-wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://rutsum.com/migration-from-blogger-to-wordpress</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 01:12:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Apoorv Khatreja</title>
		<link>http://rutsum.com/migration-from-blogger-to-wordpress/comment-page-1#comment-95</link>
		<dc:creator>Apoorv Khatreja</dc:creator>
		<pubDate>Mon, 04 Feb 2008 12:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://rutsum.com/migration-from-blogger-to-wordpress/#comment-95</guid>
		<description>Yes, you CAN manually change your options to get Blogger style URLs. But what is the use of shifting to Wordpress if you don't use it's flexibility to the max?

I wanted my post page URLs to be free of any time stamp, and to be short. Thus, I chose the format http://rutsum.com/%postname%/. This enhaces the readability of a URL, and people get attracted by short and descriptive URLs.

Don't see any image problem. I had all my images hosted on my blogger (picasa) account, and all of them are working fine. Even the links open up to give full sized images. From now on, I would be using Flickr for image hosting. Never heard of the IP blocking thing you mentioned there.</description>
		<content:encoded><![CDATA[<p>Yes, you CAN manually change your options to get Blogger style URLs. But what is the use of shifting to Wordpress if you don&#8217;t use it&#8217;s flexibility to the max?</p>
<p>I wanted my post page URLs to be free of any time stamp, and to be short. Thus, I chose the format <a href="http://rutsum.com/%postname%/" rel="nofollow">http://rutsum.com/%postname%/</a>. This enhaces the readability of a URL, and people get attracted by short and descriptive URLs.</p>
<p>Don&#8217;t see any image problem. I had all my images hosted on my blogger (picasa) account, and all of them are working fine. Even the links open up to give full sized images. From now on, I would be using Flickr for image hosting. Never heard of the IP blocking thing you mentioned there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ankur Banerjee</title>
		<link>http://rutsum.com/migration-from-blogger-to-wordpress/comment-page-1#comment-94</link>
		<dc:creator>Ankur Banerjee</dc:creator>
		<pubDate>Sun, 03 Feb 2008 16:46:08 +0000</pubDate>
		<guid isPermaLink="false">http://rutsum.com/migration-from-blogger-to-wordpress/#comment-94</guid>
		<description>Er, you CAN enable 'Blogger-style' URLs in Wordpress, if I'm not wrong. Anyway, there's ONE more problem which you didn't mention - images. Images uploaded in Blogger aren't shifted by Wordpress. And since Blogger implements leech protection by limiting pic size being called from external sites to 200px, that's an issue. Plus, if too many queries start coming from a particular external IP address, then it blocks that too.

There's a neat way to get around this I've figured out, and I wanna try it out when I move to Wordpress; but frankly, now is not the time for me to play around, because if it DOES go wrong I'll be in deep shit (and I don't have time to recover from deep shit right now).</description>
		<content:encoded><![CDATA[<p>Er, you CAN enable &#8216;Blogger-style&#8217; URLs in Wordpress, if I&#8217;m not wrong. Anyway, there&#8217;s ONE more problem which you didn&#8217;t mention - images. Images uploaded in Blogger aren&#8217;t shifted by Wordpress. And since Blogger implements leech protection by limiting pic size being called from external sites to 200px, that&#8217;s an issue. Plus, if too many queries start coming from a particular external IP address, then it blocks that too.</p>
<p>There&#8217;s a neat way to get around this I&#8217;ve figured out, and I wanna try it out when I move to Wordpress; but frankly, now is not the time for me to play around, because if it DOES go wrong I&#8217;ll be in deep shit (and I don&#8217;t have time to recover from deep shit right now).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
