When an app asks for permissions, the OS should not only let you answer yes or no. Every category should have a "yes, but feed the app fake data" option.
Want my contacts for no reason? Have these generated fake ones! Wanna listen to my microphone? Here's random ambiance sounds! Location? I'm on a tiny 5x5m island!
Hell yeah! Put it all in your databases mfers!
Actively punishing services wins over boycotts any day. Didn't want that junk in the database? Don't ask for it!
GrapheneOS does this- contacts and storage have scopes such that you can fake out the app into thinking it has access but really quarantine it to a specific folder. I use this for things like applications where I want it to have file access for photos, but only the photos I send to that folder.
Yes, but I really think the project would benefit greatly from better adoption, even if there’s a second unofficial branch that people can just compile for their own devices. Lineage made it so easy i can make my own compilation even if they no longer support it. Download official distro, run command that sets your phone’s drivers (grin their repo, even if no longer supported), compile… Go for a lunch break, profit. I’ve done this a few times for an S7, even though i have a pixel 7 running graphene now.
Why though? There was a recent post around here that I think really hit this home- “whatabboutism”. We don’t need Graphene to fulfill every scenario. We need it to do it’s job well, which is does, and if it doesn’t fulfill your needs, then pick something else like LineageOS which has much more broad support at the expense of a less secure OS.
You sure can compile Graphene on other devices with varying results, the supported/tested device list used to have things other than Google devices on it- part of this comes down to support and dev time too.
GrapheneOS does this- contacts and storage have scopes such that you can fake out the app into thinking it has access but really quarantine it to a specific folder. I use this for things like applications where I want it to have file access for photos, but only the photos I send to that folder.
Yeah, but only few newest Pixels are supported.
Kinda workaround is the Insular.
For good reason! Security updates are super important and the project extends upon having regular updates there.
Yes, but I really think the project would benefit greatly from better adoption, even if there’s a second unofficial branch that people can just compile for their own devices. Lineage made it so easy i can make my own compilation even if they no longer support it. Download official distro, run command that sets your phone’s drivers (grin their repo, even if no longer supported), compile… Go for a lunch break, profit. I’ve done this a few times for an S7, even though i have a pixel 7 running graphene now.
Why though? There was a recent post around here that I think really hit this home- “whatabboutism”. We don’t need Graphene to fulfill every scenario. We need it to do it’s job well, which is does, and if it doesn’t fulfill your needs, then pick something else like LineageOS which has much more broad support at the expense of a less secure OS.
You sure can compile Graphene on other devices with varying results, the supported/tested device list used to have things other than Google devices on it- part of this comes down to support and dev time too.