Is that practical though? Apps could just accept that and break. Food delivery app could show suggestions from the fake island, social media app could let your friends know you’re 6383km away, calculator app might switch to local currency conversion, etc.
When an app asks for permissions, it should have a “feed fake data” option
321–330 of 413 posts
Re: When an app asks for permissions, it should have a “feed fake data” option
#322I've advocated this for a long time, with the added proviso that it must be impossible for apps to figure out whether you chose to feed them fake data or not.
Take the case of contacts. If I were to use a random ID generate to create contacts and feed those to an app, then with sufficient independent sources of data the app could choose to reject any contact which appears only once. If you happen to be the One And Only True Friend of an Orphan Hermit, then yes, that rule would exclude that data, but if you happen to be personal BFFs with Beyoncé Giselle Knowles-Carter, the system could not only independently validate that such a person exists, but even that your own reported contact information is, say, directly personal rather than a mass-media point-of-contact.
The other problem is that even with generated data, so long as that is intermixed with authentic data, it's often possible to tease out signal from noise. A case here might be with browser history. There are Web browsers which generate spurious traffic. This is "real" in the senses both that it refers to actual online Web resources, and represents traffic generated by your browser, but is generated in the sense that it does not represent volitional activity on your part. However, so long as both activities are present, your actual browsing patterns exist (so that if a concern is that you did in fact visit https://example.com/xyz>, it would be possible to determine that some entity (genuine or simulated) did so, and that if the URL were simply randomly generated or visited, odds are reasonably low that that URL would appear within a browser history.
Similarly, in a combination of actual and faked contacts, if the question is "did the subject include Known Individual in their contacts", that fact can still be determined, and if statistically improbable, particularly amongst a group of individuals all including Known Individual in their contacts, the general inference of an actual relationship is strong.
The case of being able to entirely separate actual and generated information changes this dynamic ... slightly, but not overhwhelmingly.
My own upshots:
- Data chaffing and fuzzing are hard.
- The signal one wishes to obscure often leaks.
- Entirely-fabricated data is usually reasonably evident, especially in aggregate.
- Whilst some degree of chaffing has some value (signalling, protest, cost-increasing), the most effective course of action is likely effective privacy legislation and regulation.
I really wish there were more effective individual actions. I increasingly feel that there aren't, other than opting out entirely. (Something I increasingly practice myself, FWIW.)
Re: When an app asks for permissions, it should have a “feed fake data” option
#323I’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…
> apps could not require users to have “an account” in order to run There is some big qualification missing or I don't understand what does that even mean. How could a banking app run without an account? An online game? The Twitter app nowadays? Dropbox/Nextcloud/...? Etc. Yeah, I agree that for a lot of apps, requiring a account is just a marketing gimmick, but I don't think such a general rule could work.
Re: When an app asks for permissions, it should have a “feed fake data” option
#324Earlier quoted context omitted.
If open doors did a better job of UX than apple, then you would have been using Android instead of iOS in the first place
You're confusing first party apps with third party apps. Also you're forgetting that this is a forum which is heavily biased to developers. I use Android because my phone isn't a fashion piece. Some of my users sadly use iOS. They want the software on the devices they purchased and own, but Apple is preventing us from delivering this to them unless we do exactly as Apple commands. So in the end everyone loses, except…
Re: When an app asks for permissions, it should have a “feed fake data” option
#325Earlier quoted context omitted.
If open doors did a better job of UX than apple, then you would have been using Android instead of iOS in the first place
You're confusing first party apps with third party apps. Also you're forgetting that this is a forum which is heavily biased to developers. I use Android because my phone isn't a fashion piece. Some of my users sadly use iOS. They want the software on the devices they purchased and own, but Apple is preventing us from delivering this to them unless we do exactly as Apple commands. So in the end everyone loses, except…
My phone is not a fashion piece. AFAICT the blue bubbles will show up with an old 4S just as well as with a 14 Pro Max.
I have an iPhone - which I got after many years with Android - because iMessage is an essential app for me. I live in the US, so my business partners do not have [choice of alternative messaging app] installed and they are not going to install it just for me. I'm a doctor working in a hospital that has two complete dead spots for cell reception, and whose IT department blocks WiFi calling. So I can't make phone calls on either service, and only on iOS can I get messages that are really, really important over the hospital WiFi.
I could talk until I was blue in the face about how other methods are better. Or how Apple is being a gigantic bunch of assholes by not using something other than vanilla SMS if you're not an iMessage user. But it's sitting at about 30:1, and you can either go along and be aware of important things going on, or you can be left out.
When business decisions are being made over those conversations, I'd be a fool to ignore it. I don't much like the iOS way, having gotten used to Android and LineageOS, but after my experience with the Nexus 6P that suffered the infamous "battery goes to shit overnight one day" problem that Google wouldn't fix, as well as being dropped from updates after two years, five years of security updates from model introduction sounded pretty nice.
Re: When an app asks for permissions, it should have a “feed fake data” option
#326Why do we need to be awful? Here is a simple rule: No is an option, unless it's really not an option. If it's not an option, you need to be very clear about why (in the app application process maybe), otherwise your app gets declined. i.e. if tiktok/ig asks for permissions on camera and microphone, no is an option, because you don't need either to use either. If parts of your app can feasibly be used by a user withou…
Sounds good, but enforcing it how? The only party here that can do the enforcing is the Google/Apple/Microsoft App Store. I'm not sure they all have the right incentives to expend the effort to enforce that in a consistent and user-friendly way. Otherwise would have already.
Re: When an app asks for permissions, it should have a “feed fake data” option
#327Unfortunately 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.
It doesn't have to be random to be a problem.
In general any sort of intervention that moves you away from Joe average is bad news for fingerprinting.
More sophistication in this context often makes things worse not better. e.g. In this context volunteering info on every request (fake or random doesn't matter) certainly makes you unique, because the average user doesn't do that
Re: When an app asks for permissions, it should have a “feed fake data” option
#328I’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…
If it's being used locally for showing your location on a map, or searching for nearby businesses, sure, give it fake data.
But if you're talking about an app that does internet speed tests and maps the speeds for different cellular providers, or lets users report local weather conditions to improve forecasts, then I have no problem with those apps being able to say "Either give us an accurate location, or give us no location, we don't want your fake location."
The platforms would have to be an adjudicator of which apps get an exemption for users contributing back data that will affect other people rather than just influencing their own browsing experience.
I think Apple has come up with some good middle grounds on this, you don't have to grant an app "precise location," and you can grant photo access via a system provided image picker that only shows the app photos that you've selected.
Re: When an app asks for permissions, it should have a “feed fake data” option
#329Earlier quoted context omitted.
What if I (like so many others) want my device manufacturer to retain some kind of control of my device after sale?
You will act as if app store is still the only way to install apps on your iPhone.
Re: When an app asks for permissions, it should have a “feed fake data” option
#330I think this is a technical solution for a social problem. Compare it with the "unsubscribe" button in spam newsletters that does nothing. Sure, fuck you, I will just block the unique email address you are using and you won't be able to contact me at all. If everyone was playing nicely, we would not need it.