[ruszki]

In the thread to which you replied, somebody mentioned that it’s possible to do that on top RCS, and Google already did it. If Apple wants to make their own encryption they can do it, nothing stops them. Interoperability would still be better, just like in the case of Google with other RCS solutions.

[riscy]

Please explain how interoperability between messaging apps is possible if two different, proprietary E2EE schemes are used atop RCS.

Google's interop "solution" with the Samsung messages app is by not using encryption. Apple has that same level of support coming to iOS next year, and has also announced plans to work with GSMA on adding standardized encryption to RCS.

[ruszki]

I like that you put Google’s solution into apostrophes, while Apple’s current solution has the same problem, and even more. But I’m glad that we agree.

[nicce]

> In the thread to which you replied, somebody mentioned that it’s possible to do that on top RCS, and Google already did it

Google made a copy of iMessage since it is closed source and can talk to only to the same app. How is that better?

[ruszki]

I don’t know what you talk about, because both can talk to whatever they want, because both support SMS.

[nicce]

Then there isn’t issue with iMessage either?

But you know what I mean - E2EE of Google Messages is closed solution.

[ruszki]

Both have issues. iMessage has problems with interoperability, RCS has problems with requirement of operator support.

[jacksontrom]

Google is still working on the standard and adding features to it. If their previous statement is true, they will open source it after that.