Profile avatars with AWS S3 versioning
Abraham Williams
--
Abraham Williams | Community Advocate | http://abrah.am
Project | Out Loud | http://outloud.labs.poseurtech.com
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States
Andrew Badera
+1
--ab
Wynn Netherland
---
Wynn Netherland
blog: http://wynnnetherland.com
twitter: pengwynn
skype: pengwynn
linkedin: http://linkedin.com/in/netherland
Abraham Williams
Eric Woodward
Browsers are not the only thing to consider. If a standard URL is used
that never changes a desktop or mobile client will not know it has
changed. I will have to redownload it now and again to be sure, or
manually track and check these cache headers myself, which is
annoying.
Adding payload to the user object in the API response with the last
timestamp the avatar was changed would make it dead simple to know if
you have the latest one (already downloaded) or not. In my mind, this
is the proper solution that should have been implemented years ago.
These avatar issues have been an issue since day one, and no one at
Twitter has ever seemed to mind much (or it would have been fixed long
ago). They do have bigger ongoing problems, I will grant.
--ejw
Eric Woodward
e...@nambu.com
On Apr 5, 9:19 am, Abraham Williams <4bra...@gmail.com> wrote:
> There is now a petition going to get screen_name based profile_image_urls:http://act.ly/1vk
>
> Abraham
>
>
>
>
>
> On Fri, Feb 12, 2010 at 19:03, Andrew Badera <and...@badera.us> wrote:
> > On Fri, Feb 12, 2010 at 10:02 PM, Abraham Williams <4bra...@gmail.com>
Raffi Krikorian
our infrastructure - we want to allow rapid changing data to be
present (and accurate) in our user representations. When that update
is put in place, attempting to correct profile images is on our list.
> --
> To unsubscribe, reply using "remove me" as the subject.