So, Hasweb briefly disabled Movable Type over the weekend. They said mt.cgi was consuming too many resourced — I suspect they just took a snapshot of the system's CPU utilization during a rebuild for a new entry, making it seem like we were hogging the machine (we were, but only for five seconds or so once or twice a day). I convinced them to turn things back on, but they're keeping a watchful eye on us.

The thing is, mt.cgi isn't supposed to be cause these problems. The comment scripts can (as in Unfogged's case), but not mt.cgi itself. As far as I can tell this is just a combination of bad luck and some slightly inefficient templates.

So, just a word of warning: I'm likely to put up a Six Apart-approved template sometime today. It'll just be a stopgap — Catherine has come up with a good-looking design, but I want to add some bells and/or whistles, then it'll probably take me some time to turn it into HTML. So, something mediocre is forthcoming. But hey, it couldn't be as bad as the status quo, right?