News for hackers. Stuff that matters.
Re:Twitter’s poor API documentation practices by flyosity on Monday January 09, 2012 @05:16PM (#3444560)
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.

Thanks, Twitter!

Re:Twitter’s poor API documentation practices by polemic on Monday January 09, 2012 @06:16PM (#3444794)
Really? An expected response from a foreign (uncontrolled) source brought you servers down?

Are you validating responses now, or just assuming they'll never change / always be correct?

Re:Twitter’s poor API documentation practices by mattdeboard on Tuesday January 10, 2012 @04:09AM (#3446274)
"Well, we got a string instead of an integer and yada yada yada, our network almost collapsed."

That's a pretty big "yada yada yada" you left out. I am going to assume there's a legit reason why getting a string back instead of another type of reason crippled your servers, but I'd like to know what it was.

Re:Twitter’s poor API documentation practices by sutterbomb on Tuesday January 10, 2012 @12:18AM (#3445810)
Yup same issue bit me once too - sorting tweets by their RT count doesn't work well when the count is no longer an integer. (Fortunately I was only building a little app for myself to try to learn Ruby and Sinatra.)
Re:Twitter’s poor API documentation practices by azth on Monday January 09, 2012 @07:02PM (#3444959)
Hooray for type safety?
Re:Twitter’s poor API documentation practices by ac2u on Tuesday January 10, 2012 @06:25AM (#3446555)
Not alone in testing a heavy stream of tweets using "Bieber" then!