Do you have any code examples for this? So you basically maintain a  
local db of id-to- screen_names? Do you get all of a user's friend/ 
follower id's and then look up their screen names with individual API  
calls? What do you do when a user has more relationships than the API  
limit will allow you to query? And what about users that change their  
screen name? In short, can you provide a bit more background to your  



On Sep 4, 2009, at 11:23 PM, TjL <> wrote:

> caching is the best answer i have found
> On Fri, Sep 4, 2009 at 9:01 PM, dizid<> wrote:
>> Hi,
>> When i request friends (or followers) from the Twitter API i want to
>> get the screen_name's based on the id's.
>> I use users/show for this, inputting the id and getting back de
>> screen_name.
>> This costs ALOT of API calls and i run into the API rate limit fast,
>> especially with many friends.
>> Is there a better way of getting screen_names for friends /  
>> followers?
>> ( Better, meaning in fewer API calls.)
>> Thank you.

Reply via email to