Since yesterday, geocoded searches have been broken intermittently.
Sometimes results are returned normally, then for stretches of time
(30 minutes or more) no results are returned. During that time,
there's a "warning" like the following:
adjusted since_id to 8230615843933184 due to temporary err
Any update on this? It is still an issue.
On Oct 7, 9:46 pm, Siim Saarlo wrote:
> Hi,
>
> Search API with location restriction (geocode parameter) used to
> search through tweets that were geotagged and also tweets that were
> tweeted by user who had set her location in profile settings.
> Seems
I'm seeing this problem too, but it only started today, around five
hours ago. Here's an example search:
http://search.twitter.com/search?q=near%3Aedmonton
That's returning a fraction of the tweets it was before. This problem
happens occasionally, but not usually for this long.
On Oct 7, 3:10 pm
If you want every tweet on a topic we highly suggest
> the streaming interface.
>
> Jonathan
> @jreichhold
>
> On Mon, Jun 28, 2010 at 8:09 AM, Mack D. Male wrote:
>
>
>
> > What's the deal with search? It's not returning all the data. Just
> > look at any of the trending topics for instance. The Status site
> > hasn't been updated.
What's the deal with search? It's not returning all the data. Just
look at any of the trending topics for instance. The Status site
hasn't been updated.
There seems to be something wrong with the search API. It is only
returning a tiny subset of what I would expect (after looking at the
same query on search.twitter.com for instance) and is reporting the
following:
"adjusted since_id to 16201119561 due to temporary error"
Any word on what this tem
This is a problem when filtering by geo as well - searching for tweets
"near:vancouver" also returns retweets of users in vancouver by users
in other locations.
On Jan 22, 10:18 am, "Ryan G." wrote:
> Hello,
>
> As @Sarah Richards reported earlier, we are being impacted across many
> of our web p
Twitter Search has been very problematic today, mainly for searches
using operators. For instance, this search currently returns an error
message:
http://search.twitter.com/search?q=near%3Aedmonton
"The page you were looking for doesn't exist.
You may have mistyped the address or the page may ha
ot;You must enter a
> >> query" if I try this search on my browser window.
>
> >> On Sep 8, 10:05 pm, Alex Payne wrote:
>
> >> > Our Search Team informs me that they shipped a new query parser today.
> >> > This is likely a bug in the new pa
Awesome, thanks!
On Sep 8, 7:05 pm, Alex Payne wrote:
> Our Search Team informs me that they shipped a new query parser today.
> This is likely a bug in the new parser, and I've let them know about
> it.
>
> On Tue, Sep 8, 2009 at 17:48, Mack D. Male wrote:
>
> >
Until a couple of hours ago, searching for something like "edmonton OR
#yeg OR near:edmonton" (or the API equivalent) worked just fine. Now
it doesn't return anything new, and seems to return an odd set of old
results.
You can search for them separately, as in "edmonton OR #yeg" and
"near:edmont
Wed, Feb 18, 2009 at 4:19 PM, Mack D. Male wrote:
>
>
>
>
>
> > Looks like they just added the "source" property to a result...so make
> > sure you're decoding properly.
>
> > On Feb 18, 12:21 pm, TCI wrote:
> >> I am getting an error &quo
Looks like they just added the "source" property to a result...so make
sure you're decoding properly.
On Feb 18, 12:21 pm, TCI wrote:
> I am getting an error "no element found" when querying the API for
> CostaRica's followers... Anything going on?
13 matches
Mail list logo
