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

I'm genuinely scared of what is going to happen once the AI bubble properly pops and we are left with mountains of slop that are starting to get more and more difficult to discern from human written and audited code.

Just re-write it all in Rust

I'm fairly ready to disable rsync on my archlinux mirror given the nature of AI introducing massive security issues constantly. please keep the AI out.

In case anyone else wants to install rsync at 3.4.1 with Homebrew, the historical formula at https://raw.githubusercontent.com/Homebrew/homebrew-core/94249dc6edd437beef79685427631893d2470dcc/Formula/r/rsync.rb still works, but:

1. The mirror URLs from mirrorservice.org and mirrors.kernel.org can't be used because those URLs are dead
2. The original source URL is dead.
3. The formula must be called rsync in order for the bottles to work.

So the following seem to be the options for placing this in another tap:

• Keep the formula name as rsync and install from bottles.
• Remove all mirror … lines, change the main URL to https://github.com/RsyncProject/rsync/releases/download/v3.4.1/rsync-3.4.1.tar.gz , and install from source.

I've used the latter for my personal tap at: lgarron/dotfiles@eb09b8f

Honestly, I don't understand why we even need to use AI/LLMs to build rsync. Rsync worked fine, it did it's job well, and it's not like theres going to be any new features to rsync soon (unless there's some crazy rewrite planned soon... please don't).

As rsync is an important piece of software for my workflow, I'll most likely migrate to OpenBSD's openrsync. It's already the default rsync implementation installed at /usr/bin/rsync on MacOS anyways.

we need rs-ync, rewritten in Rust lol

@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.

The amount of self-important smugness and vitriol bottled all into a single message to defend subpar AI-generated code in an attempt to make yourself feel better is hilarious. Any more offloading problem-solving to corporations that explicitly want to commodify it and I'm afraid we might not get a response from you.

So what if he hasn't "shipped features", had people "depend on his code"? Would you go as far as to say emphasizing learning how to program from first principles is unimportant? You are loyal to statistics and quarterly results. Open source is spiritually anathema to these ideals. Do you think rsync started because they wanted to "shiiiip bro haha we need to make money and get cracked jobs"? The neurotic, materialistic, pencil-pushing archetype you conform to that has manifested in this field over the past decade is a blight.

trust have no place in systems. we kept using things as long as they kept working.

how come entire planet uses rsync for backups, file copies and migration on bsd (+mac), linux (+android) & windows (== basically all oses), including many companies which earn money from it, yet rsync is basically a one man free job?

that's much better question than potential vibings

Advice of switching to openrsync is mental. Nothing important added, and instead of GPLv3 you get a weaker BSD licence. Pinning 3.4.1 for now, half of LTS distros are on 3.2 anyway.

OP's language seems as if it belongs to someone who trains their children that gender and sex are different and sincerely hopes his son will play with dolls

@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.

What lie did you detect when you attacked OP for not contributing code? Are coders' opinions the only ones that matter? Especially now that everyone with a $10 subscription is a "master coder"? How about listening to the users who, without ever needing to write a line themselves, know what they need from a software better than any coder in the world?

The software needs to work and be stable in every sense of the word. When the master coder breaks it for no good reason, just because AI made it so easy to throw stuff at the wall, that warrants a user to put a spotlight on it. I don't care that you use AI to do your job or to do the job better. But when you use AI to do a worse job then you really need to rethink your strategy.

This false dichotomy about an opinion's value being tied to the lines of code you worked and the playing the victim when the person you shamelessly attacked threw your crap right back at yo need to stop. They made a good point and it's generally applicable, not just to this software. Nobody came to complain that AI made the software so much better. AI might be the means but the complain is about the end. Do not fuck up the software. Doubly true when it's a very good one, has been for years, it's used by so many, and didn't need AI because it doesn't need any major, high volume intervention. It just means so many will see and suffer because of the screw up. The excuse that we're just users and didn't contribute code or even money will never fly. This is the perfect way to lose the users.

Unless you're building the software for the sake of building it, spare a moment to understand what your users want and need. The users will tell you, you just have to listen. This time they're literally telling you to do less, not more (less AI, less random features for the sake of adding novelty, etc.).

@stsquad @ppowo you don't have the contributor badge that would make your tone policing in the issue tracker valid — cut the crap, and let actual repo contributors decide if the #929 is valid or not

oh, and @ppowo, unless you're going to list your public contributions, telling some "[they] know nothing" is as empty an argument as your github profile — no one's taking your shit serious kid

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.

see? much better than the previous "STFU N00B!", but…

This issue is entirely useless.

no it is not. it is useful to me, and i'd wager it is also useful to others.

want to see a really good and informative comment? take a look at @broman's comment

where's the proper place to tell a maintainer that you disagree with the direction they're taking?

@mackensen here is fine. the issue description should be better than that, as @stsquad argued, but this is better than nothing — as a user of rsync i appreciate being alerted that the quality may be affected in the latest versions

@II-Paulus-II don't do this "tell everyone who you work for" thing — not cool

I just want to avoid software made by you or touched by you.

you can just block them, that's an option. their complaint is valid — perhaps, your comment was badly worded?

rsync is infrastructure, and deserves the attention and scrutiny that is also placed on other popular tools.