RE: https://grapheneos.social/@GrapheneOS/117227060857282972
Bull-fucking-shit. Using the climate destroying, technofascist torment nexus for "code review."
A Magic 8 Ball would be just as accurate but with none of the environmental destruction, and torturing people in the Global South to screen it for you. 🙃🙃🙃
I've been writing about cybersecurity for well over a decade.
Marcus Hutchins is better known than I am, and he developed the killswitch for WannaCry in 2017.
He has written a ton lately on how horrifying and pathetic "using" Gen AI for "code review" or anything is. @malwaretech
Fuck you, GrapheneOS. I may have to switch to LineageOS. 🖕🏻🖕🏻🖕🏻
@aphedges @paulshryock We have high standards for code quality and that's not going to change. Tools to criticize our code and find things we missed despite repeatedly reviewing it ourselves are very useful. It's fine if most of the output is wrong because it finds actual issues.
Attackers are heavily using AI models to discover vulnerabilities and develop exploits. For example, Cellebrite is heavily using it including developing frameworks for reverse engineering and vulnerability discovery.
@kimcrawley @malwaretech Here's the official LineageOS policy for AI coding assistants:
https://github.com/LineageOS/charter/blob/main/ai-coding-assistants.md
Our requirements for people making contributions using AI coding assistants are significantly stricter than that. We require people to have a full understanding of the code beyond reviewing it. AI generated parts should have been cleaned up or rewritten in advance. It shouldn't look like they used it and needs to meet our high standards. We'll usually just ignore AI generated PRs.