<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="0.92">
<channel>
	<title>Dryice Liu's Blog</title>
	<link>http://dryice.name/blog</link>
	<description></description>
	<lastBuildDate>Tue, 31 Aug 2010 12:01:11 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Google reader won&#8217;t follow 301</title>
		<description>Well I said some time ago that I use mod_redirect while migrating from pyblosxom to wordpress. It turns out not all the RSS readers are following a 301 redirct. At least for the one I'm using, Google Reader, won't do this. So now all my subscribers would think I no ...</description>
		<link>http://dryice.name/blog/wordpress/google-reader-wont-follow-301/</link>
			</item>
	<item>
		<title>Use Pretty Permalinks on Lighttpd</title>
		<description> Well on the WordPress site they said the Pretty Permalinks like
/category/title is only available on Apache. Well this is definitely
not true as long as you know your web server.

Here is how I made it with Lighttpd, and some tips to keep my original
rss link.

My original rss link is http://dryice.name/blog/index.rss. The ...</description>
		<link>http://dryice.name/blog/wordpress/use-pretty-permalinks-on-lighttpd/</link>
			</item>
	<item>
		<title>Migrating from pyblosxom to WordPress</title>
		<description>Well in times of switching blog system, one BIG challenge is to save all the old posts and comments. Fortunately (or not?) for me is that I didn't get too much comments before. So the only thing I need to worry about is the posts.

At first I found a perl ...</description>
		<link>http://dryice.name/blog/misc/migrating-from-pyblosxom-to-wordpress/</link>
			</item>
	<item>
		<title>Switched to WordPress</title>
		<description>Well this begins several days ago. When I tried to solve a challenge and I google around, and well, Google give me a result in my own blog. And it turns out that I've fixed the problem a year ago :)

So I decide to blog more, rather than one or ...</description>
		<link>http://dryice.name/blog/misc/switched-to-wordpress/</link>
			</item>
	<item>
		<title>fighting with spam</title>
		<description>There became more and more spam post on my blog, so I decide to fight with them.

There are several ways I can think off:

	personal verify. That is, I review every post and decide if it should go into my blog. Well I don't have time for this.
	Only registered user can ...</description>
		<link>http://dryice.name/blog/misc/fighting-with-spam/</link>
			</item>
	<item>
		<title>So it all begins</title>
		<description>After several hours work, I've got my muse+pyblosxom setuped. So now it's my start of my blog.

The first thing I'll need to do is to go through my planner pages and get the notes somewhat like a blog into this blog system.

I'll write most of my blog in English, as ...</description>
		<link>http://dryice.name/blog/misc/so-it-all-begins/</link>
			</item>
	<item>
		<title>export notes to pyblosxom</title>
		<description>well I decide to give this up.

The main reason is that muse-blosxom-new-entry makes the file name from blog title. I think it's a good idea. But that make me harder, if possible, to keep the planner notes sync with blog entries.

What's more, I might use different sub-set of muse features ...</description>
		<link>http://dryice.name/blog/emacs/planner/export-notes-to-pyblosxom/</link>
			</item>
	<item>
		<title>OK, I&#8217;ll go with the official hardcodedates.py</title>
		<description>And this will save some confusing about versions. I can give time 00:00 for notes without a note taken timestamp. Anyway this is what Michael give for blog files with only date in the timestamps file.

Share This
 </description>
		<link>http://dryice.name/blog/emacs/planner/ok-ill-go-with-the-official-hardcodedatespy/</link>
			</item>
	<item>
		<title>I can use unison to sync the comments</title>
		<description>unison can sync two directories, which are changing on both side. It updates that do not conflict are propagated automatically. Conflicting updates are detected and displayed.

This is perfet for the comments back and force of planner-pyblosxom: people can comment on the blog via web interface, and I can reply comments ...</description>
		<link>http://dryice.name/blog/emacs/planner/i-can-use-unison-to-sync-the-comments/</link>
			</item>
	<item>
		<title>new idea: planner-pyblosxom</title>
		<description>After playing with muse-blosxom.el, (emacs-wiki-)blosxom.el, remember-blosxom.el and pyblosxom, I found it's pretty wired that I'm writting everything in my planner page, while I'd have to write something again for my blog. Also that means I'd have to keep a seperate set of data, and it's not an easy work to ...</description>
		<link>http://dryice.name/blog/emacs/planner/new-idea-planner-pyblosxom/</link>
			</item>
</channel>
</rss>

