On Sat, Feb 28, 2009 at 8:50 AM, Alex <aybarb...@gmail.com> wrote: > The only way I can think of offhand to fetch the profile is via the > users/show call, i.e. > http://twitter.com/users/show.xml?user_id=12345 > > Is there an easier way to do this? Ideally a way that does not > require user authentication? That doesn't require user authentication, but it is rate limited by IP.
> Alternatively, would you consider adding an option for the social > graph calls to return actual usernames instead of the user_id? It's been requested but they can't do it without killing performance. See http://code.google.com/p/twitter-api/issues/detail?id=265 > I forgot that we could just fetch their profile via HTTP GET such as: > http://twitter.com/users/show/12667242.xml > > Do queries such as this count towards the max limit per IP per hour? Yes. In general, GET requests do count, but POSTs do not. You can also apply for whitelisting here by describing to Twitter what your app does: http://twitter.com/help/request_whitelisting -damon -- http://twitter.com/damon
