42 karma · joined November 27, 2019
https://webbrowsertools.com/privacy-test/ https://panopticlick.eff.org/ https://tenta.com/test/ https://dnsleaktest.com/
This page has lots good info on this topic. https://browserleaks.com/
Mozilla/5.0 (iPhone; CPU iPhone OS 13_2_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
My point is that if we are going to try to fix it, we should address the problem, not mask it or throw up our hands and just set the UA to some silly constant. The information is helpful in troubleshooting issues and avoids people having to ask the inevitable "what browser/device are you using?" and also helps to allocate resources when testing. I honestly don't know what we would do as software developers and testers without somewhat accurate UA information.
Maybe where we are right now is the best we can do. You can pretend to be Chrome and most of the major devices/clients will report their UA accurately, but if everyone did what you are claiming is your right to do, we would not have a viable ecosystem.
You are arguing that it should be ok for your software to lie about who/what it is. If we go down that road, we end up with chaos. Software misreporting who/what it is so a server that will think it is a compatible system and agree respond, when it might otherwise refuse.
fraud n. A deception practiced in order to induce another to give up possession of property or surrender a right. n. A piece of trickery; a trick.
Personally, despite the obviously good intention to provide a reliably working software system, I think building a software system that systematically lies when reporting who/what it is is worse than a one-off lie to a customer support person on a phone call.
Surely there is a solution that does not involve deception.
Even if the user frees-up some space on their device, not enough to upgrade to iOS 13.x, but enough to run our app theoretically, our app still fails to run for them. Uninstalling and reinstalling the native app that contains the webview that runs our web app doesn't solve the problem either. My theory is that there are truncated versions of some of our javascript files left over from when the device ran out of storage that don't get re-downloaded even when storage is later made available....
I've been telling people to free-up space on their device and upgrade it to iOS 13 to fix the problem. I sure hope that works...
If all user agents become a fixed string, how on god's green earth will we troubleshoot problems reported by users? I sure hope we get another header that will tell us the real client platform information so we can eventually repeat this exercise after another few years...
This scenario is complicated, but my point is really that of course we need a User Agent to accurately tell what platform the client is running for entirely legitimate reasons and mega corporations should not do patently evil things to make the lives of developers and support people even more frustrating than they already are. There should be laws against things like this. It really is fraud to change something like the User Agent string to a constant value that is incorrect, and it WILL lead to damaging events in real people's lives if it happens. People could be fired for being led down the wrong investigative path when troubleshooting problems. From the article, it sounds like significant damage has already been done.