[deleted]
I suggest go to Privacy Guides https://www.privacyguides.org/en/. They have a ton of articles and tool recommendations.
Recommended approaches and apps by the GrapheneOS team
[deleted] thanks. I think most people now about them, but it isn't easy to go throw for awry one. I like this side and it is indeed informative, but my idea described above can help people further and hopefully more easily.
That is what i will discuss here. :)
I invite all to proof me Wrong, evtl. We came together to a better idea. :)
the GOS homepage is very informative and gives a lot of information and tips
7 days later
AlphaElwedritsch that's true, but its not what iam talking about. :)
Keep in mind that the GrapheneOS development and moderation teams already have enough on their plate and that diverting time and resources to create and manage/keep up-to-date something like this will only hinder more important tasks that are a much higher priority for them.
ErnestThornhill i know. My hoping is that many question don't have bean ask in the forum for example because of a website like this.
kebab_definite I'm not sure what you are trying to say but there are already plenty of guides available and websites similar to what you suggested which align with GrapheneOS and this community.
all this information is available. It's just not described as a guide in case studies. But you can find it all.
and that's exactly what's good. That everyone can configure their needs individually.
you have to get to grips with the subject. The topic is too difficult for lemmings
kebab_definite try Michael Bazzell digital book on mobile devices. It’s updated every few months and represents the (for lack of better word) more extreme way of how to handle grapheneOS and your mobile device.
- Edited
Bootlace1170 I love Michael Bazzell and learned a lot from him, but his books are not the universal answer either. He gives specific advice like using ProtonVPN, Twilio VoIP numbers and PopOS on Laptops from System76. These can never be the answers for everyone (they're not even objectively the best answers when it comes to security and privacy). People need to learn to not fall for best practice fallacy and find their own, unique answers that serve their threat models best.
For this, privacyguides has a very good database to draw from after you asked the right questions and know what you specifically need to protect against whom.
All we (as a community) could do is an even more extensive database that requires maintaining. But I think the individual approach we have is much better. People ask questions specific to their situation and we can give education for them to make informed decisions. It's not the convenient solution, but it's the only one that truly works in my experience.
I'm not speaking for the project btw.
That all being said, yes educate yourself with Michael Bazzel's books. And podcasts and channels from The Hated One, Naomi Brockwell, Side of Burritos and Closed Network by Simon Walsh. And also learn which channels to avoid as they give harmful advice (some maliciously, some just from ignorance).
- Edited
N1b People ask questions specific to their situation and we can give education for them to make informed decisions
OK, good, practical use case then: what are the community's recommendations for the thread model described at the end of the report right here ?
Please keep in mind that the usecase described implies plausible deniability for highly non-technical users, and that it must be assumed that the devices will be searched. The adversary's remote capabilities are described here.
I think using this great tool adequately/properly is as important as the tool existing. Unless it really doesn't matter how we set users and apps up. It doesn't need to be a developer. It can anybody who fully understands how it works. I am heading over to some of the links provided above. Very much appreciate it.
[deleted]
Michael no longer recommends Twilio, VoIP.ms is what he recommends.
Voip ms welcomes individuals to use their service. With Twilio and Telnex? one has to get a domain with some history and con their way into getting service.