Yes, sorry about that! I broke some things while setting up the new servers. (Kasumi, Ukyo and Shampoo arrived today.) I had to rearrange the way the servers identified each other, and Movable Type got fruitcaked for about an hour.

It should be completely fixed now; if you see it happen again, email me at andrew -at- pixymisa -dot- net. You might not be able to post or comment at all while it's happening.

This is an explanation of the fruitcake error I wrote a while back:

Basically, it's a this-should-never-happen code. When someone gets a 403 or a 500, it could be any of a dozen different problems. And it's hard to get people to report the exact details of what they were doing and what the error said.

But when the screen comes up with "fruitcake error", they have no trouble reporting that, and I know immediately what it means. There's also an "atomic wedgie" error that I set up. Like the fruitcake one, it only happens when things are seriously screwed.

I think I prefer fruitcake to atomic wedgies... at least I can use fruitcake as a doorstop.