Matt,
Here is another thread pseudo-related to the issue.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/b7b6859620327bad/77927af246c77907#77927af246c77907
Again, thanks to Chad.
Brooks
On Jul 21, 1:35 pm, matthew jesc...@gmail.com wrote:
Chad,
Good to know.
Brooks,
Thanks for the link - helps me understand some of the stuff I've been
seeing.
Matthew
On Jul 22, 1:15 pm, Brooks Bennett bsbenn...@gmail.com wrote:
Matt,
Here is another thread pseudo-related to the issue.
http://groups.google.com/group/twitter-development-talk/browse_thread...
That usually happens when the search servers get out of sync and the
since_id tweet hasn't been indexed on the other server(s) yet, so it
thinks it's a tweet from the future.
-Chad
On Tue, Jul 21, 2009 at 12:38 PM, matthewjesc...@gmail.com wrote:
I am polling the Search API and intermittently
Chad,
Good to know. Thanks for your help.
Matthew
On Jul 21, 2:13 pm, Chad Etzel jazzyc...@gmail.com wrote:
That usually happens when the search servers get out of sync and the
since_id tweet hasn't been indexed on the other server(s) yet, so it
thinks it's a tweet from the future.
-Chad
