Oh! I should avoid creating multiple user accounts in that case. I would like to perform analysis on a target set of users and not streams. How do I proceed? I should add that 350 requests per hour is highly insufficient for my use case.
--Regards, Denzil On Sat, Jun 4, 2011 at 11:33 PM, Tom van der Woerdt <[email protected]> wrote: > I'd like to point out that this is against the TOS. You should limit your > API requests where possible - for a normal application with user interaction > you won't need more than 350 per hour. If you do some sort of data analysis, > you may need to use streams instead. > > Tom > > > On 6/4/11 7:53 PM, Correa Denzil wrote: >> >> Tom : >> >> Thanks. I will create multiple user accounts. I guess about 20 (350 * >> 20 = 7000 considering 1 request per second) should solve my issue. >> >> >> >> --Regards, >> Denzil >> >> >> >> >> On Sat, Jun 4, 2011 at 3:35 AM, Tom van der Woerdt<[email protected]> wrote: >>> >>> If you authenticate, all requests (except for search) will go into the >>> 350 >>> requests. If you want 500, then perform 150 unauthenticated and 350 >>> authenticated. If you need even more, use more accounts to do the >>> requests. >>> >>> Tom >>> >>> >>> On 6/3/11 11:06 PM, Correa Denzil wrote: >>>> >>>> Ah! I feel similar. >>>> >>>> Which essentially means that despite acquiring data which is publicly >>>> available I will be limited to 150 requests per hour and even OAuth >>>> will not help increasing it to 350 ? >>>> >>>> >>>> --Regards, >>>> Denzil >>>> >>>> >>>> >>>> >>>> On Sat, Jun 4, 2011 at 2:32 AM, James Gifford<[email protected]> >>>> wrote: >>>>> >>>>> The way I'm reading it it falls under 1. But I might be mistaken. >>>>> >>>>> --James Gifford >>>>> http://jamesrgifford.com >>>>> >>>>> On Jun 3, 2011, at 17:01, Correa Denzil<[email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am collecting Twitter data for my research. The API says that : >>>>>> >>>>>> [1] "Anonymous calls are based on the IP of the host and are permitted >>>>>> 150 requests per hour. This classification includes unauthenticated >>>>>> requests (such as RSS feeds), and authenticated requests to resources >>>>>> that do not require authentication." >>>>>> >>>>>> [2] "OAuth calls are permitted 350 requests per hour." >>>>>> >>>>>> I want to seek a clarification on point [1]. Lets say I want to access >>>>>> a list of followers of a user id (which is public). Would this be >>>>>> counted as rate limiting under point [1] or point [2] ? >>>>>> >>>>>> >>>>>> --Regards, >>>>>> Denzil >>>>>> >>>>>> -- >>>>>> 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 >>>>> >>> -- >>> 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 > -- 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
