@crell@phpc.social2026-05-16 18:32:53
@crell@phpc.social2026-05-16 18:32:53
@mgorny@social.treehouse.systems2026-05-18 03:34:20
@dichotomiker@dresden.network2026-06-09 08:33:35
@wyri@toot-toot.wyrihaxim.us2026-04-08 07:33:01
@frankel@mastodon.top2026-05-24 12:19:57
@neverpanic@chaos.social2026-04-02 15:11:45
I have the feeling my smartphone OS is trying to tell me something. OnePlus, never settle.
#slop #OnePlus #NeverSettle
@jackie@social.linux.pizza2026-03-22 22:24:36
@sjn@chaos.social2026-05-08 13:00:26
@draxil@social.linux.pizza2026-03-23 13:21:27
@smurthys@hachyderm.io2026-04-01 08:19:33
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
@mgorny@social.treehouse.systems2026-06-13 11:07:29
Content warning: IT being a neverending nightmare
Computers used to be fun. I used to use Windows 9x, and it was unstable as hell, and you kept having to lean over backwards to get things to work. Then I used bleeding edge Linux, and at some point I've ended up running pure framebuffer tty for months because X11 was broken. But despite all the breakage (or maybe even because of it), it was fun. It was fun because random accidental breakage was the worst you could expect.
Nowadays, accidental breakage is rare. Things are relatively stable. However, every step of the way you have to watch out for bad actors. No, not criminals, they are rare. Evil corporations who are looking at every opportunity to fuck you up. Using computer is no longer fun, it's no longer a tool that helps you, and it's no longer your choice. You are forced to use it, and if you don't want to be hurt every step of the way, you have to spend all the effort on fighting back. And you're fucked up anyway, because even if you manage, your family and all the people around you won't care and will let their devices, their computers and their smartphones fuck you up.
I've started using FLOSS so many years ago, for the trivial reason that I didn't want to pay for software. I stayed because I enjoyed doing it. And I wanted to make a difference, I wanted to contribute positively to the world. Even if in a little way, but I wanted to be able to say that as much harm I've done to the planet, there's at least something positive to balance it out.
But nowadays I hate FLOSS. It's been overrun by the worst people in the world. The people who aren't happy with just fucking you up. They want everyone to keep fucking everyone up. It's the kind of horror where whatever you do, it turns out you're causing harm.
I don't trust my #Gentoo #packaging work anymore. So much of the software I touch turns out to be #slop. When I file a pull request, I'm worried it will trigger #LLM reviews. When I file a bug, I'm worried it will trigger LLM responses. And today, I've learned that my old bug report to a #NoAI project resulted in a dozen slop pull requests already. Whatever you do, #AI folks smile and tell you "see, you fucked up the world even more after all".
Honestly, I don't know what to do. I hate all of this so much. But even if I managed to figure out something else to do for a living, I can't escape computers. And if I stop doing them, if I stop fighting them, I will only end up being fucked up more.
#NoLLM #AI #FreeSoftware
@thomasrenkert@hcommons.social2026-04-27 06:59:02
als diejenigen, die alleine oder zu zweit an sowas saßen. Hier hat KI vor allem gleiche Wettbewerbsbedingungen geschaffen. Aber das System ist für so ein faires, ebenes Spielfeld gar nicht geschaffen und ächzt jetzt unter seiner Überforderung - wohlgemerkt ist das schon das SEKUNDÄR-System, das eigentlich nur das Primärsystem Wissenschaft unterfüttern soll.
Zum jetzigen Zeitpunkt sollten wir einen Richtungswechsel einleiten: radikale Abwehr von aller Slop-Produktion - egal ob menschen- oder maschinenbasiert - die auf der einen Seite als Pseudoproduktion echte Forschung verhindert, und die auf der anderen Seite hypertrophe institutionalisierte Gatekeeping-Apparate finanziert. (Es gibt genügend Forschungen dazu, dass sich Innovation und wissenschaftliche Fortschritte auf diese Weise sowieso nicht garantiert herstellen lassen.)
Ohne Fokus auf #slopmaxxing könnten wir auch darüber nachdenken, wo KI uns um echte Erkenntnisgewinne in der Wissenschaft bereichern kann.
@mgorny@social.treehouse.systems2026-03-21 11:50:52
@mgorny@social.treehouse.systems2026-04-03 14:18:26
#PythonPoetry is yet another project that disrespectfully treats human bug reporters with #slop:
#NoAI #NoLLM
@mgorny@social.treehouse.systems2026-03-19 12:23:26
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