@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.

@davidgerard Only the finest artisanal slop

@davidgerard

I was always suspicious of the fact that they focused mainly on using Google software 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?

@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.

@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.

@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.

@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"

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