3 ms·

Still waiting on a non-Google implementation of this so-called standard.

MBCook 2y ago
I think Google‘s was something different. This is an actual standard that Apple is committing to implement. I was under the impression Google’s encryption was just their own layer thing they added on top it was not actually standardized. When people asked last year about why Apple wasn’t implementing encrypted RCS I think they even said that they wanted to wait for a standard.
- ocdtrekkie 2y ago
  So an important context here is the server side implementation of RCS is Google's at every major carrier. Google bought the carrier-side provider of RCS services, Jibe, and so the entire RCS stack is still basically just Google Chat with an "it's a standard" label on it. https://9to5google.com/2024/02/01/verizon-rcs-google-jibe/ https://9to5google.com/2024/02/01/verizon-rcs-google-jibe/ Verizon, AT&T, and T-Mobile all use Google's RCS implementation, the only way to not send Google your messages in the US is to own an iPhone and disable RCS.
  - tredre3 2y ago
    > Verizon, AT&T, and T-Mobile all use Google's RCS implementation, the only way to not send Google your messages in the US is to own an iPhone and disable RCS. You can disable RCS on Android too.
jeroenhd 2y ago
There have been dozens, called anything from Message+ to Joyn. Most seem to be shutting down, though, because nobody used RCS since its inception from somewhere around 2009 and renewed interest in launching RCS services around 2012. There are a few implementations on Github. https://github.com/android-rcs/rcsjta https://github.com/android-rcs/rcsjta seems to be the most complete but uses an older version of the spec. https://github.com/Hirohumi/rust-rcs-client https://github.com/Hirohumi/rust-rcs-client is a modern implementation. The spec is here: https://www.gsma.com/solutions-and-impact/technologies/networks/gsma_resources/rich-communication-suite-advanced-communications-services-and-client-specification-version-14-0/ https://www.gsma.com/solutions-and-impact/technologies/netwo... if you're looking to implement it yourself.

I think Google‘s was something different. This is an actual standard that Apple is committing to implement. I was under the impression Google’s encryption was just their own layer thing they added on top it was not actually standardized. When people asked last year about why Apple wasn’t implementing encrypted RCS I think they even said that they wanted to wait for a standard.

ocdtrekkie 2y ago
So an important context here is the server side implementation of RCS is Google's at every major carrier. Google bought the carrier-side provider of RCS services, Jibe, and so the entire RCS stack is still basically just Google Chat with an "it's a standard" label on it. https://9to5google.com/2024/02/01/verizon-rcs-google-jibe/ https://9to5google.com/2024/02/01/verizon-rcs-google-jibe/ Verizon, AT&T, and T-Mobile all use Google's RCS implementation, the only way to not send Google your messages in the US is to own an iPhone and disable RCS.
- tredre3 2y ago
  > Verizon, AT&T, and T-Mobile all use Google's RCS implementation, the only way to not send Google your messages in the US is to own an iPhone and disable RCS. You can disable RCS on Android too.

jeroenhd 2y ago

There have been dozens, called anything from Message+ to Joyn. Most seem to be shutting down, though, because nobody used RCS since its inception from somewhere around 2009 and renewed interest in launching RCS services around 2012. There are a few implementations on Github. https://github.com/android-rcs/rcsjta https://github.com/android-rcs/rcsjta seems to be the most complete but uses an older version of the spec. https://github.com/Hirohumi/rust-rcs-client https://github.com/Hirohumi/rust-rcs-client is a modern implementation. The spec is here: https://www.gsma.com/solutions-and-impact/technologies/networks/gsma_resources/rich-communication-suite-advanced-communications-services-and-client-specification-version-14-0/ https://www.gsma.com/solutions-and-impact/technologies/netwo... if you're looking to implement it yourself.