2026-09-09 22:59 UTC
@GrapheneOS@grapheneos.social many of your users spent a number of years recommending others to specifically avoid projects like calyx and "/e/" due to all the technical, security, and privacy reasons tirelessly documented by you, and use grapheneos instead, if they're able, *because* of your higher standards.
and now you keep saying on here that you can't avoid the upstream slop anyway.. others are doing it too, and that somehow makes it ok to use and "carefully" cook your own? this is wrong, and you know it
Replies (1)
-
@GrapheneOS@grapheneos.social 2026-09-09 23:14
@ludonaut@timetheft.rip That's the direct opposite of what we've said. We're primarily using it to improve the quality of our code through additional passes of code review. We started doing that after multiple external contributors used AI to find a bunch of issues throughout our code. Most of those were issues like crashes but some were more important. Some of our low-level hardening features were not providing as much security as they were meant to be. We began using it proactively to catch issues early.