Things should be working now. That was quite the interesting failure. Today's Site Journal entry has the details.

Thanks to Paul A. who brought the problem to my attention before it had a chance to get too far out of hand.