RCS is only interoperable with apps and carriers that adopt the Jibe protocol, so not much has changed.
Comment on Samsung joins Google in RCS shaming Apple
Tetsuo@jlai.lu 1 year agoThe simple fact that iMessage has 0 interoperability makes it much worse than everything else.
So I doubt RCS could be as bad except if they remove the ability to operate with other RCS clients. And even for Google and Samsung that would be extremely stupid.
Virkkunen@kbin.social 1 year ago
glimpseintotheshit@sh.itjust.works 1 year ago
At least it sends standard SMS to everyone without an iPhone. Wouldn’t call that 0 interoperability
whofearsthenight@lemm.ee 1 year ago
I’ve just been googling a bit because I haven’t read about RCS in a while, but I remember thinking then that the show stopping thing is that it’s not E2E, and Apple would be dumb to move to since iMessage is. It seems now that E2E is supported but requires clients to support it, which tbh seems the worst of all worlds. At least today I know blue = encrypted, green = not encrypted. If it’s optional and we end up in a “is this encrypted? we’ll see ¯_(ツ)_/¯” type of world that is honestly terrible. I also don’t know how great it would be if you have to rely on the client vendor to accurately report encryption status because there are some I trust, and especially when it comes to “just download whatever RCS client you want” I absolutely would not trust that.
ozymandias117@lemmy.world 1 year ago
iMessage is only meaningfully E2E encrypted if both users have iCloud disabled or have gone into their iCloud settings and enabled “Advanced Data Protection”
glimpseintotheshit@sh.itjust.works 1 year ago
Wow, thanks. Always assumed E2E was enabled by default. That sucks.
whofearsthenight@lemm.ee 1 year ago
Fair point. It looks more specifically they’re not if you enable “messages in iCloud” or iCloud backup with messages.
Natanael@slrpnk.net 1 year ago
The RCS e2e extension is client controlled, the client app knows if it’s active