this post was submitted on 12 Oct 2023
665 points (95.2% liked)
Technology
60056 readers
3593 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
RCS was meant to be a SMS replacement spec for carriers to implement but it never reached ubiquity like SMS did.
And of the carriers that rolled it out, not all of them rolled it out to the same spec either so they’re not even completely interoperable.
Then there’s the fact that many of the Google Messages features such as E2E encryption aren’t a part of the RCS Spec. They were built on top of it by Google.
And unless you’re Samsung, good luck on building a messaging app that’s interoperable with the Google version of RCS they use in messages.
In short, Google RCS runs through Google’s servers, not the carriers like it was designed for. As far as I see it, it’s just the Google version of iMessage.
https://arstechnica.com/gadgets/2021/06/google-enables-end-to-end-encryption-for-androids-default-sms-rcs-app/
If you want to download the actual RCS universal profile spec as defined by GSMA you can find it here, missing quite a few things from the Google version you see in Messages:
https://www.gsma.com/futurenetworks/rcs/universal-profile/