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
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
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 -
Hey,
So /statuses/friends.json is documented here:
http://dev.twitter.com/doc/get/statuses/friends
but as Taylor said we recommend you use /friends/ids.{format} in combination
with /users/lookup.{format}.
Matt
On Mon, Aug 9, 2010 at 10:52 AM, Tom allerleiga...@gmail.com wrote:
I just ran
