Yeah, to be fair, the current state of encryption has been one of the major grievances with RCS.
The fact that Apple is pushing for a more universal E2E standard, and having Google onboard for it, is a good thing for everyone.
Also, those unencrypted messages will be called on their clients. Messages on Android gets the no lock icon, and Messages in Apple’s ecosystem gets green bubbles.
This Sunbird thing is some bullshit because people think it’s encrypted, and it isn’t. Unencrypted comms are getting blue bubbled.
You could say the same about RCS. Apple’s implementation of RCS next year will not have e2ee, at least not at first.
Can’t wait to lose my RCS e2ee thanks to Apple.
Google only allows E2EE between its own app, though, because there is no E2EE in RCS yet.
You can’t send a message from Google’s RCS supporting app to another RCS app or platform and utilize E2EE.
What Apple’s asking for is to have a standard encryption for RCS rather than a 3rd party implementation.
Yeah, to be fair, the current state of encryption has been one of the major grievances with RCS.
The fact that Apple is pushing for a more universal E2E standard, and having Google onboard for it, is a good thing for everyone.
Also, those unencrypted messages will be called on their clients. Messages on Android gets the no lock icon, and Messages in Apple’s ecosystem gets green bubbles.
This Sunbird thing is some bullshit because people think it’s encrypted, and it isn’t. Unencrypted comms are getting blue bubbled.