Those sites use different authentication mechanisms. For picasaweb you
enter you username (gmail address) and password. These aren't stored,
so you will have to enter them each time you login. For flickr, you
must give phraymd write access to your account. When you click login,
a new browser window will open where you have to confirm flickr access
for phraymd. The flickr credentials are stored persistently in
~/.flickr (this is the default behavior of the flickrapi). Once you
have logged in there is no facility for logging in again with a
different account yet.
After you have chosen service, you can freely drag items from the
browser to the upload queue. The plugin will try to use the images
tags and other descriptive info as appropriate. Select items in the
upload queue to set metadata, album/set to upload to and other
preferences. Click upload to start uploading and stop to stop
uploading. If there is an error, the upload will stop, but don't
expect to see any error messages (yet). The user interface still needs
some polish and there are quite a few bugs/missing features.
*I haven't thought deeply about what the potential security issues
are. The APIs should be taking care of this, but If you are highly
risk averse, don't use this plugin.*
PLUGIN TODO LIST:
* bug: right click multiple selection to remove items from queue
doesn't work -> the selection changes to a single item before the menu
spawns
* ability to add new albums (not just select from the available ones)
* album combo box entry should be album combo box (choose from
available albums or "None" to use default for that service.)
* make "resize to" entry a combo box or some other mechanism to allow
user to choose from standard sizes
* use more informative error messages (upload failures are silent)
* interrupt uploads in progress mid-photo (google api limitation and
just not implemented for flickr)
* facebook and smugmug support
* simplify and tidy the user interface
* support gif and other non-RGB formats (note that RAW should work ok
because it easily converts to jpeg)
* use gnome keyring to store credentials
* track the unique ID that web services assign to the photos (e.g.
store in the XMP) so that user can keep track of what has been
uploaded
* Use the IPTC author field to fill the "credit" on picasaweb (and
whatever is equivalent on flickr)
> Those sites use different authentication mechanisms. For picasaweb you
> enter you username (gmail address) and password. These aren't stored,
> so you will have to enter them each time you login. For flickr, you
> must give phraymd write access to your account. When you click login,
> a new browser window will open where you have to confirm flickr access
> for phraymd. The flickr credentials are stored persistently in
> ~/.flickr (this is the default behavior of the flickrapi). Once you
> have logged in there is no facility for logging in again with a
> different account yet.
> After you have chosen service, you can freely drag items from the
> browser to the upload queue. The plugin will try to use the images
> tags and other descriptive info as appropriate. Select items in the
> upload queue to set metadata, album/set to upload to and other
> preferences. Click upload to start uploading and stop to stop
> uploading. If there is an error, the upload will stop, but don't
> expect to see any error messages (yet). The user interface still needs
> some polish and there are quite a few bugs/missing features.
> *I haven't thought deeply about what the potential security issues
> are. The APIs should be taking care of this, but If you are highly
> risk averse, don't use this plugin.*
> PLUGIN TODO LIST:
> * bug: right click multiple selection to remove items from queue
> doesn't work -> the selection changes to a single item before the menu
> spawns
> * ability to add new albums (not just select from the available ones)
> * album combo box entry should be album combo box (choose from
> available albums or "None" to use default for that service.)
> * make "resize to" entry a combo box or some other mechanism to allow
> user to choose from standard sizes
> * use more informative error messages (upload failures are silent)
> * interrupt uploads in progress mid-photo (google api limitation and
> just not implemented for flickr)
> * facebook and smugmug support
> * simplify and tidy the user interface
> * support gif and other non-RGB formats (note that RAW should work ok
> because it easily converts to jpeg)
> * use gnome keyring to store credentials
> * track the unique ID that web services assign to the photos (e.g.
> store in the XMP) so that user can keep track of what has been
> uploaded
> * Use the IPTC author field to fill the "credit" on picasaweb (and
> whatever is equivalent on flickr)
here is a bug :
Select the Web Upload tab, then Picasa Web Albums (don't login), then
Flickr (don't login), then Pacasa again : you can't use the plugin
anymore (configuration window is empty).
Deselect Web Upload Sidebar is Configure tab and re-select it : web
upload plugins is repaired
On Nov 16, 1:11 am, antistress <thibaut.beth...@gmail.com> wrote:
> > Those sites use different authentication mechanisms. For picasaweb you
> > enter you username (gmail address) and password. These aren't stored,
> > so you will have to enter them each time you login. For flickr, you
> > must give phraymd write access to your account. When you click login,
> > a new browser window will open where you have to confirm flickr access
> > for phraymd. The flickr credentials are stored persistently in
> > ~/.flickr (this is the default behavior of the flickrapi). Once you
> > have logged in there is no facility for logging in again with a
> > different account yet.
> > After you have chosen service, you can freely drag items from the
> > browser to the upload queue. The plugin will try to use the images
> > tags and other descriptive info as appropriate. Select items in the
> > upload queue to set metadata, album/set to upload to and other
> > preferences. Click upload to start uploading and stop to stop
> > uploading. If there is an error, the upload will stop, but don't
> > expect to see any error messages (yet). The user interface still needs
> > some polish and there are quite a few bugs/missing features.
> > *I haven't thought deeply about what the potential security issues
> > are. The APIs should be taking care of this, but If you are highly
> > risk averse, don't use this plugin.*
> > PLUGIN TODO LIST:
> > * bug: right click multiple selection to remove items from queue
> > doesn't work -> the selection changes to a single item before the menu
> > spawns
> > * ability to add new albums (not just select from the available ones)
> > * album combo box entry should be album combo box (choose from
> > available albums or "None" to use default for that service.)
> > * make "resize to" entry a combo box or some other mechanism to allow
> > user to choose from standard sizes
> > * use more informative error messages (upload failures are silent)
> > * interrupt uploads in progress mid-photo (google api limitation and
> > just not implemented for flickr)
> > * facebook and smugmug support
> > * simplify and tidy the user interface
> > * support gif and other non-RGB formats (note that RAW should work ok
> > because it easily converts to jpeg)
> > * use gnome keyring to store credentials
> > * track the unique ID that web services assign to the photos (e.g.
> > store in the XMP) so that user can keep track of what has been
> > uploaded
> > * Use the IPTC author field to fill the "credit" on picasaweb (and
> > whatever is equivalent on flickr)
> Select the Web Upload tab, then Picasa Web Albums (don't login), then
> Flickr (don't login), then Pacasa again : you can't use the plugin
> anymore (configuration window is empty).