I noticed the same thing as Buzz today. Another data point for you guys to track it down: I'm seeing different results for "following" between what is returned by http://twitter.com/users/screen_name.json and http://twitter.com/friendships/exists.json (with user_a=chockenberry&user_b=mikeysan).
I'm also seeing that the XML doesn't contain the element and the JSON does. Sure does look like a cache problem :-) -ch On Jan 13, 9:59 am, Matt Sanford <[email protected]> wrote: > Hi Buzz, > > This sounds like a caching bug on the Twitter side. Please open a > ticket athttp://code.google.com/p/twitter-api/issuesand we'll look > into it. Be sure to include the URLs you're using. Usernames are also > helpful so we can check the exact cache entries for traces of what > went wrong. > > Thanks; > — Matt > > On Jan 13, 2009, at 09:48 AM, buzz wrote: > > > > > An added bit of data that makes me even more convinced I'm not crazy > > and that this is a Twitter API bug: the JSON representation of the > > very same users include thefollowingbit that the XML is missing. > > > -- > > Buzz
