This whole debate seems asinine to me. Erik must know he's in the wrong here. The idea that we can force any company to allow third party clients to their service by regulation is an obviously bad idea. Just because Beeper (probably) isn't doing something shady with user data doesn't mean Apple must be required to trust them.
What if I make a 3rd party client that actively records my users' iMessages and sells them to Facebook? Should Apple be required to support my app too? If not, are they expected to audit and vouch for every third party client? If yes, how is Apple supposed to make any claims about the security of iMessage if I have no control over the client my recipient might be using?
The whole interoperable API argument comes from the same place as "encryption where the good guys have keys," yet somehow demands for interoperability seem to be much more popular on HN. The E2E in E2E encryption stands for end-to-end, which inherently requires trusting both ends. Otherwise you might as well not have encryption.
Note that whether or not companies should be required to support third party clients is a different debate than whether or not Apple should be required to support Android, even if the end result happens to be similar in this case. I think most people defending Beeper are interested in the latter and are willing to burn down encryption to get it via the former. As a user, sure I'd love for my Android friends to use iMessage too. But this is not the way.
(To be clear, I don't think we should regulate that Apple has to support Android either. If I develop a new OS, would every company be required to build a client for their service for my new OS too? But at least I understand the merits of that debate.)
This project exists so Google can go to the (EU) regulators and demand Apple stop anti-competitive actions and lets poor small-time startups like Beeper freely interact with iMessage. The EU is much more likely to protect Beeper from Apple than Google due to them being in the same weight class, so this is a solid strategy.
What if I make a 3rd party client that actively records my users' iMessages and sells them to Facebook? Should Apple be required to support my app too? If not, are they expected to audit and vouch for every third party client? If yes, how is Apple supposed to make any claims about the security of iMessage if I have no control over the client my recipient might be using?
The whole interoperable API argument comes from the same place as "encryption where the good guys have keys," yet somehow demands for interoperability seem to be much more popular on HN. The E2E in E2E encryption stands for end-to-end, which inherently requires trusting both ends. Otherwise you might as well not have encryption.
Note that whether or not companies should be required to support third party clients is a different debate than whether or not Apple should be required to support Android, even if the end result happens to be similar in this case. I think most people defending Beeper are interested in the latter and are willing to burn down encryption to get it via the former. As a user, sure I'd love for my Android friends to use iMessage too. But this is not the way.
(To be clear, I don't think we should regulate that Apple has to support Android either. If I develop a new OS, would every company be required to build a client for their service for my new OS too? But at least I understand the merits of that debate.)