The statuses/friends method was specifically recommended to me to work around the RateLimit problem I was having. I don't know any other way to get the statuses of approximately 60 users every minute when my app is behind a firewall (preventing OAuth authentication for each individual user). So I use my app's access token/secret to get my friends (and their most recent status).
I can't use the statuses/user_timeline because of basic auth going away and OAuth requiring a callback to my server all due to rate limiting and my inablity to get whitelisted. Besides, what is the point of having an API method if it isn't reliable (even when it successfully makes the call)? On Oct 19, 3:55 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Hi Joe, > > This is likely a caching sync issue. You can report bugs > tohttp://code.google.com/p/twitter-api/issues/list > > I personally recommend avoiding statuses/friends as it's more of a legacy > method than other means of discovering the same information. I personally > recommend using friends/ids and users/lookup in conjunction with each other > instead. While there's a best-effort to provide the most recent status in > embedded user objects, the definitive means to determine this is by getting > the most recent tweet from the user's statuses/user_timeline > > Taylor > > > > On Tue, Oct 19, 2010 at 12:41 PM, Joe Rattz <joeratt...@gmail.com> wrote: > > How do I report a bug? > > > I am seeing what appears to be a bug right now and it is reproducbble > > in the Twitter Twurl. > > > What I am seeing is a discrepancy in the latest status returned with > > the statuses/friends web service call. Basically, the XML interface > > works properly but the JSON one does not. I have a specific user that > > is not returning the latest status for JSON (but does for XML). > > > I am hoping that someone could take a look at this quickly (yeah, > > right) since it is reproducible. I also suspect the issue may be > > related to the fact that the user I am seeing this happen to is set to > > private. My user account is an approved follower though. As I said, > > the webservice works for XML, but not for JSON. > > > -- > > 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- Hide quoted text - > > - Show quoted text - -- 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