• Nix@merv.news
      link
      fedilink
      arrow-up
      17
      ·
      1 year ago

      Google version or Verizons version or samsungs version or… lmfao

      End to end encryption shouldve been enforced by RCS theres no point for apple to implement it when android hasnt even made it so anyone can make an rcs app with E2EE by default other than Google

    • heyspencerb@sh.itjust.works
      link
      fedilink
      arrow-up
      15
      arrow-down
      29
      ·
      1 year ago

      RCS is not an open standard, it’s just Google’s version of iMessage and it all goes through their servers. Stop regurgitating Google propaganda

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

          The whole iMessage/RCS conversation is really only relevant in the US; in other countries basically everyone uses WhatsApp or Kakao or LINE or whatever the local favorite is. In the US, there is no industry-standard RCS. It’s theoretically a carrier-based messaging service but all of the carriers outsourced it to Google so, as an alternative to iMessage, the option is a proprietary extension of RCS running on Google servers, something that is exactly as open as iMessage itself.

          If you want a true industry standard way to send messages to people, the iPhone has had that since 2007: email.

          • timbuck2themoon@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            I think it’s still very relevant to everyone else. An open standard is better than a closed system like WhatsApp.

            One day we’ll wonder why we let so much get tangled up in single companies. You’d think Twitter would wake people up.

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

              RCS the open standard is missing critical features. Google’s implementation fixes that, but is not open. I don’t think we should give a pass to RCS just because it’s open. SMS is a legacy format but it’s unconscionable these days to release a new messaging platform without E2E encryption. That’s a minimum viable product feature, not a maybe nice to have in the future feature.

        • BURN@lemmy.world
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          1 year ago

          It might be owned by someone else, but google is the only one pushing it and the only one supporting it. Technically it’s open, but it’s googles standard.

            • BURN@lemmy.world
              link
              fedilink
              arrow-up
              1
              arrow-down
              4
              ·
              1 year ago

              Does anything outside of Google use this standard? I haven’t even heard of open source apps that use it. The only major player backing it is google. It’s their standard, just like iMessage is apples.

      • allywilson
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        1 year ago

        It’s a bit more complicated than that unfortunately. RCS wasn’t made by Google, but they did join the GSMA that manages it. They are pushing it as an alt/war against iMessage, but it doesn’t go through their servers as far as i know, it’s still a Mobile Operator service (like SMS), so it goes through your provider (and I guess Google’s if you use Google Fi).

        I kinda think the smart thing for Apple to do is to implement RCS support (make the bubbles orange/purple or something) and then they’ve done it and can continue working on iMessage if they like.