Are you going to shut off the S3 URLs immediately or will they still be
accessible for a time? I understand that newly updated avatar images would
not be updated at S3 after the switch but I'd like to know when we can
expect any S3 URLs we may have in our caches to all go dark.

Thanks.

Hayes

On Thu, Jul 9, 2009 at 8:53 AM, Clint Shryock <cts...@gmail.com> wrote:

> I'm still having issues with the profile_image_url attribute of users/show
> updating in a timely fashion, any chance this issue be resolved with this
> update?
> +Clint
>
>
> On Wed, Jul 8, 2009 at 11:55 PM, Doug Williams <d...@twitter.com> wrote:
>
>> Andrew Stone asked a great question off list and I wanted to share the
>> answer here.
>>
>> Images will be hosted from a number of sub-domains of twimg.com.
>> Therefore you should not expect all images to be served from a0.twimg.comas 
>> in the examples provided, but instead should expect an aribitrary
>> sub-domain (*.twimg.com).
>>
>> Thanks,
>> Doug
>>
>>
>> On Jul 8, 2009, at 6:20 PM, Doug Williams <d...@twitter.com> wrote:
>>
>> Folks --
>> We are going to be moving images to a new domain ( <http://twimg.com>
>> twimg.com) to streamline our image hosting and offer better performance.
>> We hope this will have limited impact as will only change the image URL.
>> Example URLs include:
>>
>> Profile images:
>>
>>
>> <http://s3.amazonaws.com/twitter_production/profile_images/35240332/2929920.gif>
>> http://s3.amazonaws.com/twitter_production/profile_images/35240332/2929920.gif
>>
>> <http://a0.twimg.com/profile_images/35240332/2929920.gif>
>> http://a0.twimg.com/profile_images/35240332/2929920.gif
>> Background images:
>>
>>  
>> <http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg>http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>>
>>  
>> <http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg>http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
>>
>> Thanks,
>> Doug
>>
>>
>>
>

Reply via email to