We made a proof of concept RCS messaging app. It already has end-to-end encryption with MLS compatible with Google Messages and iOS, typing indicators, delivery/read receipts, reactions and media/file sharing. We'll use what was learned to integrate RCS into our Messaging app.
@GrapheneOS so does this mean that someday it *may* be possible to use rcs on an install of Grapheneos without Google Play services at all?
@az Yes, it's a planned feature and can definitely be done. There are 2 ways to do it. It can be done by directly using RCS from carriers providing it as a standalone feature or by reimplementing the Google services ourselves. Doing the latter is quite impractical in a lot of ways and has very limited benefits so we'd rather just implement a non-Google form of RCS to use when it's available.
@GrapheneOS @az great work! I'll happily switch carriers to one that supports a standalone implementation.
Another first top feature by GrapheneOS 👍😎👍
@GrapheneOS ...not Revision Control System, I suppose, but what?
Rich Communication Services.
To be *very* short, it's a way to bring modern media and messaging features into SMS.
We are talking about read receipts, typing indicators, verified senders and so on.
@MagentaMold @xentrac RCS is a modern replacement for both SMS and MMS. It's a whole different protocol and doesn't depend on those. Our proof of concept app is purely RCS without SMS or MMS support. It will be different when it's integrated into Messaging since it needs to work with contacts without RCS and needs a way to support downgrading to SMS/MMS if they stop having RCS available.
@logburn RCS is largely implemented via Google servers in practice but it exists without them too. Most carriers delegate it to Google but it's federated to an extent similarly to SMS and MMS.
Google Messages already works on GrapheneOS with RCS available by toggling on the access needed by Play services. What we've made replaces Google Messages but still uses Play services for now. We can make a standalone implementation too in the future for when the carrier supports using it without Google.
@winston_smith It's going to work everywhere it does with Google Messages since we're using Google's services for RCS initially. Adding support for non-Google RCS is future work and won't work with most carriers since most delegate it to Google. It isn't entirely clear how Apple does it but they likely just use their own services and federate with Google from those.
I guess I'm just confused. What is the advantage of RCS over any purpose built app like Signal or WhatsApp or Google Messenger?
Doesn't the carrier have veto power over whether a phone can use RCS (in a way that it doesn't have as to whether the phone can use Signal or WhatsApp)?
@bradr Using Signal requires convincing each contact to use it. SMS/MMS/RCS is the baseline which everyone has available in practice. The purpose of providing RCS is improving the usability and privacy for the baseline messaging included in the OS. It provides end-to-end encryption with users on Google Messages and iOS.
Google Messages is an SMS/MMS/RCS app rather than a Google specific messaging service. SMS/MMS is a fallback if RCS is unavailable but it's unusual for it to be unavailable.
@GrapheneOS This is incredible. Thank you for all of this effort.
@GrapheneOS I love it. Great news. Thank you for working on that.
Most carriers delegate RCS to Google and use proprietary Google services for it. Our initial implementation depends on sandboxed Google Play but avoids the requirement to use Google Messages for RCS. We plan to eventually make it work fully standalone for carriers supporting it.