• falkerie71@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    2 months ago

    Not entirely disagreeing with you but, what exactly is “malicious” about separating photo and metadata? It could be just how their servers process and stores those photos, with the added benefit of geotagging videos.

    I use Google Photos and upload in original quality. When I download from takeout, the metadata is still in the original files. Iirc, only if you select upload in “high quality” where they compress it again, do you lose the metadata in the file stored in the cloud.

    • abrahambelch@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      2 months ago

      When you re-import the images into another program/library, they will not be displayed in the correct order and all other information will be lost as well.

      Metadata in general is very useful and contains a lot of valuable information like location data, lens, focal length and device information which you have to manually re-integrate into each and every photo.

      I mean yes, I could write a quick and dirty Python script for this, but why should I have to do this in the first place?

      In my subjective opinion this is malicious as in it only being this way to make it as hard as possible to migrate away. I highly doubt this is the way their servers store the images as it is very inefficient and the images are likely stored in a database instead. This means in order to retrieve a file they have to process each image anyway, so why not follow the universally accepted and well defined standard and include the metadata in each file?

      • falkerie71@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        Fair. I guess I never really needed to deal with that since I upload in original. That and Google Photos Takeout Helper made migrating easy for me.