inquisitrlogo

 
The day Twitter clients go KABOOM!


NuclearBomb

You might not know this but June 12, 2009 is the day that a lot of the Twitter clients we use stand a very good chance of – for the lack of better words – going kabooie. This is according to the team at Wherecloud a mobile solutions company out of Canada.

This Twitpocalypse, as they call it, will happen because the unique identifier (a signed integer) associated with each tweet will exceed 2,147,483,647 which is the limit of signed integers. At this point many of the third party clients for Twitter could either malfunction or crash if they are not coded to handle this problem.

While Wherecloud suggests this date is only an approximation because of the estimation of the calculated number of tweets per second they jokingly suggest not to plan your vacation around that time.

All jokes aside if this is even close to being correct can you just image the number of people going off the deep end if it does happen. What will Aston Kutcher do then I wonder?

collapse











Comments


One Archived Response to “ The day Twitter clients go KABOOM! ”

  1. MySQL’s BIGINT upper limit tops out at 18,446,744,073,709,551,615. To put that value into perspective, every single one of the 6.8 billion people on Earth would have to post 2.7 billion tweets each to reach this limit. So, now I have a goal :)