I'm already working on this. It'll be new methods, I think. Should be ready to deploy by early next week.
On Thu, Jan 22, 2009 at 10:15, Scott C. Lemon <scottcle...@gmail.com> wrote: > > Alex, > > Thank you for the quick reply ... and I agree ... it seems that > returning the list of followers or friends as an array of IDs would be > most effective. This is somewhat how Facebook does it with their > API. That would allow us to gain access to the information in a much > more compact way. > > Obviously this would also make the amount of data being returned much > less, as it wouldn't have to include the status of those people or > anything else ... we can get that in subsequent requests, or by > monitoring and caching the feed. > > So maybe there could be two new APIs? > > http://twitter.com/statuses/friendIDs.format > http://twitter.com/statuses/followerIDs.format > > What do you propose as next steps for this? Do I/we have to enter a > bug/issue to make the request? Or are you already working on a > solution for this? We would be very interested in seeing this new API > so that we can fine tune our operation and minimize the number of > requests we'll be making ... > > Scott > > > On Jan 21, 11:49 pm, Alex Payne <a...@twitter.com> wrote: >> > Can you please address the issue of how you would recommend that an >> > application be able to fetch the total list of a users followers? I'm >> > hearing all sorts of accusations and bluster, but want to understand >> > from your perspective how you would propose an application do this? >> >> Right now, you can page through the lists of friends and followers. >> We'll see about ways to get the friends list in one shot. I think our >> best bet for a method that returns the entire set of friends or >> followers would be simply returning an array of user IDs. >> >> > Even here on the list there are people suggesting that you enhance the >> > API to simply drop the current status ... and only return the list of >> > followers ... which would seem to be a much simpler, and less >> > intensive, query. >> >> We'll certainly consider that. >> >> > As a side note, we are currently working on three twitter >> > applications ... two that are hosted services, and one that is a >> > desktop application. I want to ensure that we continue to build these >> > fully understanding how to work cooperatively with you! >> >> All you need to do is send us an email, and we'll find solutions. It >> may take some time if the solution you need isn't on our development >> roadmap, but we're here to make it happen. >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
