When an app asks for permissions, it should have a “feed fake data” option
mastodon.gamedev.place
When an app asks for permissions, it should have a “feed fake data” option
1–10 of 413 posts
Re: When an app asks for permissions, it should have a “feed fake data” option
#2> 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”
Guy driving alongside the ocean: “ok”
Car: *splash*
Re: When an app asks for permissions, it should have a “feed fake data” option
#3XPrivacy 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.
Re: When an app asks for permissions, it should have a “feed fake data” option
#4> 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…
This is an entirely UX problem then. You could bury the data faking deep in the settings, clearly explain what it does in plain language before enabling it as well as plainly telling the user onscreen that the application is being fed information for privacy reasons that they themselves enabled (and can easily disable).
There is always someone who will end up enabling this erroneously, but it would provide a lot of value to a lot of users that didn't.
Re: When an app asks for permissions, it should have a “feed fake data” option
#5This wouldn't stem the requests; it would just lead to data analysts figuring out how to algorithmically filter the junk data.
... which is fine. Incentives to refine data analysis are always welcome.
Re: When an app asks for permissions, it should have a “feed fake data” option
#6> 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…
This is an entirely UX problem then. You could bury the data faking deep in the settings, clearly explain what it does in plain language before enabling it as well as plainly telling the user onscreen that the application is being fed information for privacy reasons that they themselves enabled (and can easily disable). There is always someone who will end up enabling this erroneously, but it would provide a lot of v…
The people who are savvy enough to jump through those hoops are savvy enough to rock a phone that is modded to feed fake data already.
Re: When an app asks for permissions, it should have a “feed fake data” option
#7> 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…
Then make the setting a power-user opt-in, so that the uninitiated wouldn't even see the option.
Re: When an app asks for permissions, it should have a “feed fake data” option
#8> 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.
Re: When an app asks for permissions, it should have a “feed fake data” option
#9I really wish browsers would take this approach with notifications.
If a website asks if I have notifications enabled, tell them yes, and send them all into the oblivion.
Edit: to clarify, I already disable all notifications in Firefox. I was referring to websites that check via JavaScript whether you have notifications turned on and trigger a pop up to ask you to enable them.
Re: When an app asks for permissions, it should have a “feed fake data” option
#10> 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…
This is an entirely UX problem then. You could bury the data faking deep in the settings, clearly explain what it does in plain language before enabling it as well as plainly telling the user onscreen that the application is being fed information for privacy reasons that they themselves enabled (and can easily disable). There is always someone who will end up enabling this erroneously, but it would provide a lot of v…
Right, locking the functionality off to only people with a deep understanding of it would work but it’s sidestepping the problem. People without understanding would still benefit from it so it’s a shame to lock them out of it and it’s harder to justify a feature only 0.5% of your user base will use.