Hi Buzz,
This sounds like a caching bug on the Twitter side. Please open a ticket at http://code.google.com/p/twitter-api/issues and 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 the following bit that the XML is missing. -- Buzz
