Re: [twitter-dev] Oauth in Twitter via Python
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 i...@tvdw.eu 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 Giffordja...@jamesrgifford.com 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 Denzilmcen...@gmail.com 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
Re: [twitter-dev] Oauth in Twitter via Python
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 Woerdti...@tvdw.eu 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 Giffordja...@jamesrgifford.com 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 Denzilmcen...@gmail.comwrote: 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
Re: [twitter-dev] Oauth in Twitter via Python
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 i...@tvdw.eu 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 Woerdti...@tvdw.eu 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 Giffordja...@jamesrgifford.com 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 Denzilmcen...@gmail.com 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
Re: [twitter-dev] Oauth in Twitter via Python
If you have the permission of the users, you can probably use their OAuth tokens, which gives you an almost infinite API limit (actually it's still 350 per user, but you won't easily break that). If you want to perform an analysis on a group of users without their consent (without OAuth access), you'll have to find a better way to do it. Tom On 6/4/11 8:12 PM, Correa Denzil wrote: 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 Woerdti...@tvdw.eu 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 Woerdti...@tvdw.euwrote: 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 Giffordja...@jamesrgifford.com 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 Denzilmcen...@gmail.com 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
Re: [twitter-dev] Oauth in Twitter via Python
Tom : I probably missed the point. I see the targeted users, their data is public and accessible using no authentication but the API limits are too small. I can't gain OAuth access from them. I would like to increase this to more API calls using OAuth. --Regards, Denzil On Sun, Jun 5, 2011 at 1:41 AM, Tom van der Woerdt i...@tvdw.eu wrote: easily -- 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-dev] Oauth in Twitter via Python
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
Re: [twitter-dev] Oauth in Twitter via Python
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 mcen...@gmail.com 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
Re: [twitter-dev] Oauth in Twitter via Python
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 ja...@jamesrgifford.com 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 mcen...@gmail.com 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
Re: [twitter-dev] Oauth in Twitter via Python
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 Giffordja...@jamesrgifford.com 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 Denzilmcen...@gmail.com 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-dev] OAuth with Twitter
I had a few questions I was hoping someone could help answer for me: 1. Does Twitter support https:// on all of its API calls? 2. If so, is it possible to use PLAIN_TEXT signatures in OAuth? 3. Does a simple end-user iPhone app need to provide a full 3-legged OAuth request, or can the 2-legged OAuth variant be used as referenced in the OAuth specification (i.e. Application wishing to use OAuth as an alternative to HTTP ‘Basic’, should use the the Consumer Key and Consumer Secret to hold the username and password, and leave the Token and Token Secret empty.? Thanks!
Re: [twitter-dev] OAuth with Twitter
1. Does Twitter support https:// on all of its API calls? yup. 2. If so, is it possible to use PLAIN_TEXT signatures in OAuth? nope. 3. Does a simple end-user iPhone app need to provide a full 3-legged OAuth request, or can the 2-legged OAuth variant be used as referenced in the OAuth specification (i.e. Application wishing to use OAuth as an alternative to HTTP ‘Basic’, should use the the Consumer Key and Consumer Secret to hold the username and password, and leave the Token and Token Secret empty.? search the forums for the note of xAuth - you could use that. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Oauth and Twitter for login.
Hi, I have just started to implement oAuth for http://www.twollo.com, and when registering my app for oAuth I noticed: Use Twitter for login: Yes, use Twitter for login Does your application intend to use Twitter for authentication? This is excellent news, for reasons I have mentioned in previous emails, however, unless I have missed something, is there anything I need to do to use this functionality? Or is it just the normal oAuth workflow - I am hoping that it is similar to the way I implement oauth support on http://oauth.twe2.com/ Paul.