Don't trust carriers, but trust sms? 🤔🫤

Poofdirtpirate

I believe in the g.o.s. cause and have major respect , it's saved me from some lowlife trolls countless times , but how do all you badass dudes develope this stuff and we're still using sms by default?:/ Im frustrated AF been trying for the Google messages e2ee for a week now while my sms are 2 steps behind?

MetropleX

Poofdirtpirate are you asking about RCS not being available in the stock SMS app?

This is only available with Google Messages and Play Services installed as Googles RCS implementation is closed source not included in AOSP and the RCS API hasn't been released to third party/non google devs.

Also GrapheneOS has a position on using legacy cellular communications:

Legacy calls and texts should be avoided as they're not secure and trust the carrier / network along with having weak security against other parties.

raccoondad

Poofdirtpirate and we're still using sms by default

Its not, you are choosing to use it, its just a supplied function of android. Its not a "default"

RCS isn't supported on the messaging app because android itself doesn't support it for its messages application, you need to install it with google services

SMS doesn't require non-open source application code, RCS does. Simple as.

de0u

Poofdirtpirate The current state of RCS is not great (source). Lots of carriers are signing up to use Google's implementation (source).

So in theory RCS is a huge upgrade from SMS/MMS that "just works" because it's from your carrier like SMS/MMS is, but out here in the real world RCS is delicate and largely a proprietary service of Apple or Google.

Many users have decided to use Signal instead, including the Molly client.

BeepBeep

https://discuss.grapheneos.org/d/22775-rcs-with-planned-messaging-app/4