@GrapheneOS Really? Will you be selling out-of-the-box grapheneOS devices in Brazil?
That's where i live!
@cornflakes4dinner @richardisaguyyyy Motorola officially has a long term partnership with us. They're actively working on GrapheneOS support and meeting all of our requirements. The aim is to have support on devices launched in 2027 and things are proceeding towards it. They also want to use our code within their OS to improve it but that's a separate thing from GrapheneOS and interests their business users rather than being what our users are interested in.
https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/
Could you share more infos about when and involved modells which this collaboration will start with?
is it a good idea to have a "age proxy" like the mechanism for filesystem access "spaces"?
when an app doesn't run unless the OS tells it the user is id-verified, then grapheneOS could say yes, the user is, even if the user hasn't done the process because they don't want to risk their biometric information
I'm no expert, just thinking aloud
@Kow @joenio California's law defines multiple age brackets:
* under 13
* 13 to under 16
* 16 to under 18
* 18 or older
This means it will leak a child's birth date to apps and websites on their 13th birthday.
There are ways to reduce the harm such as deferring age bracket updates to January 1 but those approaches likely wouldn't be accepted by parents and children. What's actually going to happen is leaking the birth dates of minors to apps and websites.
@DekOfTheYautja Toronto is the only location where the GrapheneOS Foundation operates. Having contractors elsewhere isn't our own direct operations as they're not employees but rather are their own businesses. We don't have any contractors in Brazil regardless.
If Canada passes a similar law then we'll need to contest that in court and plan out moving GrapheneOS elsewhere in case it becomes necessary. It would be an enormous pain and would disrupt things a lot but we'll do what's necessary.