Twitter's own 'Y2K' problem
Tuesday, May 19, 2009 | 10:37 AM ET
By John Bowman, CBCNews.ca
Back on Blog Watch a few months ago, I wrote about how Unix computer systems tell time by counting the number of seconds since midnight on Jan. 1, 1970, and how in 2038, that number will no longer fit into a 32-bit integer.
Well, Twitter is going to be hitting that limit a lot sooner than that.
Each post on Twitter is given a unique identifying number and Twitter is running out. Once Twitterers create more than 2,147,483,647 posts, Twitter will start giving them negative ID numbers: -1, -2, -3. And third-party apps will likely crash as a result.
According to Twitpocalypse.com, Twitter is quickly approaching 1.85 billion tweets. Martin Dufort and Fred Brunel of WhereCloud, the Montreal developers behind the site, told the Montreal Gazette that Twitter could hit the 32-bit limit sometime in June.
WhereCloud set up Twitpocalypse.com as a marketing campaign for its iPhone app, Reportage, which is still awaiting approval by Apple.
« Previous Post |Main| Next Post »
This discussion is nowOpen. Submit your Comment.
« Previous Post |Main| Next Post »
Post a Comment
Tech Bytes »
Recent Posts
- Universe hates Higgs boson, Chicago Cubs
- Friday, October 23, 2009
- Large Hadron Collider goes Back to the Future
- Monday, October 19, 2009
- Multi-touch concept for desktops: 10/GUI
- Thursday, October 15, 2009
- Finland makes broadband a legal right
- Wednesday, October 14, 2009
- Google Maps goes it alone
- Tuesday, October 13, 2009
- Subscribe to Tech Bytes
Archives
- October 2009 (10)
- September 2009 (13)
- August 2009 (12)
- July 2009 (15)
- June 2009 (10)
- May 2009 (18)
- April 2009 (17)
- March 2009 (13)
- February 2009 (11)
- January 2009 (12)
- December 2008 (10)
- November 2008 (10)
- October 2008 (9)
- September 2008 (4)
- August 2008 (4)
- July 2008 (16)
- June 2008 (9)
- May 2008 (12)
- April 2008 (15)
- March 2008 (13)
- February 2008 (13)
- January 2008 (47)
- December 2007 (12)
- November 2007 (12)
- October 2007 (17)
- September 2007 (18)
- August 2007 (17)
- July 2007 (27)
- June 2007 (18)
- May 2007 (28)
- April 2007 (25)
- March 2007 (28)
- February 2007 (25)
- January 2007 (35)
- December 2006 (25)
_(720p).jpg)
 OFFICIAL HD MUSIC VIDEO.jpg)
.jpg)
Comments
Marc B
Saskatoon
Why is this such a big deal? If Twitter was originally built with a signed-32bit integer as their tweet primary key, then we can say at least one or more of the following:
a) Twitter never expected to get this big
b) The developers lacked the knowledge/foresight/intelligence to at least used an UNSIGNED integer as their primary key
c) The developers were too cheap to spend the extra 4 bytes of disk space per tweet to make the primary key 64bit
Posted May 19, 2009 06:08 PM
Franois Caron
Are you certain of that? It could be a 32 bit unsigned integer. Or if Twitter is running on a 64 bit operating system, the theoretical limit will be reached some 2 BILLION years from now, assuming the same rate of growth.
Posted May 19, 2009 06:53 PM
gukid
So you make one unique identifier for the user, and another for the post of that user, thus exponentially increasing the limit, it's easy. There are actually hundreds of different ways of dealing with this problem.
This, is just a publicity stunt. People will join, and post, to try and "crash" twitter, but it will never happen, and their user base will increase.
Posted May 25, 2009 02:58 PM
Chris Thomson
Twitter's not going to be setting status_ids to negative numbers. As Matt Sanford, a Twitter API developer, has said:
"There is no change to the format of responses and the number will continue to grow upward."
Some clients that cannot properly interpret 32-bit signed ints so large will have an issue with negative numbers.
Posted June 12, 2009 05:32 PM