RCS planned, I'm all for it
post
replies:
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.
replies:
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
This is good news
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.
So, apparently there's a new UI, but no screenshots?
🤦
replies:
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.
when can I get the motorola flagship
all 14 comments