

No, it isn’t massive for privacy.
It’s hardware-bound, meaning at a minimum who you’re communicating with and when will always be known, today and in the future.
And I haven’t seen anything showing that it has Perfect Forward Secrecy, so all someone has to do is save the messages and if it’s ever cracked, they’ll know exactly what you said, when, and which device.
It’s a feel good to make people think something is being done, when it’s far from “good”.
BTW, hardware-bound ID was determined to be a bad idea 40 years ago. Even SPX moved away from it in the 90’s.









This isn’t about restrictiveness - it’s a problem of RCS being ass-backwards garbage.
This isn’t a an Android issue, it’s a Google and cell provider issue. And that RCS (like SMS), are based on ancient technology/concepts, and both need to just die.
SMS is based on the physical architecture of cellular networks, and has no error handling whatsoever - it’s a Best Effort transmission.
RCS uses a hardware-bound ID, something we decided was a Bad Idea 40 years ago, and is wholly dependent on cell provider support.
We have a protocol, TCP-IP, that eliminates all these issues. It’s been the networking standard since the mid-90’s when even Netware decided it was a superior solution to IPX/SPX. It’s wholly hardware independent (it’s not tied to a physical device’s ID), so you can transmit/receive from any device without having to update everyone else that this is your new device.
We have numerous IP-based instant messaging systems today, with one in particular (XMPP) being open, flexible, extensible.
There’s no use for an archaic solution like RCS, except keeping your messaging in a system controlled by Google and carriers.