I just ran into this one in an old application of mine (List 'em All, http://quonos.nl/list-em-all/): https://api.twitter.com/statuses/friends.json
Seems to show 100 users as well, without having to send IDs (which saves another API call). However, I'm only mentioning it to correct my last post - it's a non-documented API endpoint and as far as I know, they should not be used. Tom On Aug 9, 4:58 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > The friends/ids method has a friend of its own: users/lookup -- which allows > you to bulk your users/show calls by about 100 users at a time. > > So you would perform the sequence of using friends/ids and then for each set > of 100 ids you get back, you'd send them to users/lookup to get the detailed > information back. > > http://dev.twitter.com/doc/get/users/lookup > > Taylor > > > > > > > > On Mon, Aug 9, 2010 at 7:53 AM, Tom <allerleiga...@gmail.com> wrote: > > I don't think that there is an API which allows you to do this. > > > Caching is important here. What you can do, for example, is simply get > > the home timeline (which also contains user objects) and store these > > users in your cache - possibly a few (max. 32) pages. > > > Tom > > > On Aug 9, 1:03 am, Alex Chang <changcommaa...@gmail.com> wrote: > > > What's the best method for display a list of friends to a twitter > > > user? In most other oauth / social network apis - they usually return > > > an id as well as a name. > > > > What's the best way to go about showing a list of friends without > > > getting killed by the api limit? > > > > Right now I'm using /friends/ids.json. Then looping on it for /users/ > > > show.json in order to get the screennames. This will kill the api > > > limit. > > > > Any suggestions?
