Hi Steve,
In answer to your questions.
1. users/lookup returns information about the user_ids or screen_names you
pass to it. You may choose to pay follower ids, friends ids, or both. It's
purpose is to just expand the user_id or screen_name into a hydrated user
object.
2. If you stay within the rate limits when making requests there shouldn't
be any issues. More on rate limits can be found here:
http://dev.twitter.com/pages/rate-limiting
3. followers/ids and friends/ids will give you just the IDs. If you need the
screen_name you need to call users/lookup or users/show but you would
receive all the information. We don't offer a lightweight version of that
request.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Thu, Jan 6, 2011 at 5:19 PM, Lingzhi Zhang <[email protected]> wrote:
> Thanks, Matt
>
> I looked at the user/lookup. I have three questions on using that API
> to get ids and nickname of friends/followers.
>
> 1. user/lookup returns "up to 100 users worth of extended
> information". Are the users friends or followers? I would need to
> differentiate friends and followers.
>
> 2. If the friends/followers are more that 100, I will have to make
> multiple calls to get user info. For instance, 10 calls to get 1,000
> user info. Does Twitter allow multiple calls to user/lookup one after
> another. Is there any limitation?
>
> 3. This is not big issue. user/lookup still returns extended
> information. However, most of them I don't need at this moment. If
> there is a lightweight API to just get friends/followers' ids and
> nicknames, that'll be ideal.
>
> Thanks again.
>
> Steve
>
> --
> 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
