4 ms·
This definitely sounds like a bug worth tracking down. If you're interested in using your account as example, it would be helpful to file in-app feedback includ
by subsonicswe 6y ago
This definitely sounds like a bug worth tracking down. If you're interested in using your account as example, it would be helpful to file in-app feedback including at least the following two things:
1. "I grant permission to look at my account metadata to debug this issue"
2. An easily searchable tag like #OriginalSetting
- posguy 6y agoWill this result in the problem getting addressed? Google likely assigns these preference quirks to be low priority bugs, which when combined with an under-resourced, unprofitable/breakeven service means it will be eternally neglected.
- subsonicswe 6y agoThat's a lot of speculation. Why wouldn't Google care about losing user data? Especially for such an important setting.
- computerphage 6y agoBecause not caring is the default?
- verytrivial 6y agoThe shipped has LONG sinced sailed on my expecting Google to fix Photos in this regard. I've spent literally YEARS dealing with this Photos shortcoming. They have all the information they need. And even if they fixed it, I've already spent the hours sifting through my repeated Google Take Away downloads and hacking Python scripts to dedupe / etc the issue. Seriously, the support channel reps were saying things like "Oh, just delete all your images then upload again from originals". But what about tagging, meta data, albums, and so on? And how do I know which of the thousands of pictures need this rough handling? "Shrug!" They don't CARE! It's just another data-bucket to them. Summary: Anyone who cares about the fidelity of their images has long ago stopped using Google Photos. So, as I say, use another photo service and treat Google Photos like a cruddy, light-touch 'microfiche' of your pictures: better than nothing.