I think this is delayed. And also 21:00 GMT is 16:00 Eastern and 13 Pacific. Please let us know when the move forward in time will happen.
Martin - www.wherecloud.com On Jun 12, 3:45 pm, Steven Degutis <[email protected]> wrote: > To clarify: > > This problem only affects applications who use a "signed integer" (32- > bit C-library) type, or equivalent, to store the unique ID of tweets? > Or does it originate on your end, where we will get incorrect IDs > right off the bat? > > -Steven Degutis > > On Jun 12, 12:23 pm, Matt Sanford <[email protected]> wrote: > > > > > Hi all, > > > The overflow of the 32-bit signed integer value for status ids > > (a.k.a "The Twitpocalypse" [1]) is fast approaching. The current > > estimate is around tomorrow at around 11am GMT, or 3:00am Pacific time > > in the case of Twitter. There is some discussion internally about > > accelerating things so we'll be in the office and able to cope. Nobody > > is their freshest at 3:00am, not to mention it would be nice to not > > have apps broken throughout the weekend if one-person developer teams > > don't notice. No decision has been made yet but I wanted to get > > something out to you all so you know what's going on in the event we > > decide to do this. > > > Thanks; > > – Matt Sanford / @mzsanford > > Twitter Dev > > > [1] -http://www.twitpocalypse.com/
