Post by netbsd - Paul Wilde's littleFedi

Drew DeVault

@drew @social.freebitcoin.gay

Oct 20, 2026, 09:02 UTC Public en

Need a logo for #AlpineBSD, any artsy types want to take a crack at it?

Replying to @drew@social.freebitcoin.gay

@ell1e @hachyderm.io

Oct 20, 2026, 11:58 UTC Public en

@drew i wonder, has anybody ever asked #NetBSD to reconsider the "core can approve slop" clause, or to publish some info on whether core has approved #slop so far?

sounds quite cool though! I'm still hoping somebody might fork an older #Linux #kernel - might be hard to keep that going but it would send a sign.

#LLM #NoSlop #ensloppification #AI #NoAI #FreeSoftware #FOSS #FLOSS #OpenSource

Show moreShow less

Replying to @ell1e@hachyderm.io

NetBSD Foundation 🚩

@netbsd @mastodon.sdf.org

Oct 20, 2026, 12:21 UTC Public en

@ell1e @drew They have not done so since the policy was clarified in 2024.

Anyway, it needs clarifying again, since there's some third-party code we're not necessarily ready to remove, upstream has accepted AI contributions, it needs updates, and the decision between shipping slop and shipping vulnerable code to users is a huge catch-22.

Replying to @netbsd@mastodon.sdf.org

ell1e coding things

@ell1e @hachyderm.io

Oct 20, 2026, 12:23 UTC Public en

@netbsd @drew well, you could always write a manual fix for an AI reported vulnerability. so I don't think shipping slop is required for that either.

Replying to @ell1e@hachyderm.io

NetBSD Foundation 🚩

@netbsd @mastodon.sdf.org

Oct 20, 2026, 12:29 UTC Public en

@ell1e @drew we unfortunately don't have the resources to fork and take over maintenance of large software projects like Postfix and BIND, but thankfully they are entirely optional.

their choices also advance the argument for having a smaller base system by default.

Replying to @netbsd@mastodon.sdf.org