If you look there and hit F5 (one each second, 10 times maximally), you'll see that few responses
- don't have jsonp callback
- don't have search response
Is that problem on my side (that URL) or is that just Twitter API's fault?
If you look there and hit F5 (one each second, 10 times maximally), you'll see that few responses
Is that problem on my side (that URL) or is that just Twitter API's fault?
This is definitely twitter's fault, even the official link often returns plain instead of padded JSON.
[2011-07-16] Seems fixed now. Maybe some twitter devs reading here?