<?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: Moving to Movable Type</title>
	<atom:link href="http://pthree.org/2009/08/21/moving-to-movable-type/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2009/08/21/moving-to-movable-type/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Fri, 17 May 2013 20:46:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta2-24176</generator>
	<item>
		<title>By: Joseph Scott</title>
		<link>http://pthree.org/2009/08/21/moving-to-movable-type/#comment-110112</link>
		<dc:creator>Joseph Scott</dc:creator>
		<pubDate>Wed, 26 Aug 2009 05:41:19 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1117#comment-110112</guid>
		<description><![CDATA[As a point of reference WordPress.com uses an advanced cache plugin for memcached (makes for fewer DB queries) and the batcache plugin to cache the rendered HTML of pages in memcached (serves static content from memcached instead of a file).  Both of these work for regular WordPress.org powered blogs as well.

We do a fair bit of traffic ( http://www.quantcast.com/profile-search/wordpress.com ) and have found this to work pretty well.]]></description>
		<content:encoded><![CDATA[<p>As a point of reference WordPress.com uses an advanced cache plugin for memcached (makes for fewer DB queries) and the batcache plugin to cache the rendered HTML of pages in memcached (serves static content from memcached instead of a file).  Both of these work for regular WordPress.org powered blogs as well.</p>
<p>We do a fair bit of traffic ( <a href="http://www.quantcast.com/profile-search/wordpress.com" rel="nofollow">http://www.quantcast.com/profile-search/wordpress.com</a> ) and have found this to work pretty well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boredandblogging</title>
		<link>http://pthree.org/2009/08/21/moving-to-movable-type/#comment-110105</link>
		<dc:creator>boredandblogging</dc:creator>
		<pubDate>Sat, 22 Aug 2009 17:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1117#comment-110105</guid>
		<description><![CDATA[From my own experiences, MT is a better platform than WP. The only downsides I&#039;ve seen are a lack of plugins, decent themes, and a slight learning curve. 

Might be tedious for you, but it would be nice to see a good walk-through on the transition.]]></description>
		<content:encoded><![CDATA[<p>From my own experiences, MT is a better platform than WP. The only downsides I&#8217;ve seen are a lack of plugins, decent themes, and a slight learning curve. </p>
<p>Might be tedious for you, but it would be nice to see a good walk-through on the transition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Peddicord</title>
		<link>http://pthree.org/2009/08/21/moving-to-movable-type/#comment-110104</link>
		<dc:creator>Jacob Peddicord</dc:creator>
		<pubDate>Sat, 22 Aug 2009 14:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1117#comment-110104</guid>
		<description><![CDATA[Be sure to update your Atom template (atom.xml under Design &gt; Templates) to be reader friendly. By default, when you edit a post, MT will change the &quot;updated&quot; field while leaving the published field the same. This makes sense, but most feed readers will burp your posts (Planet included) when you update them and you&#039;ll end up spamming your feeds when you edit posts.

To remedy, find the relevant lines in atom.xml and change them to this:
http://pastebin.com/f4b77ce71

(Basically, just make the published and updated lines look the same.)

On all other levels MT is awesome; you&#039;ll enjoy it.]]></description>
		<content:encoded><![CDATA[<p>Be sure to update your Atom template (atom.xml under Design &gt; Templates) to be reader friendly. By default, when you edit a post, MT will change the &#8220;updated&#8221; field while leaving the published field the same. This makes sense, but most feed readers will burp your posts (Planet included) when you update them and you&#8217;ll end up spamming your feeds when you edit posts.</p>
<p>To remedy, find the relevant lines in atom.xml and change them to this:<br />
<a href="http://pastebin.com/f4b77ce71" rel="nofollow">http://pastebin.com/f4b77ce71</a></p>
<p>(Basically, just make the published and updated lines look the same.)</p>
<p>On all other levels MT is awesome; you&#8217;ll enjoy it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2009/08/21/moving-to-movable-type/#comment-110103</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Sat, 22 Aug 2009 14:08:42 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1117#comment-110103</guid>
		<description><![CDATA[@patrickdk When you get on the frontpage of Digg or Reddit, you&#039;re grateful that your database isn&#039;t getting slammed. Static HTML pages are so much faster, and much less overhead than DB queries in such a scenario.]]></description>
		<content:encoded><![CDATA[<p>@patrickdk When you get on the frontpage of Digg or Reddit, you&#8217;re grateful that your database isn&#8217;t getting slammed. Static HTML pages are so much faster, and much less overhead than DB queries in such a scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrickdk</title>
		<link>http://pthree.org/2009/08/21/moving-to-movable-type/#comment-110102</link>
		<dc:creator>patrickdk</dc:creator>
		<pubDate>Sat, 22 Aug 2009 14:06:46 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1117#comment-110102</guid>
		<description><![CDATA[I don&#039;t really agree with you. I see lots of my customers with flatfile scripts like yabbs and they run horribly slow. Mainly cause they store everything in one directory of thousands of files instead of hashing it out. The database screams so much faster and less load than them.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t really agree with you. I see lots of my customers with flatfile scripts like yabbs and they run horribly slow. Mainly cause they store everything in one directory of thousands of files instead of hashing it out. The database screams so much faster and less load than them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: foo</title>
		<link>http://pthree.org/2009/08/21/moving-to-movable-type/#comment-110101</link>
		<dc:creator>foo</dc:creator>
		<pubDate>Sat, 22 Aug 2009 11:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1117#comment-110101</guid>
		<description><![CDATA[Try ikiwiki instead!]]></description>
		<content:encoded><![CDATA[<p>Try ikiwiki instead!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Gündüz</title>
		<link>http://pthree.org/2009/08/21/moving-to-movable-type/#comment-110100</link>
		<dc:creator>Ali Gündüz</dc:creator>
		<pubDate>Sat, 22 Aug 2009 09:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1117#comment-110100</guid>
		<description><![CDATA[I didn&#039;t know Movable Type has gone free, so I was WTF&#039;ing for a minute there. :)]]></description>
		<content:encoded><![CDATA[<p>I didn&#8217;t know Movable Type has gone free, so I was WTF&#8217;ing for a minute there. <img src='http://pthree.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BUGabundo</title>
		<link>http://pthree.org/2009/08/21/moving-to-movable-type/#comment-110099</link>
		<dc:creator>BUGabundo</dc:creator>
		<pubDate>Sat, 22 Aug 2009 09:08:42 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1117#comment-110099</guid>
		<description><![CDATA[i&#039;ve become very fond on posterous.]]></description>
		<content:encoded><![CDATA[<p>i&#8217;ve become very fond on posterous.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
