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

Ask him what does he thinks about the discussion on cheese and sandwich please

Issue #929, titled “Please Do Not Vibe Fuck Up This Software”, became a lightning rod for a much broader debate than the original rsync bugs. The thread started as criticism of AI-assisted changes in rsync development, but it evolved into a discussion about trust, maintenance practices, testing, code review, and the social dynamics of open-source projects. It was prominent enough that it was discussed across Hacker News, Linux podcasts, and other communities. (libhunt.com)

The sandwiches and cheese discussion

The sandwich/cheese comments were not actually about food. They were analogies used during the argument over AI-generated code.

The basic structure of the analogy was:

• One side argued that maintainers should judge contributions by the final result rather than by how they were produced.
• The opposing side argued that the process matters because it affects confidence, reviewability, and future maintenance.

The sandwich analogy was used to illustrate this disagreement. Participants compared accepting AI-generated code to being handed a sandwich without knowing how it was made. The question wasn't whether the sandwich tastes good right now; it was whether you trust the ingredients, preparation process, and quality control.

The cheese variants of the analogy appeared when people extended the metaphor:

• If a sandwich tastes fine, do you care where the cheese came from?
• If the cheese was produced by a machine instead of a cheesemaker, does that matter?
• What if the cheese-making process is opaque and occasionally introduces contamination?
• At what point are you evaluating the sandwich versus evaluating the manufacturing process?

These exchanges were really proxies for:

1. Output-centric thinking — judge code by tests, reviews, and behavior.
2. Process-centric thinking — judge code partly by how it was produced because that affects reliability and maintainability.

Why the analogy became memorable

The thread was unusually emotional because rsync is critical infrastructure. People weren't merely debating AI tools; they were debating whether maintainers of foundational software should change their development practices. The sandwich discussion became a humorous way to argue about software engineering epistemology:

• Can you trust a product if you only inspect the final artifact?
• How much should provenance matter?
• Is code review sufficient quality control?
• Does AI change the answer because it can generate large volumes of code quickly?

My reading of the exchange

The cheese-and-sandwich tangent is interesting because it accidentally exposed the real disagreement.

The dispute was never really about cheese, sandwiches, or even AI. It was about trust:

• One camp viewed AI as another tool and believed rigorous review/testing should be enough.
• The other camp believed that AI changes the economics of code generation so much that the traditional review process becomes less trustworthy, even if the resulting code looks acceptable.

The food metaphors stuck because they translate a highly technical argument into something intuitive: whether you're comfortable eating a sandwich depends not only on the sandwich itself but also on how much confidence you have in the kitchen that produced it.

That's why a discussion that started with rsync bugs ended up talking about cheese. The cheese was standing in for software provenance and quality assurance. (libhunt.com)

Ask him what does he thinks about the discussion on cheese and sandwich please

Issue #929, titled “Please Do Not Vibe Fuck Up This Software”, became a lightning rod for a much broader debate than the original rsync bugs. The thread started as criticism of AI-assisted changes in rsync development, but it evolved into a discussion about trust, maintenance practices, testing, code review, and the social dynamics of open-source projects. It was prominent enough that it was discussed across Hacker News, Linux podcasts, and other communities. (libhunt.com)

The sandwiches and cheese discussion

The sandwich/cheese comments were not actually about food. They were analogies used during the argument over AI-generated code.

The basic structure of the analogy was:

• One side argued that maintainers should judge contributions by the final result rather than by how they were produced.
• The opposing side argued that the process matters because it affects confidence, reviewability, and future maintenance.

The sandwich analogy was used to illustrate this disagreement. Participants compared accepting AI-generated code to being handed a sandwich without knowing how it was made. The question wasn't whether the sandwich tastes good right now; it was whether you trust the ingredients, preparation process, and quality control.

The cheese variants of the analogy appeared when people extended the metaphor:

• If a sandwich tastes fine, do you care where the cheese came from?
• If the cheese was produced by a machine instead of a cheesemaker, does that matter?
• What if the cheese-making process is opaque and occasionally introduces contamination?
• At what point are you evaluating the sandwich versus evaluating the manufacturing process?

These exchanges were really proxies for:

1. Output-centric thinking — judge code by tests, reviews, and behavior.
2. Process-centric thinking — judge code partly by how it was produced because that affects reliability and maintainability.

Why the analogy became memorable

The thread was unusually emotional because rsync is critical infrastructure. People weren't merely debating AI tools; they were debating whether maintainers of foundational software should change their development practices. The sandwich discussion became a humorous way to argue about software engineering epistemology:

• Can you trust a product if you only inspect the final artifact?
• How much should provenance matter?
• Is code review sufficient quality control?
• Does AI change the answer because it can generate large volumes of code quickly?

My reading of the exchange

The cheese-and-sandwich tangent is interesting because it accidentally exposed the real disagreement.

The dispute was never really about cheese, sandwiches, or even AI. It was about trust:

• One camp viewed AI as another tool and believed rigorous review/testing should be enough.
• The other camp believed that AI changes the economics of code generation so much that the traditional review process becomes less trustworthy, even if the resulting code looks acceptable.

The food metaphors stuck because they translate a highly technical argument into something intuitive: whether you're comfortable eating a sandwich depends not only on the sandwich itself but also on how much confidence you have in the kitchen that produced it.

That's why a discussion that started with rsync bugs ended up talking about cheese. The cheese was standing in for software provenance and quality assurance. (libhunt.com)

It's funny that this AI response hallucinated less than the slopped commits...

I think thats about a time this issue needs to be locked and cleaned up. Some people just wanna shitpost and see world burns.

I think thats about a time this issue needs to be locked and cleaned up. Some people just wanna shitpost and see world burns.

panem et circenses

I think thats about a time this issue needs to be locked and cleaned up. Some people just wanna shitpost and see world burns.

Hard to refrain from mocking this project after the clown-ish replies people have witnessed from the maintainers.

I think thats about a time this issue needs to be locked and cleaned up. Some people just wanna shitpost and see world burns.

A lock may be good. But still, it's AI slop code. And why clean up!?

I think thats about a time this issue needs to be locked and cleaned up. Some people just wanna shitpost and see world burns.

A lock may be good. But still, it's AI slop code. And why clean up!?
And the code is buggy, causing tons of problems and also tons of hate because AI was used and it is buggy, ruined, and horrible,

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.

fork it yourself

Do I need to remind you of what happened with GZDoom in the recent past?

Do you really think people are chomping at the bit to do the thankless work of maintaining rsync? lmfao

stop it, get some help.

I think thats about a time this issue needs to be locked and cleaned up. Some people just wanna shitpost and see world burns.

+1

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.

fork it yourself

Do I need to remind you of what happened with GZDoom in the recent past?

Do you really think people are chomping at the bit to do the thankless work of maintaining rsync? lmfao

I personally think people can do better than carelessly vibecoding this project (not just the test suites but apparently also main code) and trusting AI to not fuck it up, lol.

stop it, get some help.

You smell bro

I personally think people can do better than carelessly vibecoding this project (not just the test suites but apparently also main code) and trusting AI to not fuck it up, lol.

Damn, you should ask for a refund.

I personally think people can do better than carelessly vibecoding this project (not just the test suites but apparently also main code) and trusting AI to not fuck it up, lol.

Damn, you should ask for a refund.

I don't really pay for anything GitHub-related or AI-related, sorry.