, but it probably is the best solution to cache it, and one
that Twitturly uses.
-Joel
On Oct 8, 4:25 pm, Nicolas Grasset [EMAIL PROTECTED] wrote:
Is there a way to get a static profile picture URL when using the API,
since picture updates will break old links?
My
photo:http://s3
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 agree too. This request could really cut down on API calls.
On Oct 8, 4:25 pm, Nicolas Grasset [EMAIL PROTECTED] wrote:
Is there a way to get a static profile picture URL when using the API,
since picture updates will break old links?
My
photo:http://s3.amazonaws.com/twitter_production
http://code.google.com/p/twitter-api/issues/detail?id=117
On Oct 9, 9:03 am, Shannon Whitley [EMAIL PROTECTED] wrote:
I agree too. This request could really cut down on API calls.
On Oct 8, 4:25 pm, Nicolas Grasset [EMAIL PROTECTED] wrote:
Is there a way to get a static profile picture
to
their files, but it probably is the best solution to cache it, and one
that Twitturly uses.
-Joel
On Oct 8, 4:25 pm, Nicolas Grasset [EMAIL PROTECTED] wrote:
Is there a way to get a static profile picture URL when using the API,
since picture updates will break old links?
My
-linking to
their files, but it probably is the best solution to cache it, and one
that Twitturly uses.
-Joel
On Oct 8, 4:25 pm, Nicolas Grasset [EMAIL PROTECTED] wrote:
Is there a way to get a static profile picture URL when using the API,
since picture updates will break old links
