Apple's flavor of RCS won't support Google's encryption extension
appleinsider.com
appleinsider.com
> Later next year, we will be adding support for RCS Universal Profile, the standard as currently published by the GSM Association.
Or was it because carriers couldn’t get their shit together? [1]
[1] https://arstechnica.com/gadgets/2021/04/verizon-att-and-t-mo...
Apple and Google are equally guilty of forcing their way upon carriers. Indeed, Apple has probably done more of this (visual voicemail, etc.).
(This is orthogonal to the concept of whether the carriers needed or should have needed forcing).
...and they would still display as green bubbles, I presume having trained iPhone users that they're bad and to be avoided.
1. The big one is obviously encryption, but in the hypothetical RCS with actual encryption future wouldn't be as relevant
2. Indicates that the message requires a cellphone (iMessage does not) because RCS is carrier+phone number based
3. Indicates that the message costs money (plenty of carriers still charge for RCS as they do SMS - I have a friend who accidentally spend $5 texting because they didn't realize international messages were "toll" messages not included in their "500 free texts" plans), similarly plenty of carriers charge to receive text messages as well.
Even if RCS were encrypted, that does not fix 2 and 3, and RCS is still unencrypted by default and the ability to send encrypted RCS is solely dependent on carriers not choosing to block it because supporting RCS _requires_ supporting downgrade attacks.