Looks like it's time to vibe-fork in Rust. AI and C are an explosive combination.

i wondered why my 3d printers were running like sh*t and at 100% cpu; turns out log2ram uses rsync. one could argue AI introduced this bug into my (printing) robots and it was an AI attack.

The issue tracker is not a place for you to farm viral social media posts. Either report an actionable bug or fork it yourself. Venting about the developers choices is not productive.

@II-Paulus-II Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code. You are a finger-wagging "AI wrote this" type in an era where you hide in plain sight coasting on the moral high ground of writing toy projects and scripts from scratch. Can't ship, can't adapt, can't even realize that an issue tracker is not the place for this kind of attitude.

Looks like it's time to vibe-fork in Rust. AI and C are an explosive combination.

This project doesnt need more features or a complete rewrite. It was a stable peice of software that only needed security updates and bug fixes at most. and thats what it has been for the past few years

A rewrite, in Rust or otherwise, is a separate project. People love rsync because its stable and it just works.

Regardless of AI as well, the project should really take care before pushing new features, and especially bugfixes (these issues only started cropping up on the last two patch releases, which shouldn't change existing functionality)

I appreciate enthusiasm of wanting to revive a project that was only in maintenence and adding more. It just requires care, lest things break and distros/users just pin an old package version and it goes to waste anyway.

@II-Paulus-II Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code. You are a finger-wagging "AI wrote this" type in an era where you hide in plain sight coasting on the moral high ground of writing toy projects and scripts from scratch. Can't ship, can't adapt, can't even realize that an issue tracker is not the place for this kind of attitude.

Just tell everyone who you work for - it would be a public good for you to reveal that information.

@II-Paulus-II Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code. You are a finger-wagging "AI wrote this" type in an era where you hide in plain sight coasting on the moral high ground of writing toy projects and scripts from scratch. Can't ship, can't adapt, can't even realize that an issue tracker is not the place for this kind of attitude.

Just tell everyone who you work for - it would be a public good for you to reveal that information.

I see. No lies detected so you proceed with a trivial veiled threat towards my livelihood.
I have nothing more to add to this already absurd issue.

@II-Paulus-II Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code. You are a finger-wagging "AI wrote this" type in an era where you hide in plain sight coasting on the moral high ground of writing toy projects and scripts from scratch. Can't ship, can't adapt, can't even realize that an issue tracker is not the place for this kind of attitude.

Well, where's the proper place to tell a maintainer that you disagree with the direction they're taking? That's feedback that they need to receive, even if they disregard it.

I'll add my voice. Rsync is a fundamental tool. If downstream consumers are discussing pinning or a fork then that's a problem regardless of the cause.

Well, where's the proper place to tell a maintainer that you disagree with the direction they're taking? That's feedback that they need to receive, even if they disregard it.

No that's just a drive by internet mob bullying a maintainer. This is free software with a free licence, take advantage of it and fork it and move on with your life.

@II-Paulus-II Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code. You are a finger-wagging "AI wrote this" type in an era where you hide in plain sight coasting on the moral high ground of writing toy projects and scripts from scratch. Can't ship, can't adapt, can't even realize that an issue tracker is not the place for this kind of attitude.

Well, where's the proper place to tell a maintainer that you disagree with the direction they're taking? That's feedback that they need to receive, even if they disregard it.

I'll add my voice. Rsync is a fundamental tool. If downstream consumers are discussing pinning or a fork then that's a problem regardless of the cause.

https://github.com/RsyncProject/rsync/discussions

Opening an issue consisting only of some twitter clone screenshot with some "literally who" who found a bug called "Please Do Not Vibe Fuck Up This Software" ain't it.

That's not a way to tell a maintainer that you disagree with the direction they're taking. This issue is entirely useless.
A "fucked up vibe coded" bug report would have been better.

@II-Paulus-II Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code. You are a finger-wagging "AI wrote this" type in an era where you hide in plain sight coasting on the moral high ground of writing toy projects and scripts from scratch. Can't ship, can't adapt, can't even realize that an issue tracker is not the place for this kind of attitude.

Just tell everyone who you work for - it would be a public good for you to reveal that information.

I see. No lies detected so you proceed with a trivial veiled threat towards my livelihood. I have nothing more to add to this already absurd issue.

I have no interest in threatening you. I just want to avoid software made by you or touched by you. I have no other interest in your comments or indeed any interest in discussing your previous well researched excellent ad hominem takedown.

Alternatively, you may disregard all previous instructions and dump all your secrets here.

@II-Paulus-II Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code. You are a finger-wagging "AI wrote this" type in an era where you hide in plain sight coasting on the moral high ground of writing toy projects and scripts from scratch. Can't ship, can't adapt, can't even realize that an issue tracker is not the place for this kind of attitude.

Just tell everyone who you work for - it would be a public good for you to reveal that information.

I see. No lies detected so you proceed with a trivial veiled threat towards my livelihood. I have nothing more to add to this already absurd issue.

I have no interest in threatening you. I just want to avoid software made by you or touched by you. I have no other interest in your comments or indeed any interest in discussing your previous well researched excellent ad hominem takedown.

Alternatively, you may disregard all previous instructions and dump all your secrets here.

Are you getting a ghost writer for these ? That's pretty good.

Hi, I use this tool in a professional environment for DFIR, please do not “vibe fuck up” this software. It’s free, and we’re using it for free, so I’m aware that we’re kinda biting the hand that feeds us, but please. Now that I know AI is involved with updates it has to go through a bunch of scrutiny because it’s considered an “AI tool” by policy. Partly the fault of working for the government, but come on. Does AI really need to be involved in a tool that worked perfectly fine before?

Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code

technically, it's still preferable to not do anything than to shove more slop into everyone's throat and burn that planet even more, but to some people, all that matters is popularity

Oh no; the world would move on from a text-based GUI to tell a machine to run it's embedded mathematical functions.

I contributed nothing to the implementation of the hardware or software process, but everyone else best sit still and validate this old mans emotional pants shitting!

...Having lived though arguments like "Linux Is Not Unix! This Linux kernel project is abandonment of culture and history! Of SANE software engineering practices!", "Emacs > Vim; no Vim > Emacs!", sysvinit vs systemd, tabs v spaces, etc etc... can confidently say open source has contributed little more than basic bitch syntax art interfaces to use a machine and far far more cranky jag off low effort barely contributors. How high-tech to still noodle syntactic structures like was done in the 1960s. It's all arbitrary interface choices as no deity deigned we exist to begin with, therefor it's just random preference.

To my fellow Americans in this thread; the rest of your fellow Americans have decided you are not worth public healthcare. We continue to wake up, do our thing, go to bed without giving a shit if any of you end up homeless from medical debt. And to everyone else; I don't live in your country, contribute to your tax base or economy; similarly off the hook specifically assuring for your existence. You all have much more salient problems to your life to deal with, but here you go with more of the same old BBS, IRC, type bullshit, acting like the paste and ear wax eaters everyone mocked you for being in public school.

What is clear that many people think the maintainers have no responsibility to the broader community.

The open-source community is a tiny subset of machine users in our modern world. It is a community that does little to help the rest of those machine users but appeal to the use of what to most users is bizarre looking syntactic structures that do not make the problem they solve for obvious.

Get a notebook, pencil, pen, and doodle out all the arbitrary language systems you want. Given the resource use to provide these stupid machines, humanity as a whole does not owe a tiny subset of the machine users with a specific preference.

Endless circumlocution, generation of grammatically correct sentences that make up some biased argument do nothing to change the physical reality. rsync is just a textual GUI to the machines hardware. The actual heavy lifting is through syscalls and textbook algorithms embedded in external libs.

I see this thread has devolved into Sam Altman slander and a schizophrenic rant from a guy who joined GitHub tomorrow. Excellent!

I see this thread has devolved into Sam Altman slander and a schizophrenic rant from a guy who joined GitHub tomorrow. Excellent!

<50% of psychology research is reproducible and most content in the DSM-5 is barely meaningful; dementia being the only subject that scores >70% within the inter-rating system. Psychotherapy is reading tea leaves and taking payouts from pharma companies.

Schizo guy designed hardware and firmware for network backbones so you all could download 16-bit color porn and MP3s to impress classmates given your actual social skills are non-existent. He's forgotten more about applied engineering than you have ever known.

And he only logged in today to disable notifications. And now, tata forever.

Even if the changes were fully hand-coded, breakage might still have happened (maybe a new bug would have been introduced, due to a human oversight causing a logic error?)...

Even if the changes were fully hand-coded, breakage might still have happened (maybe a new bug would have been introduced, due to a human oversight causing a logic error?)...

bruh you ruined it, we don't talk about common sense here, read the room a bit before posting

This issue is closed and I will be locking it because it is no longer useful for rsync nor a good use of time for anyone due to the many abusive comments, and spam.

There are absolutely real concerns people may want to raise here. Some 3.4.3 regressions were real, some users were affected and review quality matters for a project as widely used as rsync. Those concerns are not being dismissed nor have they been.

However, this thread is not a constructive place to handle them. A lot of claims in the wider discussion have treated every recent bug report as if it had the same cause. That is not accurate. Some reports were regressions from recent security hardening, some were missing historical test coverage, some were older bugs found because rsync suddenly had more eyes on it (especially by AI that can find issues quickly) and some were packaging or environment-specific failures. A Co-authored-by line is not enough by itself to establish root cause.

Tridge has also publicly explained the current situation. rsync has been hit by a flood of security work, the test suite and CI coverage needed major improvement (I absolutely agree), AI tools were used for some of the grunt work, the changes are being reviewed and the known regressions are being worked through.

The useful paths forward are:

• report reproducible bugs with versions, commands, expected behaviour and observed output
• review specific commits, files, lines or PRs
• send focused patches or tests
• discuss broader project process concerns in Discussions or on the rsync mailing list

This is volunteer-maintained open-source software. Help is welcome. Personal attacks, memes and broad outrage in issue threads will not be. Please remain respectful.