this post was submitted on 30 Apr 2024
178 points (90.8% liked)
Technology
69391 readers
2711 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- 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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically 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
Last I had looked into it, although the standard exists, they use their own servers and are not compatible with other rcs implementations
They are also the only RCS supplier on Android. A random messaging app can't simply add RCS messaging functionality.
It's not really much of an open standard at all, in practice.
You are correct that an app can't directly implement RCS but it can support it. RCS is implemented by the carrier, not by Google or any other text application.
RCS is an open standard that any carrier can implement to replace SMS/MMS. The only thing special that Google does is on top of RCS is provides E2E via its own servers for handling messaging. The E2E isn't a part of RCS, though it should be IMO. Regardless, Google doesn't 'own' the Android implementation because it isn't a part of Android, other than it can support the carrier's implementation of RCS.
No app on Android can use RCS yet, other than Google messages.
Not true. Both Samsung and Verizon messages uses RCS, so long as your carrier has implemented RCS.
Samsung had to sign a deal with Google with unknown terms and is Google messages underneath.
Verizon idk, I'm not American.
Samsung signed a deal so that they can use the Jibe API to be a part of E2E when using RCS.
Since I'm sure there's Internet where you're at, you can take a look from Verizon's RCS roll out on messages+ in 2021 to Samsung's S9, prior to relying on Google Jibe. Verizon did eventually switch to use Jibe for their entire RCS implementation now instead of relying on their own infrastructure as did T-Mobile.
Any FOSS or privacy friendly implementation?
Samsung messages is just a reskinned google messages
E2EE via server sounds wrong.
Well sure. You've got to trust that Jibe isn't man in the middling the key exchanges but regardless, it doesn't change what I said.
And just to note, the same is true of iMessage & Apple.
If you didn't create private and exchange public keys with the other party, you aren't fully in control. I'm not saying that as some kind of righteous purist, just a technical point of note.