The first Twitpocalypse involved the tweet ID's moving past the highest 32-bit *signed* integer (which is 2,147,483,647).
This time around the tweet ID's will move past the highest 32-bit *un*signed integer (which is 4,294,967,295). Developers should make sure the code they are using to store/manipulate tweet ID's is treating them as (at least) 64 bit integers (BIGINT in sql or "long long" in some other typed languages, unsigned preferably). Some people have expressed storing tweet ID's as strings, however never having personally done that, I'm not fully aware of the implications of doing so. -Chad Twitter Platform Team On Fri, Jul 31, 2009 at 6:21 PM, Dean Collins<d...@cognation.net> wrote: > > Huh? I thought this issue was resolved already? > > My developer for www.MyTwitterButler.com said he solved this problem > back in June? > > Am I missing something? > > > > Cheers, > > Dean > > > > > > -----Original Message----- > From: firstname.lastname@example.org > [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Marcel > Molina > Sent: Friday, July 31, 2009 5:53 PM > To: email@example.com; > twitter-api-annou...@googlegroups.com > Subject: [twitter-dev] Twitpocalypse: The Second Coming is on the > horizon > > > Twitter status ids are fast approaching the maximum 32-bit *unsigned* > integer value (4,294,967,295). > > The current estimate is that this will occur in approximately 60 days, > at the end of September. The 60 day window is a best-guess > approximation based on projections. It could conceivably happen > sooner. > > Developers are encouraged to not only update their applications to use > a 64-bit integer (BIGINT/long long), but also verify that all > libraries they use are also prepared to handle 64-bit integers. > > -- > Marcel Molina > Twitter Platform Team > http://twitter.com/noradio >