Thanks for the information collected on this. We're investigating this
issue at the moment and updates will be posted to our status blog:
http://status.twitter.com/post/1058895068/investigating-invalid-responses-from-the-api
Matt
On Sep 3, 8:44 am, Marsh Gardiner <ma...@apigee.com> wrote:
> I see it too. Here's a cached version of the
> response:http://app.apigee.com/console/apigee-console-snapshots-1283317200000_...
>
> The same request with xml seems to be working
> fine:http://app.apigee.com/console/apigee-console-snapshots-1283317200000_...
--
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?hl=en
