2026-10-20 12:21 UTC
@ell1e@hachyderm.io @drew@social.freebitcoin.gay 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.
Replies (1)
-
@ell1e@hachyderm.io 2026-10-20 12:23
@netbsd@mastodon.sdf.org @drew@social.freebitcoin.gay 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.