End-to-end RCS encryption is via proprietary Google extension and not even available to other Android RCS messaging apps.
Beeper was explicitly told it was not available to others when they wanted to implement Google's encrypted RCS on their Android client.
If Google's strategy was anything other than "get Apple to adopt, then screw them", Google would have contributed the enhancements back to the standard.
FaceTime is not really true either. This was a convenient mistruth. There were several way to remedy that situation.
Also your misremembering iMessage there was no such issue.
> Yes but that would have meant giving up sales in exchange for actually backing up their words.
What word did they not back up with respect to iMessage? When did they ever say they'd open it up?
I saw that you moved the goalposts in your reply, but anyway: which words?
> They aren’t even going to use the developed encrypted RCS protocol.
The protocol that was designed by Google and in which Google’s infrastructure is crucial? It’s not Apple’s fault that RCS does not have mandatory end-to-end encryption.
> I have intimate experience here with them both openly lying and purposefully deceiving their user base in this case.
Do you mean that they lied to you personnally? You should write about that, it sounds much more interesting.
Encrypted RCS was. And it is proprietary.
They often presented specs that clearly showed security holes then simply would deny they were there or say “that’s secure”. It was a truly wild experience.
1) This tier of work is roundly invisible to almost everyone in the field. Many in the field are so confident in their knowledge of 'how things work.' that they simply can't accept the real 'in the room' realities of whats going on. Often engineers most of all, who are often deceived by their executives on the real goals. Are you and eng? Have you ever had that feeling of being gaslit by your VP? Yea you probably were, and you didn't know why.
2) Even at that level, I had a limited picture and a good extrapolation of what was going on in other rooms, but nothing I can say fully factually
3) No one wants to know. People love the just-so stories of these companies and really genuinely seem to get hurt/be in denial when they are faced with the reality that they are made up of ultra-selfish, shark like people with very little invested in the consumer, the company, or really anyone else. It's a game played to win for personal satisfaction. I've found that most people, simply cannot accept this.
Google's proprietary closed source fork of RCS?
> Google's version of RCS... is definitely proprietary, by the way. If this is supposed to be a standard, there's no way for a third-party to use Google's RCS APIs right now. Some messaging apps, like Beeper, have asked Google about integrating RCS and were told there's no public RCS API and no plans to build one.
If you want to implement RCS, you'll need to run the messages through some kind of service, and who provides that server? It will probably be Google... So the pitch for Apple to adopt RCS isn't just this public-good nonsense about making texts with Android users better; it's also about running Apple's messages through Google servers. Google profits in both server fees and data acquisition.
https://arstechnica.com/gadgets/2022/08/new-google-site-begs...
They aren’t even going to use the developed encrypted RCS protocol.
Apple, when it comes to their values, is all lip service.
I have intimate experience here with them both openly lying and purposefully deceiving their user base in this case.