I pull json results from a url like this:

http://api.twitter.com/1/statuses/user_timeline/XXXX.json?count=9&include_rts=true&callback=jsonp1295903703204&_=12959037

Where XXXXX is the feed name. Normally, this works (I can't say what
the feed name is, unfortunately).  But I recently renamed the account,
and now, intermittently, I get back jsonp that ends with something
like this:

o_screen_name":null,"created_at":"Mon ...45 +0000 2011"},  
0,  0,  0,  0,  0]);

You can't see them, but there are two bizarre, unknown illegal
characters in there before all the zeros. json parsers, of course,
choke on them quite badly.  If I look at them in a text editor, they
are "EOT" and "BS" in black boxes instead of regular characters.

Any idea why this would be happening?  Could it be related to changing
the name of the account, and will it go away quickly?

-- 
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

Reply via email to