Hey TweetTrak, I think you're down again... not getting any of my DMs

ack, found another place where i am connecting to twitter where i am not trying to catch any unexpected behavior.

Sadly, most of this code was written in a weekend and hasn't been put under heavy load. There are only two methods that actually need to connect, and i had only added the error handling code to one of them.

i am in the process of rewriting everything so that it is object oriented (nerd speak so that it is more elegantly designed to reduce code duplication and make it easier to find, fix, and prevent these sorts of problems).

TweetTrak now gives me useful error messages, and if it goes down again in the near future, it will be in a unique and unexpected way.

There was about 6 hours of downtime this time around. (I like to be honest and transparent about the project). Its working now and has sent out all of the delayed notifications.

Sorry for the trouble, but Thank You for reporting it!