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 regula
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 jus
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 infrastr
jstrellner wrote:
> I don't think they should do anything, but ask you guys to cache the
> profile pictures yourself. By linking directly to the file, you are
> increasing their Amazon costs. It doesn't take much to cache it
> yourself, and then every time someone does an update, you just check
Just set the profile image as "USER_ID.jpg" so that no mater what they
use for their image it will always be a unique file name to the user.
We are developing an iPhone application which among other things
aggregates content from different social networks to create a pulse
view.
Given the bad tools for memory management on the iPhone, cached photos
are quickly swapped out so this solution is our temporary one but
still requires a fix
The changing URLs have been an asset for quick cache expiry for us,
but I understand that more predicable URLs would be easier for
developers. We'll consider changing this behavior in the next major
release of the API, but it's not going to change in the current
version.
I would suggest caching
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 p
I don't think they should do anything, but ask you guys to cache the
profile pictures yourself. By linking directly to the file, you are
increasing their Amazon costs. It doesn't take much to cache it
yourself, and then every time someone does an update, you just check
to see if the old URL that
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_prod
Kee Hinckley wrote:
>
> On Oct 8, 2008, at 7:25 PM, Nicolas Grasset wrote:
>> Is there a way to get a static profile picture URL when using the API,
>> since picture updates will break old links?
>
> That would really be nice. Given the security checks you have to do
> when you use the user-provi
On Oct 8, 2008, at 7:25 PM, Nicolas Grasset wrote:
Is there a way to get a static profile picture URL when using the API,
since picture updates will break old links?
That would really be nice. Given the security checks you have to do
when you use the user-provided filename, it seems like sta
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/profile_images/38643882/avatar_bigger.JPG
... will have a different URL if I change it on Twitter, which means
we cannot trust o
13 matches
Mail list logo
