• bamboo@lemm.ee
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    I don’t think google is doing anything particularly nonstandard, they basically wrote the standard. RCS requires a server for the device to talk through, and google has been the main server most devices use. Some mobile carriers hosted their own but found it wasn’t worth the effort since google would do it for them, and the encryption is such that carriers didn’t have much to monetize.

    Even if google was doing something nonstandard, the amount of begging they’ve put in to get Apple to support RCS means I’m sure they will do everything on their part to ensure interoperability on their end.

    • kirklennon@kbin.social
      link
      fedilink
      arrow-up
      14
      ·
      1 year ago

      RCS does not support end-to-end encryption, only Google’s proprietary extension does. Google has been simultaneously promoting RCS as a “standard” while prominently advertising a non-standard feature.

    • thehatfox@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      So will Apple be rolling their own backend RCS infrastructure for this? It seems unlikely they would want to depend on Google for that.

      • bamboo@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Nobody knows at this point outside of Apple. Articles do say that it would require carrier support, so maybe Apple is telling the carriers to do it, or maybe Apple will host their own backend like Google does.