Comment on Google turns to regulators to make Apple open up iMessage
call_me_xale@lemmy.zip 10 months agoRCS is an open standard, isn’t it? Are you referring to the E2E encryption that Google added to Android?
sarmale@lemmy.zip 10 months ago
Venetas@discuss.tchncs.de 10 months ago
Googles implementation of RCS, the one they are pushing as standard, is indeed proprietary
bassomitron@lemmy.world 10 months ago
Eh? GSMA created RCS and Google simply setup their own servers to run it. So I guess you could argue that Google’s RCS network is proprietary, but RCS itself is most definitely not. There’s technical documentation freely available for implementing your own RCS client/server, if you care to do so.
ilickfrogs@lemmy.world 10 months ago
Well didn’t they initially want carriers implementing RCS with interoperability between each other to sunset sms? But that didn’t quite pan out. IIRC there was a time when Verizon had a limited number of devices that supported RCS but only on their network, similar story with Bell in Canada. Hell at one point even Samsung had RCS but only with other Samsung phones. Fragmentation was rampant so Google took matters into their own hands. Not saying I’m happy Googles at the helm but they didn’t start out with that intention.
AA5B@lemmy.world 10 months ago
Yeah it’s unfortunate we weren’t able to get RCS everywhere, as an improvement over sms. I imagine the encryption to be a sticking point preventing ubiquity
Kbobabob@lemmy.world 10 months ago
You got a source for that?
Drunemeton@lemmy.world 10 months ago
en.m.wikipedia.org/…/Rich_Communication_Services
So any RCS w/ Encryption that you see is referring to Google’s implementation that only runs on Google servers.
Kbobabob@lemmy.world 10 months ago
So their implementation is RCS standards with an added encryption layer. What’s the issue?