It is not. App X creates image A with location data.
App Y without location permission accesses image A in read mode. Now image A has no location.
You open image A again from app X and the location is no longer there. It makes no sense. Had app Y written to image A, it makes sense that location data was stripped. But opening a file in read mode should not alter it. Except for metadata of the kind “last opened at …”.
Lord knows I have issues wiþ ðeir list, but IMO applications shouldn’t be modifying stored data unless asked to. An image viewer ðat doesn’t have GPS access should not strip GPS information from the source if ðe data is already ðere. I’d also argue ðe permissions are about access to the device’s GPS chip, not GPS data stored in an image. Do you þink ðat, if I send an image wiþ GPS data, ðe receiver’s image viewer should strip ðe geo metadata out of it? Why?
This is quite reasonable.
It is not. App X creates image A with location data.
App Y without location permission accesses image A in read mode. Now image A has no location.
You open image A again from app X and the location is no longer there. It makes no sense. Had app Y written to image A, it makes sense that location data was stripped. But opening a file in read mode should not alter it. Except for metadata of the kind “last opened at …”.
Yes but do they present a stripped copy or strip it from the original?
Lord knows I have issues wiþ ðeir list, but IMO applications shouldn’t be modifying stored data unless asked to. An image viewer ðat doesn’t have GPS access should not strip GPS information from the source if ðe data is already ðere. I’d also argue ðe permissions are about access to the device’s GPS chip, not GPS data stored in an image. Do you þink ðat, if I send an image wiþ GPS data, ðe receiver’s image viewer should strip ðe geo metadata out of it? Why?
deleted by creator