Conversation

Notices

1. Embed this notice
   daniel:// stenberg:// (bagder@mastodon.social)'s status on Saturday, 10-May-2025 18:32:26 JST daniel:// stenberg://

   AI_slop_counter++;

   • Kevin Beaumont, Cadu :neurodiverse_w: and Rich Felker repeated this.
   • Embed this notice
     Nils Ballmann (nils_ballmann@infosec.exchange)'s status on Saturday, 10-May-2025 18:32:25 JST Nils Ballmann

     in reply to

     @bagder

   • Embed this notice
     daniel:// stenberg:// (bagder@mastodon.social)'s status on Sunday, 11-May-2025 06:22:30 JST daniel:// stenberg://

     in reply to

     So the user actually found a memory leak in #curl (using a fuzzer) and reported it correctly. All good.

     Then, in a follow up comment the user makes the ugly choice of trying to "help" us with this bug by asking an AI for help and proposing that as a solution.

     And again it broke horribly and the AI made up a broken patch that did not even fix the problem.

     Now that reporter is banned.

     Haelwenn /элвэн/ :triskell: likes this.
     Rich Felker repeated this.
   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Monday, 12-May-2025 01:25:23 JST Rich Felker

     in reply to

     @bagder Big props for doing this even when the reporter's initial work was somewhat helpful.

   • Embed this notice
     Ondřej Surý (ondrej@mastodon.rfc1925.org)'s status on Monday, 12-May-2025 01:28:56 JST Ondřej Surý

     in reply to

     @bagder I have a similar issue reported against BIND 9: https://gitlab.isc.org/isc-projects/bind9/-/issues/5280

     It is a real issue, but the reporter exaggerated it and it feels like generated by AI, but I can’t really put a finger on it, so I can be mistaken. Somehow I don’t think humans use phrases like this one: “Here's the enhanced technical description”