This would be great if I could actually use it in AOSP without Google’s own app, and view/reply to RCS conversations on my laptop using a 3rd party application. Open the APIs, Google, or you’re just blowing hot air.
Yeah, I have a lot of mixed feelings about it, but I’m tending towards some forced adherence to standards. Or at least interoperability through open federation.
The standard RCS lacks e2e encryption. You wouldn’t have been able to use other clients with the google messages app either way even if they were developed.
That’s why we need them to open up the APIs in the short term, but the long term goal should be to get the Universal Profile advanced, and move away from a Google-centric implementation.
Which, to be fair, Google really did seem to want carriers implementing their own interoperable RCS solutions. But they needed shit to be done, so they ended up doing it themselves.
This would be great if I could actually use it in AOSP without Google’s own app, and view/reply to RCS conversations on my laptop using a 3rd party application. Open the APIs, Google, or you’re just blowing hot air.
deleted by creator
Yeah, I have a lot of mixed feelings about it, but I’m tending towards some forced adherence to standards. Or at least interoperability through open federation.
The standard RCS lacks e2e encryption. You wouldn’t have been able to use other clients with the google messages app either way even if they were developed.
That’s why we need them to open up the APIs in the short term, but the long term goal should be to get the Universal Profile advanced, and move away from a Google-centric implementation.
Which, to be fair, Google really did seem to want carriers implementing their own interoperable RCS solutions. But they needed shit to be done, so they ended up doing it themselves.