Accounts with more followers will naturally take you longer to process. The majority of users on Twitter do not have exceptionally large follower counts (though your user base may reflect different demographics).
You can do analysis for users with low follower counts within an hour. For users with larger counts, you accomplish what you can in the first hour, then move on to the next. For users with 1 million followers, you could potentially use GET followers/ids with cursors to get 5000 ids at a time. That would take you 200 requests. If you used all 350 requests for a user in a hour on just followers/ids, you could potentially get data for 1.75 million users. How many cases do you have where one of your users wants to perform up-to-date follower analysis on a user with 1M followers? When that user comes along, queue the job and send them an email when the results are ready. If it's bulk analysis that you want to do -- multiple accounts analyzed every which way against each other -- you can still do it. But it will take you more time. Taylor @episod <http://twitter.com/episod> - Taylor Singletary - Twitter Developer Advocate On Mon, Feb 21, 2011 at 7:37 AM, Jo Seibert <joseib...@gmail.com> wrote: > On 21 Feb., 06:50, "Orian Marx (@orian)" <or...@orianmarx.com> wrote: > > I don't know what the current state of this is but it looks like Site > > Streams will support unfollow events for this purpose: > http://groups.google.com/group/twitter-development-talk/browse_thread... > > From the mentioned thread: > "I'm only seeing unfollow events where the tracked > user is doing the unfollowing." > > So if only those unfollowings are reported by the stream, that the > tracked user is doing himself, I am not able to watch the followers, > that he has lost (other followers unfollow the tracked user). > That's not sufficient for follower tracking how we do it. > > Unfortunately no statement from the twitter guys... > > Cheers. > Jo Seibert > > > > > On Feb 18, 5:11 pm, Jo <jseib...@seibert-media.net> wrote: > > > > > > > > > It seems as if no one at twitter as an answer or a solution on this. > > > That's bad... > > > Or are they still thinking about it? > > > > > Cheers. > > > Jo Seibert > > > > > On 15 Feb., 11:03, Dewald Pretorius <dpr...@gmail.com> wrote: > > > > > > Thanks Tim. So the point is, we still need to rely on the follower > ids > > > > list API method if we want to maintain an up to date picture of an > > > > account's followers. For larger accounts this becomes impractical > with > > > > a limit of 350 calls per hour. > > > > > > On Feb 15, 4:13 am, Tim Haines <tmhai...@gmail.com> wrote: > > > > > > > It sends you an event when our subject user follows someone else, > unfollows > > > > > someone else, or when they are followed by someone else. It does > not send > > > > > an event when they are unfollowed by someone else. > > > > > > > Tim. > > > > > > > On Tue, Feb 15, 2011 at 3:08 AM, Dewald Pretorius < > dpr...@gmail.com> wrote: > > > > > > If I remember correctly, Site Streams sends you a transaction > only > > > > > > when the user follows another user (adding to Following). It does > not > > > > > > send you a transaction when someone else follows that user > (adding to > > > > > > Followers). I don't know if this work the same in User Streams. > > > > > > Clarification by Twitter will be appreciated. > > > > > > > > On Feb 14, 12:38 pm, David Giamanco <dgiama...@gmail.com> wrote: > > > > > > > I believe the new way to do this is to initially call the REST > API to get > > > > > > > all of the ids for the first time you process this user. Then > you setup a > > > > > > > User Stream on the user and process any requests that come in > through > > > > > > there. > > > > > > > For your uses, if you only show users the differences in > follower counts > > > > > > > then you don't need the initial call to the REST API to collect > all ids. > > > > > > All > > > > > > > you need is a count of the ids and then to initiate a User > Stream. The > > > > > > User > > > > > > > Stream will give you the differences in real time and you can > store just > > > > > > the > > > > > > > differences, instead of the entire set of ids. > > > > > > > > > David Giamanco > > > > > > > > -- > > > > > > 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 > > -- > 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 > -- 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
