I would welcome if this global legislative push would end up in a more open app ecosystem for iOS overall. BrowserEngineKit is a thin wrapper over XPC and iOS' extension system. The system would be so much better to develop for if XPC was an open API, and JIT for isolated sub-processes was permitted without Apple's blessing. * Messengers could have separate sub-processes for preprocessing untrusted inputs -- iMessage…
>and as we all know that'll be the end of the world. I'll enjoy seeing all the accounts on MacRumors clawing their eyes out when that happens. It would be naive to think that Apple isn't funding sites and narratives on the internet to serve their economic interests. One of the most outlandish one being that freedom to use your phone however you want would necessarily compromise security and privacy for everyone. It's…
I suppose in a round-a-bout way, it could, more specifically around iMessage, which is Apple's baby in the US and a big part of their lock in effect for US users.
Right now, you can reasonably assume that using iMessage with another iPhone user that both ends are reasonably secure and private. Break open the walls of the garden and now you could say that you can't trust that the other end you are communicating with hasn't installed some random crapware or malware that's scraping their messages, or recording the screen during a facetime call, thereby compromising your own privacy by interacting with a bad devices.
In that instance, Apple is correct - but what Apple doesn't tell people is that all other forms of digital communication are open to the same risks so they aren't special.