Right now we are using the method:

http://twitter.com/friends/ids.json

to get a user's friends, but it doesn't have the friend's screen_name,
which is obviously how users identify their friends. So what we are
currently having to do, is store the id's in our database then loop
through and use the method:

http://twitter.com/users/show/<id>.json

to figure out the screen_name associated to the id, and store that in
our system as well. This is a failed system because users can change
their screen names and it burns through API requests to fast.

API DEV TEAM: anyway you guys can add screen_name in the response for
the method http://twitter.com/friends/ids.json?

That would solve this issue.

If I'm missing something obvious, or if anyone has a better approach
please reply. Thanks!

Reply via email to