I have a different take. The reason that I liked blosxom's filesystem based approach is that ultimately, I view my blog as a part of my personal information infrastructure. And I want to be able to take that infrastructure with me wherever I go (especially after today's Centrino launch). The biggest problem that I have with using a regular SQL database is the disconnected operation problem. The blog has to be up and running on the web all the time. But I want to be able to work on entries on an airplane or on the ferry, and I want an easy way of synchronizing the web version and my private version. I'd rather not write a database synchronization package. So at the moment, the use of the blosxom filesystem seems to be the best that I can do. But the nasty mtime sorting is really a pain.

Sam took me to task for the nasty way that I'm storing comments in my prototype comment system for pyblosxom. He's right of course, but that leads me to another nasty point. I'd like to store the comments as RSS items. But then it feels weird to me to be storing the articles themselves as text. Especially if there ends up being a blog API based on delivering RSS Items via HTTP or SOAP.

Joe Gregario posted the latest version of Pamphlet. I'm using Joe's wonderful Aggie as my aggregator, and I've been paying attention to what he's been doing with RESTLog.

My biggest gripes with pyblosxom as it is are:

• Comments are non-existent as are trackbacks and pingbacks (but I'm working on all of these)
• The UI for posting is bad (fixable via a CGI form)
• The UI for editing is bad (also fixable via CGI form)
• Can't support multiple categories
• No support for private entries