What is Nostr?
mikedilger /
npub1acg…p35c
2024-05-13 09:25:43
in reply to nevent1q…e7un

mikedilger on Nostr: I've been using GrapheneOS since day 1, because I was using CopperheadOS for several ...

I've been using GrapheneOS since day 1, because I was using CopperheadOS for several years until the point that Daniel Micay burned the signing keys.

So I don't need to make any switch. I have a Google Pixel 8. And I'll keep using GrapheneOS for the time being.

But I have moods. Sometimes I get really paranoid about Google and Intel processors (more than other companies). I was really paranoid about Google at the time when I made the post. I thought "what if the explanations for why it only works on Google hardware are a lie?" I thought "Anybody can make explanations, they might not be true!"

Turns out you can lock the bootloader on LOTS of hardware that is not Google hardware. And the long list of features that MUST be on the phone to be supported are really not all necessary IMHO for the phone to be plenty secure. So call me a skeptic, but I'm still just not sure, and I don't have the time to dig into it.

Also Daniel Micay seems to be clinically paranoid and accusatory of all kinds of harrassment he doesn't actually receive, and that instability itself is kinda worrying. I like my developers to be paranoid, but not to the level that they can't function with other people. Before even CopperheadOS he was sort-of run off from the Rust community for making drama. They say he stepped down, but he's still the guy producing most of the commits. I hope he gets and stays well, but should I trust the OS? I dunno. I'm trusting it because I don't have a better option (I could read the source, compile myself, compare to AOSP and LineageOS and other AOSP projects, but that would take a year).
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c