this post was submitted on 10 Nov 2024
43 points (92.2% liked)

Privacy

4241 readers
2 users here now

A community for Lemmy users interested in privacy

Rules:

  1. Be civil
  2. No spam posting
  3. Keep posts on-topic
  4. No trolling

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 1 week ago* (last edited 1 week ago) (3 children)

I understand the decision. It’s kind of unreasonable to expect a developer to maintain a release without access to reasonably-maintained source to work on.

[–] [email protected] 5 points 1 week ago* (last edited 1 week ago) (2 children)

Yep.

But in the Real World, what's the pragmatic difference between Graphene and a well-managed Lineage or DivestOS device, since security and privacy are both managed via layers?

I'm genuinely not being snarky. I tried running Graphene and had issues, and their support was atrociously condescending and critical, so now I'm running DivestOS instead. I've run Lineage on other devices without Google.

[–] [email protected] 2 points 1 week ago (1 children)

I think there’s definitely security concerns which is their highest priority. If the kernel isn’t maintained, security issues aren’t getting patched. You might be able to cobble something together, but there’s going to be holes.

I think they’re paranoid and that’s not a judgment. Rightly so if security is your first priority.

[–] Kernal64 4 points 1 week ago

According to the Graphene OS website, the main issue isn't even that. It's that you can't relock the boot loader on almost any device other than a Pixel. That leaves a huge security hole on the phone, and it's one that almost all rooted users of other phones have open, whether they realize it or not.