Thanks for the reply John. Our primary reason for needing the followers list is that they are the only users that we can send DMs to. We use the DM functionality to let someone know that they have received money, so it is usually a DM they are interested in receiving.
Wouldn't it be beneficial for scalability for both parties to have reduced API requests and to include the events in the stream rather than leaving the clients to constantly be refreshing the follower ID lists? I understand the need to reduce spam, but does the current system really make it that much more difficult? On Dec 18, 9:25 am, John Kalucki <j...@twitter.com> wrote: > We'd like to help developers maintain a local copy of their authorized > users' followings -- the accounts that their users follow. We hope to enable > a feature that will make this easier in early 2011. > > We're not particularly interested in helping developers maintain the set of > an account's followers. There are awful scaling issues involved here, > vectors for spammy behavior, and generally not much value for end-users in > providing this data. Twitter is mostly about who you follow and what you are > interested in. Who is following you is becoming less and less relevant. > > -John Kaluckihttp://twitter.com/jkalucki > Twitter Inc. > > > > > > > > On Fri, Dec 17, 2010 at 8:15 PM, Shane <shaneneuerb...@gmail.com> wrote: > > We currently need to maintain accurate follower lists for our Twitter > > connected users. Using the site streams, we are able to easily add new > > followers with the follow event. However, I have not found a clean, > > efficient method of determine who has unfollowed a user. Currently, > > unless I'm missing something, I have to retrieve all of the user's > > follower IDs and compare them to what we have in our database. While > > this is fine for a user with only a couple thousand followers, it gets > > ugly in a hurry with when you have several users that have 50k+ > > followers. > > > Is it possible to have the unfollow events sent in the streams? At > > least in our case, it would cut down the amount of API requests and > > bandwidth consumed significantly. > > > -- > > 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
