um... "As mentioned previously, the Twitter operations team will artificially increase the maximum status ID to 4294967296 this coming Friday, September 11th. This action is part of routine database upgrades and maintenance. "
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/8fde4804c5a75fb2 it appears to me that tw2k9 (<-- my new abbreviation, sorry, have typed twitpocalypse 2 too many times) is about using the full 32-bit int space. agreed, it didn't make much sense to announce that you were going to now utilize the full address space, but that *is* how it was announced - increase the new *maximum* status ID [emphasis mine] to 4294967296. $ echo $[ 65536 * 65536 ] 4294967296 thanks! Joseph Cheek jos...@cheek.com, www.cheek.com twitter: http://twitter.com/cheekdotcom Chad Etzel wrote: > On Thu, Sep 24, 2009 at 2:29 PM, Joseph Cheek <jos...@cheek.com> wrote: > >> already past 32-bit signed but not 32-bit unsigned, right? >> twitpocalypse moves the max to 2^32-1, right? or did i misread it? >> > > They have passed 32-bit *un*signed. My latest tweet id is 4345383616 > (which is > 2^32 - 1) > > Twitpocalypse 2 was about overflowing the 32 bit int space. > > -Chad > > > >> Chad Etzel wrote: >> >>> This has already happened. Tweet ids are now bigger than a 32 bit int >>> can store. That's what Twitpocalypse 2 was all about. >>> >>> -Chad >>> >>> >> -- >> Joseph Cheek >> jos...@cheek.com, www.cheek.com >> twitter: http://twitter.com/cheekdotcom >>