this post was submitted on 17 Jun 2024
125 points (91.9% liked)
Technology
59405 readers
2848 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
And why should apple (or anyone for that matter) be forced to use googles proprietary code for an “open standard”?
Also,
https://www.techradar.com/phones/iphone/breaking-apple-will-support-rcs-in-2024
Well then why did you describe them not doing that as malicious compliance?
To support E2EE in RCS?
Apple offers first party E2EE messaging for their clients, via iMessage.
As part of China’s certification requirements, Apple has been tasked to support RCS, which, per the spec, does not have E2EE feature.
I’ll say this again: RCS does not support E2EE.
If that’s not registering: RCS does not support E2EE.
Come to the think of it, it would actually be surprising if China is mandating an E2EE capable implementation, but I digress.
In order to comply with this requirement, Apple implemented RCS per the specs of RCS. Again, RCS does not support E2EE. There is no specification of RCS that supports E2EE at this time.
Google runs a proprietary system that they’ve built based off of RCS, but is not RCS. This proprietary protocol, which is not RCS, has custom extensions of their own to offer E2EE. Apple is under zero obligation to implement against this, because this is not RCS. In fact, as demonstrated, even other Android systems don’t do this. They use the carrier RCS, which while fragmented and incomplete, consistently does not have E2EE, because, again, RCS does not support E2EE.
There are plenty of cross platform E2EE solutions available: Matrix, Signal, and WhatsApp, are a few major players that popped to mind. I’m sure there are plenty of others that I didn’t call out. They are cross platform which means they already exist on both iOS and Android platforms.
Neither Apple nor Google have any reason to implement those protocols, as, again, they already exist on platform.
How is Apple not implementing Google’s proprietary extension malicious compliance as you called it?
Judging by the community response here… no, you have not, please write better.
I won’t bother replying anymore.
To add to this: Apple is actively working with Google and the GSMA to add E2EE to the RCS standard. Apple can no do this on their own, as RCS is a standard set by the GSMA. They need to go through the entire slow and bureaucratic process to add a feature to RCS, so while this will appear eventually I wouldn’t hold my breath.
This also shows exactly why something like RCS cannot ever offer anything other than the bare basic messaging functionality. You cannot innovate on RCS because every change needs to go through a committee who’s all want to have a say in it and before you know it you’re spending years in committee meetings to add a single feature.
Meanwhile, Apple decides they want to add a feature to iMessage, they roll it out in the next iOS update and it’s available to billions of users pretty much overnight.