Twitter's own 'Y2K' problem
- May 19, 2009 10:37 AM |
- By John Bowman
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.
About the Authors
- Tara Kimura
is a multimedia producer for CBCNews.ca.
Categories
All News blogs
Most Commented
Most Recommended
Tech Bytes
Most Commented
Most Recommended
Recent Entries
- Universe hates Higgs boson, Chicago Cubs
- By John Bowman, CBCNews. A physicist working on the Large Hadron Collider doesn't think much of the theory that the universe is sabotaging the project to prevent the discovery of the Higgs boson. Might as well say that Nature hates... Continue reading this post
- Large Hadron Collider goes Back to the Future
- By Peter Evans, CBCNews.ca. Two respected physicists have put forward the theory that the Large Hadron Collider's stated aim of finding the Higgs boson might be so abhorrent to nature that mysterious forces are traveling back through time and sabotaging... Continue reading this post
- Multi-touch concept for desktops: 10/GUI
- By John Bowman, CBCNews.ca. I'm a fan of alternative ideas for human-computer interaction, so this video caught my attention. It shows an idea for a ten-finger touchpad interface and associated changes in the way a computer would handle multiple windows.... Continue reading this post
Comments (4)
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
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.
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.
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.