Fair enough, though it hasn't corrected itself yet and I'm seeing it
on every user I test against so this feels like a systemic problem.
Our application caches all historical mentions of our users. How are
we to know when the API gives us valid results or not?

On Nov 8, 11:28 am, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> There are times when the cache is not warm with more recent tweets. These
> times will pass and there's really not much you can do from an API
> perspective when this condition is happening to a particular user's
> timelines. The data is just inaccessible to the API at the moment.
>
> Taylor
>
> On Sun, Nov 7, 2010 at 1:41 PM, Aaron Rankin <aran...@sproutsocial.com>wrote:
>
>
>
>
>
>
>
> > I'm seeing errors with this endpoint. A request for the last 200
> > mentions of @aaronrankin returns 29 mentions that were created between
> > February and now, with many missing. Per my own cache of tweets, there
> > were 200 mentions of @aaronrankin between September 3rd and today.
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to