rsync was basically done until the maintainer discovered vibecoding

[odd@mstdn.social]

@hailey oh boy. Well I hope #Gentoo's no AI policy is working against upstream vibecoding as well.

But what madness to have to check whether a fundamental piece of software is still trustworthy in the future.

[fogti@chaos.social]

@zl2tod @hailey sure https://codeberg.org/fogti/rsync-nai

[coldclimate@hachyderm.io]

@hailey what are the commits? Scrolling back they seem to be adding tests and some CI type stuff recently

[hailey@hails.org]

@coldclimate this for one thing https://mastodon.gamedev.place/@JeremiahFieldhaven/116654345332213390

[ki@chaos.social]

@hailey
what the fuck is wrong with this reality

[sreycoyrehourcq@social.sciences.re]

@hailey cc @khinsen @civodul @zimoun Even Rsync, this is the end... Now we need to maintain ai slop blacklisted list of packages to update debian.

[wtl@mastodon.social]

@hailey @auxonic <screams into digital void>

[endlessmason@hachyderm.io]

@fionasboots @hailey
Also, is this even real snake in this oil?!

[endlessmason@hachyderm.io]

@WTL @hailey @auxonic
Most voids have been digital for so long that is pretty unlikely you've actually encountered a genuine analogue one, let alone an acoustic

[dalias@hachyderm.io]

@hailey Distro packaging systems need a workflow that auto pins all packages at last tag before any commits crediting slop bots.

[viq@social.hackerspace.pl]

@fogti @zl2tod @hailey https://man.openbsd.org/OpenBSD-6.6/openrsync.1

[exec@furry.engineer]

@hailey Apparently some people can't comprehend that software can be completed and finished

[zl2tod@mastodon.online]

@viq

Which reminds me of something that really annoys me about rsync: imcompatibility between versions.

@fogti @hailey

[auxonic@ottawa.place]

@EndlessMason @WTL @hailey when I was a kid in Alberta we’d visit a cave some summers and go into the dark of the mountain. Sometimes I think that might be the best place. https://hikebiketravel.com/canyon-creek-ice-cave/

[deepbluev7@nheko.io]

@odd@mstdn.social @hailey@hails.org It generally doesn't prevent AI generated projects from getting packaged, but considering that this is a core package for Gentoo, it likely will have additional review and such done, which will affect if it gets unmasked and such?

[endlessmason@hachyderm.io]

@auxonic @WTL @hailey
I hope this email does not find you.

[patterfloof@meow.social]

@hailey damnit, that's my backup program, picked because its easy & doesn't have unwieldy imports to restore

[linuxandyarn@hachyderm.io]

@hailey Oh hell, no one should be allowed to fuck up rsync like that. Package pinning time!

[jra@soc.jra.sh]

@hailey@hails.org It's so incomprehensible. For someone to develop rsync, a software that serves a particularly sensitive purpose and thus must be a rock-solid block of bits, I would assume:

1. The maintainer actually used and depended on rsync, and would be the first to suffer if the software's dependability started to degrade;

2. That the maintainer actually took pride on rsync being so well-reputed and considered an integral part of many, many people's workflows;

3. More importantly: if the maintainer felt unable / simply didn't want to continue working on rsync for any reason, that he would try to pass the torch to someone that ensured its future in the same molds.

Instead, rsync is proudly making an effort to join the rapidly-growing lists of software that will be remembered sadly for quite some time for their pre-LLM existence. Until one day they're simply forgotten.

[erik@mastodon.infrageeks.social]

@fionasboots @hailey Already done a few years go due to some licencing issues to produce openrsync (https://github.com/kristapsdz/openrsync)