AFT. I'd rather have some semblance of standards so I don't have to deal with fragmentation, than worry about the handful of people who care about whether the client employs encryption, colored bubbles, animated emojis, avatars or any other proprietary feature. It's a goddamn phone, it should allow me to communicate, not create barriers against it. Hand the standard back to the standards bodies and sit on said bodies, or open up imessage if they are so concerned about what google is doing with it/ how google is handling it.
Now I can't wait to see how gimped their implementation is, just so we can say 'rcs sucks'.
Their implementation won’t be gimped. Apple’s lock-in does not depend on RCS sucking. Instead, it depends on Apple adding new features to iMessage -- real features like group messaging, or gimmicks like “Genmoji”. RCS is a moribund carrier-controlled standard and has no hope of keeping up feature parity with iMessage. It will always be outdated, no matter how good or complete the implementation is (or isn’t).
No mention of end-to-end encryption. Hopefully the carriers + Apple + Google can work something out.
Yes, Google has end-to-end encryption on RCS. It is proprietary and requires using Google software. Yes, Samsung also supports it — using a special API that Google made for them. No way in hell Apple is using that. But it could be extended to become an actual standard.