Hey Chad,
Thanks for the reply, and I can understand how tricky that must be.
It's kind of curious though--at some point over the weekend, several
more (but still not all) of our tweets were indexed and searchable,
yet our live tweets still aren't. This at least leads me to believe
that our
Search has been doing that for a month or two, as far as I know.
It tells you there are new tweets, but when you click refresh, it does
not show you the new tweets. Or it would say there are 35 new tweets,
and show you only 5 when you click refresh.
Dewald
On Sep 11, 3:20 pm, Voolkan
This usually happens during peak tweet times and the search servers
get out of sync updating the indexes across all of the boxes. So, when
you refresh, you might be getting results from a different server with
a non-identical set of results. We're working to eliminate these
discrepancies, but as
You're a LIFE SAVER man. Thank you very much.
And I couldn't agree more: @twitterapi should have notified us. I sent
him a @reply but got no answer so far.
On Sep 8, 11:10 pm, Hrishikesh Bakshi bakshi.hrishik...@gmail.com
wrote:
Quick fix:
Add q=* to your URL
On Tue, Sep 8, 2009 at 10:04
Another note: the Search API documentation has been updated to reflect
that querying based on geocode is not compatible with disjunctions (OR
queries).
Please see the Operator Limits section of
http://apiwiki.twitter.com/Twitter-Search-API-Method:-search.
On Wed, Sep 9, 2009 at 11:19, Samuel
Hey Folks,
The bug is specifically that all queries using the geocode parameter
with no query string return no results. We'll launch a bug fix today.
In the interim, you can use the geocode: operator in the query string
or add a bogus string as someone else has suggested. Sorry for the
Sorry, why is it not compatible with disjunctions? That seems like a
bug, not a change in functionality. Basically what you're saying is
that if I search for edmonton and geocode it, I get location
information. Or if I search for #yeg and geocode it, I get location
information. But if I search
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. Malemaster...@gmail.com wrote:
Until a couple of hours ago, searching for something like edmonton OR
#yeg OR
Awesome, thanks!
On Sep 8, 7:05 pm, Alex Payne a...@twitter.com 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. Malemaster...@gmail.com wrote:
Geocoded API searches are also broken. This is the geocoding example
from the API documentation, which used to work and now doesn't:
http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%2C25km
My website (blablabra.net) does similar searches and now receives only
403 Forbidden
FFS.
Any chance that things will actually be tested before they are rolled
out into PRODUCTION?
Dewald
On Sep 8, 10:25 pm, Jose Tinoco jose.tin...@gmail.com wrote:
Geocoded API searches are also broken. This is the geocoding example
from the API documentation, which used to work and now
These people should notify us about these changes:
http://twitter.com/twitterapi
On Tue, Sep 8, 2009 at 10:10 PM, Hrishikesh Bakshi
bakshi.hrishik...@gmail.com wrote:
Quick fix:
Add q=* to your URL
On Tue, Sep 8, 2009 at 10:04 PM, Dewald Pretorius dpr...@gmail.comwrote:
FFS.
Any
Quick fix:
Add q=* to your URL
On Tue, Sep 8, 2009 at 10:04 PM, Dewald Pretorius dpr...@gmail.com wrote:
FFS.
Any chance that things will actually be tested before they are rolled
out into PRODUCTION?
Dewald
On Sep 8, 10:25 pm, Jose Tinoco jose.tin...@gmail.com wrote:
Geocoded API
13 matches
Mail list logo
