Closed matchboxbananasynergy closed 1 year ago
I believe it's important to cover the following three points (related to each other). I realize it's actually android related instead of grapheneOS so it may be a better fit somewhere else on the website :
This could then be referenced in your work to introduce higher number of users (now 32) and inter user notifications
That's what I mean, I forgot about that part. The task list looks good to me then
I think it may be good to explain the location services in gOS. A limited amount of apps won't work well with redirected play services to GPS and generally GPS is quite bad (especially in cities with high buildings). It took me quite some time to figure out how to make an exception in one profile for apps I need sometimes to navigate when GPS isn't available.
Might be good to mention that VPN is based on the profile.
Might be good to explain that apps like Signal won't ring when you are in another profile. This is not super obvious because normal calls can be received in other profiles (depending on config).
A part of this guide, could point out specific privacy features GOS has:
I'm thinking we could cover SIM PIN codes, and some GrapheneOS specific features like media scopes, lte only mode etc. The page is quite long, and I think directing attention to specific areas of it could be helpful.
Another thing we could revisit is Google Phone/Google messages in https://github.com/privacyguides/privacyguides.org/pull/682, especially in light of Signal Removing SMS support from Signal Android.
There is often a barrier to get people to install something like Signal, and with modern phones often coming with Google Messages it may make more sense to use this on than an SMS/MMS application with no encryption. We wouldn't be adding it as a "recommendation card" to the instant messaging page, although we might mention it and link to this description.
The thought behind the Google Phone/Messaging application is that
I really want to nail home on the PG using Google Messages is a better alternative to installing some random SMS application "becuz Google" and sending all that data over an unsecure, unencrypted network, to a lazy telecommunications operator which are notoriously known for dragging their boots on security due to "legacy first" thinking.
Is this necessary with the GrapheneOS documentation? Seems like they do a good job listing all the features/guides on how to install etc.
Auditor Installation User Profiles Storage Scopes Sandboxed Google Play Banking Apps
Seems like there's really nothing we could add here.
I'm also not really interested in writing instructional guides on using GrapheneOS. I could maybe see a "feature highlights" blog post that could maybe act as a review of various features, but not a how-to and not KB content. That's my 2¢ anyways.
The idea here is to create a page that will walk people through GrapheneOS's features in a practical way to help them get up and running the way they want to. As GrapheneOS provides a lot of flexibility with things like Storage Scopes and User profiles, there are a few things to think about and consider before deciding how you want to set up your device.
The overall goal is to provide a useful resource about the OS without duplicating their existing documentation.
Ideas welcome.
Current task list: