by Viper
13. June 2009 13:32
Last night twitter got hit by Twitpocalypse. What this means is that they made a bad decision about representing status id (aks tweet id) as signed INT. Last night they ran over that limit. This morning lot of applications were broken because of this change. All applications who were using signed INT for status id were getting overflow errors. For example in Tweetsharp in TwitterStatus object, there are two places where this status id is being used. Make sure that you change these properties to use "long" and not "int". This will fix the problem if you are running into conversion issues.
Subscribe