My guess is that you have something like
curl http://search.twitter.com/search.json?q=hellorpp=50
That '' in there is sneaky and will be interpreted by your shell as a
meta-character to background the process.
Try wrapping the URL in quotes and see what happens:
curl
curl -s -x http://gatekeeper:8080
http://search.twitter.com/search.json?q=testrpp=2
Returns 15 results.
On May 27, 10:39 am, Matt Sanford m...@twitter.com wrote:
Hi Jim,
There is no known issue but if you can provide the curl command
you're using we might be able to help.
Thanks;
Hi Yusuke,
Unfortunately the source: operator as it is currently
implemented has a few shortcomings. One is that it requires a query,
and the second is that it can only search the last 7 days. This is a
known performance issue and we're still looking for a way we can
remove the
Never mind. I figured out the problems was I switched queries to
.xml instead of .json, and XML isn't one of the choices for the
search API.
On Apr 21, 12:43 pm, hjl hojohn@gmail.com wrote:
I'm doing some testing this morning with the search API, which was
working for a while but now is
Please see our article on rate limiting [1]. You will learn why the Search
API does not have a notion of authentication and how its rate limiting
differs from the REST API.
1. http://apiwiki.twitter.com/Rate-limiting
Thanks,
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Mon,
Hi,
I've experienced a few 404's on search.json this morning.
Sometimes works, sometimes doesn't can't seem to pinpoint any
particular pattern to it happening.
--
Leu
On Apr 17, 5:11 am, Chad Etzel jazzyc...@gmail.com wrote:
Just a quick update:
The problem as popped up again. Doug is
Ok, dunno what was happening... I gave my server a swift kick with my
steel-toed boot and all seems well again... weird.
-Chad
On Thu, Apr 16, 2009 at 10:27 PM, Doug Williams d...@twitter.com wrote:
I just sent 200 queries through without seeing the 404. Are you still seeing
this?
Doug
Just a quick update:
The problem as popped up again. Doug is aware of this problem, and he
says the servers are all stretched pretty thin (understandable). Just
curious if anyone else is seeing this as well?
-Chad
On Thu, Apr 16, 2009 at 11:30 PM, Chad Etzel jazzyc...@gmail.com wrote:
Ok,
Perfect, thanks Matt
On Apr 8, 5:27 pm, Matt Sanford m...@twitter.com wrote:
Hi Pete,
Every 5 seconds is well below the rate limit and seems like a
good rate for reasonably quick responses. It sounds like you're doing
the same query each time so that should be fine.
For
Yes, this is possible. Have you actually tried it yet? Make sure to
use capital OR between the hashtags.
http://search.twitter.com/search?q=%23followfriday+OR+%23pawpawty+OR+%23gno
-chad
On Sun, Apr 5, 2009 at 2:36 PM, Matt matthewk...@gmail.com wrote:
Is it possible with the current
Thanks. Wasn't aware I could pass along operators.
On Apr 5, 2:41 pm, Chad Etzel jazzyc...@gmail.com wrote:
Yes, this is possible. Have you actually tried it yet? Make sure to
use capital OR between the hashtags.
http://search.twitter.com/search?q=%23followfriday+OR+%23pawpawty+OR+...
Hi,
There is a rate limit for the Search API but it is higher than 100 requests
per second imposed by the REST API. The limiting is performed by the IP
address. The default limit is high enough that most applications shouldn't
be affected.
As the search architecture has no notion of accounts, it
some information inline …
On Mar 6, 2009, at 01:25 PM, Scott C. Lemon wrote:
I'm working on our site - http://www.TopFollowFriday.com - and am
currently using the search API to search for the #followfriday
hashtag. All is well, and it's working ... except ...
The search feed only returns
Hi Chad,
This anchor is how search gets the data from Twitter so we keep
it consistent and pass it along that way. For the next version of the
API we have an outstanding request to break these two apart (See http://code.google.com/p/twitter-api/issues/detail?id=75)
.
Thanks;
— Matt
Thanks for the info.
Anchor - that's the word I was looking for... could have searched
for that if I had remembered anchor.
Sorry for wasting your time, you may now shoot me /monty-python
-Chad
On Wed, Feb 25, 2009 at 11:44 AM, Matt Sanford m...@twitter.com wrote:
Hi Chad,
This anchor
201 - 215 of 215 matches
Mail list logo
