Twitpocalypse is the name of the twitter bug that is similar to the Y2K bug. Every tweet sent out has a unique numeric identifier and this identifier is about to hit the signed integer limit which is 2,147,483,647. Some of third-party Twitter services are not designed to handle such a case and therefore the sequence will suddenly turn into negative numbers and those apps are likely to crash as a resultAccording to the countdown, the big bang was supposed to happen sometime tomorrow, but Twitter is forcing the failure to happen in the next couple of hours (21:00 GMT/2PM Pacific/5PM Eastern time today).
As of this writing, The unique identifier associated to each tweet has now exceeded 2,147,483,647 but there still yet no reports of massive failures (Current rate is 169 tweets per seconds)
Here is an update from the Twitter developer Doug Williams:
Just an update, there is a lot of coordination that it takes to pull something like this off. We need the operations team to watch the servers and application. The services team to work closely with the ops folks to ensure that any problems on our end are properly tracked and fixed. And Matt is running around coordinating the entire effort.
That said, the deadline may slip a bit as we work to ensure that we’ve covered our bases, and that the engineering team is ready to react to unforeseen problems.
Doing what we can to keep the tweets flowing.
Update: Twitterrific, TweetDeck and Destroy Twitter: 1st Victims of Twitpocalypse?
To stay up-to-date on Technology news, subscribe now.
0 comments:
Post a Comment