E2EE via server sounds wrong.
Comment on How RCS on iPhone Will Make Texting Better for Everyone
Kid_Thunder@kbin.social 2 months agoThey are also the only RCS supplier on Android. A random messaging app can’t simply add RCS messaging functionality.
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.
bjoern_tantau@swg-empire.de 2 months ago
Kid_Thunder@kbin.social 2 months ago
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.
lengau@midwest.social 2 months ago
And just to note, the same is true of iMessage & Apple.
ArtVandelay@lemmy.world 1 month ago
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.
BearOfaTime@lemm.ee 2 months ago
No app on Android can use RCS yet, other than Google messages.
Kid_Thunder@kbin.social 2 months ago
Not true. Both Samsung and Verizon messages uses RCS, so long as your carrier has implemented RCS.
TheGrandNagus@lemmy.world 2 months ago
Samsung had to sign a deal with Google with unknown terms and is Google messages underneath.
Verizon idk, I’m not American.
Kid_Thunder@kbin.social 2 months ago
Samsung didn't have to do anything. It uses the Jibe API to be a part of E2E when using RCS.
jaagruk@mander.xyz 2 months ago
Any FOSS or privacy friendly implementation?
Blisterexe@lemmy.zip 1 month ago
Samsung messages is just a reskinned google messages