Same here.
On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote:
About 5 days ago, Suddenly Search API Optional lang had no results..My
optional lang is ko.
Did anybody apply Search API lang option? Did the results come out
correctly?
--
Twitter developer documentation and resources:
And same with some search operators (like source:xxx)
Sorry for posting twice :)
On Nov 29, 1:50 am, Jeong Hoon Kim redi...@gmail.com wrote:
About 5 days ago, Suddenly Search API Optional lang had no results..My
optional lang is ko.
Did anybody apply Search API lang option? Did the results
Same problem here. When lang=all is used I am getting results. When a
language is specified I get zero results most of the time, while in
some cases I do get a result. Seems very strange.
On Nov 29, 9:25 am, fbparis fbou...@gmail.com wrote:
And same with some search operators (like source:xxx)
I'm seeing this as well. Including filter:links or setting that language
causes the search to fail. I get an error message saying since_id has been
adjusted due to a temporary error. I'm *not* including a since_id in the
search parameters.
Hayes
On Mon, Nov 29, 2010 at 10:08 AM, Randomness
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:
There is an issue with Twitter's language detection. When specifying a
language (lang=nl) , there is no result, when using lang=all, I do get
results, in my language.
Using lang=all gives us so many results, that we're hitting the rate
limits with lots of stuff we're throwing away straight away
