I am sorry to say Graphene has fallen to the slop.

[angelthorns@social.treehouse.systems]

@davidgerard luckily my grapheneos phone just blew up anyway

[dysfun@social.treehouse.systems]

@davidgerard yes it's just more of the same "it's only vibe coding if you don't read it" bollocks

[dysfun@social.treehouse.systems]

@davidgerard also omg ph33r our 1337 code reviews, which will definitely catch all the bugs

[angry_drunk@union.place]

@davidgerard "Look man, it ain't gambling. See, I gots a system." <twitch>

[haverholm@radikal.social]

@davidgerard They're literally doing the "Guns don't kill people, we have to have guns to kill other people with guns" argument.

"Get more and bigger guns now, it's just a tool"

[dnkboston@apobangpo.space]

@davidgerard the part about contractors paying for their own llm tokens is pretty wild.

https://grapheneos.social/@GrapheneOS/117227373537383215

Also, the sock puppets seem like they used an llm.

[dnkboston@apobangpo.space]

@haverholm That pushed past offensive and straight to crazy.
@davidgerard

[violetmadder@kolektiva.social]

@dnkboston @haverholm @davidgerard

Dammit

[haverholm@radikal.social]

@dnkboston It's just mutually assured destruction now, but with "AI" companies profiteering. @davidgerard

[shimst3r@famichiki.jp]

@davidgerard "Many valid issues are reported in between the hallucinations and other nonsense. It takes additional time to confirm which issues are real and address it."

Well, how does it help then?

How does it help?

In an OS that people use because they fear for their lives.

How does it help?

I am beyond angry.

[piffio@mastodon.social]

@davidgerard That sucks.

I wonder if anyone has started making up a list of untainted/ethical/respectable OSS projects, as it's becoming increasingly hard to find projects that haven't given up to the broligarchs.

If not, should we start one? I reckon it might be depressingly short.

[robinsyl@meow.social]

@shimst3r @davidgerard I think I posted this in another thread but like, I should start creating issues saying a random block of code has a vulnerability. They must take my issues seriously because what if I am right and they miss out on a valuable report?

[haverholm@radikal.social]

@piffio I'm not sure there is a list with both criteria, but I've seen a few #NoAI lists floating about.
* https://noai.starlightnet.work/list.html
* https://noailist.org/
* https://codeberg.org/brib/slopfree-software-index

...of course I can't find the first one I thought of right now. Edit: found it! Added to top of list.

@davidgerard

[contrasocial@mastodon.social]

@davidgerard

I was always suspicious of the fact that they focused mainly on using Google hardware honestly. They claimed it was because it has the best security features, but then go and use a method of generating code that's notorious for creating security problems?

[oheso@ieji.de]

@davidgerard Only the finest artisanal slop

[zimzat@mastodon.social]

@davidgerard A cursory glance at their posts suggests they're stressing it isn't vibe *coding* if it's only "auditing" existing code?

Which is a very fine line that still results in /using/ the slop machinery.

I wish the software development ecosystem would fix the underlying architectural problems rather than keep brushing them under the rug. But we're now all so entrenched in arguing to slop or not to slop that few are talking about what it means not to slop.

[bredroll@mas.to]

@haverholm @davidgerard they may well just be "tools" but they are tools created by stealing the work of our artists, writers and musicians and free software legacy, tools that are run by companies that cant even spell "ethics" let alone coherently define it with a straight face.

[raccoon@fedi.raccoonden.moe]

@davidgerard
Time to switch to a fairphone with calyx next time I have to change phone

[mansalia@social.maid.zone]

@davidgerard
You posts atrract immense amounts of whiny imbeciles with reading impairments

[haverholm@radikal.social]

@Bredroll @davidgerard Narrator: "They were not, in fact, only tools"