Conversation

Notices

1. Embed this notice
   abadidea (0xabad1dea@infosec.exchange)'s status on Saturday, 30-May-2026 02:43:39 JST abadidea

   I spent some time looking into the rsync regressions. I found the general shape of the cause of one of them, and a discord buddy was able to further nail the exact chain of failure. We reported our findings in the appropriate github issue. (It was a classic: security fix introducing a new bug. New tests for the fix didn't expose it.)

   I took the opportunity to politely push back that there has been a sudden flurry of very large Claude-cosigned commits, and that seeing things like the entire test suite being rewritten from bash to python by an AI in a single commit sets off a lot of alarm bells in my head for ugly surprises. Too much, too fast.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Saturday, 30-May-2026 04:18:00 JST Rich Felker

     in reply to

     • Joe ❌👑
     • Dave Wilburn :donor:

     @not2b @DaveMWilburn @0xabad1dea And the startup rushing to product a MVP to show before they run out of funding just.. should not exist.

   • Embed this notice
     Dave Wilburn :donor: (davemwilburn@infosec.exchange)'s status on Saturday, 30-May-2026 04:18:01 JST Dave Wilburn :donor:

     in reply to

     @0xabad1dea

     This modern obsession with using AI to increase code velocity is insane. Writing new code is the last piece that we should be optimizing.

   • Embed this notice
     Joe ❌👑 (not2b@sfba.social)'s status on Saturday, 30-May-2026 04:18:01 JST Joe ❌👑

     in reply to

     • Dave Wilburn :donor:

     @DaveMWilburn @0xabad1dea Code velocity makes sense for a startup rushing to produce a minimum viable product to show before they run out of funding. For a mature tool that everyone relies on (like rsync) changes should be slow and cautious.