Twitter’s poor API documentation practices
Ha, this exact issue bit us in the ass a few months ago. We were working on some streaming Twitter utilities (put in a username and we fire off some events if a mention or a RT of them occurs) and just to test the scalability of our services we entered Justin Bieber. Well one of his tweets got over 100 RTs fairly quickly and we weren't expecting a string to come back. Long story short, it solidly fucked up our event queueing/processing pipeline and brought some of our servers to their knees.<p>Thanks, Twitter!