Hacker News new | ask | show | jobs
by keyboardP 4880 days ago
I think you're conflating two very different scenarios. Someone saying "I'm in San Francisco" or posting a picture of them at the Golden Gate Bridge is clearly aware that their location can be determined. EXIF data hidden within a JPEG file is not so clear cut and most users are unlikely to be aware of it.

As you said, Location Services and Photo access are different permissions. Users are therefore likely to assume that location data is not being retrieved if they deny permission to it. If I deny location data to an app, it's because I don't want that app to have my location data. It seems somewhat underhanded, to me at least, to assume that the user wouldn't mind me accessing location data from their photos, knowing full well that the majority of users will not know what EXIF data is. I'd go so far as to say that I would explicitly ask the user if EXIF data should be read alongside the standard location services.

1 comments

But really, you're the one speculating that a user's intent is different than what their explicit actions on the phone indicate. You're guessing that a user is not aware that photos are geotagged, despite that fact that the Location Services permission is optional on the Camera app as well.
Judging by the post we're commenting on, it's not exactly a shot in the dark guess. Technically, Path has done nothing wrong. They've been given permission to the photos and that's what they're accessing with all the information it brings.

But, to me, if I was told that my app can't access location information, I would assume that it's because the user doesn't want my app to access location information and have my app run with that mindset.

You want your iPhone's camera to access location for one app, but not for another. What would you do? What you're saying is that the user has no choice and it's all or nothing. Give location data to all apps requiring photos or disable it completely.