Infeasible
Status Update
Comments
jf...@google.com <jf...@google.com> #2
Thanks for filing this feature request!
Unfortunately this is not a use case the Google Photos Library API is designed for and this is not something that is currently on our roadmap.
If you know the specific date, you might be able to do this through a search in the Photos app.
Otherwise, you can also check the Google Photos help community and ask your question there:https://support.google.com/photos/answer/6156065?hl=en&ref_topic=6156079
Unfortunately this is not a use case the Google Photos Library API is designed for and this is not something that is currently on our roadmap.
If you know the specific date, you might be able to do this through a search in the Photos app.
Otherwise, you can also check the Google Photos help community and ask your question there:
ni...@gmail.com <ni...@gmail.com> #3
I've played with the Google Photos API today and I'm disappointed because API cannot access or do all features of the Google Photo webapp.
In my case, I want to remove a compressed photo (from Android backup feature that compress the picture) to replace it with the original photo (like current backup).
In my case, I want to remove a compressed photo (from Android backup feature that compress the picture) to replace it with the original photo (like current backup).
ka...@gmail.com <ka...@gmail.com> #4
Please reconsider this decision,
The need to delete / move to recycle-bin will increase more and more with storage limitation imposed with June 2021. Many customers, including me, are reconsidering alternatives for storage of photos.
Best Regards,
Ionut C.
The need to delete / move to recycle-bin will increase more and more with storage limitation imposed with June 2021. Many customers, including me, are reconsidering alternatives for storage of photos.
Best Regards,
Ionut C.
0....@gmail.com <0....@gmail.com> #5
Not allowing API access to remove photos limits users' ability to use 3rd-party tools to help them manage their private data... which is a big red flag. The ability to easily get rid of private data on someone else's servers en masse is crucial for reducing the attack surface for identity theft, revenge porn, etc.
ku...@gmail.com <ku...@gmail.com> #6
The fact that this feature hasn't been reassessed and added to the api, in the last 4 years is utterly indefensible, unless someone at google thinks that a person's personal data somehow becomes google''s property.
pe...@mac.geek.nz <pe...@mac.geek.nz> #7
Google, this deliberate attempt to hold my data hostage only makes me more insistent on moving it elsewhere
Ja...@waters.com <Ja...@waters.com> #8
I am going to have to stop using google photos over this. Either need to give API functionality to delete photos, or google photos needs to appear as a folder on drive as it once did. This lack of flexibility is killer.
br...@gmail.com <br...@gmail.com> #9
I really want to use those apps that help you identify and remove junk photos cluttering up your library. Without this feature, my use case is null since all my photos are backed up to Google Photos. Please let us manage our libraries more efficiently.
te...@gmail.com <te...@gmail.com> #10
Please!! This is nuts!! We should be able to decode on our own if we allow a 3rd party to access our photos, not Google! I'm worth the others here so say this is a deal- breaker.
al...@deusto.es <al...@deusto.es> #11
Marking this issue as "Infeasible" (ha!) means no more Google Photos for our Workspace accounts. We cannot delete that storage usage without deleting the account, so we are not letting it be an issue in the first place anymore.
ca...@gmail.com <ca...@gmail.com> #12
Just to confirm. A photo my application has just uploaded cannot trash it a few minutes later?
br...@gmail.com <br...@gmail.com> #13
Please reconsider this decision. The ability to properly manage our historical archives with third party tools is invaluable. Allowing innovation through API support can assist Google Photos with becoming the standard for cloud hosted image management. Don't let Apple beat you to the punch on this one.
ph...@gmail.com <ph...@gmail.com> #14
Voicing hope this can be reconsidered. A generally positive experience around my Google Photos library is the biggest thing keeping my from moving to iOS. With the trajectory of storage caps, purposefully limiting data access/control forcing unmanageable collections, and a feeling that Google views user's photo libraries as a padlock to keep user in the ecosystem, I'm going to need to jump ship before that padlock traps me forever. If this continues, I can't see myself continuing to be a satisfied Google Photos user in 5 years from today, which means I need to start exiting the ecosystem now-ish. =(
is...@gmail.com <is...@gmail.com> #15
I'm removing my photos from Google photos over this instead of paying for yet more storage. Happy to pay for storage that I need but the inability to easily delete what doesn't need stored means you're just cash grabbing for Google One fee's.
Description
Photos API is missing functionality to delete photos or to organize/move photos into folders. If deleting photos from API is considered "dangerous", maybe implement it as a move to a "trash" folder (then user can recover the photos).
What is the purpose of this new feature?
Note that delete/move functionality is already present in android photos app. Lack of public api for deleting/moving photos limits usability.
Please provide any additional information below.
I have a particular use case. A while ago I imported my photo collection to google photos. Due to a bug in google importer at the time, a large number of photos were imported at very low resolution. I'd like to clean up my collection on google photos by going through the photos and re-uploading photos at the proper resolution. Due to large number of photos, it's not possible to do manually.