Post #2781381
2026-04-16 18:32 UTC
@josephholsten@mstdn.social having a hard time seeing how this is a slippery slope? the policy is pretty clear that if you're contributing code, it can't be generated; end of story
a PoC of a vulnerability is not a code contribution and requires neither ongoing maintenance, merging, nor copyright assignment
maybe I'm missing something
Replies (1)
-
@technomancy@hey.hagelb.org 2026-04-16 18:57
@josephholsten@mstdn.social oh ok, I missed that you were replying to the old post rather than the most recent one, so this makes a little more sense now but overall I think the sensible response to avoid the slippery slope is the same