this post was submitted on 15 Oct 2026
236 points (77.2% liked)
Fuck AI
8557 readers
1063 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.
Rules:
- Relevant posts only.
- No bigotry.
- This isn't a place to talk about the cons and (supposed) pros of AI for different use cases. This is /c/fuck_ai .
- Especially no AI advocacy.
- Don't make any posts that are just AI content with no context unless the point of your post is obvious from content. (Don't just post slop advertisements or slop political cartoons. At least make your point about it clear so we know you aren't just trolling.)
- Venting is part of the purpose of this community, but don't aim frustration or accusations at other users.
- These rules are a living document that may change in the future.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I only recently installed Linux for the first time on my HTPC last year and it was flawless at first. Last couple months I've noticed a handful of bugs and system hangs that never happened before. Anecdotal, I know, but it worries me as a novice. I built my home server on this machine specifically to avoid microslop...
I get random blackscreens with my OcuLink-connected Radeon GPU on the latest kernels...anecdotal evidence, too, but my slopcode senses are tingling. It worked really well on 6.x kernels last year.
Software will probably get worse, but very slowly. One little stab at a time until it becomes very noticeable.
I find this annoying where every regression now gets associated with "AI slop". I agree that genuine slop is bad. But Radeon regressions were pretty damn common pre-AI-slop too. My 6600M, my Vega iGPU and others all had regressions. And I've seen this pattern with everything else lately too, where even bugs that have existed for over a decade are associated with LLMs. Pointing things out specifically is important in these scenarios IMO. "This LLM-generated and claimed-to-be-human-reviewed patch caused this regression." That's much more useful than "slopcode senses" that people seem to be triggering in projects that have existed for so long. (I do get where you're coming from though...)