Hi all,

  Per my previous comment I wanted to follow up and say the issue has
been fixed. It looks like Alex handled the other question.

Thanks;
  — Matt Sanford

On Nov 12, 10:50 am, "Jorge Handl" <[EMAIL PROTECTED]> wrote:
> Ok, I can live with that. Thanks for fixing it!
>
> On Wed, Nov 12, 2008 at 4:50 PM, Alex Payne <[EMAIL PROTECTED]> wrote:
>
> > Apologies, but in the current system there's not a great way to
> > recover data.  We're working on that.
>
> > On Wed, Nov 12, 2008 at 9:16 AM, jungle <[EMAIL PROTECTED]> wrote:
>
> > > Thanks Matt!
>
> > > What will happen with the lost data period?
> > > Can we have at least a part of that sent our way or are just left with
> > > a blank period?
>
> > > On Nov 12, 3:10 pm, Matt Sanford <[EMAIL PROTECTED]> wrote:
> > >> Hi Jungle,
>
> > >>   It's a problem in the back-end system and we're working on it right
> > >> now. I'll update the ticket (http://code.google.com/p/twitter-api/
> > >> issues/detail?id=150) as I get more information and will update this
> > >> thread when we have a fix.
>
> > >> Thanks;
> > >>  — Matt Sanford
>
> > >> On Nov 12, 9:05 am, jungle <[EMAIL PROTECTED]> wrote:
>
> > >> > Hi!
>
> > >> > The public timeline feed has stopped updating the posts, returning the
> > >> > same posts for the last 12 hours or so. The latest post is from "Wed
> > >> > Nov 12 02:57:29 +0000 2008".
>
> > >> > What happened?
>
> > --
> > Alex Payne - API Lead, Twitter, Inc.
> >http://twitter.com/al3x

Reply via email to