So, I still hate HTML, and in particular I hate tidy for not even understanding xmlns. (Seriously! WTF, people?) And not, AFAICT, having any way to hook in something that will grok py:strip as a null container. But there’s the slightly-new layout.

I think I wrote that headline about 50 times before it was remotely close to even. I am very sloppy. And my markers suck. I was going to work on these exercises some but I think it may be a lost cause.

I was also going to put the diacritical mark on the ū, but I forgot. I need to dig through my books and website notes and finish the front page for this stupid domain name that explains what it means and why I somewhat arbitrarily chose not to transliterate it as “hu”. (Because I’m Irish and it makes more sense to me that way. Shut up.)

Also, here is something I was going to link yesterday (from Michael), but forgot: The Sarong Theorem Archive.

0.8 is up. I was going to fix a bunch of the docs and examples, because someone requested it, but then I found an actual bug so it seemed like a good idea to get it out now.

I need to write Last.fm docs too. Procrastinate, procrastinate.

Erich, I’ve been working on one for this blog. No persistent cache to speak of except for the files themselves when their sources haven’t been touched, and I haven’t found any reason to need XML, but I was trying to avoid much of the same nonsense you mention. As such, the templating is as dumb as possible. Perhaps you can do a lot more with XSLT, but I didn’t find it very interesting. Templating systems in general make me itchy.

I am now, however, thinking about making it easy to subclass that part of things as well, which could be interesting. Write something to talk to the big XML library, one import in layout, a few lines to save the cache in a pickle... hmm!

(I always stick a “raw-html” role into reST if I really need it for something, but generally, I try not to think about HTML period.)

I haven’t heard from anyone about it yet so I don’t know which X, Y, and Z are obviously lacking. :)

I decided to grab a large Maildir from my actual email and run it through Mnemosyne for shits and giggles. For 1184 messages: 1:49 to build from scratch, 0:14 to verify that nothing has been touched. No tags, just archives. (This wouldn't be a half-bad way to archive a mailing list, really...)

This is with reST off, though, because docutils likes to die “SEVERE”-ly if you just throw random garbage at it. However, the published result is cached (during each run), so that will only grow linearly.

In the common use case... this entry will hit nine pages (three of which are tags), and assuming stuff is actually filled up, index will cache everything that day and permalink need, year/month/tagindex don't use content at all, and the only really expensive thing will be republishing every old entry for each tag that it hits. I can live with that. And for all the recursion overhead, optimizing how much of the Maildir we really need to care about shouldn’t be very hard.

I just need some actual users to bitch at me about other stuff.

Okay, I’m putting this blog on Planet Debian... now. The old one is not gone yet, because I’m tired and I don’t think I’ll do it until tomorrow.

In a fit of hubris, I wrote some software to run this blog (which is just a bunch of generated static files), called Mnemosyne. I was bored of PyBlosxom and it was slow. I believe Erinn said something like, now it’s only a matter of time until I write my own RCS... If I get to that point I will really start worrying. If anyone is looking for something along these lines, please tell me what sucks and/or what is broken.

Anyway, rather than categorizing things (ugh), I’m just putting anything tagged “planet” in the feed that goes here. I think this will work better.

Oh, and I almost forgot: my blog now has automatic flooding-prevention. Nothing older than a day gets in this feed. I don’t know why feeds in general don’t have some sort of time limit.

Since this blog thing is kind of functional, let’s see how much fat I’ve been able to avoid. Lines of non comments/blanks/continued-docstrings:

433. Eh. I can do better. It’s still ugly. Hopefully getting it clean enough to not be embarrasing can involve removing some more code, and not adding too much. DRY. That’s the principle here.

There are more examples to add, of course. A good procmail recipe definitely. And my blog is slightly more complex than the example.

Update at the end of the next day-ish: 445. Lots of ugliness replaced. Wrote 120 more lines of README. Not bad.

I suppose now that this is reasonably dogfoodable I should think about what I want to do here. Okay. It’s pretty simple actually.

• Post more often
• Post less me
• Post more web

In a sort of tumblelog fashion (inspiration from Projectionist.) I tend to take these sort of things and put them in my away message and then when they’re gone, they’re gone.

More importantly I’ve got my LiveJournal again so all the diarying stuff can go there.

I’m posting from Mutt, and I spent a few hours making a hacky Vim plugin for ReST that makes entering links super easy. Notice all the links in that sentence? So. Who knows where this will go.

What a fabulous new weblog system.