1. You can use 127.0.0.1 instead of localhost.

2. You can authorize your app as many times as you like from the same twitter account without the necessity to revoke it. However, the authenticate action will only prompt for Allow/Deny once and all subsequent authenticate requests will just pass through until you revoke the privilege.

Twitter s "rate limiting" for API GET calls is based on IP address of the caller. So, you can test your app from your server, using the same IP address, and get (once approved) 15,000 API calls per hour. That means you can pound on your app with many different usernames, as long as your approved IP address remains the same.

When you send the e-mail to Twitter to ask for an increase to your rate limit, you can also ask for the increase to apply to your Twitter username too.

I believe Twitter requires you - if you need to change your IP address, or change the username that is using the app - to send in another request asking for the rate limit increase for that new IP address or username. But, in my experience, Twitter has been pretty quick at turning around these requests (maybe less than 48 hours?).

use like this for Website :http://127.0.0.1 and for callback URL: http://127.0.0.1/home or any of your page address like http://127.0.0.1/index

Have you tried creating your own caching mechanism? You can take the result of an initial query, cache it on thread local, and given an expiration time, refresh from Twitter. This would allow you to test your app against Twitter data without incurring call penalties.

There is also another solution (a workaround, rather) which requires you to edit your hosts file.

Here is how you do it on a linux box:

1. Open your /etc/hosts file as root. To do this, you can open a terminal and type something like sudo vi /etc/hosts.

2. Pick a non-existent domain to use as your local address, and add it to your hosts file. For example, you will need to add something similar to the following at the end.

   127.0.0.1 localhost.cep # this domain name was accepted.
   

So, that s pretty much it. Pointing your browser to localhost.cep will now take you to your local server. Hope that helped :)

In answer to (1), see this thread, in particular episod s replies: https://dev.twitter.com/discussions/5749

It doesn t matter what callback URL you put in your app s management page on dev.twitter.com (as long as you don t use localhost). You provide the real callback URL as part of your request for an OAuth token.