Lukas,
Thank you for the pointer to and the effort put into creating the WADL
and WSDL.
I'm new to the group, and to Twitter for that matter, but I'm somewhat
surprised that there aren't an official WADL and WSDL for the service.
Or any other complete specification that I can find. Am I missing
We should also consider the user experience. Some of my friends
change their avatar daily (if not hourly). If each application caches
the avatar, the user might end up with a different avatar on each
application. That would especially apply to applications that do not
need to update data
Carl: They provide the URL to the image in all of that users updates,
so if you are getting tweets for a user, you are getting their profile
picture (avatar) URL. It shouldn't require any additional calls.
Alex: Any easy way to appease everyone who needs to access it, without
doing any
On 10 Oct 2008, at 10:26, jstrellner wrote:
Alex: Any easy way to appease everyone who needs to access it, without
doing any infrastructure changes on your part, is to add a new API
call, http://twitter.com/statuses/user_avatar/username (for example).
Then when someone requests that URL, you
I have a case where I am calling http://twitter.com/statuses/friends
and http://twitter.com/statuses/followers on the same user to discern
who is a friend, follower or mutual. There seems to be something wrong
with the data that is returned because some people who are mutually
following are not
