• https://grapheneos.social/@GrapheneOS/117225731764489295

RCS planned, I'm all for it

This is good news

I'm surprised it took this long, given how insecure SMS and MMS are.

On the other hand, I don't think I know anyone that uses SMS regularly, so maybe it just wasn't a priority? Pretty much the only SMS messages I get are automated. It's more common to see people using either Messenger, WhatsApp, Signal, or Telegram (or iMessage in the USA but that's mostly an outlier compared to the rest of the world).

From one linked thread:

RCS isn't an open platform in practice. It isn't even as open as SMS/MMS. It heavily depends on proprietary Google and carrier infrastructure in practice. We can start by replicating Google's approach and then we can work on only using carrier services for carriers where it's actually supported.

So yeah, probably why it took so long

To be clear, it's not done yet. The past tense in the post title is misleading.

It heavily depends on proprietary Google and carrier infrastructure in practice.

This is the same as practically every carrier feature though. Carriers are a pain to deal with and all their infra is proprietary, so usually only the big companies like Google and Apple have the motivation to integrate with them and build out new services.

So, apparently there's a new UI, but no screenshots?

🤦

If I'm reading the clipboard part right, and seems people on the forms are thinking the same;

If an app can only access clipboard content that it set, does that mean we can't copy/paste between apps? That would be ridiculous.
Does the act of pressing "paste" over right the block, and GrapheneOS will only block the background access apps have?

I like IOS approach, where it asks you before pasting "this app is trying to copy from another app", and you can allow or decline it. But it is really annoying sometimes.

They mention permissions so my guess, without seeing it in action, is the permission is to be able to access the global clipboard, otherwise you're just using an isolated clipboard.

Also they mention the keyboard having a paste button as a fallback for misbehaving apps, but IDK if that locks you into using GOS' very mediocre keyboard.

In the longer term, we plan to add support for RCS including support for the standard end-to-end encryption (E2EE)

thank god i can finally ditch google messages if i want rcs

Hopefully they got rid of the ugly monochrome icons.

The important distinction to me is whether clipboard access is user-initiated or happens silently in the background. Explicit paste should stay frictionless, while background reads are where tighter controls make sense. If GrapheneOS can enforce that boundary without adding an iOS-style prompt every time, that seems like a strong compromise.

I am reading through lines and I seem to be stuck confused. Why isn't the whole clipboard partitioned?

Example:
Youtube - separate array(whatever) holding its clipboard
Facebook - separate array(whatever) holding its clipboard

When trying to copy-paste between apps, simply link its containers and provide cross-access for said apps.
This way you keep it modular and as secure as possible while not allowing other services to access a specific container.

I have yet to use GrapheneOS, sadly past phones I had did not support it.

when can I get the motorola flagship