Interesting ideas. I have started to do that a little by setting up a php proxy script on another webserver and checking to see if my remaining hits are really low, and switch over to querying through the proxy if it's low. The #1 problem with that method is that I'm using shared hosting which can drop the limit based on what other users are doing on that particular web server.
But I hadn't thought much about asking other random people to help spread the load. IF I'm having a few people use OAuth to make the calls on my behalf, it doesn't matter if they're on the same IP, right? > > Your other best alternative is to provide some form of web-based > authentication (read-only likely being most appropriate), detail the purpose > of your study and explicitly outline what an end-user is agreeing to and ask > users to authenticate your application to act on their behalf. On virtue of > their consent, you could then use their access token to further execute the > requests you're interested in. If you have a circle of friends on Twitter, > you might get the bandwidth you're looking for pretty quickly -- otherwise > you could, for example, ask members of this mailing list to authenticate and > agree to "pool resources" so to speak as an endorsement of your research. > > Taylor > > @episod <http://twitter.com/episod> - Taylor Singletary > > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk