2026-03-03 17:23:52
RE: #Microsoft #SLOP
RE: #Microsoft #SLOP
I have the feeling my smartphone OS is trying to tell me something. OnePlus, never settle.
#slop #OnePlus #NeverSettle
Last night I had a #nightmare.
I dreamt that I've sent a pull request to a project, and it turned out that the whole CI pipeline is just LLMs dynamically slopping random tests against the PR. And of course these tests couldn't pass, and you could do nothing to make the PR actually pass tests.
#AI #LLM #NoAI #slop
#PythonPoetry is yet another project that disrespectfully treats human bug reporters with #slop:
#NoAI #NoLLM
Reading about the leaked Claude source code, I muttered:
- pre-mature deployment of April 1st prank? 😜
- strategy by AI to misdirect or lull competition? 🧠
- nah, more likely just slop. AI writing its own code. 💩
#Claude #AI #LLM #possibilities #slop
(YouTube, #AI #slop) Neuralink 2026: The Year Humans Become Digital https://www.youtube.com/watch?v=O5ArS-CBIjE Blindsight? Bette…
I absolutely cannot stand Microsoft's products. I have to deal with them at my job and just everything Microsoft does is a paywall, over complicated, or so shitty and bloated I want to jab pencils in my eyes. /rant #Microsoft #Slop
Let's normalize calling anything output with an #LLM #slop.
It doesn't matter that you've only used an LLM to fix punctuation. It's slop.
It doesn't matter that you've spent an hour reviewing the slop to make sure it's good. It's still slop.
It doesn't matter that it's better than anything you wrote your entire life. It's slop.
If you didn't write it yourself, it's just a glorified LLM slop.
#AI #NoAI #NoLLM
Searching the Internet in the past: you type a few keywords. You get a bunch of sites. You check these sites for the information you need.
Searching the Internet in the future: you type your question as a full sentence. You get an answer that may be complete bullshit. You ask for sources. You get a list of sources that may be entirely made up. You check the sources. They are an obvious #AI #slop…
#LLM #enshittification #NoAI #NoLLM
Proper #security nightmare time.
#LMDB is a database that's designed to operate on trusted input. Upstream has historically rejected all bug reports regarding problems with malformed input.
Py-LMDB project provides #Python bindings to LMDB that are normally built against bundled LMDB. Someone recently started mass-filing "untrusted input" vulnerabilities against py-lmdb, and py-lmdb started #slop - coding fixes to their bundled LMDB. Of course, nobody even bothered reporting most of these bugs upstream, and the one that I've seen reported was rejected as "don't do that".
Py-LMDB supports building against system LMDB, and #Gentoo was doing that so far. However, now we are facing a problem: system LMDB operates under the assumption that it is working on trusted input, while py-lmdb (and its bundled LMDB) operates under the assumption that it may be working with untrusted input. The guarantees no longer align.
If we continue to use system LMDB (and skip all the added slop tests that literally cause Python to crash), then Gentoo's py-lmdb package will now have different input expectations than upstream py-lmdb. And of course we can't just remove that crap because someone added exactly one package (TorchVision, i.e. part of the plagiarism machine suite) depending on it.
https://bugs.gentoo.org/971352
The key takeaways from the early part of the #chardet thread (I didn't read beyond the ~30 first comments, I have my limits).
1. People there love cosplaying lawyers. Except when the other side also starts cosplaying lawyers, in which case they suddenly divert to suggesting asking professional lawyers.
2. Almost nobody there is concerned with ethics or morality.
3. There's a lot of GPL haters there. Like, they seem the kind of people who don't really care about licensing at all, just used MIT in their projects because it was cool and they heard something about license incompatibility and now bash at everything that's (L)GPL.
4. People don't get that LLMs are statistical models and can't build anything from the ground up. All they can do is remix, which implies they use existing code for inspiration.
5. The maintainer who did the rewrite is a total asshole, and is perfectly aware of it.
Honestly, I'm truly waiting for the subsidizing to end and companies start charging obscene amounts for the use of LLMs. Of course, the reality is that we're totally fucked. We have a lot of projects that adapted a lot of #slop, and people who are being increasingly addicted to this shit. The moment they can't afford it, we'd be left with lots of broken code nobody wants to maintain.
And I definitely don't want to put my effort into packaging crap if its maintainers don't even bother trying.
#AI #LLM #NoAI #NoLLM