Custom Query (1173 matches)
Results (46 - 48 of 1173)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1053 | fixed | API Image object height/width attributes missing | ||
Description |
Image containers in the API Image object doesnt have width/height attributes current: { u'fullImage': { u'url': u'gmg.tld/path/123.png' }, u'image': { u'url': u'gmg.tld/path/123.thumbnail.png' } } expected: { u'fullImage': { u'height': 128, u'width': 256, u'url': u'gmg.tld/path/123.png' }, u'image': { u'height': 32, u'width': 64, u'url': u'gmg.tld/path/123.thumbnail.png' } } |
|||
#1049 | fixed | API Location object should have 'displayName' attribute | ||
Description |
API Location object should have the 'name' attribute renamed to 'displayName'
current:
expected:
|
|||
#27 | fixed | API Support for Mobile Uploads | ||
Description |
This might be a bit broad and/or already considered elsewhere, but having API support to upload media from third-party clients (especially on mobile computers) would be a killer feature. For example, on my N900, Maemo has share plugins which support Flickr, Twitpic, etc., and integrate well into the build in camera software. StatusNet implemented the Twitter API to allow for broad support, but I'm only familiar with Flickr, not so much Picasa or Deviant Art or other platforms. Would it make sense to implement (parts of) the Flickr API here to benefit from that same kind of support? Is there another API to consider? Or does it make more sense to create something new? `http://www.flickr.com/services/api/ <http://www.flickr.com/services/api/>`_ The feature request end goal is having some kind of API support for third-party upload clients, especially on mobile devices. Not sure if this has been considered, or what the best way to do this is. |