I was just thinking in terms of reducing the upload bandwidth and
duplicate storage of images.
I'm not sure how useful it would be as a third-party app but I might
give it some thought.
Dave Kinsella
http://twitter.com/Techn0tic
On Apr 27, 6:54 pm, Doug Williams d...@twitter.com wrote:
This is not an enhancement that would likely be made to the API itself. Have
you thought about making this as an application that other developers could
use? All of this functionality could be contained within a third-party app.
Thanks,
Doug Williams
Twitter API Supporthttp://twitter.com/dougw
On Mon, Apr 27, 2009 at 2:39 AM, DaveK kinsella.d...@googlemail.com wrote:
Just kind of thinking aloud here.
I was thinking about the bandwidth overhead for applications which use
the API to set avatar or profile background images and had an idea.
How about allowing an application to register an uploaded image with
some sort of id or handle and then be able to set the avatar or
background image to that id?
e.g.
app foobar uploads an image and registers it as bg1
it can then make calls to update several accounts and set the profile
background image to foobar:bg1 or similar.
