this post was submitted on 24 Feb 2024
122 points (88.1% liked)

Privacy

30812 readers
1557 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 4 years ago
MODERATORS
 

I want to mainly use it for privacy over its "security". I don't know what makes everyone fine with running it on fucking google pixels. Is there some kind of "low security" version or something for other phones? I'm so tired of certain organizations infiltrating privacy communities and making people believe in improving "security" by voluntarily giving up on privacy and using even non free software like that insecurities blog and other people.

you are viewing a single comment's thread
view the rest of the comments
[–] sv1sjp@lemmy.world 11 points 5 months ago (5 children)

You can use DivestOS which pretty much it offers anything that can be found on GrapheneOS. Also, DivestOS supports relocking the bootloader to many devices

[–] jet@hackertalks.com 16 points 5 months ago* (last edited 5 months ago) (3 children)

I love the divest guy, but he is a one man show.

https://divestos.org/pages/about

Divest is lineageos plus patches.

My personal recommendation for secure devices is: grapheneos, then calyxos, then divestos, then lineageos

There are big differences between graphene and divest: sandboxed Google play for instance. For a detailed comparison see privacy guides https://www.privacyguides.org/en/android/#divestos

[–] sv1sjp@lemmy.world 4 points 5 months ago

Ι was talking about degoogled experience. DivestOS supports a lot of devices which is not a case with calyx and graphene.

load more comments (2 replies)
load more comments (3 replies)