We would prefer large applications to cache and serve images locally to offload our operation costs. However, for smaller applications and development efforts, serving from the S3 URL provided with the API is acceptable.
Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Thu, Apr 30, 2009 at 4:03 AM, Christian Fazzini < [email protected]> wrote: > > Hello all, > > Im am currently making a website that uses the twitter api. I am able > to obtain the background image of my twitter profile using the url > http://twitter.com/users/show.xml?screen_name=screen_name_here > > Which returns something like this: > http://static.twitter.com/images/themes/theme1/bg.gif > > On my website, I am wondering if I should save this background image > onto my own database and loat it from my server or load it directly > from the twitter website. > > I am thinking that the 'friendliest' way is to save the image onto our > server and load it from there. This way, we dont have to use Twitter's > bandwidth everytime. > > What are your opinions on this? > > > >
