So, Google's #RCS supposedly has End-to-End #encryption (E2EE) in some instances. But the RCS API standard is closed source and isn't an open. This is also controlled by #Google, hence why only Google Messenger works with it (except for iMessage only because Google worked with them to maintain their duopoly).
Furthermore, the #E2EE is not part of the RCS standard but is a proprietary encryption method from Google that only works with Google Messenger.
All messages will also now go through Google's servers. As opposed to your choice of Cellular provider
in summary, it can't be trusted to not be another corporate #spyware with built-in State back-doors.
The app also reads your messages and uses it to provide smart text prediction when you're chatting. Contradicting the whole point of E2EE *(timestamp 38:30)
The spam and abuse protection features can also be an AI censorship tool (Google actively uses reported messages to train their AI)
- Video (start at 15:22): https://odysee.com/@switchedtolinux:0/rcs-messaging-privacy-concerns:9?t=922
#messaging #chats #endtoendencryption #imessage
Tourne1
npub1y5…n8cs9
2024-09-20 13:29:12
Author Public Key
npub1y5yw2yk36z828k3tklnm3ww66t46q8mw8k4dthw6ygrjjdalzulqrn8cs9Published at
2024-09-20 13:29:12Event JSON
{
"id": "a1ec70d90b1feb98409ff158744767b8ec3d7ec873c34bd54d5bae50e675f10b",
"pubkey": "2508e512d1d08ea3da2bb7e7b8b9dad2eba01f6e3daad5ddda22072937bf173e",
"created_at": 1726838952,
"kind": 1,
"tags": [
[
"t",
"rcs"
],
[
"t",
"encryption"
],
[
"t",
"google"
],
[
"t",
"e2ee"
],
[
"t",
"spyware"
],
[
"t",
"messaging"
],
[
"t",
"chats"
],
[
"t",
"endtoendencryption"
],
[
"t",
"imessage"
],
[
"nonce",
"11",
"3"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "So, Google's #RCS supposedly has End-to-End #encryption (E2EE) in some instances. But the RCS API standard is closed source and isn't an open. This is also controlled by #Google, hence why only Google Messenger works with it (except for iMessage only because Google worked with them to maintain their duopoly).\nFurthermore, the #E2EE is not part of the RCS standard but is a proprietary encryption method from Google that only works with Google Messenger.\nAll messages will also now go through Google's servers. As opposed to your choice of Cellular provider\nin summary, it can't be trusted to not be another corporate #spyware with built-in State back-doors.\nThe app also reads your messages and uses it to provide smart text prediction when you're chatting. Contradicting the whole point of E2EE *(timestamp 38:30)\nThe spam and abuse protection features can also be an AI censorship tool (Google actively uses reported messages to train their AI)\n\n- Video (start at 15:22): https://odysee.com/@switchedtolinux:0/rcs-messaging-privacy-concerns:9?t=922\n\n#messaging #chats #endtoendencryption #imessage",
"sig": "d5eeb65fcdb58d5324e1159d6ee7e4e1187873d9f77e89b79d5b588e813b3c88671a87da65cb7cfe3d4c7ccee602411dc69a3eb4d983a28f1e362ec6a468bc03"
}