From 9cbbb209e8ad82c154097c4617d8ae93bf54ddcd7b81aafa541f532065836deb Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Thu, 6 Jul 2023 00:00:00 +0000 Subject: Correct typo --- content/entry/the-problem-with-grapheneos.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content') 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. -- cgit v1.2.3