5 ms·

My problem with this is that it is "Google Messages end-to-end encryption", rather than "RCS end-to-end encryption". It's not a distinction without a difference

My problem with this is that it is "Google Messages end-to-end encryption", rather than "RCS end-to-end encryption". It's not a distinction without a difference because it ties me down to a single RCS client and discourages interoperability. The moment I send an RCS message over Google Messages to someone who is using a different RCS app, I'm assuming it will just send plaintext. Having Google Messages preinstalled on all Android phones and set as the default is not a good solution either. Encryption has to be baked into the protocol, not individual clients.

izacus 5y ago
Sure, but what exactly do you expect here though? Telecom operators (your own most likely among them) have decided to lobby and block any kind of E2E messaging and have also been directly dragging their feet at implementing even the unsecure RCS protocol. The pretty much only choice left is to give you messages to proprietary services - either Apple, Facebook, Google or Signal. If you can get anyone to use the last one.
- approxim8ion 5y ago
  Well, you have Matrix and XMPP (+OMEMO), but obviously the adoption for those is even lower than Signal. It's just sad is all.
  - driminicus 5y ago
    IIRC matrix was started because of how terrible RCS is.
    - Arathorn 5y ago
      This is true. Matrix was a direct reaction to our experiences having just implemented RCS 5.1.
  - izacus 5y ago
    Yeah, still, the biggest issue was carriers (especially US ones) actively fighting against preloaded messaging clients and attempting to "compete" with their own (see Verizon RCS saga). Matrix doesn't help you if carrier refuses to sell phones that feature it preinstalled.
    - approxim8ion 5y ago
      Yeah, I understand. It's a whole mess. I've never really understood the US model of carriers selling phones on contracts with stuff bundled. Ideally they wouldn't have any say in these matters, but that is how it is.

izacus 5y ago

Sure, but what exactly do you expect here though? Telecom operators (your own most likely among them) have decided to lobby and block any kind of E2E messaging and have also been directly dragging their feet at implementing even the unsecure RCS protocol. The pretty much only choice left is to give you messages to proprietary services - either Apple, Facebook, Google or Signal. If you can get anyone to use the last one.

approxim8ion 5y ago
Well, you have Matrix and XMPP (+OMEMO), but obviously the adoption for those is even lower than Signal. It's just sad is all.
- driminicus 5y ago
  IIRC matrix was started because of how terrible RCS is.
  - Arathorn 5y ago
    This is true. Matrix was a direct reaction to our experiences having just implemented RCS 5.1.
- izacus 5y ago
  Yeah, still, the biggest issue was carriers (especially US ones) actively fighting against preloaded messaging clients and attempting to "compete" with their own (see Verizon RCS saga). Matrix doesn't help you if carrier refuses to sell phones that feature it preinstalled.
  - approxim8ion 5y ago
    Yeah, I understand. It's a whole mess. I've never really understood the US model of carriers selling phones on contracts with stuff bundled. Ideally they wouldn't have any say in these matters, but that is how it is.