4 ms·
Unfortunately these OS level privacy countermeasures are trivial to circumvent. Instead of checking for [photo permission denied] or [camera permission denied]
by schiffern 10y ago
Unfortunately these OS level privacy countermeasures are trivial to circumvent.
Instead of checking for [photo permission denied] or [camera permission denied], on supported OS versions the app can check for [empty image list] or [black camera image]. Then display the impenetrable wall, or disable the goodie, or lock out the content because it can't verify that there are N or fewer viewers, or...
- logicallee 10y agoI addressed this explicitly: an advanced user could create fake contacts, take or upload fake photos (for example, I might not care about EXIF data), create fake SMS's. How should an app determine the difference between a user with a new phone with few or no SMS's, and a user who has chosen to fake a few or no SMS's? More to the point, the phone could simply generate fake content algorithmically, and these algorithms could change all the time. How would an app keep up? If it helps you think about it, at this point the phone is the bot and the App is the one trying to keep a bot from successfully using its API. Surely possible, but not "trivial".