2026-10-19 16:55:54
Today in #GenAI fail. What the hell is this?
This is not the 669 area code and nothing on this map of the San Francisco region of California is accurate.
The shape of California isn’t even right.
#sfbayarea #slop
If someone slopped a fix, should I be thanking the model instead?
#slop
Okay, so how does a comment like the following sound like as a way to thank for a #slop - fix?
EDIT: it's not about *my* project. It's about a bug in other project that I've reported, so I should thank for the fix.
"""
Thank you for the fix.
Also thanks to all the FLOSS contributors whose work was stripped of attribution and used to train the model that was used to deliver the fix, as well to the low-wage data workers that curated said data.
"""
#NoAI #FreeSoftware
RE: https://mastodon.social/@nexthorizon/117382312970446408
Well that’s one way to split the difference. I see both a gulf of america and a Gulf of Mexico in the third image.
So I've finally copied my music to the phone, and then discovered that the #Fossify media player (which was supposed to be simple) has all the fancy media library features, except it doesn't have the most basic feature of letting you go through a directory tree and select a directory to play. The best you can do is either run along a flat tree of all directories (which isn't very good when the immediate directory name is "Disc 1") or through artists and albums (which doesn't work when the tags are imperfect and both discs get merged into a single album with interspersed tracks).
So I went to #FDroid. Unfortunately, it's quite filed with #slop already; everyone's got their awesome "simple" music players, which are all the same kind of useless shit, and also don't have this most basic feature. Well, finally found two that somewhat work; not that either really appeals to me.
If I were to judge demand for kinds of software based on #Python package releases last month, I'd say we have a very quickly rising demand for:
• a (redundant) package providing virtual environments (23 releases in a month)
• a package providing test environments (16 releases)
• a package providing lockfile support (15 releases)
• a package providing support for special platform directories (XDG, etc.) (12 releases)
Or maybe it's just #slop. I don't know, they're not admitting to it in their very verbose commit messages.
Tired: Garbage in, garbage out. #GIGO
Wired: Slop in, slop out. #SISO
#tiredWired #slop #saying
I feel that #Gentoo #GURU is getting much less interest since the change of rules.
Not sure if that's a bad thing, given how much of the interest we're getting are people who just made a slopware and now are aggressively pushing it to all the distributions they can find. Some just do an automated submission without bothering to follow the rules. Other claim that they have read and agree to the rules, even though the rules explicitly forbid doing that.
Then, there are all these people who asked for access but apparently never committed anything.
#slop
Zero days since I regret filing a bug since it meant that some random asshole used life-destroying, nazi-supporting #slop machine to (checks notes) perform a two-line change that was precisely suggested in the bug report and add a test case that was also literally given on the bug. Well, at least they added a wall-of-slop explanation to the changes, so they wouldn't have to copy the one sentence explanation given on the bug.
#NoAI #Python
There's #JSONSchema, that's well supported, has good docs and so on.
Then there's #YAMLSchema which is based on JSON Schema, which makes that quite damn convenient.
And then there's self-proclaimed #TOMLSchema, which is apparently 100% vibe-coded piece of shit.
#slop
In the meantime, #GitPython, the package that used to be dead (because the author is busily working on their next great thing) is now slopping out 4 "security" releases a week, as their #slop machine is busily fixing unintended variable expansion in every single URL they call. Unfortunately, they probably don't have enough tokens to fix them all at once, so instead all downstreams have to deal with the churn of endless security releases. Or the brain to figure out that maybe they could just disable variable expansion by default and solve them all at once.
It's truly a great time to be a #Python packager.
#NoAI #NoLLM
So I'm getting fed up with #spam on #Gentoo #Bugzilla.
A while ago we've introduced a timed block on new accounts posting URLs. It helped for a while. But now someone actually bothered implementing a dedicated tool, and we're getting a daily create-wait-post loop. I can't think of a really good way of getting rid of this.
So far I was thinking of:
• blocking new accounts based on the predictable e-mail pattern (they're just going to switch patterns, also may hit real users)
• limiting URLs pasted to an allowlist (this is going to suck hard)
• requiring manual request for every account via IRC (this is going to be pain for us, for users, and a lot of people just won't bother)
It really feels like whatever we do, it's going just to cause pain to us, to our legitimate users, and the spammers will just slop their way around it.
And on top of that, every comment posted is fucking #slop. Totally meaningless sentences added to random bugs, in the hope that we're too stupid to see that they've just spammed us.
I hate this timeline. Can we do Butlerian Jihad now, please?