I figured out this problem; it was not related after all. I needed to
set the user-agent when using curl, with the curl_setopt command (in
PHP). Once I did that I did not have problems using the Search API.
On Aug 29, 7:03 pm, Dan danec...@gmail.com wrote:
I'm not sure if this is related.
I'm not sure if this is related. I've been using Services_Twitter to
use the Search API and I keep getting the error message Unsupported
endpoint search. I'm searching a simple 7-letter word. Anyone have
any idea what that message means? Maybe this is related to something
going on with
I agree I have been using the Twitter search APIs for more than a year
on 3 App Engine apps, this is seriously handicapping my usage of the
API.
-Ben Hedrington
On Aug 27, 1:42 am, Paul Kinlan paul.kin...@gmail.com wrote:
Hi,
I still think something is going on (or at least different) - I have
Hi,
Just a question, I am starting to see very heavy throttling to the Twitter
Search API from the Google App engine.
I am receiving 503's enhance your calm very frequently. I have a custom set
User-Agent string and I am probably doing less than 1 search per second.
It has been happening for a
Hi Paul,
If you are sharing your IP with any other GAE twitter apps that are
also doing search, then you are sharing the resource at that point.
The limiting is by IP first, then user-agent. Also, 1 search per
second is on the borderline of the normal rate-limit anyway, so I
would try calling
Hi Chad,
Has this limit changed recently? I used to query it far more frequently from
the app engine. Obviously, Google use a lot of different IP addresses so I
presuming it can fluctuate. But over the last couple of days I have noticed
far more that I used to get.
If it is by IP first what is
150 is a per-user rate, not a per-IP rate, to begin with, isn't it?
The issue here is whitelisted IPs sharing 20k total, right?
∞ Andy Badera
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)
On Sun, Aug 23,
Another data point: I also run a Python app on Google App Engine. It
hits the Twitter search API 3 times per minute, with different search
parameters. About 20% of my app's search requests get a 503L error
code, and the other 80% return search results as expected. There is no
clear pattern or
Just to clarify: I am testing with unauthenticated calls
On Aug 23, 5:17 pm, boaz sapirb...@gmail.com wrote:
Hello everyone,
I checked the behavior on an AWS instance _without_ static IP (which
is called by Amazon elastic IP) and I do not see any problem with the
limits. The limit status
Hopefully to add some clarity:
I have not used AWS or EC2, but as I understand it, Elastic IP's are
IP's that you 'own' under your account that you can assign at will to
your instances. In this way, it acts as a Static IP since you use it
exclusively.
-Chad
On Sun, Aug 23, 2009 at 11:06 AM,
not sure about GAE, but for AWS, you can request for a static IP, it
costs some $, but it's the only way to work with Twitter API if rate
limit is an issue for you
On Aug 21, 1:29 pm, BenHedrington b...@hedrington.com wrote:
I agree GAE throttle on the Search API is not behaving as it has in
On Sat, Aug 22, 2009 at 6:26 AM, Beierbeier...@gmail.com wrote:
not sure about GAE, but for AWS, you can request for a static IP, it
costs some $, but it's the only way to work with Twitter API if rate
limit is an issue for you
GAE has no such IP offering yet. Also, by its very nature, all
Hello Chad,
Can you confirm that this is not the case for AWS elastic IPs which
had been previously whitelisted by Twitter?
Thanks,
Darren
On Aug 21, 4:35 pm, Chad Etzel jazzyc...@gmail.com wrote:
Hello,
I have replied to Jud off-list, but for everyone's benefit we'd like
to reiterate that
I agree GAE throttle on the Search API is not behaving as it has in
the past, Can someone please look into this?
-Ben Hedrington
On Aug 21, 11:48 am, Jud jvale...@gmail.com wrote:
I've got a python app running on Google App Engine (appspot hosted)
that
Hello,
I have replied to Jud off-list, but for everyone's benefit we'd like
to reiterate that AWS and GAE are shared resources and therefore share
the rate limit across applications. A dedicated IP and unique UA will
guarantee the maximum API limits. There are several cheap and reliable
VPS
15 matches
Mail list logo
