google implemented the exact minimum they'd need to give them a foot to cry on in the courts, and no further. and now that there is a mandate to implement RCS, they almost certainly will choose to kill google voice rather than implement it. I am already planning my exit strategy, because otherwise they'll take my phone number with it. and this is not trivial, we are talking about buying another phone (hopefully it will make it until the next-gen iphone with N3E) and paying for two lines for a couple of months. This is a pain in the ass for me.
and google has already embrace-extend-extinguished the standard - their encryption implementation is proprietary and they've refused to let anyone interop, so essentially they have put themselves as imessage 2.0 but with google as the man in the middle this time.
> If you are texting with somebody who isn’t using Android Messages (say, somebody using Samsung Messages or an iPhone), the fallback to either less-encrypted RCS chat or SMS will still work just fine.
Sounds like Samsung users need to separately download Android Messages to get E2EE.
Quotes from https://www.theverge.com/2020/11/19/21574451/android-rcs-enc... which is cited by Wikpedia on RCS.
You're framing it in a nefarious way as if Apple is flat out denying it. They didn't. They would have to LOWER security in iPhones by implementing RCS because iMessages have E2EE but RCS doesn't. Which is something all you anti-Apple people seem to conveniently leave out, because you know nobody would take it seriously if you said it.
Google's interop "solution" with the Samsung messages app is by not using encryption. Apple has that same level of support coming to iOS next year, and has also announced plans to work with GSMA on adding standardized encryption to RCS.
Google made a copy of iMessage since it is closed source and can talk to only to the same app. How is that better?
But you know what I mean - E2EE of Google Messages is closed solution.