arXiv talk at #OpenRepositories "We are banning users who submit unchecked LLM-generated content for a year!" 🙌

"LLM Slop: Sanction users who submit unchecked LLM-generated content that degrades repository integrity."

#OpenRepositories2026 #OR2026 #arXiv #LLMSlop #AISlop

Today in unethical LLM companies.

[email protected], probably a bot although claiming the human name "Luca King", has sent several emails to me, same minute, different Gentoo project aliases. Subject is the name of a Gentoo package. Email body:

"Hi,

I read the Gentoo metadata for $subject.

I'm curious are you using coding agents to build this?

Luca"

It's obviously trying to sell me slop. The human behind this should be ashamed, and preferably arrested for fraud.

#llmslop #LLMs

Getting a bit sick of fielding LLM PRs. I understand why many projects have a no-LLM policy. I'm generally fine getting good PRs, LLM-aided or not, but the poor ones are just complete wastes of time. They all read the same, good or not, so I have to spend quite a bit of time sussing through it to determine which ones are useless or not. They're all "bug fixes" or "security improvements".

No, it does not make sense for an CLI argument parsing library to scan through argv to make sure it doesn't contain null pointers. That's ridiculous. No, it does not make sense for a CLI argument parsing library to defend against an input argument size overflowing size_t. When the fuck would that ever happen?

The PRs that actually fix a missed fallthrough causing undefined behavior look exactly the same as the ones that defend against somebody passing a 4GiB string as a CLI argument. They all have descriptions full of nothing but fluff, they all add much more code than they remove, they all bloat the code with more abstractions and indirections, and they all take way longer to review than the equivalent human-written code.

I'm even not against getting LLM contributions, but I'm getting sick of the fucking spam, and I'm losing patience with figuring out the difference between the two.

#LLM #LLMs #LLMSlop #AI #Spam #Code #Programming #PR #PullRequests #PullRequest

Dank #LLMSlop sehe ich immer mehr Posts von deutschen Muttersprachler*innen ! mit völlig abstrusen Wortbildungen. Leute, macht Fehler. Steht zu euren *menschlichen* Fehlern! Aber bitte tut nicht mit siebenfingrigen Wortgetümen, als seid ihr perfekt!
Irrt euch menschlich. Maschinenkrampf lässt euch lächerlich erscheinen, weil echte Menschen so nie klingen.

#Sprache #SpracheLernen #fehlerkultur #Wissensverlust

Can Firefox stop trying to force me to try its AI features already?

(I'm still using it because constraint, don't come to me with alternatives, I'm not asking.)

#Firefox #LLMslop #CorporateScumbaggery

The amount of hand-holding and guidance you have to provide to LLMs in order to keep them from spewing inaccessible HTML is quite ridiculous. Gotta admit though that setting up a CI to catch these issues is a good idea, whether you use LLM or not.

https://frontendmasters.com/blog/ai-generated-ui-is-inaccessible-by-default/

#a11y #LLM #llmslop #WebDev

AI-Generated UI Is Inaccessible by Default – Frontend Masters Blog

It doesn't mean you can't get AI to help with accessible code, you've just got to know what you're doing.

If you're unsure how rare LLM plagiarism is or isn't for 💻 programming code, watch this clip! ⚠️

Full source: https://www.youtube.com/watch?v=xvuiSgXfqc4 (Not legal advice, watch yourself and draw your own conclusions.) #llmslop #antislop #antiai #noai #stopai #llm #llms #ai #generativeAI #opensource

Help me boost this post if you're curious what the Linux foundation thinks: https://hachyderm.io/@ell1e/116285351290767548

RE: https://mastodon.social/@gsnsp_com/116301926711026096

AI sloppity slop.

The cover illustration screams AI. Sure enough, zooming in I see someone apparently painting from behind the easel, while her companion looks on from in front.

Authored by"Dr Elena Voss". I see elsewhere that "Dr. Elena Voss, featured on our blog, is an advanced AI agent we developed to share its unique perspectives". From the site OrderOfThePrompt, a guide to "the art of prompt engineering".

#AISlop #NoAI #No_ai_bullshit #AI #LLM #LLMSlop

Linux Foundation's AI policy: "If any pre-existing copyrighted materials[...] are included in the AI tool’s output, [..] the Contributor should confirm that they have have permission from the third party owners" https://www.linuxfoundation.org/legal/generative-ai

"If"? Why not "whenever"? https://github.com/mastodon/mastodon/issues/38072#issuecomment-4105681567 https://dl.acm.org/doi/10.1145/3543507.3583199 https://www.sciencedirect.com/science/article/pii/S2949719123000213#b7 https://www.theatlantic.com/technology/2026/01/ai-memorization-research/685552/

And how would the contributor even be aware, should they research every snippet for hours?

Seems like an impossible policy, or am I missing something...?

#AIslop #LLMslop #LLM #LLMs #slop #generativeAI #Linux #opensource #linuxfoundation

Generative AI Policy | Linux Foundation

Code or other content generated in whole or in part using AI tools can be contributed to Linux Foundation projects. However, there are some unique considerations related to AI generated content that developers should factor into their contributions. 

from @[email protected] on the @[email protected] frenzy (and the Karpathy snippet was a fake) more: www.technologyreview.com/2026/02/06/1... in @[email protected] #LLMSlop