69
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jun 2026
69 points (87.9% liked)
Opensource
6626 readers
222 users here now
A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!
⠀
founded 2 years ago
MODERATORS
Taking a project that works fine and making it actively worse by introducing AI made bugs is imho a valid reason to hard fork. The maintainer might not owe you anything, but it shows very poor judgement to slopify a good project like rsync this way.
Enjoy maintaining your hard fork!
how did he slopify anything? he got a huge invtease in contributions and used a tool to help weed out slop.
They could have just refused merging slop. Rsync didn't need these "contributions".
What about the 6 critical security bugs he fixed in that release. Didn't rsync need those "contributions"?
The "critical" bugs that I have recently seen being found by AI were all extremely unlikely to be exploitable under realistic assumptions 🤷
Which of the CVEs in question are you referring to?
The ones in Nginx and the Linux kernel.
I mean the ones in the latest release of rsync, tf does nginx have to do with anything ?
I have not looked at the CVEs in Rsync specifically, but given the deludge of "critical" security issue found by AI lately that have been mostly nothing burgers, I am near certain the same applies to those included in that Rsync patchset.
It must be nice to have technical opinions that don't need to be grounded in facts. Why would you check your assumptions when you can just vibe.
Nice that you are so self aware 😅