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
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.
Now, now - this is the Twitpocalypse, not the Twittocaust.
--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
Ok, seriously, this message I wrote wasn't worth the electrons it took
to transmit it... let's see if I can increase the s2n ratio:
4294967296, that an unsigned 32-bit int? ok, fair enough. i know some
of my apps use signed 64bit ints, but i'm not sure about the db... will
need to check... might be signed32...
Joseph Cheek
jos...@cheek.com, www.cheek.com
twitter: http://twitter.com/cheekdotcom
Nicholas Moline wrote:
> And nobody thought about the significance of accelerating anything
> called a *pocolypse to be on the anniversary of a date that thousands
> died in a terrorist attack.... Tactful Twitter... Real Tactful
>
> On Wed, Sep 9, 2009 at 1:00 PM, Alex Payne <al...@twitter.com
> <mailto:al...@twitter.com>> wrote:
>
>
> 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<hwee...@gmail.com
> <mailto:hwee...@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
Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
> -----Original Message-----
> From: twitter-deve...@googlegroups.com [mailto:twitter-
> developm...@googlegroups.com] On Behalf Of Alex Payne
> Sent: Wednesday, September 09, 2009 1:01 PM
> To: twitter-deve...@googlegroups.com
> Subject: [twitter-dev] Re: Alert: "Twitpocalypse II" coming Friday,
> September 11th - make sure you can handle large status IDs!
>
>
We have been able to work with our operations team to delay the forced
update until around September 21st or 22nd (over a week away). Since
this twitpocalypse is based on the tweet count, it is impossible to
predict exactly when it will happen and therefore we can only make
projections based on current usage and possible spikes. With that
being said, it *could* happen as early as Sept 16th (Wednesday), so
please start updating your applications now to handle the change. We
will be able to give you better estimates as the event moves closer
and we will be sure to update the list when we know the exact time of
the update.
Let us know if you have any questions and be sure to stock up on water
and non-perishable goods :)
Ryan
That is definitely part of the plan and hence why we are aiming for
that Monday / Tuesday. We know what a strain it can be to push stuff
out at the end of the week.
Best, Ryan