From the API documentation:
http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
Warning: The user ids in the Search API are different from those in
the REST API (about the two APIs). This defect is being tracked by
Issue 214. This means that the to_user_id and from_user_id field
Pretty odd, I am able to use curl to get
http://search.twitter.com/search.json?q=^_^lang=zh
but have the same problem as you fetching it through Firefox/Safari.
On Mar 22, 12:51 pm, Irokez iro...@gmail.com wrote:
http://search.twitter.com/search.json?q=^_^lang=en - works
As someone who's developing some applications right now specifically
involving the search APIs I now have to worry about whether or not I
should pre-emptively include the result_type parameter so my app
doesn't become non-functioning when the changes are pushed to the
site. Why do the popular
