RCS is walled off by design, so that users are dependent on Google and their phone carrier. If they wanted an open standard they would have adopted something like XMPP.
No… RCS is a protocol (from GSMA) anyone can implement, Google just spearheaded it and developed Jibe to make it easy for operators to implement, but by doing this it means Google gained a lot of control of it and added their own features to such as end-to-end encryption.
The proprietary RCS standard is owned by the GSMA. They can license the use of RCS to large companies such as Google, Samsung, or mobile operators. But can a private developer get a license and develop his own RCS client? I think not.
Yet one more reason to not use the hot garbage that is RCS
I wish they would open it up to other apps
RCS is walled off by design, so that users are dependent on Google and their phone carrier. If they wanted an open standard they would have adopted something like XMPP.
No… RCS is a protocol (from GSMA) anyone can implement, Google just spearheaded it and developed Jibe to make it easy for operators to implement, but by doing this it means Google gained a lot of control of it and added their own features to such as end-to-end encryption.
RCS is designed to be used with a phone number though. And fall back to SMS when unavailable. If XMPP was used.
If RCS was fully walled off, Apple would not be able to implement it like they said they would
The proprietary RCS standard is owned by the GSMA. They can license the use of RCS to large companies such as Google, Samsung, or mobile operators. But can a private developer get a license and develop his own RCS client? I think not.
RIP but true, I only interact via matrix bridges but maybe I should setup a iMessage one to cover all bases lol