• conciselyverbose
    link
    fedilink
    arrow-up
    2
    ·
    7 months ago

    The whole point of text messaging is that the number is all you need and the recipient is guaranteed to get it. That cannot be done without the carriers intermediating. It’s a completely obligatory feature.

    The only actual options that Apple is capable of using with that compatibility in the US are RCS or SMS/MMS. They were slow with RCS, but the reason for that is because RCS doesn’t support any of the stuff people are complaining about. Google’s proprietary RCS extensions do, and dealing with Google’s proprietary extensions would be a massive betrayal of their user’s trust.

      • conciselyverbose
        link
        fedilink
        arrow-up
        2
        ·
        7 months ago

        I’m well aware, but that’s an entirely different environment. Everyone being required to cooperate is completely different than expecting Apple to somehow make RCS not dogshit on its own.

        • BrikoX@lemmy.zipOPM
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          7 months ago

          If Apple can’t figure it out with their unlimited R&D budget, then they are failing on purpose. They have full control over all aspects of hardware, kernel, software, and ecosystem. You literally can’t have a better advantage to create a new popular standard than this.

          • conciselyverbose
            link
            fedilink
            arrow-up
            2
            ·
            7 months ago

            It has literally nothing to do with R&D.

            You can’t make other companies cooperate with you. Google’s proprietary RCS extensions are exactly identical to iMessage, and “we’ll let you use the extensions we control” from Google is not something it could have ever been acceptable for Apple to engage with.

            • BrikoX@lemmy.zipOPM
              link
              fedilink
              English
              arrow-up
              2
              ·
              7 months ago

              They don’t need to use Google proprietary extensions to enhance RCS, they can build their own. The standard is semi-open, and can be extended the same way Google did. Or, like I said, they can use a completely different standard and make it interoperable with RCS. And yes, R&D is pointless if the goal from the onset is to fail.

              • conciselyverbose
                link
                fedilink
                arrow-up
                2
                arrow-down
                1
                ·
                edit-2
                7 months ago

                If they don’t use Google’s extensions, people are in the exact same situation they are now, with text messaging between iPhone and Android being shit. They do support RCS on 18, btw.

                And that’s the point. It won’t mitigate any of the complaints, because the actual standard that Google will match them on is not capable of any of the features people are complaining about not having, because RCS is still a fucking terrible standard. (iPhones do support virtually every other standard you listed btw, because they allow third party apps.)