
686: Stop Desktop Slop
By Jupiter Broadcasting
Aired Sep 28, 2026 · 1h 32m · Last boosted 16d ago
Chapters
Show Notes
KDE’s fight over AI generated code explodes at exactly the moment Plasma is making some of its biggest changes in years. Sponsored By: Jupiter Party Annual Membership: Put your support on automatic with our annual plan, and get one month of membership for free!Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. Support LINUX Unplugged Links: Web Boost — Send us a boost via sats or USD💥 Gets Sats Quick and Easy with Strike📻 LINUX Unplugged on Fountain.FMJupiter Garage SWAGGoing...
Nostr Boost Stats
- sats
- 6.2k
- boosts
- 3
- boosters
- 2
- sats
- 0
- boosts
- 0
- boosters
- 0
- sats
- 500
- boost
- 1
- booster
- 1
- sats
- 6.2k
- boosts
- 3
- boosters
- 2
Nostr Community
Everyone who has boosted 686: Stop Desktop Slop on Nostr, ranked by sats sent, all time.
- dahjah 5.7k sats
- user13811801 500 sats
Episode Boosts
Every boost sent to this episode, as published to Nostr, newest first.
-
-
Also, we've been putting in a couple lines in our agents.md file to have the agent do something trivially obvious to a human, and that's been surprisingly good at filtering out the AI-made-this-without-a-human-looking-at-it-whatsoever, and automatically sending it back to the contributor to fix and resubmit. It's not bulletproof by any means, but it is good enough to catch most people who don't really care about the quality of their submissions. If they don't care enough to perform a simple task like that, I don't really want their contributions regardless of if they are AI generated/assisted or not. We've seen a lot of success in treating agents.md and Claude.md similar to contributing.md- give the agent lots of self-verification steps and it catches itself before it even commits a lot of the time. Sure, it technically uses more tokens, but I think that's a fair trade to reduce load on the maintainers.
-
I'm so happy a lot of projects are finally getting out of the "AI is good"/"AI is bad" rut. I've ended up somewhere similar for my engineers at work- at the end of the day, they are responsible for their code. Period. People have been making slop for decades, anyway, so if they submit a PR with GPL code in it, or security flaws, or anything else, it's not mergeable and needs to be sent back regardless of if AI was involved. The biggest benefit we've seen from this is finally upping our CI game. Before it was ok to not have it in tip top shape because contributions were low, but now that they are high, we're forced to do what we should have been doing in the first place in terms of automated checks and code quality rules.
























