there’s no end-to-end encryption (E2EE) support between the two platforms
Called it. Malicious compliance, as expected.
They’re adhering to the bare minimum specifications of RCS.
E2EE is not part of the standard and only exists as a proprietary Google extension, using Google’s servers. Implying that implementing RCS would get everyone cross-platform E2EE is misinformation.
E2EE is not part of the standard and only exists as a proprietary Google extension
Yes, that is the point I was making, thank you for elaborating.
Implying that implementing RCS would get everyone cross-platform E2EE is misinformation.
Correct again, thanks.
And why should apple (or anyone for that matter) be forced to use googles proprietary code for an “open standard”?
Also,
There is, naturally, a wrinkle here. The RCS standard still doesn’t support end-to-end encryption. Apple, which has offered encrypted messaging for over a decade, is kind of a stickler about security. Apple says it won’t be supporting any proprietary extensions that seek to add encryption on top of RCS and hopes, instead, to work with the GSM Association to add encryption to the standard.
https://www.techradar.com/phones/iphone/breaking-apple-will-support-rcs-in-2024
And why should apple (or anyone for that matter) be forced to use googles proprietary code for an “open standard”?
They shouldn’t.
Well then why did you describe them not doing that as malicious compliance?
Because there are 5000 different open protocols they could have chosen from.
To support E2EE in RCS?
To support E2EE
Correct
