>    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/

> Hello again,

>    The responses to @twitterapi and all discussions internally show a
> preference to not waiting until the middle of the night. The current plan is
> to force this issue at 21:00 GMT (2:00pm Pacific/5:00pm Eastern for those in
> the US). This will let us make sure we have all staff available in the
> unlikely event something goes wrong on our end. We'll also be available when
> people who don't follow the twitter-dev-talk list start reporting errors.
> While we did warn developers about the Twitpocalypse I'm sorry we didn't
> think about setting a drop-dead date and scheduling this previously. We'll
> keep trying to improve on warnings like this.

> Good night, and good luck.

> Thanks;
>  – Matt Sanford / @mzsanford
>     Twitter Dev

> On Jun 12, 2009, at 10:23 AM, Matt Sanford 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/

>      The responses to @twitterapi and all discussions internally show  
> a preference to not waiting until the middle of the night. The current  
> plan is to force this issue at 21:00 GMT (2:00pm Pacific/5:00pm  
> Eastern for those in the US). This will let us make sure we have all  
> staff available in the unlikely event something goes wrong on our end.  
> We'll also be available when people who don't follow the twitter-dev-
> talk list start reporting errors. While we did warn developers about  
> the Twitpocalypse I'm sorry we didn't think about setting a drop-dead  
> date and scheduling this previously. We'll keep trying to improve on  
> warnings like this.

> Good night, and good luck.

> Thanks;
>   – Matt Sanford / @mzsanford
>       Twitter Dev

> On Jun 12, 2009, at 10:23 AM, Matt Sanford 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/

>> Good night, and good luck.

> @ttytter stands ready!

> --
> ------------------------------------ personal: http://www.cameronkaiser.com/ --
>  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
> -- NetBSD - a devil of an operating system. -- Julian Assange -----------------

>      The responses to @twitterapi and all discussions internally show  
> a preference to not waiting until the middle of the night. The current  
> plan is to force this issue at 21:00 GMT (2:00pm Pacific/5:00pm  
> Eastern for those in the US). This will let us make sure we have all  
> staff available in the unlikely event something goes wrong on our end.  
> We'll also be available when people who don't follow the twitter-dev-
> talk list start reporting errors. While we did warn developers about  
> the Twitpocalypse I'm sorry we didn't think about setting a drop-dead  
> date and scheduling this previously. We'll keep trying to improve on  
> warnings like this.

> Good night, and good luck.

> Thanks;
>   – Matt Sanford / @mzsanford
>       Twitter Dev

> On Jun 12, 2009, at 10:23 AM, Matt Sanford 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/

>      The responses to @twitterapi and all discussions internally show  
> a preference to not waiting until the middle of the night. The current  
> plan is to force this issue at 21:00 GMT (2:00pm Pacific/5:00pm  
> Eastern for those in the US). This will let us make sure we have all  
> staff available in the unlikely event something goes wrong on our end.  
> We'll also be available when people who don't follow the twitter-dev-
> talk list start reporting errors. While we did warn developers about  
> the Twitpocalypse I'm sorry we didn't think about setting a drop-dead  
> date and scheduling this previously. We'll keep trying to improve on  
> warnings like this.

> Good night, and good luck.

> Thanks;
>   – Matt Sanford / @mzsanford
>       Twitter Dev

> On Jun 12, 2009, at 10:23 AM, Matt Sanford 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/