rockerest’s avatarrockerest’s Twitter Archive—№ 18,622

    1. I want the UI of PulseSMS, the standardization of RCS, plus E2E Encryption (a la Google's RCS implementation, which has it, but isn't technically in the RCS standard) I genuinely don't think this is too much to ask.
  1. …in reply to @rockerest
    The problem is that - in all likelihood - Google will not move their RCS integration into Android/an API because they're trying to get app lock-in for Android Messages. The only way a third party (a la Pulse) could use RCS (at all, even without E2E encryption) would be an API.
    1. …in reply to @rockerest
      I suppose I could cross my fingers and hope Google moves the E2E-encrypted RCS stuff into an AndroidDev API, but I'm - sadly - not holding my breath.
      1. …in reply to @rockerest
        I think the incentive here can ONLY be a marketing coup against Apple. While Apple claims to want privacy, they're choosing to send messages unsecured if you don't stay in their ecosystem. Privacy, but only if you pay with your freedom. Google could advertise "privacy, for all"
        1. …in reply to @rockerest
          But I'm not sure they care enough to give up potential Messages/Chat lock-in.