The E2EE element of RCS has basically been a property Google thing, despite all their marketing BS about RCS seeming like some sort of open universal career messaging platform.
Although, allegedly they’ve finally relented and a universal encryption solution is now in the works.
tentacles9999@lemmynsfw.com 6 months ago
Last I had looked into it, although the standard exists, they use their own servers and are not comparable with other res implementations
TheGrandNagus@lemmy.world 6 months ago
They are also the only RCS supplier on Android. A random messaging app can’t simply add RCS messaging functionality.
It’s not really much of an open standard at all.
Kid_Thunder@kbin.social 6 months ago
You are correct that an app can't directly implement RCS but it can support it. RCS is implemented by the carrier, not by Google or any other text application.
RCS is an open standard that any carrier can implement to replace SMS/MMS. The only thing special that Google does is on top of RCS is provides E2E via its own servers for handling messaging. The E2E isn't a part of RCS, though it should be IMO. Regardless, Google doesn't 'own' the Android implementation because it isn't a part of Android, other than it can support the carrier's implementation of RCS.
BearOfaTime@lemm.ee 6 months ago
No app on Android can use RCS yet, other than Google messages.
bjoern_tantau@swg-empire.de 6 months ago
E2EE via server sounds wrong.