[twitter-dev] Public Timeline Frozen

2010-04-20 Thread mattarnold1977
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


Re: [twitter-dev] Public Timeline Frozen

2010-04-20 Thread Taylor Singletary
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, Twitter
http://twitter.com/episod


On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977
matt.arnold.1...@gmail.comwrote:

 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



[twitter-dev] Public Timeline Frozen

2009-11-12 Thread mattarnold1977

I just checked my server log and noticed that the public timeline
hasn't been responding for about 2 hours.  Has anyone else been
experiencing this?  Is anything going on that we should know about?
Perhaps they are working on that service?

-Matt


[twitter-dev] Public Timeline Frozen (Again)

2009-05-10 Thread mattarnold1977

Not sure if this is an outcome of the site maintenance, but it looks
like the public timeline has been sending out the same statuses since
about 9:20pm on 5/8/09.  The timeline was frozen last week, but was
fixed.  Thus, I'm guessing this is a result of the maintenance that
was just performed.  Please let us know if this is a known issue.


[twitter-dev] Public Timeline Frozen

2009-05-07 Thread mattarnold1977

I just checked the log on my server and noticed that the public time
line has been putting out the same status information since around 5
o'clock yesterday.  Is this a known issue?

-Matt