Skip to content

Caliban – Opinion and Righteous Anger

Ian, Sarah, Eloïse and Lucas kick against the pricks.

Archive

Category: This Site

Two site updates in as many days. I’ve been busy.

I’m continuing to get to know WordPress, delving into the guts of the system to understand how widgets, themes and plug-ins work. The more I see, the more I’m impressed.

Sarah wasn’t wild about the new look. I liked it, but she’s probably more representative of the public at large, so I’ve heeded her advice and moved to something that’s less of a departure from the look of the old Movable Type site.

The link to allow subscriptions by e-mail, courtesy of FeedBurner, disappeared with the move to the new theme, so I’ve had to add some code to put it back. In any case, I don’t recommend you use it. FeedBurner updates are but daily, so you could be up to 24 hours behind a posting, if you’re unlucky. You should really be using the RSS feed instead. If you don’t know what that is, go to Google Reader and find out what a news aggregator can do for your browsing experience. I set up Sarah today on Google Reader and she’s quite impressed.

You’ll have noticed that things look a little different today. It was time for a change.

I’d been using Movable Type for many years; more than five, at least.

When I first started using it, it seemed flexible and powerful, but quite complex. For one thing, making changes to a MT-managed site required laborious and error-prone editing of intricate templates. Once one’s templates were edited in this way, upgrades of MT itself became an even more unattractive proposition, as one now had to port one’s changes to a new, probably incompatible set of templates.

This has effectively kept this site running the same version of Movable Type for many years. MT has moved on to version 5.0, but this site was stuck at 3.34, because I couldn’t steel myself to do the upgrade. Everything worked well enough and you know the old adage, right? If it ain’t broke, don’t fix it.

The trouble is that technology moves on. Not only was running an old version of Movable Type an ever greater security risk as new vulnerabilities were discovered, the Web itself had moved on and left this old version of MT for dead. Whereas everything these days works with AJAX, my Movable Type installation was still doing everything with CGI scripts, fifteen year old technology. That’s a lifetime in Internet years.

Another problem was with the Movable Type code itself. Occasionally, it proved necessary to delve into this, but it’s a mass of very complex Perl. I’m proficient in Perl, but it’s not the most legible of languages at the best of times. Where it goes really awry is when the programmer makes heavy use of Perl’s abortive attempt at OO (object orientation). Movable Type understandably, yet ultimately also lamentably, makes great use of this feature.

Aged technology isn’t necessarily bad per se, but in this case, it was bad. MT was designed to use CGI scripts to generate static pages. That worked well in an earlier, more innocent age, but on today’s Web, that approach generates high server load as comment spammers all over the world attempt to add their links for Viagra and Russian dating sites to your pages.

Now, I don’t know how modern the latest version of MT feels or which of these problems have been addressed in which way by the authors, but I didn’t really care to find out, either. Back when I started using Movable Type, it was very powerful and arguably the best of breed. Budding competitors were still busy playing catch-up.

That was more than half a decade ago and there are now some very mature alternatives available. They are also vastly easier to use; I really can’t emphasise how much easier. Tricky template editing has all but given way to drag-and-drop technology, with widgets like sidebar blogrolls and archived entry listings being a mere mouse gesture away from being added to a your blog and automatically configured. Wow.

As far as I’m concerned, the clear winner of the publishing platform/content management sweepstakes has got to be WordPress. I’m very impressed with the design of the system and the ease of use that stems from that well thought out design.

I’ve spent the day getting the new site ready. 95% of the work was accomplished within minutes. The remainder has been, as always, in the fine tuning: installing plug-ins, minor editing of templates, patching up botched data after importation, etc.

There are almost certainly still broken links, but I’ve taken care of the obvious stuff with some Apache mod_rewrite magic. WordPress actually contains a good deal of its own magic to make all kinds of strange links point to the canonical link for an item, so this wasn’t nearly as hard as it might have been.

The new site is really quite simple, but looks good, I think. I hope you agree.

The old site was too busy. Gone are the AdSense banners. Gone is the Last.fm Flash. I don’t want to see Flash in my daily browsing, so why should I make you?

Gone are all of the widgets with links to Amazon. Gone, too, is the obligatory list of links to other sites. In fact, gone, even, are the links to other areas of caliban.org, most of which were only of dwindling historic interest, anyway. One or two of them will find their way back home in the coming days, but I intend to keep the site free of pointless clutter.

Also consigned to the celestial bit bucket is the old mailing list for notification of new blog postings. Instead, there’s a field at the top right of the front page where you can subscribe to e-mail notifications via FeedBurner. A more modern way to stay abreast of updates is to subscribe to this site’s RSS feed in your favourite news aggregator. If you don’t yet have one, I suggest Google Reader as a place to start.

I hope the new look and feel will encourage me to post more regularly. Maybe Sarah can even be drawn out of the woodwork, although that’s probably hoping for a bit too much. She spends most of her time at the computer on Fa(e)ce(s)book, keeping up to date with subatomically trivial events in the life of people she once bumped into in a supermarket. That stuff makes my rants here seem Shakespearean in prosaic value and universal in relevance.

Well, it wouldn’t be me talking if I didn’t get a dig in somewhere, would it?

It has been brought to my attention that the Atom feed for this site was very poorly formatted. If you read my twaddle using this feed, you’ll be pleased to know that the problem has now been fixed.

I’ve also added an RSS 2.0 feed feed, should anyone prefer or need that.

Update: This site no longer uses Movable Type, so there’s a new URL for the RSS 2.0 feed. An Atom feed is no longer offered.

In the absence of female distraction, I took the opportunity in recent weeks to upgrade all of the machines in the house to Fedora 7, including the MythTV box.

A couple of years ago, with a few weeks still to go before the birth of Eloïse, I took advantage of the calm before the storm to move my domain to dedicated hosting at managed.com. Unfortunately, and as I’ve documented in the past, that company turned out to be less than dedicated, so after a year, caliban.org ended up back in our cellar, hosted over a domestic DSL line.

With the girls out of the country for a while, the time was ripe to move the domain back out to dedicated hosting. The DSL line has been incredibly reliable, but there’s always the chance that it will go on the blink while we’re travelling. Moving house would also automatically mean downtime, which is out of the question when one is responsible for one’s own domain e-mail. Downtime means lots of bounced e-mail, not to mention an unreachable Web site.

I’d done my homework before the girls left for their trip, so with the new contract signed, the slow process of copying all of our files over the slow upstream DSL link to the new server began. The process wouldn’t be completed until approximately ten days later.

As you read this, all services have been migrated to the new machine (and have been for over a week).

For you, the user, there shouldn’t be much noticeable difference, except that browsing our photo gallery should be considerably faster than before. For me, however, it’s nice to know that the continuity of our e-mail and Web site is no longer tied to our home DSL being up.

Some time ago, I turned off the ability of unauthenticated users to comment on entries made to this blog. Registered TypeKey users could still comment, but apparently it was too much trouble for a lot of people to register with this service. After all, who cares about being able to comment on what I say?

Well, in case you do care, I’ve now switched unauthenticated commenting back on and moved to a CAPTCHA-based scheme for distinguishing between human and automated users. If you want to comment on an entry now, you just have to answer a simple question with a one word answer and your comment will be accepted for publication.

Note, however, that if you are a registered TypeKey user, nothing changes. You can continue to post comments as an authenticated user without having to jump through any hoops.