!blosxom
Originally this blog was a blosxom blog. I learned of blosxom through hobix, which also made me intensely fascinated by why and his subsequent disappearance.
Here’s why I liked blosxom, and eagerly installed it on lovecraft, my eee server:
- it’s perl
- I can use vim to edit my posts
- it doesn’t insist on rdbms bloatware (I’m looking at you, mysql)
- it’s hip. I guess.
Unfortunately, my experience was less than stellar. It started off great–the installation was easy and I was up and running within a few minutes. I made my first post with ease. I was still starting at a nineties-looking black-text-on-white-background ‘flavour,’ however, and decided to update it; unfortunately blosxom failed to ever find my flavour files and refused to change styles. I read and reread the docs on the blosxom website (which, I began to notice, has many broken links and some links that simply go to the wrong place) to no avail. I googled around; I found no information or documentation more recent than 2007. I finally logged onto #blosxom on freenode and asked there as politely and fully as possible; that was about 24hrs ago (Yes, I’ve been lurking) and I never received a response from the dozen or so lurkers in there.
I was worried that as I started to add stuff like comments and search that I would have a similar experience, so I made a wordpress blog for myself just like I did for my sweetheart.
And, jeez. WordPress is just awesome. I will gladly overlook the php and the mysql for all the eye candy ease-of-use goodness awesome it provides.
