summaryrefslogtreecommitdiff
path: root/content/entry/the-problem-with-grapheneos.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/entry/the-problem-with-grapheneos.md')
-rw-r--r--content/entry/the-problem-with-grapheneos.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/entry/the-problem-with-grapheneos.md b/content/entry/the-problem-with-grapheneos.md
index 532d3a0..46b1835 100644
--- a/content/entry/the-problem-with-grapheneos.md
+++ b/content/entry/the-problem-with-grapheneos.md
@@ -3,7 +3,7 @@ title: "The Problem With GrapheneOS"
date: 2023-07-06T00:00:00
draft: false
---
-[GrapheneOS](https://grapheneos.org) offers far more privacy and security than the Googled vendor-and-carrier-modified versions of Android that most Android users have. This would still be true even if people continued using the same proprietary apps after transitioning to GrapheneOS. For that reason, I don't want this entry to discourage anyone using who already has a Pixel from flashing GrapheneOS.
+[GrapheneOS](https://grapheneos.org) offers far more privacy and security than the Googled vendor-and-carrier-modified versions of Android that most Android users have. This would still be true even if people continued using the same proprietary apps after transitioning to GrapheneOS. For that reason, I don't want this entry to discourage anyone who already has a Pixel from flashing GrapheneOS.
However, I think the way GrapheneOS is marketed is potentially harmful. GrapheneOS is marketed as private and secure despite it only supporting devices with proprietary firmware and blobs.