Featured Articles

Crowdfunding on Crowd Supply (Review of my experience)
Nightmare on Lemmy Street (A Fediverse GDPR Horror Story)
Detecting (Malicious) Unicode in GitHub PRs
WordPress Multisite on the Darknet (Mercator .onion alias)
Introducing BusKill: A Kill Cord for your Laptop
Continuous Documentation: Hosting Read the Docs on GitHub Pages (2/2)
WordPress Profiling with XHProf (Debugging & Optimizing Speed)
Trusted Boot (Anti-Evil-Maid, Heads, and PureBoot)
Hardening Guide for phpList
previous arrow
next arrow

Why I was banned from GrapheneOS by Daniel Micay

Why I was BANNED from GrapheneOS

Why was I banned from GrapheneOS? That’s a good question.

Anyone who follows me on GitHub knows that I make a lot of contributions to many different open-source projects, especially security-related ones.

A couple years ago, I wanted to try-out both GrapheneOS and CalyxOS, but I found that a niche security feature that’s very important to me hasn’t been implemented in either ROM, so I opened a friendly feature request ticket in both ROM’s repos:

https://github.com/GrapheneOS/os-issue-tracker/issues/2052 https://gitlab.com/CalyxOS/calyxos/-/issues/1573

My feature request for GrapheneOS

My feature request for CalyxOS

Neither ticket got much traction. There was some discussion on the CalyxOS ticket. But the GrapheneOS ticket was closed by Daniel Micay (Lead Developer of GrapheneOS at the time) 5 hours after I opened it. I forgot about it.

A year later, someone commented on the GrapheneOS ticket (it was the first and only comment other than Micay’s) expressing interest in my feature request, including some useful information: an implementation (that was blocking the CalyxOS ticket) was already written by LineageOS.

When I saw the comment in my email inbox (and realized it might unblock the feature getting added to CalyxOS), I got excited. I tried to
. . . → Read More: Why I was banned from GrapheneOS by Daniel Micay