d_ed in Elk: "@aks @f4grx @thomholwerda @kde The tool doesn'..."

Not SlopWatch yet, as the patches need to be approved, but slopcode is coming to the amdgpu driver and... Kwin. All of the code involved was "written" by Claude.

What's

's policy on slopcode?

https://hwentland.github.io/2026/03/10/plane-color-pipeline-csc-3d-lut-kwin.html

hwentland.github.io

Plane Color Pipeline, CSC, 3D LUT, and KWin - Harry's Blog

holy fuck how cooked are we?

i have been warning people but nobody listens

The tool doesn't matter, the output does.

Handling LLMs is such a spectrum, from vibe coding without reading or understanding anything to being 100% identical to what the author would have written by hand. Banning the latter would be like banning certain text editors.

We have been getting human written slop for years! We deal with this the same way.

March 14, 2026 at 1:25:21 PM

as long as the output does not cause legal issues, yes

that being said there is whole mountain of ethical issues behind the tooling, that being from energy issues to dubious legality.

Slop has always been there, but the cost of the slop is different

Yes, but unlike text editors, LLMs and the companies behind them also:
- assist in waging war using the same tech
- drive up costs for marginalized and often poor communities by building lots of data centers
- throw out all their climate goals to pursue AI
- lie constantly about the capability of their tools to hype them up, causing lots of damages
- I could keep going...

point is, unlike a text-editor, LLMs have real implications to their use that reach beyond the software.

It's a fundamental mistake to imagine a product as a static thing completely separate from the process that produced it. And the tool shapes the hands of the person who uses it.