The series began 3 days ago (Part 1, Part 2) and has since then spilled over to other sites, but all the important points will remain here in the "core" series (that's also how we covered GitHub fraud, leading up to SLAPPs).
Earlier in the week we thought of down the latest kernel git file/s, unpacking it, searching for "assisted by", then sorting the list and reducing the output to a list of serial sloppers who contaminate Linux, eventually making a "shame list", maybe tracing that back to employers and aggregating across staff (paraphrasing IRC). Some people in our community supported this idea (no issue related to ethics of "shame lists") and urged us to go ahead and do that.
Going to git.kernel.org over HTTPS, this is what I get: (kernel.org, made by slop bots, hammered by bots too)
Due to de facto DDoS. It's a motif now, isn't it?
Should we take such a status quo for granted?
After some "JavaScript games" I finally get some JavaScript-free (actual) page:
Who knows how many of those recent commits are LLM slop. There are real names of real people behind such slop and not all of them offer a disclosure of their misuse of "Plagiarism Engines" to obfuscate other people's code (RMS has just commented on that) or basically make it seem plausible and original.
"It's not just one repository," an associate points out, as "there are dozens which go into making a single kernel..."
So there can be a per-repo (repository) sloppers shame list with "high scorers", plus totals for all repos combined. █