@HeartyBeast@stefano@Haphazard9479 Google put up their own because the carriers botched the rollout. The carriers were very fast to deploy MMS servers because they could charge by the picture. Now that they no longer can do that, they were in no hurry to do the upgrade.
Using Pixel phones, RCS is pretty nice. You do get the three step confirmation (sent, received, read) and end to end encryption.
Finally, Apple says it will work with the GSMA members on ways to further improve the RCS protocol. This particularly includes improving the security and encryption of RCS messages. Apple also told 9to5Mac that it will not use any sort of proprietary end-to-end encryption on top of RCS. Its focus is on improving the RCS standard itself.
Apple is going to use their weight to get the carriers to improve RCS itself, including adding encryption, so that they drop Google’s proprietary implementation.
It would behoove Google to use the open standard since they’ve pushed for Apple to adopt RCS for so long.
And if the carriers actually start supporting it properly, there’s no need for Google to run it’s own proprietary version. Plus, proprietary encryption protocols are always less secure than the widely tested open standards.
@HeartyBeast @stefano @Haphazard9479 Google put up their own because the carriers botched the rollout. The carriers were very fast to deploy MMS servers because they could charge by the picture. Now that they no longer can do that, they were in no hurry to do the upgrade.
Using Pixel phones, RCS is pretty nice. You do get the three step confirmation (sent, received, read) and end to end encryption.
Hopefully Apple will implement the encryption.
Apple said they are going to implement the open standard so no. Encrypted RCS is proprietary to Google.
Apple is going to use their weight to get the carriers to improve RCS itself, including adding encryption, so that they drop Google’s proprietary implementation.
It would behoove Google to use the open standard since they’ve pushed for Apple to adopt RCS for so long.
And if the carriers actually start supporting it properly, there’s no need for Google to run it’s own proprietary version. Plus, proprietary encryption protocols are always less secure than the widely tested open standards.