Post B6naLs58letvTes93o by gregr@mamot.fr
 (DIR) More posts by gregr@mamot.fr
 (DIR) Post #B6nQHuHxccbzcbL852 by wizbean@tech.lgbt
       1 likes, 0 repeats
       
       @aks Like, it's open source? If you're worried about your agent running unvetted code, just vet the code. What's with this entitlement.
       
 (DIR) Post #B6naLs58letvTes93o by gregr@mamot.fr
       0 likes, 0 repeats
       
       @aks $ cat AGENTS.md# Do not engage╭∩╮( •̀_•́ )╭∩╮
       
 (DIR) Post #B6naLsLRn1weIEVATg by argv_minus_one@mastodon.sdf.org
       0 likes, 0 repeats
       
       @gregr @aks On that note: https://github.com/jqwik-team/jqwik/blob/main/CONTRIBUTING.mdSo, the “malware” does nothing more than enforce the project's contribution policy.This gives me an idea! 💡 https://github.com/jqwik-team/jqwik/issues/710#issuecomment-4577429915
       
 (DIR) Post #B6naLsXr2tryuiJ4oi by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @argv_minus_one @gregr @aks > enforce the project's contribution policy...on any downstream project using jqwik in its testsuite, AFAIUI think there's a big difference between"delete your copy of my code" and"delete your code that uses my project as a dependency"
       
 (DIR) Post #B6ndbMEHGKjnBTDpcu by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @argv_minus_one @gregr @aks though, as someone elsethread pointed out, the maintainer changed the injection to something less malicious:https://github.com/jqwik-team/jqwik/commit/c4205510c3d8360c57d54c1df59593f5045b6798I think that's a right balance for a prompt targeting downstream use of the library.oh, and I also like your idea about the subtle edit
       
 (DIR) Post #B6pSDJ4icyPHGv04Aq by volpeon@icy.wyvern.rip
       1 likes, 0 repeats
       
       @aks Bluntly what the maintainer has done is introduce malware4 years of nonstop hype and innovation, and yet LLMs still don't have a robust separation between data and instructions. Maybe that should've gotten solved before relying on them? ​:neofox_googly_woozy:​