Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
Not necessarily. Google has implemented E2EE in their implementation, but it only works if both parties are using Google Messages. It’s not a standard part of the spec.
I too could manually encrypt data and send it via regular old sms. That would require the other party to know of and make use of extra tools to be able to read and reply. If not, then they might not be able to read the message, or worse, reply in plaintext. That’s what google is doing with rcs. Rcs is not encrypted. the google app encrypts the data and sends it “unencrypted” over rcs. From rcs’ point of view it looks like “this user is trying to send random junk… who am I to judge?”
Not necessarily. Google has implemented E2EE in their implementation, but it only works if both parties are using Google Messages. It’s not a standard part of the spec.
I too could manually encrypt data and send it via regular old sms. That would require the other party to know of and make use of extra tools to be able to read and reply. If not, then they might not be able to read the message, or worse, reply in plaintext. That’s what google is doing with rcs. Rcs is not encrypted. the google app encrypts the data and sends it “unencrypted” over rcs. From rcs’ point of view it looks like “this user is trying to send random junk… who am I to judge?”