> If Apple were truly acting in their users best interest, they would want their users to have encrypted and fast communication with all devices, through an open protocol or otherwise.
yeah that protocol exists. itβs called RCS and it is coming to ios soon. imo apple is allowed to gate imessage behind ios-only if RCS support is a thing
RCS has no end-to-end encryption in the standard, though. That's a non-standard google messages extension. I think a better example would be the cross-device messengers like signal/whatsapp/etc.
Google is slacking here and I hope Apple's involvement in RCS will help to move this forward. Samsung Messages also does not support Google's E2EE even though it supports RCS and pretty much all of the user-facing features Google Messages provides. Based on Google's whitepaper [1] about their E2EE support, I imagine it's because of the identity service they use for key exchange being centralized and internal (when really the identity service a contact uses should be an RCS capability in the extended contact system [RCS terminology here], and they should interoperate).
yeah that protocol exists. itβs called RCS and it is coming to ios soon. imo apple is allowed to gate imessage behind ios-only if RCS support is a thing