• gregorum
      link
      fedilink
      English
      2
      edit-2
      1 year ago

      Clearly they also saw the benefits of keeping it to Apples platforms, but that doesn’t remove the technical limitations, at least, early on.

      Like I said, I don’t know if those limitations still exist. Clearly, the profit motive would if it weren’t for all of the legal and regulatory liabilities that exist abroad. This is why I suggested in another comment that purchasing and integrating this compatibility layer would be a good workaround for them in that regard.

      • @Jakeroxs@sh.itjust.works
        link
        fedilink
        English
        21 year ago

        The limitation was added after the fact anyway, like I mentioned in my edit, secure enclave wasn’t added until the A7 chip, which was first used in the iPhone 5S in 2013, two years after iMessage became available.

        • gregorum
          link
          fedilink
          English
          31 year ago

          Although true, it was added to make iMessage (and every other service) more secure, not just as some sneaky way to keep iMessages off android devices.

          • @Jakeroxs@sh.itjust.works
            link
            fedilink
            English
            11 year ago

            It’s really not necessary though, it’s just a justification after the fact. There are several secure e2e apps available without utilizing a special chip to house that data, even Google has e2e with their RCS implementation