I would also like to request the API limit to be raised as soon as
possible. I am not able to roll out an update for my desktop Twitter
client, simply because the API limit is too low for the features I
have implemented. The new version of my client utilizes Lists related
APIs, which consumes a lot
> > The problem here is distinguishing the two. OAuth doesn't (and I was
> > told this by one of the people on the OAuth committee) specifically
> > allow you to unambiguously and securely identify an application just
> > because it has a certain app key
>
> Huh? Can you translate this into either
> > > Another hunch: desktop apps are negligible and the real load comes
> > > from web apps who spider asynchronously 24/7. Should the load be
> > > differentiated across client and web apps? Client apps are typically
> > > only one user per device at a time, whereas the web app may be
> > > spide
Not really that hard to distinguish between 5 IPs making 20k API hits and
20k IPs making 5 API hits each...
Abraham
On Wed, Jan 20, 2010 at 16:50, Cameron Kaiser wrote:
> > Another hunch: desktop apps are negligible and the real load comes
> > from web apps who spider asynchronously 24/7. Shoul
On Jan 20, 4:50 pm, Cameron Kaiser wrote:
> The problem here is distinguishing the two. OAuth doesn't (and I was
> told this by one of the people on the OAuth committee) specifically
> allow you to unambiguously and securely identify an application just
> because it has a certain app key
Huh? C
> Another hunch: desktop apps are negligible and the real load comes
> from web apps who spider asynchronously 24/7. Should the load be
> differentiated across client and web apps? Client apps are typically
> only one user per device at a time, whereas the web app may be
> spidering on behalf of wh
On top of all that, AFAIK the 1500 limit for OAuth is still vaporware
at this point, so everybody is capped at 150.
To inform the discussion, I wonder if Twitter could share any figures
like what's the actual API use distribution? Like what combination of
users/apps hit the cap regularly and cause
I've "discovered" that the API rate limit is 450 per hour for pages/
cursors within a "followers_ids" or "friends_ids" call, if that helps.
But I really think that increasing the API rate limit for basic HTML
auth is a bad idea - let's make oAuth work!
On Jan 20, 3:04 pm, Josh Roesslein wrote:
>
