What is your goal for this application? Are you trying to get a sampling of statuses for analysis, or for occasional casual display? If the former, you should use a sample method on the Streaming API. If the later, please persist in your quest for a reasonably unique result set. The public timeline isn't used much anymore and regressions could theoretically and regrettably, exist for a bit without anyone noticing.
-John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Apr 29, 2010 at 4:54 AM, mattarnold1977 <matt.arnold.1...@gmail.com> wrote: > This is the third time I've reported this issue in the last couple of > weeks. I still have not received any word back from Twitter support > regarding this issue. My server log is filling up with duplicate > status errors coming from the public timeline. I'm waiting to hit the > timeline until after the cache period, so it's not that. And, yes > it's not just duplicate status ids I'm seeing, it's also duplicate > statuses as well. Every time I hit the public timeline I compare the > results against a months worth of data that I have saved. Is anyone > else having this issue? > > -Matt >
