Confirmed here too.
On Sep 3, 8:57 pm, gabriele renzi rff@gmail.com wrote:
Hi everyone,
I am noticing that my home timeline and that of a few other people is
returning some messed up stuff,
basically intemingling something that looks like a random sequence of
bytes to normal messages.
Here too!
Lots of binary garbage coming for a:
/statuses/user_timeline.json?
count=40include_rts=truescreen_name=chockenberryoauth_consumer_key=...oauth_nonce=...oauth_signature_method=HMAC-
SHA1oauth_timestamp=...oauth_token=...oauth_version=1.0oauth_signature=...
Twitter for iPhone also
Same phenomenon occured in xml.
URL is below
http://api.twitter.com/1/statuses/user_timeline.xml?user_id=93771355
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
+1, unable to parse timeline due to garbage in the XML feed. Many of
our users are reporting the same problem.
On Sep 3, 7:35 am, koujitaro kohura12345...@gmail.com wrote:
Same phenomenon occured in xml.
URL is
belowhttp://api.twitter.com/1/statuses/user_timeline.xml?user_id=93771355
--
Twitterrific users have been seeing this for at least 2 hours, now.
On Sep 3, 2010, at 8:47 AM, TheGuru wrote:
+1, unable to parse timeline due to garbage in the XML feed. Many of
our users are reporting the same problem.
On Sep 3, 7:35 am, koujitaro kohura12345...@gmail.com wrote:
Same
I see it too. Here's a cached version of the response:
http://app.apigee.com/console/apigee-console-snapshots-128331720_b7a1fe22-6ec8-4996-ba1a-2720227c896c/rendersnapshotview
The same request with xml seems to be working fine:
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
For what it's worth, I confirm the issue for paper.li - invalid json
response on home_timeline and list statuses
- unparseable json format.
On Sep 3, 12:57 pm, gabriele renzi rff@gmail.com wrote:
Hi everyone,
I am noticing that my home timeline and that of a few other people is
returning
For what it's worth, all of the garbage data seems to be /between/ the
status updates. We (Flipboard) have deployed a temporary hack to split
the raw JSON at status boundaries and verify the integrity of each one
before trying to parse the JSON.
--
Twitter developer documentation and resources:
