If you're acting on your own behalf and don't have "users", likely you'll just have to deal with the rate limiting and consider that for you to obtain all the data you're interested in, it's going to take time -- 24 hours in a day, 350 requests an hour, 7 days in a week...
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 On Fri, May 13, 2011 at 10:24 AM, torncanvas <torncan...@gmail.com> wrote: > Any other ideas before I head out to fight the white dragon? :P > > -- > 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 > -- 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
