Much better!
I let http://jsfiddle.net/NBCGf/34/ run 1000 tries successfully before
taking mercy on your servers and shutting it off.
Good job and thanks,
//mh
On Tue, Jun 14, 2011 at 11:28 PM, themattharris
thematthar...@twitter.comwrote:
Hey everyone,
Thanks for all the information you
Can confirm this is happening to me too, for this request:
http://search.twitter.com/search.json?q=from%3Atfr%20OR%20from%3ASOIANYCrpp=5callback=jQuery16106527990615355083_1308086280457_=1308086281400
(I'm fetching tweets from two users - tfr and SOIANYC - if I
remove SOIANYC from the query, it
Thanks for all the extra info, folks -- this is very useful and I've now got
a reproducible case. We'll look into this.
Thanks!
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Tue, Jun 14, 2011 at 2:20 PM, Matt guitarroman...@gmail.com wrote:
Can confirm this
We are seeing the same problem on our latest
site: http://grb.culturemap.com/senior-games/
It is intermittent; sometimes good JSON is returned and sometimes not.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter:
Fyi Guys,
The way I worked around this since a try-catch was useless is that I used a
window.oneerror = function(){ to ignore the offending tweet and count errors
etc.
//mh
On Tue, Jun 14, 2011 at 6:17 PM, Paul Bailey paul.m.bai...@gmail.comwrote:
We are seeing the same problem on our latest
Re: error handling the jsonp script error
I started using the previously mentioned window.onerror mechanism
wherein I reload the iframe from which I'm initiating the jsonp call,
up to 10 times, 3 seconds apart (the average delay in getting the
script back from twitter, which triggers the error
Marc,
Nice theory but I'm not so sure since I'm reloading the same exact tweet (I
think)over and over again and its getting corrupted.
Although I've heard of type of thing before where an application (notepad)
tries to do charset encoding detection but fails and outputs a corrupted
file upon
Hey everyone,
Thanks for all the information you provided. We were able to reproduce
the problem and the engineers have now released a fix.
You shouldn't receive any garbled API responses anymore, if you do
please let us know.
Best,
@themattharris
On Jun 14, 7:59 pm, michael hazzard
