Google turns to regulators to make Apple open up iMessage::iMessage serves should be regulated under the EU’s new Digital Markets Act (DMA), Google and a group of major European telcos has told the European Commission.
Google turns to regulators to make Apple open up iMessage::iMessage serves should be regulated under the EU’s new Digital Markets Act (DMA), Google and a group of major European telcos has told the European Commission.
RCS is an open standard, isn’t it? Are you referring to the E2E encryption that Google added to Android?
Googles implementation of RCS, the one they are pushing as standard, is indeed proprietary
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.
You got a source for that?
https://en.m.wikipedia.org/wiki/Rich_Communication_Services
So any RCS w/ Encryption that you see is referring to Google’s implementation that only runs on Google servers.
So their implementation is RCS standards with an added encryption layer. What’s the issue?
I have no dog in this race.
That being said, I guess it’s that it belongs to Google, is therefore propriety, and they have a less than stellar record with honoring privacy and/or keeping projects going.
Add on that telecoms didn’t want RCS to have encryption, which is why the default standard doesn’t have it, and you have a clusterfuck of privacy concerns, longevity concerns, and licensing concerns.
Then there’s the abuse factor: https://www.theverge.com/2022/6/1/23150243/google-rcs-ads-india-spam-verified-business
So, then the argument here is to just use standard RCS without encryption?