Switching accounts to get around whitelisting is not in the spirit of the
reason whitelisting exists. If your application needs more requests than the
default rate limits provided to applications, you should request being
whitelisted for increased rate limits.

You can apply for expanded rate limiting here:

Here's a portion of the relevant Terms of Service regarding rate limiting:

"3. Your use of the Twitter API and Twitter Content are subject to certain
limitations on access, calls, and use of the Twitter API as set forth on
dev.twitter.com or as otherwise provided to you by Twitter. If Twitter
reasonably believes that you have attempted to exceed or circumvent the rate
limits, your ability to use the Twitter API and Twitter Content may be
temporarily or permanently blocked. Twitter may monitor your use of the
Twitter API to improve the Twitter service and to ensure your compliance
with these Rules."

Taylor Singletary
Developer Advocate, Twitter

On Tue, May 4, 2010 at 10:02 AM, Gaurav Shaha <gauravshah...@gmail.com>wrote:

> Like Rushikesh i am also facing same problem, before my application start
> working i need to check weather i have ample of call remaining to complete
> my task for that i had white listed my 2-3 accounts.
> so the idea that i am thinking is if the OAuth shall give me the remaining
> call then as per that i should switch automatically to my next white listed
> account without acknowledging user.
> Thank you in advance.
> On Tue, May 4, 2010 at 7:26 PM, Taylor Singletary <
> taylorsinglet...@twitter.com> wrote:
>> Hi Rushikesh,
>> You're asking a few things here, so I'll try to help clear them up:
>>   - Your app will need to do some kind of authentication for each of the
>> users. If your application is a web application, and you plan to have more
>> than just the two users you've mentioned, you'll want to implement the
>> entire OAuth 1.0a flow: request token acquisition, sending the user to
>> Twitter's authentication page, and then exchanging the request token for an
>> access token. You would then use the access token for each member to make
>> API calls. If the pool of users for your application will not go beyond the
>> two you mentioned, you might find yourself better served by applying for a
>> one-time use of xAuth to exchange your login credentials for access tokens.
>> If you're building a desktop or mobile application, you will want to use
>> either the OAuth 1.0A PIN/oauth_verifier flow or use xAuth.
>>   - Rate limiting is communicated through HTTP headers in the responses
>> you get from the API server.  See
>> http://dev.twitter.com/pages/rate-limiting
>>   - You can also use the
>> http://api.twitter.com/1/account/rate_limit_status end point to query on
>> rate limits. When using an access token in the request, the response will
>> indicate the rate limit status for the user represented by that access
>> token. If you aren't using an access token, it will indicate the rate limit
>> for the IP address.
>> Taylor Singletary
>> Developer Advocate, Twitter
>> http://twitter.com/episod
>> On Tue, May 4, 2010 at 2:00 AM, Rushikesh Bhanage <rishibhan...@gmail.com
>> > wrote:
>>> Hi there,
>>>       I am studying Abraham's code on github for Oauth to deal with my
>>> problem. In my app, user is not going to do authentication. I have two
>>> account with(username/password) and I have to use it to get ratelimit
>>> status. Studying code shows that, it is redirected(redirect.php) to
>>> twitter's window for user authentication. So instead of authenticating user
>>> on authentication window,  can I get ratelimit status of these two accounts
>>> authenticated through the code on github. Is it possible to do or
>>> alternatively what should I do?
>>>       can you suggest me any clue, please?
>>> Thank you in advance.
> --
> Warm Regards,
> Gaurav Shaha
> 9823359549.
> "Don't try to show off, just be youself and do what you ENJOY doing...."

Reply via email to