As comfortable with Serendipity as I had become using it as my blog engine, there were still some things about it that I felt it lacked. The first little while, I had fun tweaking it just the way I liked, finding features it lacked and adding them by hand (pain-stakingly I might add, albeit enjoying it in a twisted sort of way). The more I used it, the more it seemed to lack, and the more tired it made me seem to feel, knowing I’d have to wait possibly months for someone to add a feature, or knowing I could add it myself if I just dedicated some time for it.

And therein laid the problem. I’ve got better things to do with my time than tinker with the backend of a blog engine, for a blog with a readership of maybe one person (two if I include my self).

I wanted to stick with all the features Serendipity already has, but wanted native cruft-free URLs, threaded categories, better administration, and better support. So after looking a some alternatives, I’ve decided to try out WordPress for a while. Importing my existing posts over to WordPress wasn’t impossible, but there was a slight problem. I used Serendipity’s export RSS feature, and imported the XML using WordPress’s Import RSS. However, all the entries had the tags HTML-encoded (i.e. <a href=”"> became &lt;a href=&quot;&quot;&gt;), which was obviously a pain. A couple hours later and all the entries were back to normal. There was probably a quick way to do it, but I’m a lazy programmer, so of course I grumbled through it the hard way.

Oh, and it looks like it lost the comments. I still have them in the database, so I can probably fabricate them somehow.

And of course, I plan on redesigning the look and feel of the site. Right now, it’s still using the default WordPress template.

Why the new domain name? It’s one I’ve had for a couple of years that I’ve been meaning to activate, so what better way than a new revision of my blog. Why wqoq, though? Rotate it 180° and you’ll see. Clever, ain’t it?

Anyway, we’ll see how this goes.