4 ms·
That assumes that Apple would be blamed for Edge/Brave/Firefox's security oversight.
by spaceribs 3y ago
That assumes that Apple would be blamed for Edge/Brave/Firefox's security oversight.
- etchalon 3y agoThey would absolutely be blamed by users for it.
- ChilledTonic 3y agoWhy wouldn't they be? Especially considering their existing reputation in consumers minds for security and reliabilty?
- spaceribs 3y agoBecause they own and maintain the operating system, not the vulnerable software? I understand that they've built this image of being a grand infinite protector for all their users within the walls of their garden, but they've had plenty of security issues within their own software, and plenty of cases where application developers have sidestepped their rules. This relationship of trust with Apple is cultish at best. To say that I can trust Apple but not Mozilla? What are we smoking here?
- pjerem 3y agoBecause it never ever happened on any other platform including MacOS.
- shagie 3y agoIf you add a PWA (with Safari) a year ago to your Home Screen and then change your browser to Firefox, and that PWA breaks out and steals some other application data... Will you blame the software maker that you used to install the icon on the screen? or the one that is seemingly unrelated to the icon on your Home Screen?
- seszett 3y agoI would probably blame the "the software maker" for silently switching the engine used by previously installed PWAs. Why do that?
- rickdeckard 3y agoYou think this uneducated me would know that this was a PWA and no app and also remember that it was installed by Safari, an app I apparently don't own anymore at this stage...? Why wouldn't Safari remove all its PWA icons when I uninstall it, considering that it anyway cannot transfer the data to another browser...?
- m-p-3 3y agoWhy silently change the underlying browser engine of an existing PWA without the user's knowledge? That sounds like a bad UX. At least make the existing PWA stay with Safari and provide the ability to switch the underlying engine for each PWA afterwards if migrating is possible.
- shagie 3y agoAs I understand the legislation, Apple has three choices for how to comply with the law. They can either allow third party browsers the elevated system access that Safari currently has in order to be able to access the data for multiple PWAs ... which compromises Apple's security standards, but puts Safari and other browser engines on the same footing. Or, Apple can remove the additional security permissions that Safari uses in order to access the data of multiple PWAs so that Safari and other web browsers are on the same footing again. Or, Apple can invest significant time and resources into creating a new sandbox for browser engines (including Safari) such that a PWA running in the browser engine will not be able to escape and access the elevated permissions of the browser engine or the data of other PWAs through a flaw in the browser engine. Given the amount of effort that the third option would take, the low adoption of PWAs from most users within the European market, and the not going to compromise on the first option - the second option of removing security permissions from Safari (and other browser engines) to run PWAs is the only option to comply with the law in Europe.