... or even really how to fix it.  However, I do know what someone else broke.  As was pointed out earlier, people were having difficulties pinging my weblog posts with trackbacks.  Owing to the fact that the only defense I have against spam pings at the moment is a plugin that automatically junks a ping if it does not link to the appropriate post, I could not figure out what the problem was.  Well, unfortunately, that plugin does not actually stop the spam - my web server still receives it, it just files it appropriately.  Suffice it to say, the incoming spam reached epic proportions... or at least levels that started engaging ping throttling, and my webpage basically shut down. 

I have to admit, this is not exactly an ideal situation. 

As such, the TCode plugin has been re-initalized.  I realize this has caused problems for people in the past, but I think I have narrowed it down to this - you will (probably) always get a "Could not ping" error when you attempt to trackback ping one of my posts.  In all likelihood, however, the ping did get through, and is just awaiting my moderation.  Once moderated, it will show up.  If you are really concerned, give it a day or so, and if the trackback does not appear on my weblog, drop me a comment.  At least, this is all based on the experimentation I have done with trackbacking my own posts and stuff... your mileage may vary. 

I will try and install Movable Type 4 at the earliest opportunity (due to its supposedly improved spam-handling capabilities), but given my error-ridden, remarkably-buggy, and generally disastrous attempt earlier today with the Beta, I think I will wait until all of the kinks have been ironed out, and it is a solid package.  Until then...  my weblog has enough issues as it is, thank you kindly. 

Anywise, to make up for it, this post is another instance of open trackback goodness.  Enjoy!