2 ms·
> and still have not even implemented RCS despite their full-court marketing push for the mandatory adoption of the standard. As a user, I find it hard to be u
by talldayo 2y ago
> and still have not even implemented RCS despite their full-court marketing push for the mandatory adoption of the standard.
As a user, I find it hard to be upset about that. RCS as a standard is so bad that my running theory is Google intentionally ruined it so they could promote a broken standard and force Apple to standardize iMessage instead. It's like a thrown-over-the-fence spec that they expect other people to finish for them. I'd have expected the court to block it on the grounds of being an unfair business practice if it didn't promote the smartphone duopoly and surveillance network it entails.
And it's not just the security issues, since both protocols suffer dearly for being centralized. It's a further fracturing of a system we can both agree is broken, pushing us towards Another Competing Standard that doesn't even want to compete. Since we're all in agreement that both iMessage and RCS are backdoored just like SMS, can't we just let the government coordinate text messaging and stop wasting everyone's time with proprietary products? It's exhausting and runs opposite to what we expect from modern communications infrastructure.
- paulmd 2y agoI honestly don’t know that level of nuts-and-bolts detail on it, what is bad about it? /curious (I know the encryption annex that google has tacked on would basically kill the promise of interop, but other than that, still bad?)