GrapheneOS imposes a set of restrictions on how generative AI can be used in our project and community. It isn't forbidden but rather we imposed rules based on actual issues.
Posts made in our forum, chat rooms, issue tracker and the rest of our project must be written by humans. There's an exception from this rule for translation and accessibility features. That means commit messages, pull request messages, bug reports and feature requests are expected to be written by humans, not a machine.
Replying to @GrapheneOS@grapheneos.social
@GrapheneOS for an OS project that refused porting to non-PIxel h/w for so long b/c other platforms didn't meet security reqs, this pro-LLM stance is ludicrous.
~all bugs found by LLMs can likely be found by other methods using the same-or-less compute resources, especially w/ the human effort "babysitting" the LLMs to ensure they don't go off the rails.
there just aren't billionaire fascists subsidizing that compute, be honest about it.
stop covering + doing PR-by-action for LLM fascists
Replying to @elle@weathered-steel.social
@elle @GrapheneOS what's the relation of Google being Google and a language model?
Replying to @dasmatus@mastodon.social
are you serious? what is the relation b/w GrapheneOS taking security so seriously that they wouldn't port their OS to h/w that didn't have Pixel's special sauce, and now being fine using LLM code + bug reports + dedicate human time to "babysit" the LLMs?
my intention is not to "bully" @GrapheneOS. we need folks like you in FOSS building rock-solid projects. I'm merely voicing criticism, and hoping the team explores other alternatives.
leave big (proprietary) LLMs in the bin
Replying to @elle@weathered-steel.social
@elle @dasmatus GrapheneOS is based on Linux, AOSP, Chromium and hundreds of other upstream projects heavily using AI generated code.
Our OS development team hasn't been using any AI code generation but yet the OS is heavily using it because the vast majority of the code comes from upstream projects. Linux and Chromium are both massive projects.
Firefox is heavily using it too, so that isn't relevant to this. It's nowhere close to what we would need to use it as a replacement regardless.
Replying to @GrapheneOS@grapheneos.social
I know, that's why we need as many folks on the side of "we're not using this shit, those big-tech LLM fucks can get bent"
it's also clear FOSS teams don't have the resources to rebuild / fork foundational projects like Linux / Chromium / Firefox, each one containing millions of LoC.
Replying to @elle@weathered-steel.social
@elle @GrapheneOS @dasmatus if you have watched reported vulnerabilities over the last few months, you'll see that there is a huge increase in the last few months due to LLMs. LLMs finds vulnerabilities that older methods such as static analysis and fuzzing didn't and don't find.
Since security is paramount to GrapheneOS and adversaries are using LLMs, the only way to defend is to use LLMs for auditing too.
LLMs are here to stay, let's boost open models to own the means of production.