Okay, point taken.
I did look at the URL, however, a 500 is still something to bring up. In any case, it needs to be fixed, and seeing as it's a cgi page on his site, there could be some deeper problem.
Besides, it's stopped throwing the 500 now.
I'm sorry for dragging this off topic. :)