A bigger concern for me is using 10 API calls against my limits. That is what's kept me from doing much with this data. I hope this changes sometime in the future.
-- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Fri, Nov 21, 2008 at 10:30 PM, Chad Etzel <[EMAIL PROTECTED]> wrote: > > > On Fri, Nov 21, 2008 at 10:26 PM, Amir Michail <[EMAIL PROTECTED]> wrote: >> >> On Nov 21, 10:11 pm, "Chad Etzel" <[EMAIL PROTECTED]> wrote: >> > As per the API documentation, you might want to look at the "page" >> > parameter. The API documentation is pretty extensive in this regard. >> > Don't >> > be afraid to read it :) >> >> Currently, you would need to perform 10 queries to get 1000 >> followers. I suspect that would be pretty slow. >> >> Amir > > Slow is a frame of mind :) You are correct though. To collect 1000 > followers you'd need to do 10 calls. Not super efficient, but at least it is > possible. > -Chad >> >> > >> > followers >> > >> > Returns the authenticating user's followers, each with current status >> > inline. They are ordered by the order in which they joined Twitter >> > (this is >> > going to be changed). >> > >> > *URL:*http://twitter.com/statuses/followers.*format* >> > >> > *Formats:* xml, json >> > >> > *Method(s):* GET >> > >> > *Parameters:* >> > >> > - id. Optional. The ID or screen name of the user for whom to >> > request a >> > list of followers. >> > Ex:http://twitter.com/statuses/followers/12345.jsonor >> > http://twitter.com/statuses/followers/bob.xml >> > - page. Optional. Retrieves the next 100 followers. Ex: >> > http://twitter.com/statuses/followers.xml?page=2 >> > >> > On Fri, Nov 21, 2008 at 10:02 PM, Amir Michail <[EMAIL PROTECTED]> >> > wrote: >> > >> > > Hi, >> > >> > > Or if not, please give us some control over which 100 followers are >> > > returned. >> > >> > > Amir >
