• TexMexBazooka@lemm.ee
    link
    fedilink
    arrow-up
    63
    arrow-down
    4
    ·
    10 months ago

    iMessage uses it’s own protocols and shit that are proprietary, and uses the standard sms protocol as a fallback. Android can use something called RCS which catches up feature wise, but doesn’t play nice with apple.

    It’s to create an illusion of exclusivity and therefore social pressure to use an apple device.

    • brandocorp@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      36
      arrow-down
      1
      ·
      10 months ago

      but doesn’t play nice with apple.

      This isn’t technically wrong, but to be clear, iMessage is closed source. No one can play nice with Apple, in that regard.

      RCS on the other hand is a more open standard that anyone is free to implement and use. It just doesn’t come with end-to-end encryption as a part of the standard.

      • Keith@lemmy.zip
        link
        fedilink
        arrow-up
        8
        arrow-down
        4
        ·
        10 months ago

        Nope, RCS isn’t. It’s still not opened up for 3rd party Android apps.

        • EvokerKing@lemmy.world
          link
          fedilink
          arrow-up
          10
          ·
          10 months ago

          I mean it’s just a gsm standard with some extra features. Realistically you could probably (relatively) easily figure it out and code it yourself like beeper mini did with iMessage but I don’t think gsm or Google is going to change the standard to stop you.

          • Keith@lemmy.zip
            link
            fedilink
            arrow-up
            3
            arrow-down
            4
            ·
            10 months ago

            …no, you can’t. I’ve seen people try. Google says they will open the RCS protocol to 3rd parties… soon?

            • brandocorp@lemmy.dbzer0.com
              link
              fedilink
              arrow-up
              6
              ·
              10 months ago

              Google doesn’t own the RCS protocol. This is like saying they own the SMTP protocol because they provide Gmail. They are just one company that has implemented the protocol in their default text message app. They built end-to-end encryption into their implementation, which is currently closed source. I’m guessing this is what you’re referring to.

              Anyone can implement RCS. It may cost you some money and some time, but it is possible. That’s the difference I was originally trying to highlight.

              • Keith@lemmy.zip
                link
                fedilink
                arrow-up
                4
                arrow-down
                8
                ·
                edit-2
                10 months ago

                No, anyone cannot. That’s why I said it wasn’t really open. 3rd party android apps can’t use RCS. I would need to use Google’s Messages app.

                • brandocorp@lemmy.dbzer0.com
                  link
                  fedilink
                  arrow-up
                  6
                  arrow-down
                  1
                  ·
                  10 months ago

                  No. I’m sorry. You can’t just say it and make it true. Please show me how Google owns RCS or prevents other developers from implementing it within their own apps.

                  • thisisnotgoingwell@programming.dev
                    link
                    fedilink
                    arrow-up
                    2
                    arrow-down
                    2
                    ·
                    10 months ago

                    I’m convinced you’re incorrect. SMTP is an open transport protocol defined in RFC 2821 by the IETF. Anything that is an IP “open protocol” would be defined by IETF as an RFC. No one owns it. No license is required to operate an SMTP server. Same with other common protocols like SIP. It sets qualifications/requirements for what it is so anyone can use it.

                    RCS is a proprietary standard owned by the GSMA. It seems there is some support for developers that want to use RCS but it’s through an API. Meaning your use is licensed and at a cost. Also, you can’t really see what it’s doing. You’re just using an API. Your access can be revoked. So is it an open standard? No.

                    I did my own research and I plan to try these APIs because I have used other messaging services like twilio for paging applications. But here are some other geeks arguing about it:

                    https://www.reddit.com/r/Android/comments/wm18td/stop_telling_people_that_rcs_is_an_open_standard/

                  • Keith@lemmy.zip
                    link
                    fedilink
                    arrow-up
                    1
                    arrow-down
                    3
                    ·
                    10 months ago

                    I don’t have the technical knowledge to explain how what works, but there are no FOSS or 3rd party RCS apps for a reason and you can find various posts on social media from devs trying to implement or even reverse engineer RCS and failing

            • EvokerKing@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              10 months ago

              That’s their rcs protocol. It’s the one with the features. Without the features is easy, the features are what make it difficult.

          • Keith@lemmy.zip
            link
            fedilink
            arrow-up
            1
            arrow-down
            4
            ·
            10 months ago

            All using Google Messages. Yep I’m sure. Samsung skins the app but it’s all Google Messages. 3rd party apps arenct supported. I’ll use RCS when there’s FOSS on Android for RCS.