Most likely: actually using the geolocation is an extremely niche usecase for images uploaded from mobile browsers. I’d wager 99.9% of the users didn’t realize that they are effectively sending their live GPS coords to a random website when taking a photo. But yes, a prop to the input tag ’includeLocation’ which would then give the user some popup confirmation prompt would have been nice
My first eye-opening moment working within the government was with team of herpetologists at the state conservation agency. They had a pretty slick public education campaign around protecting Gopher Tortoise habitats and a grand call-to-action "let the agency know where and when they see their nests". The whole thing fell apart because they were getting tons of earnestly-submitted junk data from earnestly-engaged cit…
Android now stops you sharing your location in photos
151–160 of 330 posts
Re: Android now stops you sharing your location in photos
#152Earlier quoted context omitted.
> I’d wager 99.9% of the users didn’t realize that they are effectively sending their live GPS coords to a random website when taking a photo. I'd wager 90% of the photos on Google Maps associated with various listings don't actually know their photos are in public. I keep coming across selfies and other photos that look very personal, but somehow someone uploaded to Google Maps, the photo is next to a store or somet…
I suspect there used to be a flow which was far too easy to share directly to Google maps. I was browsing the map once and found a picture of a credit card in a room in a hotel. I guess the guy intended to send it to his PA or something.
Re: Android now stops you sharing your location in photos
#153Earlier quoted context omitted.
Wait... You post selfies on Google Maps? The thought never crossed my mind. What would the purpose be? Sorry I'm probably thick...
For that sweet local guide score.
What exactly does that mean though? Is there any benefits to it? All I see is a badge/label, that's it?
Re: Android now stops you sharing your location in photos
#154Most likely: actually using the geolocation is an extremely niche usecase for images uploaded from mobile browsers. I’d wager 99.9% of the users didn’t realize that they are effectively sending their live GPS coords to a random website when taking a photo. But yes, a prop to the input tag ’includeLocation’ which would then give the user some popup confirmation prompt would have been nice
> actually using the geolocation is an extremely niche usecase for images uploaded from mobile browsers Is it only for mobile browsers? The article makes it sound [0] as if it is a general thing, even when sharing through bluetooth, and that only copying the image via usb connection allows you to keep geolocation in exif. Not sure what happens when you upload to native apps, eg to some cloud storage app (photo specif…
Can you compress a folder with a photo it and then email that? Just curious.
Re: Android now stops you sharing your location in photos
#155Earlier quoted context omitted.
The path is different than the filename though. If I want to find duplicates, it will be impossible if the filename changes. In my use case /User/user/Images/20240110/happy_birthday.jpg and /User/user/Desktop/happy_birthday.jpg are the same image.
> it will be impossible if the filename changes. Not impossible, just different and arguably better - comparing hashes is a better tool for finding duplicates.
Re: Android now stops you sharing your location in photos
#156Re: Android now stops you sharing your location in photos
#157Earlier quoted context omitted.
My first eye-opening moment working within the government was with team of herpetologists at the state conservation agency. They had a pretty slick public education campaign around protecting Gopher Tortoise habitats and a grand call-to-action "let the agency know where and when they see their nests". The whole thing fell apart because they were getting tons of earnestly-submitted junk data from earnestly-engaged cit…
iNaturalist is great for stuff like this as it allows organizations to create projects for data collection on specific species.
Re: Android now stops you sharing your location in photos
#158In a similar move (silently changing a feature crucial to some users), in Android 11 Google suddenly removed the possibility to use "special" characters ": ?|\* in filenames[0], presumably because they're not allowed on Windows/NTFS and Windows users might end up struggling to transfer them to their Windows computer. I don't care about NTFS at all, though. I just want to be able to sync all my files with my Linux mac…
Re: Android now stops you sharing your location in photos
#159This is a common approach to "privacy" taken by orgs like Google. You don't get to access or export your own data in order to protect your privacy, but Google still gets 100% access to it. Some messaging apps do the same and won't let you take a screenshot of your own conversations. Like, someone sent me an address, but I can't take a screenshot to "protect my privacy".
I'm sure it's given some businesses the confidence to invest in iOS app development, but it felt bad.
Re: Android now stops you sharing your location in photos
#160Most likely: actually using the geolocation is an extremely niche usecase for images uploaded from mobile browsers. I’d wager 99.9% of the users didn’t realize that they are effectively sending their live GPS coords to a random website when taking a photo. But yes, a prop to the input tag ’includeLocation’ which would then give the user some popup confirmation prompt would have been nice
On that point I would agree - I never used that. But Google also lied why it wanted to destroy ublock origin. It was clear to everyone that they did it because people can break away from ads infiltrating their computers. I can't use the modern www anymore without general content blocker; ublock lite is good but nowhere as useful as ublock origin was. I notice this when I compare e. g. firefox with default chrome. So…
I have not seen an ad in years.