31–40 of 62 posts
This is exactly why even as a programmer I don't own pretty much any tech crap at all. No cloud connected home automation, photo frames, voice assistant, smart lock, wifi washing machine, nothing. The whole industry is just too brittle and unreliable and your money will evaporate the moment some product manager doesn't want to schedule a bug fix and kills the product instead because it's easier than meeting the promi…
Earlier quoted context omitted.
You can change to archive size to 50GB per file.
Only on TGZ files, not zip, which maxes out at 4GB. (This is not because of a file size limitation. The only way to get 4GB is through zip64, which has a file size limit measured in exabytes.)
Good, more security and better controls means third-party apps cannot simply scrape all of my photos.
If I authorize an app to scrape an entire album, that’s a good thing. This isn’t more security, this is google attempting to squeeze more monetization.
Earlier quoted context omitted.
Wouldn't using Google Takeout do that already? I thought that was the point, to take out your data?
Have you ever used takeout? You get 33 1GB chunks in a link sent via _EMAIL_ that then I have to click on and authenticate in my browser. 33 clicks.
Oh ffs, I just migrated my entire extended family to Google Photos for my elders' picture frames (it was the only option which didn't involve a steeply priced subscription to their service; by the way I was not involved in acquiring these frames in the first place). I'll eat my hat if they get a firmware update.
This is exactly why even as a programmer I don't own pretty much any tech crap at all. No cloud connected home automation, photo frames, voice assistant, smart lock, wifi washing machine, nothing. The whole industry is just too brittle and unreliable and your money will evaporate the moment some product manager doesn't want to schedule a bug fix and kills the product instead because it's easier than meeting the promi…
Earlier quoted context omitted.
The picker API limits access to selected photos. It doesn’t look like there is an API for “all current and future photos from an album”, which is the problem (from integrators’ perspective)
Does it? From Google's own docs, it seems tremendously unclear. But from the official page it says [1]: > For example, if your asking your users to share a specific album, you could include the following text on the same page your users connect to Google Photos: "Connect to Google Photos, then search for the album you want to share." This suggests that users are able to share a specific album that shares all photos w…
https://developers.google.com/static/photos/images/picker-pi...
They also clarify this in the documentation: "Albums, favorites, and other common photos categories are not show [sic] directly. Users can search for photos using various criteria, such as keywords, dates, locations, and album titles"
The user can search for album names, but only the images from those albums are shown, and users can only select individual images. In the screenshots, you can also see that it shows that you can only select up to 2000 images. And you can see in the docs that only Image, Video and Motion type files are returned—there's no album reference that you can grab, and the URLs for these files expire after 60 minutes: https://developers.google.com/photos/picker/guides/media-ite...
Earlier quoted context omitted.
Only on TGZ files, not zip, which maxes out at 4GB. (This is not because of a file size limitation. The only way to get 4GB is through zip64, which has a file size limit measured in exabytes.)
Just... get the TGZ then?
Also, the fact that they don't mention this difference- the UI is so poorly done that you can only tell that TGZ can go an order of magnitude larger after selecting it in one drop-down and then looking at the other drop down- is a sign of how Google wants to make this as difficult as possible.
Earlier quoted context omitted.
Does it? From Google's own docs, it seems tremendously unclear. But from the official page it says [1]: > For example, if your asking your users to share a specific album, you could include the following text on the same page your users connect to Google Photos: "Connect to Google Photos, then search for the album you want to share." This suggests that users are able to share a specific album that shares all photos w…
No, if you look at the screenshots on that page it's clear that when they mention albums, they're only talking about the search experience, not the picking experience: https://developers.google.com/static/photos/images/picker-pi... They also clarify this in the documentation: "Albums, favorites, and other common photos categories are not show [sic] directly. Users can search for photos using various criteria, such as…
If Google really has removed the ability to share all photos from a picked album, that's so idiotic I just don't get it. I don't see what possible benefit there is to security or to Google here. Why would Google screw over users for no reason at all? Companies generally remove features for a strategic reason. They don't upset consumers just for the fun of it.
Also, their blog post [1] clearly states, emphasis mine:
"The Picker API offers a secure and intuitive way for users to search for and select photos and albums through a seamless integration with the Google Photos app."
Does anyone have a link to the actual picker in action? And if it's missing selecting an album, is this intentional or an oversight that will be quickly corrected?
[1] https://developers.googleblog.com/en/google-photos-picker-ap...
