peteg's blog 2006-12-30-peteg.org.autumn

Shifting to peteg.org.

Finally got around to buying a domain: for three years from the nondescript Website Domains registrar. So far, so unimaginatively kosher. I availed myself of the freebie DNS provided by EveryDNS; they're somewhat limited in the kind of records they'll serve up, but more importantly are apparently reputable.

At the moment I've got Apache running on Debian on my dear old P120 at home, so it's all terribly slow. I feared the 64kbits uplink would sour the deal but Blosxom blindsided me by taking several tens of seconds to render the index pages. perl, gotta love it.

DNS Report has proven useful for linting all that stuff.

Root canal work on Blosxom.

I thought I'd try to tidy up a few things in Blosxom, such as the timestamps in comments, get the cookie memory-device going, that sort of thing. While the core and some plugins may be as-tidy-as-perl-can-be, the writeback (comments) one is pretty nasty.

I also tried to fix the formatting of the sidebar. Once again the lack of compositionality of HTML bit me on the arse: some things one can fix by twiddling some CSS in the flavour files, and others require a sift through the perl. To some extent it's a matter of code quality, but also there's the issue of what HTML objects are allowed with what combining forms. For example, the find plugin needs to return a form, so that'll be a div and not a span, thanks.

I guess my next trick will be some kind of functionalisation of my abbreviations plugin, so I can have some default text and also override it as needs be. Next Christmas, for sure.

The Joys of XHTML.

The theme I pinched for Blosxom claimed to use an XHTML DTD, and so idly I thought I'd try to make it conform. Yep, a complete waste of time. I naively imagined that XHTML has twenty-first-century tech but in fact everyone's been ignoring it since 1999.

Both Safari and Mozilla seem to deal with it OK. I have no idea if any of this works in Internet Explorer, sorry.

There's a semi-usable packaging of the W3's validator available here. For dynamic content I use curl to grab the page then feed it through as a file. Not very convenient but the less lazy can script it.

I find it ironic that the motivation for XHTML in the Wikipedia article is to make things more anal, purportedly for an efficiency payoff. To my eye it's just XML buzzword compliance, an opportunity to clean up the semantics of the beast squandered on syntactic busy-work.

My pet peeve is that the layout rules are so damn complex when something as semantically simple as a bunch of markup combinators could fix this mess. This tradition in CS goes back at least as far as Henderson's 1982 paper on functional geometry and continues with Lava and pretty printing and many other works. Then, instead of spending an hour finding out that one should lay out a line right-to-left (perhaps, maybe, this week at least), I could just say "title beside search box" and get exactly that!

Heck, this would even be better than CSS: define a bunch of named objects and some way to lay them out explicitly. Completely separate content and presentation, perhaps even a "declarative" layout! Somehow the fundamental notion of compositionality has been MIA here.

Andy's On-line Self-Help Call-for-Help.

The problem with a public blog is that is has to be interesting, or it languishes, as this one does, reader-less, apart from the odd Google misfire that sends people looking for the best seat in some Ticketek venue this way. At the end of the night it's hard not to verb the noun, not to non-sequitur. Others are voluble so that I may be taciturn. Andy, who apparently runs a plethora (or perhaps a cliché) of blogs, appears to be outsourcing the authorship of his self-help book.

Yes, I'm giving Blosxom a go.

Venerable NTK had a link to Blosxom back in ... well, let's just say it was many years ago. I remember being horrified by such a masochistic use of perl and instead tried to do something nice in Haskell, a project which has become too time-consuming to maintain. The models are very similar, entry-per-file, but Blosxom uses the file change date to decide where it belongs in the index.

(That last point is resolved by the entries_index plugin that caches the date when the CGI script first sees the entry... necessarily stepping away from the pure filesystem-as-database model.)

I must admit I didn't think perl could be written this readably.

Somewhat annoyingly there are several conflicts in worldview between CSE and Blosxom, the main one being blosxom's view that plugins should not be in URL-able webspace, versus CSE's wisdom of forcing all CGI-accessible things to live in public_html land... but not to worry.

Somewhat surprisingly for such an ancient instance of the blogging program genre there's an active user group. The plugins are groovy and I'm sure they're as insecure as all get-out. How long will it take to get a healthy dose of the blog-clap?

Things to fix:

Archives, get rid of list bullets.
Categories font.
Get images working.
Trackback / comments.

Hacks for the shift.

Showing how rusty my 37337 sh skills are, here's some things that help to migrate PLog entries to Blosxom:

Make PLog entries into Blosxom ones:
```
for file in *; do mv  .txt; done
```

... but before that, get blosxom's idea of the date for an entry to match PLog's:

for file in *; do echo  |
   touch -t `sed -n "1s/\(....\).\(..\).\(..\)/\1\2\30000/p;"` ;
done