This is spam for the Android operating system, nothing more.
Google claiming that RCS includes end-to-end encryption here is misleading.
Encryption got explicitly axed from the RCS spec because carriers don't like it.
The end-to-end crypto they're talking about is a custom Google thing and not part of RCS.
Friends don't let friends use unencrypted everyday communications.
Reject RCS and reject Google platform marketing.
PS: Note also that iMessage has a crypto backdoor maintained by Apple for the FBI; Google should not be encouraging iMessage to become more useful/popular, as this reduces privacy and makes people less safe.
> Note also that iMessage has a crypto backdoor maintained by Apple for the FBI
Describing iMessage as having an encryption back door is disingenuous at best. There's no known encryption back doors in iMessage. As far as can be determined iMessage is fully E2EE.
There is however a caveat that the unencrypted local messages backed up to iCloud can be turned over to LEAs/governments. This caveat holds for any unencrypted data synced to iCloud. It's no different than your e-mails sitting in your iCloud mail account. Disabling syncing of Messages with iCloud closes this hole.
Which is the same as any other E2EE system. Your OpSec is only as good as the worst OpSec as whoever you communicate with. Pretending this is an Apple issue is absurd.
Google claiming that RCS includes end-to-end encryption here is misleading.
Encryption got explicitly axed from the RCS spec because carriers don't like it.
The end-to-end crypto they're talking about is a custom Google thing and not part of RCS.
Friends don't let friends use unencrypted everyday communications.
Reject RCS and reject Google platform marketing.
PS: Note also that iMessage has a crypto backdoor maintained by Apple for the FBI; Google should not be encouraging iMessage to become more useful/popular, as this reduces privacy and makes people less safe.