Hi all,
thanks for your responses.
John, I did take a look at the stream api but was put off by the big
disclaimer saying it could change very frequently and be down for
extended periods. Also, I was kinda trying to avoid the issue I was
seeing in search where certain tweets were not being
You probably wouldn't use the streaming API 20k times/hr. You would
open one connection and consume data from it during that hour.
---Mark
http://twitter.com/mccv
On Sun, Jan 3, 2010 at 12:15 AM, Joel Hughes joelhug...@gmail.com wrote:
Hi all,
thanks for your responses.
John, I did
Hey Kyle,
Is that true re the rate limits?
I've always assumed that ANY request on an IP is xounted against that
IP's rate limit - so comes of the 20,000; and each user has their own
rate limit... normally 150 per hour.
So an authenticated request comes off both the user's and and IP's
rate
My experience with rate limiting shows that each authenticated request
is counted against that user's limit on your IP. So, you get 20,000
requests per IP, per user, per hour assuming all your requests are
authenticated. Any unauthenticated requests go towards the 20,000
request limit per IP, per
Craig,
I just ran a test, and I can also confirm what you have found.
Unauthenticated calls decrease per IP 20,000
Authenticated calls decrease per-IP per-user 20,000
Dewald
On Aug 13, 4:27 pm, CaMason stasisme...@googlemail.com wrote:
The behaviour at the moment is definitely as-described
Hi There,
What you all have been confirming is correct. The intended behavior is
20k per IP unauthenticated, and 20k per IP *per user* authenticated.
This is not a bug.
-Chad
On Thu, Aug 13, 2009 at 4:43 PM, Abraham Williams4bra...@gmail.com wrote:
I've been reading I have confirmed emails
Holy
Thanks, Chad. :)
On Aug 13, 4:58 pm, Chad Etzel c...@twitter.com wrote:
Hi There,
What you all have been confirming is correct. The intended behavior is
20k per IP unauthenticated, and 20k per IP *per user* authenticated.
This is not a bug.
-Chad
On Thu, Aug 13, 2009 at 4:43
Just to make things crystal clear, it should be stated that the 20k
rate limits apply only to GET requests to the so-called REST-API.
Other request types (I.e., POST) and / or other APIs (I.e., search,
streaming) have other rate limits.
Jim Renkel
On Aug 13, 3:58 pm, Chad Etzel c...@twitter.com
YabadabaFrigginDoo!!
I have no idea what kind of application would need to continuously
make 5 authenticated calls per second on a particular Twitter account,
but hey, if you can think of one, you know you won't be rate limited.
Dewald
On Aug 13, 5:58 pm, Chad Etzel c...@twitter.com wrote:
Hi
On Thu, Aug 13, 2009 at 5:44 PM, Dewald Pretoriusdpr...@gmail.com wrote:
YabadabaFrigginDoo!!
I have no idea what kind of application would need to continuously
make 5 authenticated calls per second on a particular Twitter account,
but hey, if you can think of one, you know you won't be
In fact, with an API response time of 0.3 seconds, you won't even run
out of rate limit if your authenticated GET script goes into an
endless loop.
Dewald
On Aug 13, 6:44 pm, Dewald Pretorius dpr...@gmail.com wrote:
YabadabaFrigginDoo!!
I have no idea what kind of application would need to
Hi Chad -
Now that the DDoS attacks are (sort of) behind us, can we seek some
closure on this? I'm dying to know the official, undisputed, written-
in-stone, we-can-finally-stop-arguing-about-it answer to the following
(which I think simplifies the question):
If my IP is whitelisted and I have
With a whitelisted IP you can make 20k auth calls per hour for each user.
Once you reach this limit for a user you cannot make any auth calls from
that IP in that duration. But the user can still use his 150 limit from
other apps.
Wowzers (bonus points for getting the reference)
It appears as if each user does get 20k (according to the linked
threads) this is I think what they intended and makes apps a LOT
easier to develop as you can now do rate limiting (ie caching and
sleeping etc...) based on each user and not on an
Bob,
Don't base your app on the assumption that it is 20,000 calls per hour
per user.
You get 20,000 GET calls per whitelisted IP address, period. It does
not matter if you use those calls for one Twitter account or 10,000
Twitter accounts.
If the API is currently behaving differently, then it
Well it seems as though Twitter is saying that 20k calls per user is
the intended functionality. Chad or someone else can you confirm this?
Also if the correct functionality is 20k per ip per hour will you then
fail over to 150 per user per hour or is it cut off?
Thanks
-Bob
On Thu, Aug 6,
Hi Inspector Gadget, er... Bob,
Yes, the current whitelisted IP rate-limit allows 20k calls per hour
*per user* on Basic Auth or OAuth or a combination thereof.
Go, go gadget data!
-Chad
Twitter Platform Support
On Thu, Aug 6, 2009 at 12:13 PM, Robert Fishelbobfis...@gmail.com wrote:
Well
Good questions. I agree the phrasing surrounding this topic in the
documentation is not extremely clear. I am digging for answers.
-Chad
On Thu, Aug 6, 2009 at 12:44 PM, Jesse Stayjesses...@gmail.com wrote:
Chad, did that change recently? I was told by Alex and others there that it
was 20,000
Chad,
Are you 100% sure of that?
I mean, in terms of rate limiting that simply does not make sense.
For my site, TweetLater.com, it would mean I have an effective hourly
rate limit, per IP address, of 2 BILLION IP GET calls per hour!
(20,000 per user for 100,000 users).
It sounds wrong to me.
Hi Dewald,
I asked The Powers That Be about it, and that was the response I
got. However, I am double and triple checking because that does sound
too good to be true :)
-Chad
On Thu, Aug 6, 2009 at 1:01 PM, Dewald Pretoriusdpr...@gmail.com wrote:
Chad,
Are you 100% sure of that?
I mean,
Chad, did that change recently? I was told by Alex and others there that it
was 20,000 calls per hour, period, per IP. When did that change and why
weren't we notified? This will save me a lot of money if it is indeed true.
Jesse
On Thu, Aug 6, 2009 at 12:37 PM, Chad Etzel c...@twitter.com
That would be the same as having no rate limit at all, because really,
which app would beed to make 20,000 GET calls per hour on one Twitter
account?
If that's how it is enforced currently, then that is the reason why
the API often gets so overloaded and slow.
Dewald
On Aug 6, 2:04 pm, Chad
Just some background. I talked with Doug about this a few months ago,
because I observed in the Rate Limit Header of get calls that the
20,000 number decremented by user, not by IP address in aggregate.
Doug informed me that he was going to hand the issue over to Matt, who
was on vacation at
I got the same response from Alex awhile back (and I think confirmed by
Doug). And I'm seeing the same results, as well. I'm pretty sure it's
20,000 per IP without regard to user.
Jesse
On Thu, Aug 6, 2009 at 1:24 PM, Dewald Pretorius dpr...@gmail.com wrote:
Just some background. I talked
@Dewald Pretorius
For my site, TweetLater.com, it would mean I have an effective hourly
rate limit, per IP address, of 2 BILLION IP GET calls per hour!
I believe 20k limit per user is the desirable behavior, but i don't think
twitter will allow you to make infinite calls in which case they will
25 matches
Mail list logo
