Unfortunately this approach makes you quite unique for fingerprinting
not if its an os feature.
When an app asks for permissions, it should have a “feed fake data” option
21–30 of 413 posts
Re: When an app asks for permissions, it should have a “feed fake data” option
#22> Every category should have a "yes, but feed the app fake data" option.
I would prefer it to be per app and not category. I may not want to feed positional data to pretty much everything but Google Maps and any app that calls for help in case of emergency. Same for contacts, personal data etc. I'd however expect an app like that to meet fierce resistance from Google and other businesses that profit from users profiling.
Re: When an app asks for permissions, it should have a “feed fake data” option
#23XPrivacy for rooted android could do this 7+ years ago and there are other modern alternatives (but I haven't rooted my phone for a long time so I can't vouch for them): https://github.com/M66B/XPrivacy Obviously that is not mainstream, I agree it should come built in. But then both Android and iOS allow bullshit like region-locked apps or preventing screenshots from DRM content, so good luck with that.
I used it in this way, and experiencing first hand how much the deck was stacked against me as a user let to me abandoning any belief that phones are computers.
They are vendor content delivery devices and you are at their mercy.
Re: When an app asks for permissions, it should have a “feed fake data” option
#24Unfortunately this approach makes you quite unique for fingerprinting
I don't think this assessment is correct. No one said completely random data. It certainly could make fingerprinting possible (or, easier than no spoofing at all) if the right considerations are not taken.
Re: When an app asks for permissions, it should have a “feed fake data” option
#25XPrivacy for rooted android could do this 7+ years ago and there are other modern alternatives (but I haven't rooted my phone for a long time so I can't vouch for them): https://github.com/M66B/XPrivacy Obviously that is not mainstream, I agree it should come built in. But then both Android and iOS allow bullshit like region-locked apps or preventing screenshots from DRM content, so good luck with that.
This would never land in a factory image or upstream Android, but it has a reasonable chance to become part of projects like LineageOS, given enough user demand for it.
Re: When an app asks for permissions, it should have a “feed fake data” option
#26XPrivacy for rooted android could do this 7+ years ago and there are other modern alternatives (but I haven't rooted my phone for a long time so I can't vouch for them): https://github.com/M66B/XPrivacy Obviously that is not mainstream, I agree it should come built in. But then both Android and iOS allow bullshit like region-locked apps or preventing screenshots from DRM content, so good luck with that.
>region-locked apps
There is no such thing. The respective app stores allow you to distribute apps in select regions. This is an important feature for app stores because an app may not be a good experience in all countries. The app may not be localized to all languages, there may not be content moderators for those languages, those countries have a multitude of laws that you need to comply with, your app may include copyrighted content which is only licensed to be distributed it certain countries, etc..
>preventing screenshots from DRM content
This is a feature requested app developers due to the legal requirements when licensing content such as movies. Movie studios don't want people streaming or recording their movies so app platforms need a way to surely show this content.
Re: When an app asks for permissions, it should have a “feed fake data” option
#27I’m all for the “fake data” idea, but also: Apps should be required to gracefully handle the cases where users deny permission to access real data. I know last time I developed for iOS, it was Apple’s policy that apps cannot punish users or exit() the app in retaliation for them denying a permission. Apps must gracefully handle it and continue running.
Also, and this was even longer ago, apps could not require users to have “an account” in order to run. I remember (this was over a decade ago) my company making a product change that forced users to have an account in order to function and we got (rightfully) rejected by the AppStore for this. It seems they must have softened this stance because I am seeing more and more apps that require an account to function.
Re: When an app asks for permissions, it should have a “feed fake data” option
#28> When an app asks for permissions, the OS should not only let you answer yes or no. Every category should have a "yes, but feed the app fake data" option. A significant amount of people don’t even know how to forward an email. Imagine the havoc that would ensue when people try to use Google Maps for navigation, and they choose to feed it fake data because they don’t understand what it means. Google Maps: “Turn right…
Do a lot of people use Google Maps on iOS? I ask because the “feed fake data” option is something I could imagine Apple doing but never in a million years would I believe Google would do it. Apple Maps wouldn’t have this issue. It’s capable of running offline (without a data connection) because it can download maps to the device.
a lot of people do, for example me. apple maps sucks badly where i live (eu). say, it has no idea my house (built 6 years ago) exists, it builds routes via non-existing roads, is not aware of road works, detours or most of the businesses around
apple maps is completely useless here, even though i don’t like using a google app, there’s no alternative
Re: When an app asks for permissions, it should have a “feed fake data” option
#29As an app developer I do not like this idea. You want to break the contract on what that permission is intended to be.
("Weather the Trip" road trip weather app for the U.S.)
Re: When an app asks for permissions, it should have a “feed fake data” option
#30Unfortunately this approach makes you quite unique for fingerprinting
> Unfortunately this approach makes you quite unique for fingerprinting
As opposed to sharing your actual latitude,longitude and microphone readings?