[twitter-dev] Client hourly limitations
I have several twitter accounts. Each account has generated its own set of OAUTH credentials. I am just using to look at data of those who are following me based on a list of all my followers IDs. I understand that there is a 150 per hour limit on client requests. But after reaching 150 with my first twitter account credentials, I then get this message for all accounts, with different credentials. hash request /1/friendships/show.xml?source_id=110236585target_id=132286315 /request error Rate limit exceeded. Clients may not make more than 150 requests per hour. /error /hash So what is being checked in order to determine the number of times a client has made a request? I also need confirmation on source_id and target_id. I am assuming *I* am the source_id and that my follower is therefore the target_id ... Mike -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Client hourly limitations
On 9/16/10 8:05 PM, yaemog Dodigo at yae...@gmail.com wrote: Check AnyEvent::Twitter::Stream for connecting to Streaming in Perl. It doesn't do oAuth yet, though. Not sure that oAuth is important here (unless your followers are protected users). At least I can get the followers of public users and create a stream based on these without using oAuth (unless you can do oAuth unknowingly, which would be sad since I cannot get oAuth to work willingly) LOL. I hear ya. Thanks for the above, I'll check it out right now cheers d -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Client hourly limitations
On 9/16/10 7:37 PM, M. Edward (Ed) Borasky at zn...@borasky-research.net wrote: Check AnyEvent::Twitter::Stream for connecting to Streaming in Perl. It doesn't do oAuth yet, though. OK I'll take a look - thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: About OAuth
On 9/5/10 4:26 AM, Scott Wilcox at sc...@dor.ky wrote: I wrote a small PHP script which can be run CLI: Its at: http://dor.ky/entry/twitter-api-oauth-update-status If you need any help adapting that to your needs, just pop me an email off list and I'll be happy to help you. Scott. Thanks Scott I appreciate you taking time to reply. I'll grab the script and see how I can adapt it. Mike -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: On the demise of basic authentication.
On 9/4/10 11:05 PM, Dustin Shea at demonicpa...@gmail.com wrote: There was plenty of notification on when Basic Auth was going to be discontinued. Dustin, I can't comment on what notification you received, and am glad you received it. I can only comment on the notification that *I* received: this was, on 9/2/10, addressed to the email addys associated with all 11 twitter accounts, the message that 3 days earlier basic auth had been expired. While I may be a perl hobbyist, in my professional life I do know how to identify, open and read an email. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
