home.social

#slopware — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #slopware, aggregated by home.social.

  1. After staring at the highway for 855 miles, I had a thought.

    slott56.github.io/2026-05-22_s

    Using LLM's to write code suggests the resulting code is expected to be worthless.

  2. Glances at #instructables, tries to read a couple of projects, rolls eyes and sighs that every single project description now seems to be #slopware writing, gives up and closes the tabs.
    FFS what's happening to our hobby. 🙄😡
    If you're interested/excited about your project and want to share it, why the fuck would you AI generate your write up.

  3. Glances at #instructables, tries to read a couple of projects, rolls eyes and sighs that every single project description now seems to be #slopware writing, gives up and closes the tabs.
    FFS what's happening to our hobby. 🙄😡
    If you're interested/excited about your project and want to share it, why the fuck would you AI generate your write up.

  4. Glances at #instructables, tries to read a couple of projects, rolls eyes and sighs that every single project description now seems to be #slopware writing, gives up and closes the tabs.
    FFS what's happening to our hobby. 🙄😡
    If you're interested/excited about your project and want to share it, why the fuck would you AI generate your write up.

  5. Glances at #instructables, tries to read a couple of projects, rolls eyes and sighs that every single project description now seems to be #slopware writing, gives up and closes the tabs.
    FFS what's happening to our hobby. 🙄😡
    If you're interested/excited about your project and want to share it, why the fuck would you AI generate your write up.

  6. “There’s also the underlying unreliability of hallucination-prone Large Language Models. While a premium request chasing its tail and spitting out half-broken code might be frustrating, that same fuckup is a lot less forgivable when you’re paying the costs yourself.”

    AI's Economics Don't Make Sense
    wheresyoured.at/ais-economics-

  7. #flickboard is not developed using LLMs/"#ai". It doesn't have any "#ai" "features". It has been against the contribution guidelines for as long as there have been any.

    But I'm also not really sure I can call it slop-free, because it's still running on Android, and it still depends on a whole bunch of Google libraries. And I'm under no illusion that /those/ aren't tainted at this point.

    It'd be a weird to draw a line calling slop libraries okay. They are still run with the same privileges, and are still harmful in the same way. But it's also hard to avoid while running on the platform at all. And it's not like I can just reinvent it all on my own.

    I don't know. I wish there was a serious alternative out there. :/

    #noai #slopware

  8. Me acaban de dar cuenta que existe codeberg.org/small-hack/open-s.

    Un repositorio de #Codeberg que enlista servicios y cosas en general hechas con inteligencia artificial o permiten su uso.

    Y me di cuenta que Hugo, el constructor de sitios que uso para administrar mi sitio web también está enlistado... Es lamentable...

    También puedes colaborar al proyecto proveyendo evidencias para hacer la lista aún más grande.

    #noai #slopware #noia #ai #ia #OpenSource #inteligenciaartificial

  9. The interesting thing about #corporate #FLOSS is that you can't tell if the #slopware migration is due to corporate pressure (pardon, “#KPI”) or due just to maintainer(s) getting the #genAI #brainworm, like many others in and out of FLOSS.

  10. Hello #Linux users. Have you uninstalled #Windoze yet? I heard that it's full of #AI and #slopware

  11. Checked all little utilities, which I'm using in my daily computing, are they still good old programs or slopware?

    I prefer to use little programs, which were created to please the needs of it's creator. And/or some folks which has the same needs. The process of such little program creation usually, if author in sane state of mind, doesn't mimick process of commercial software creation, where developers need to rush to "deliver features" to please management and investors. For now this leds to forcing developers to use LLMs on the workplace — all to "deliver features" faster. So one developer for the same price (salary) able to make more features. Profit!

    So, when I see how opensource programmer uses LLM to create some opensource program — it is a red flag for me and I'll try to avoid using such program. Because it means to me that programmer doesn't like the process of creation. Like an artist who don't like to draw or photographer, who don't like to make photos. Also, (s)he possibly has a "corporate mindset" (deliver value and features faster, no fun allowed). So, looks like his/her creature is not a pet, but a cattle. When I prefer to use "pet"-programs — usually they are nicer, simpler and doesn't bring me a lot of problems.

    Results are pretty good — only three programs are slopware now. These three programs, installed from repositories of my OS, have versions, when these programs were coded by humans.

    Here they are:

    1) rsync — version 3.4.1 is good, but the next versions will be slopware, since programming happens with Claude LLM.

    2) ImageMagick7 — installed good version 7.1.2-15. But since 7.1.2-16 it become a slopware. LLM the same — Claude, was used in one commit.

    3) python3 — installed version 3.11.15. Since 3.13.6, according to commits and release dates, it become a slopware too — there are some commits, where the same Claude LLM was used.

    #slopware #rsync #ImageMagick #Python3

  12. @m3tti Maybe itbis a bit silly to answer to this question with a meme.
    Anyway, I think that there are at least two kinds of developers: who depicted on the left side of attached meme (and who happy to turn open software into the open #slopware and perform other … uhm … strange things). And who on the right side of this meme.

    Also, I read in someones blog about another way to classify developers: there are one who are "Builders" — they just want to see the working thing, no matter how ugly it is inside; they didn't like programming and see it as a sad way to make the desired things. And there are "Artists" — people who have fun from the process (of programming); sometimes they build something as a result, sometimes not, but in both cases it is a well-spent time.

    So, I think, the folks like in the left side of meme and the "Builders" will be happy to replace joys of programming with LLMs and other big tech dependencies, bc they don't see these joys, first.

  13. Open Slopware raises awareness of AI/LLM usage in popular open-source software.
    codeberg.org/small-hack/open-s

    #slopware #foss #ai

  14. We have to deal with vibe coding because we didn't do enough work in computer literacy and open computing.

    AI is the tax we're paying for putting computers everywhere and not teaching enough people how to use them, or demystifying the process of what it takes to get a computer to do stuff.

    It's not magic, it's math. And we're reminded of that every day when a Open Claw generates like 1000 new CVEs a day, or a hot new business gets hacked in the most laughable way possible.

    Closed source software has it's own role in this, too.

    #aislop #slopware #vibecoding

  15. CW: found more slopware in my toolbox

    helix editor has become tainted too

    there's a discussion about this at https://github.com/helix-editor/helix/discussions/15408 where a maintainer suggests adopting Ghostty's policy (which welcomes AI slop and just holds it to a code standard)

    guess I'll just keep the version pinned to latest clean…
    (can't find the claude commit in main, maybe it's in one of the dev branches)


    #helix #slopware
  16. @cmccullough @quixoticgeek @keepassxc

    I think we're standing in an ever-shrinking circle, brosef. 😕

    It doesn't change the ethics of the situation, it just makes it much harder to navigate.

    I've given up on avoiding #slopware. I certainly won't choose new tools that use it, if it can be avoided, but the bloody ship has sailed.

    This is the perfect storm for the #FOSS world.

    It just hasn't realized it.

  17. The Jellyfin project started working on a new desktop client. They've deprecated the current Qt-based one and are working on a new CEF-based client.

    Opened the new repository and… well fuck, looks like Jellyfin is going down the AI slop route now:

    #jellyfin #ai #aislop #slopware

  18. The Jellyfin project started working on a new desktop client. They've deprecated the current Qt-based one and are working on a new CEF-based client.

    Opened the new repository and… well fuck, looks like Jellyfin is going down the AI slop route now:

    #jellyfin #ai #aislop #slopware

  19. Received this from a a friend.

    Small-hack/open-slopware

    Free/Open Source Software tainted by LLM developers/developed by genAI boosters, along with alternatives.

    ***

    Found it interesting to know what software I may be affected

    But as my friend says "there's also just lots of expectations from foss developers who do this in their free time & its a way for them to save some time"

    codeberg.org/small-hack/open-s

    #microslop #slopware #genAI #LLM #OpenSourceSoftware #softwaredevelopment #alternative

  20. @gwynnion My phone swipe typing algo detection is now plain shit since an update about a year or two. How weird, just when they said "AI was used to improve it".

    What the fuck is wrong with these people...? #slopware

    Edit: the fact that I had to edit this toot is an ironical illustration of that.

  21. Hi @evgandr
    Same question about the #slopware part

    Looking at the commits and issues reported I don't see any strong evidence of slopware.

    But a couple of security issues where solved which is probably a good reason to update.

  22. Whoops, #ImageMagick was updated in the #FreeBSD repos :drgn_flat_sob:

    Sadly, it is a #slopware version — time to make "pkg lock".

  23. small-hack/open-slopware: Free/Open Source Software tainted by LLM developers/developed by genAI boosters, along with alternatives. Fork of the repo by @gen-ai-transparency after its deletion. - Codeberg.org
    codeberg.org/small-hack/open-s

    #llm #claude #alternative #slopware

  24. So now #Mastodon is #AIslop now...

    github.com/mastodon/mastodon/i

    I'll not use Mastodon as much as I currently use it now, but at least is way better than Big Tech stuff, so it's not a total loss.

    #slopware

  25. Open Slopware

    “Free/Open Source Software tainted by LLM developers/developed by genAI boosters, along with alternatives.”

    codeberg.org/small-hack/open-s

    #AI #NoAI #FuckAI #SlopWare

  26. 🚨 PSA: #Slopware is NOT the next big trend! 🚨 Apparently, being told your code is trash is just a "gentle nudge" towards improvement 🤔. Who knew that #AI #misuse could make your code even more of a mess? But hey, #learning #in #public is fine—as long as you're okay with everyone seeing your digital 'oopsies.' 😂
    stopslopware.net/ #Coding #Mistakes #HackerNews #ngated

  27. 🚨 PSA: #Slopware is NOT the next big trend! 🚨 Apparently, being told your code is trash is just a "gentle nudge" towards improvement 🤔. Who knew that #AI #misuse could make your code even more of a mess? But hey, #learning #in #public is fine—as long as you're okay with everyone seeing your digital 'oopsies.' 😂
    stopslopware.net/ #Coding #Mistakes #HackerNews #ngated

  28. 🚨 PSA: #Slopware is NOT the next big trend! 🚨 Apparently, being told your code is trash is just a "gentle nudge" towards improvement 🤔. Who knew that #AI #misuse could make your code even more of a mess? But hey, #learning #in #public is fine—as long as you're okay with everyone seeing your digital 'oopsies.' 😂
    stopslopware.net/ #Coding #Mistakes #HackerNews #ngated

  29. 🚨 PSA: #Slopware is NOT the next big trend! 🚨 Apparently, being told your code is trash is just a "gentle nudge" towards improvement 🤔. Who knew that #AI #misuse could make your code even more of a mess? But hey, #learning #in #public is fine—as long as you're okay with everyone seeing your digital 'oopsies.' 😂
    stopslopware.net/ #Coding #Mistakes #HackerNews #ngated

  30. FWIW, I'm planning on continuing to maintain my fork of codeberg.org/gen-ai-transparency/open-slopware (now defunct), and will be accepting PRs. Can't let a good idea die because of loud-mouth slop peddlers.

    For now it's going to live here: codeberg.org/hausgeist/open-slopware

    EDIT: Nevermind, let's all join forces here: codeberg.org/small-hack/open-s

    #openSlopware #slopware #noAI

  31. Was mich an der modernen #SoftwareEntwicklung anwiedert:

    Wenns auch nur die geringste Chance gibt, einen scheuslichen Murks mit einem noch viel scheuslicheren Murks zu workarounden, dann wird alles da rein investiert und die saubere Lösung interessiert kein Schwein... 😕

    Bleibt mir also nur zu hoffen, dass das nur in meinem Umfeld so ist.

    #softwarequality #slowsoftware #rant #dev #slopware

  32. The interesting thing about #corporate #FLOSS is that you can't tell if the #slopware migration is due to corporate pressure (pardon, “#KPI”) or due just to maintainer(s) getting the #genAI #brainworm, like many others in and out of FLOSS.

  33. The interesting thing about #corporate #FLOSS is that you can't tell if the #slopware migration is due to corporate pressure (pardon, “#KPI”) or due just to maintainer(s) getting the #genAI #brainworm, like many others in and out of FLOSS.

  34. The interesting thing about #corporate #FLOSS is that you can't tell if the #slopware migration is due to corporate pressure (pardon, “#KPI”) or due just to maintainer(s) getting the #genAI #brainworm, like many others in and out of FLOSS.

  35. The interesting thing about #corporate #FLOSS is that you can't tell if the #slopware migration is due to corporate pressure (pardon, “#KPI”) or due just to maintainer(s) getting the #genAI #brainworm, like many others in and out of FLOSS.

  36. Meme-ing what you say is saying what you #meme ?
    #ZuckerMuskian media Era
    #SlopWare - dysphemism for today’s “generative” (read: plagiarative) #ai -
    #enshittification #incarceratedworkers
    #prisonlabour

  37. Meme-ing what you say is saying what you #meme ?
    #ZuckerMuskian media Era
    #SlopWare - dysphemism for today’s “generative” (read: plagiarative) #ai -
    #enshittification #incarceratedworkers
    #prisonlabour

  38. Meme-ing what you say is saying what you #meme ?
    #ZuckerMuskian media Era
    #SlopWare - dysphemism for today’s “generative” (read: plagiarative) #ai -
    #enshittification #incarceratedworkers
    #prisonlabour