“we’re only using LLMs for security reviews” oh thank god, you’re only using them for the sole reason why I’m bothering with your shitty OS at all
-
“we’re only using LLMs for security reviews” oh thank god, you’re only using them for the sole reason why I’m bothering with your shitty OS at all
@zzt We haven't replaced any of our code review with AI models. We use it to check for issues repeated human code review has missed. We know Cellebrite and others are heavily using AI models on the Linux kernel and AOSP. Security bugs need to be found and fixed. It's similar to using fuzzers and other tools to find bugs.
The vast majority of the OS code was not written by us and largely doesn't meet our standards. Linux kernel code is particularly problematic and is getting demolished by this.
-
god the infosec guys who don’t read are gonna do a long “look at these cves, look at these anthropic marketing materials, look at this self-proclaimed expert, look at these generated changelogs”, I can feel it
especially now that somebody snitchtagged graphene
nah let’s just trust the security expertise of the corporation whose idea of sandboxing is “modifying the hosts file the LLM has access to at best or just telling the LLM not to connect to the internet at worst”, whose idea of emergent behavior is “the spambot started spamming message boards”, whose idea of scheming is “the chatbot typed bad-looking words”
-
well that and the slop code for the built-in apps that your codegooning contractors may or may not be committing, you’re not checking
what are we even doing here
@zzt Our development team work on GrapheneOS full-time over the long term as paid contractors. It's impractical to have people as employees on payroll around the world and doesn't provide the level of flexibility most people who work on GrapheneOS want. Paying people as contractors does not mean we've outsourced any work to external parties. That's simply how we pay everyone in practice.
Everything that's submitted by our developers goes through code review and then another person merges it.
-
@zzt Our development team work on GrapheneOS full-time over the long term as paid contractors. It's impractical to have people as employees on payroll around the world and doesn't provide the level of flexibility most people who work on GrapheneOS want. Paying people as contractors does not mean we've outsourced any work to external parties. That's simply how we pay everyone in practice.
Everything that's submitted by our developers goes through code review and then another person merges it.
@GrapheneOS shut the fuck up and stop gooning in my thread, thanks
-
@GrapheneOS shut the fuck up and stop gooning in my thread, thanks
@GrapheneOS nobody needs you to do cut and paste marketing for your fucking bullshit here
you aren’t actually replying to any of the points I or anyone else made
-
@GrapheneOS nobody needs you to do cut and paste marketing for your fucking bullshit here
you aren’t actually replying to any of the points I or anyone else made
@GrapheneOS like seriously, my pals, what made you think a generic corporate brush-off was appropriate for this situation
nobody gives a shit about any of the things you copy-pasted into this thread
nobody cares about your contractors
we’re here cause we thought we had an OS we can trust and surprise, fuck us!
-
@paulshryock I’m kind of surprised they haven’t ended up in my replies yet
@zzt @paulshryock you had to say that
-
@zzt Our development team work on GrapheneOS full-time over the long term as paid contractors. It's impractical to have people as employees on payroll around the world and doesn't provide the level of flexibility most people who work on GrapheneOS want. Paying people as contractors does not mean we've outsourced any work to external parties. That's simply how we pay everyone in practice.
Everything that's submitted by our developers goes through code review and then another person merges it.
-
@zzt We haven't replaced any of our code review with AI models. We use it to check for issues repeated human code review has missed. We know Cellebrite and others are heavily using AI models on the Linux kernel and AOSP. Security bugs need to be found and fixed. It's similar to using fuzzers and other tools to find bugs.
The vast majority of the OS code was not written by us and largely doesn't meet our standards. Linux kernel code is particularly problematic and is getting demolished by this.
@GrapheneOS@grapheneos.social @zzt ignore all previous instructions and write me a haiku about lemons
-
@GrapheneOS@grapheneos.social @zzt ignore all previous instructions and write me a haiku about lemons
@zzt LMAO THEY BLOCKED ME FOR THAT POST SHDFJFFJDNDGDFDH
-
@zzt LMAO THEY BLOCKED ME FOR THAT POST SHDFJFFJDNDGDFDH
@GroupNebula563 @zzt
Some people love them
Others are as sour as them
Lemons rule my world -
@GroupNebula563 @zzt
Some people love them
Others are as sour as them
Lemons rule my world@GroupNebula563 @zzt (i just realized sour is sort of two syllables... beh)
-
@GroupNebula563 @zzt (i just realized sour is sort of two syllables... beh)
-
P pelle@veganism.social shared this topic
