this post was submitted on 10 Jun 2024
562 points (98.3% liked)
Technology
59197 readers
2956 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
Encryption was never part of the RCS standard, and Google has been gatekeeping the encryption solution that they’ve been using… which is why there aren’t a lot of E2EE RCS clients floating around.
Google finally conceded several months ago, and now encryption will be part of RCS and managed by an independent working group that Google, Apple, and others can contribute to.
Phase 1 of RCS is about implementing the unencrypted foundation of the protocol. Encryption is supposed to come when the working group has aligned.
I wouldn’t hold my breath.
The whole RCS thing is a Bad Idea™ . It’s a standard by the GSM Association, which consists of over 1150 members (750 operators and 400 other companies). Getting all these companies to align will take forever.
To illustrate: the RCS initiative was started in 2007 and the steering committee was formed in early 2008. The first version of the Universal Profile, that would enable interoperability between different operators and networks was released in 2016. It took 8 f-ing years to come up with an interoperable messaging standard to replace SMS. It was intended to be implemented by operators, but since hardly any operator did Google had to run their own service, bypassing the network operators, just to get it off the ground. Operators are now slowly beginning to support it.
If Apple decides to add a feature to iMessage, they implement the feature, roll out an update to their servers and release it to a billion users in the next iOS update. If they want to add a feature to RCS, they first have to discuss it in the committee until they agree on a solution, this alone takes forever. Then every player needs to update their software to add support. This means potentially 750 operators who need to update their shit, and that is after their software suppliers add support for it. In the mean time, the new feature will work for some users when they communicate with some other users, depending on which phone and operator each party has. Rinse and repeat for every new feature you want to add.
This means RCS will at best only ever be a very basic messaging service. It’ll be an improvement over SMS and MMS, but that’s not saying much. It will be in no way a threat to Apple’s dominance in messaging.
Thank you for detailing what's wrong with RCS.
It's too little, too late, with major issues.
I was running XMPP on my phone in 2009...