[wolvoleo]

Ah when I last checked the E2EE was only in practice implemented by Google and invented by them. It looks like this might have been opened up, unless this is an earlier version somehow? And interconnect traffic to e.g. iMessage was not E2EE.

I have to look up on this again as the last time I looked at it was during late corona (2022? 2023?) when there was a local talk to adopt RCS (which failed)

But the problem remains that they simply won't talk to you if you set up your own server. You have to be in a select club to be able to run one.

It's very unlikely I'll ever switch it on because I don't use any google account on my Android and I don't trust them nor the carriers for reasons I've clarified in the other posts in this thread.

[Groxx]

yea, from my understanding Google has had E2EE when messaging itself for a couple years or so now, mirroring how iMessage encrypts messages to itself. iMessage is even very similar (maybe identical) to MLS, and Google Messages might be as well but I don't know the details. but neither encrypts when sending to the other, nor any other client/server/etc, because there is no agreed-and-implemented spec last I looked (a few months ago).

they have, however, been touting the security improvements that RCS brings ever since work first started on it. which is so misleading that it's outright malicious imo.

Google Messages and iMessage AFAIK send RCS messages to each other just fine, but it's not encrypted. yet. ever, IMO, until the moment it's rolled out.