Please Do Not Vibe Fuck Up This Software

[II-Paulus-II]

[vladkens]

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

[thijstriemstra]

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.

[stsquad]

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.

[ppowo]

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

[ranidspace]

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]

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

[ppowo]

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

[mackensen]

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

[stsquad]

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.

[ppowo]

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

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

[ppowo]

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

[broman]

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?

[hydrargyrum]

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