[twitter-dev] Re: lang=en queries to search API not working
This has been a problem for some time now, is nothing be done to
address it? The since fix isn't great because anything outside of
that five to six day window will not be returned.
On Nov 28, 5:23 am, MartinW wright.mar...@gmail.com wrote:
Hi Steve,
I've found the same problem over the past couple of days too. I had
also narrowed it down to the lang parameter but selecting all does
still not guarantee results.
This is now impacting my live site as no results are being returned.
I'm also going to investigate whether rate limiting could be the
issue.
Please let me know if you get any further with your investigations.
Cheers
Martin Wright
http://www.twitseek.com
On Nov 27, 3:42 am, steve ick...@gmail.com wrote:
This reproduces even onhttp://search.twitter.com. If you try to
filter to en only results you get back 0 items for most queries.
Select try all languages from the search portal or remove lang=en
from your API query and you get results for your queries (most of
which are in english.)
What's weird is this seemed to be working fine until about 2 days
ago. And its been very intermittent since. Yesterday queries would
work for a while then they would stop working (same query to the
API.) But today they seem to be broken for me all day. Other members
of my team reported the same issue yesterday so it defenitly seems to
be something on your end.
BTW... When calling the API and this happens we're getting back an
error similar to this:
jsonp1290717568994({results:[],max_id:7896158276488192,since_id:
7896158276488192,refresh_url:?
since_id=7896158276488192q=Thanksgiving,results_per_page:50,page:
1,completed_in:0.019352,warning:adjusted since_id to
7896158276488192 due to temporary
error,since_id_str:7896158276488192,max_id_str:7896158276488192,query:Thanksgiving});
I did a search and this error was reported back in June but nobody
ever responded... Crossing my fingers that this message doesn't go
into the void as well...
--
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
[twitter-dev] Re: Search API Optional lang Has Problem.
This has happened before. Appending a since clause works around it, but limits your search results to only five days. Also last time this happened they fixed it within a few weeks. I just wish we could get an official comment on this. On Nov 28, 5:50 pm, Jeong Hoon Kim redi...@gmail.com wrote: About 5 days ago, Suddenly Search API Optionallanghad no results..My optionallangis ko. Did anybody apply Search APIlangoption? Did the results come out correctly? -- 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
[twitter-dev] Re: Search API reporting temporary error
I'm going directly to the URL in question; it only seems to happen to me when I have lang=en anywhere in the url. On Jun 15, 1:35 pm, Mack D. Male master...@gmail.com wrote: There seems to be something wrong with thesearchAPI. It is only returning a tiny subset of what I would expect (after looking at the same query onsearch.twitter.com for instance) and is reporting the following: adjustedsince_idto 16201119561 due to temporary error Any word on what this temporary error is, or when it'll be fixed? I'm using the latest build of TweetSharp, if that makes any difference.
[twitter-dev] Re: max_id being added to search queries?
I've been getting this as well. It only seems to happen to me when I
append lang=en to my url. If I leave that off I get the records I
expect back.
On Jul 19, 5:53 pm, Mark Linsey mjlin...@gmail.com wrote:
Hi all,
I am using the Twitter Search API. I am finding today that even though I am
not providing a max_id or a since_id, both are being added. I am getting a
response warning saying that since_id has been adjusted. I assume max_id is
being adjusted for the same reason.
I am fetching this
url:http://search.twitter.com/search.json?q=qwerpoiurpp=100page=1resul...
and getting this response:
{results:[],max_id:18949422775,since_id:18903514913,refresh_url:?since_id=18949422775q=qwerpoiu,results_per_page:100,page:1,completed_in:0.020541,warning:adjusted
since_id to 18903514913 due to temporary error,query:qwerpoiu}
I was expecting to get this tweet, which does appear on
search.twitter.com:http://twitter.com/mjltest/statuses/18953620545
I assume that these are extra limits put in place today to deal with other
issues in the Twitter API. Is there any way of getting recent search
results now?
-Mark
