I think the saddest part of the LLM infection of open-source software development is the loss of trust in each other. Beforehand, if somebody submitted some bad code, it could be assumed it was either a mistake or they weren't well-versed enough with the codebase. Nowadays, any code submitted by an unknown party brings immediate scrutiny and a "guilty until proven innocent" mentality. Its a valid defense mechanism, but I will never forgive the corpos for this.
Conversation
Notices
-
Embed this notice
justsoup :asexual_flag: (justsoup@mstdn.social)'s status on Saturday, 30-May-2026 10:31:26 JST
justsoup :asexual_flag:
- Rich Felker repeated this.
-
Embed this notice
Oyu F'ka (oyu_fka@mastodon.social)'s status on Saturday, 30-May-2026 10:31:48 JST
Oyu F'ka
@justsoup I suspect it's their way of fucking up open source software. I mean, free software? How does that create billionaires?
In all seriousness, though, how can you trust software to be clean of slop? I'm extremely wary of open source as a result. It's like unknown people are pissing in the only fresh water well around.
Rich Felker repeated this. -
Embed this notice
Έλλεν Εμίλια Ά. Arson ζ. (fogti@chaos.social)'s status on Saturday, 30-May-2026 10:31:48 JST
Έλλεν Εμίλια Ά. Arson ζ.
@Oyu_Fka @justsoup It goes much further than that. Open source is at least inspectable, and most have a minimum of awareness that they're at least disclosing LLM usage.
Now, even lead maintainers occasionally fall for the LLM-slop-gambling machine.
But I would trust proprietary software even then way less, because checking that for slop is close to impossible, except by guessing upon encountered out-of-the-usual regressions.
Rich Felker repeated this. -
Embed this notice
Έλλεν Εμίλια Ά. Arson ζ. (fogti@chaos.social)'s status on Saturday, 30-May-2026 10:32:32 JST
Έλλεν Εμίλια Ά. Arson ζ.
@Oyu_Fka @justsoup In particular, in the context of Open Source, individual people have a lot of trust to lose by trying to hide LLM usage. Additionally, the fear of copyright/license issues keeps many in check.
For proprietary software, the fact that copyright might be unenforcable is just not a concern unless/until the code gets leaked.
-
Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Saturday, 30-May-2026 10:34:15 JST
Rich Felker
@fishidwardrobe @justsoup Some of us never accepted that notion to begin with. I've considered it malicious for 20+ years. I patch or otherwise mitigate something when it has a vulnerability that actually matters, and otherwise, only update something when it has serious new functionality I want. Otherwise it's whatever version it was when I found it.
-
Embed this notice
Fish Id Wardrobe ⁂ (fishidwardrobe@social.tchncs.de)'s status on Saturday, 30-May-2026 10:34:16 JST
Fish Id Wardrobe ⁂
@justsoup i'm seriously starting to question the notion that you should update software as soon as a new version is available.