Taylor,

I have a sample from my log.  It's not very detailed, but at least you
can see that it's happening at random times.  I am waiting a full
minute before hitting the timeline, so it's not that.  Let me know
your thoughts.

4/22/2010 7:22:21 PM~Duplicate Message ID: 12667336000
4/22/2010 7:28:16 PM~Duplicate Message ID: 12667634000
4/22/2010 7:29:18 PM~Duplicate Message ID: 12667683000
4/22/2010 7:37:20 PM~Duplicate Message ID: 12668102000
4/22/2010 7:41:17 PM~Duplicate Message ID: 12668312000

-Matt

On Apr 21, 1:53 pm, mattarnold1977 <matt.arnold.1...@gmail.com> wrote:
> Taylor,
>
> That's odd then because I'm seeing duplicate status id messages in my
> log.  I'll have to dig deeper to see which ID is being repeated to
> give you an example.
>
> -Matt
>
> On Apr 21, 10:45 am, Taylor Singletary <taylorsinglet...@twitter.com>
> wrote:
>
>
>
> > It has not happened yet.
>
> > The most recent parts of the discussion are in this 
> > thread:http://groups.google.com/group/twitter-development-talk/browse_thread...
>
> > Thanks,
> > Taylor
>
> > On Tue, Apr 20, 2010 at 6:20 PM, mattarnold1977
> > <matt.arnold.1...@gmail.com>wrote:
>
> > > Taylor,
>
> > > I just remembered that you were planning to change the generation of
> > > status ids.  Has that already occurred?  If so, where is the
> > > documentation on that again?
>
> > > -Matt
>
> > > On Apr 20, 10:14 am, Taylor Singletary <taylorsinglet...@twitter.com>
> > > wrote:
> > > > Hi Matt,
>
> > > > I'm not able to see the issue at the moment -- can you provide some more
> > > > details like examples of duplicate status ids? The public_timeline
> > > endpoint
> > > > is cached for 60 seconds, so it will remain stagnant if you're 
> > > > requesting
> > > it
> > > > more often than that.
>
> > > > Taylor Singletary
> > > > Developer Advocate, Twitterhttp://twitter.com/episod
>
> > > > On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977
> > > > <matt.arnold.1...@gmail.com>wrote:
>
> > > > > It looks like the public timeline api is reporting the same statuses
> > > > > over-and-over again.  This started sometime yesterday (4/19) and
> > > > > continues today.  Is anyone else experiencing this issue?
>
> > > > > Thanks,
> > > > > Matt
>
> > > > > --
> > > > > Subscription settings:
> > > > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

Reply via email to