Seeing as 32bit signed was 2,147,483,647 and 32bit unsigned is 4,294,967,295
And 64bit signed is 9,223,372,036,854,775,807, I'd say we're safe for a good little while yet! On Sep 10, 7:23 am, "Ted Neward" <ted.new...@gmail.com> wrote: > What is the documented range for status IDs? (How high can they go?) > > Ted Neward > Java, .NET, XML Services > Consulting, Teaching, Speaking, Writinghttp://www.tedneward.com > > > -----Original Message----- > > From: twitter-development-talk@googlegroups.com [mailto:twitter- > > development-t...@googlegroups.com] On Behalf Of Alex Payne > > Sent: Wednesday, September 09, 2009 1:01 PM > > To: twitter-development-talk@googlegroups.com > > Subject: [twitter-dev] Re: Alert: "Twitpocalypse II" coming Friday, > > September 11th - make sure you can handle large status IDs! > > > Sorry, an error in phrasing. It was previously mentioned that this > > change was pending. We had not previously announced a date for the > > change. > > > Normally, we prefer to provide more advance notice where possible, but > > I'm letting you all know immediately after our operations team > > informed me that it was necessary to make this change on Friday. > > > On Wed, Sep 9, 2009 at 12:13, Hwee-Boon Yar<hweeb...@gmail.com> wrote: > > > > May I know when and where was it mentioned that it will be > > > artificially increased this coming Friday? > > > > -- > > > Hwee-Boon > > > > On Sep 10, 2:49 am, Alex Payne <a...@twitter.com> wrote: > > >> As mentioned previously, the Twitter operations team > > willartificially > > >> increase the maximum status ID to 4294967296 this coming Friday, > > >> September 11th. This action is part of routine database upgrades and > > >> maintenance. > > > >> If your Twitter API application stores status IDs, please be sure > > that > > >> your datastore is configured to handle integers of that size. > > Thanks. > > > >> -- > > >> Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x > > > -- > > Alex Payne - Platform Lead, Twitter, Inc. > >http://twitter.com/al3x
