Jun 202012
 
 Posted by on UTC 2012.06.20Wed at 15:24 Google Picasa M5XOUP, pattern flaw|bug LGB4B3  Add comments

M5XSYR: BUG: transferring/moving media (pics,video,etc) between/to-another Google Picasa account mostly impossible http://1.JotHere.com/3302#M5XSYR

  1. M3KEH0: Definition

    1. M5XOG3: for instance https://picasaweb.google.com/<OwnerGoogleAccountNum/>/<AlbumName/>?authkey=<KeyNum/>#<Photo?Num/>
    2. M5XT47: As far as doing this, according to the official docs on this(and additional sites seem to confirm), one can only do it for all the media in an account (in total bulk) and even then the destination account then looses any option to so transfer/move anything out of it.
      1. M5XTH1: Bad Google!
      2. M5XTBH: This is based on the highlighted caveat there,

        Please read this carefully, it’s not the usual yada yada. The account migration can’t be undone, and the Picasa account you transfer your photos and videos to won’t have the option to migrate to another Picasa account in the future.

        1. M5XTJ6: Searching for a fragment of this error message finds ~5 other users complaining about it but no solutions.
      3. M5XTE8: Why this limitation?
        1. M5XTFU: Even though it seems crazy, I can’t find a single source explaining it: Bad Google!
    3. M5XOJF: Problems this cause include, from least to most serious:
      1. M5XTLY: If you do a photo/video shot for someone else or some organization, including using your personal equipment & account that you want to transfer over to a business, you can’t really.
      2. M5XTOB: If you want to transfer media to other accounts to workaround the problem of not exposing your account number, you can’t.
  2. M5XSGO: Workarounds: not looking good

    1. M5XU3X: Via Picasa desktop software, download the media to a local desktop/laptop computer then upload to another account: not looking good.
      1. M5XU6U: Though I haven’t tried (since I’m running Linux which doesn’t support the software), it seems killer painful especially given all the album photo sharing would have to be recreated, as this user posts it would be.
    2. M5XSRY: No other known.

  3. M33Z0T: Additional post history, in order:

    1. M5XSYQ: I create this
      1. M3KNZ6: Why?
        1. M3KO0E: before
          1. M3KOP0: instead of this, what was done
            1. Observed one time but did not create a report
            2. M3KOSW: reached my limit when
              1. M5XTWP: Exploring doing this as a workaround to exposed owner id.
      2. M3KNXM: by:
        1. M37OOV: on (the most similar recent one=http://1.JotHere.com/3298#M5XO9I) latest version M5XSTQ, do Copy to a new draft
        2. M37OP0: then there: created this entry, give this a new ID, then updated content to fit.
    2. M5XUG5Now have a fairly usable, releasable version, so 1st publish.
    3. M7F7CL: Updated to latest header format