> Allow developers to integrate their apps and digital services directly with those belonging to a gatekeeper. This includes making messaging, voice-calling, an

> Allow developers to integrate their apps and digital services directly with those belonging to a gatekeeper. This includes making messaging, voice-calling, and video-calling services interoperable with third-party services upon request. I would think this requirement is satisfied merely by providing a public API / protocol documentation for your protocol, to allow for third-party access and integration, not some weird backend integration that everyone has to support. This would have effects on business models of running chat services for free and it would have an effect on how they handle spam and abuse, but I honestly think both of these changes are likely to be for the better... Now, I (importantly) have NOT read the actual law text yet, but given the high-level summaries I feel like a lot of people have been worried about this over nothing: having the ability to write a third-party iMessage client would ALLOW someone to build a server-mediated client for it, but I think that SHOULD be allowed, I don't think that in any way destroys the ability to create or use end-to-end clients and services, it would also allow people to build alternative e2e clients and even integrations (imagine a Samsung Android device shipping with iMessage support in their local client) without hurting the existence of end-to-end encryption.