Latest in Coding

Image credit:

Beware the coming Twitpocalypse


Oh, computers. Every time we think we've figured you out, you come up with another number-related disaster for us to fear. This time around, it's the Twitpocalypse -- apparently Twitter decided to use a unique identifier in their API for each separate tweet that goes out, and come sometime this weekend, the number will reach 2,147,483,647 and keep going. Which just happens to be too much for the variable that holds it, and that means that many of your favorite external Twitter clients, from Tweetie to Twitterific, to all of the other magic Twitter apps out there, could go down in a ball of numerically-ignited flame.

The good news is that just like the Year 2K panic, this one is more or less unfounded. We've already spoken to our friend Ged Maheux of Twitterrific, and he says that the problem has already been fixed in the latest version of the software. We'd imagine that most of the really big Twitter apps have already addressed the issue, and taken care to make sure they'll still work (either that, or they'll get on it ASAP). Plus, a Twitter outage wouldn't really be anything that might cause riots in the streets (or different from the usual downtime, actually -- rimshot!).

But it is funny and strange that as long as we have people who can't foresee the future (so, all of us) programming computers, we'll keep running into problems like this. If your favorite Twitter client goes out on Saturday, just find a basement to stay in, stock up on shotgun shells and water, and put your head between your legs -- help is on the way soon.

From around the web

ear iconeye icontext filevr