rsync was basically done until the maintainer discovered vibecoding
@hailey This is very sad.
@f4grx @hailey Yeah. I always viewed Andrew Tridgell as one of the real heroes, and thought if I ever met him I'd definitely buy him a beer.

@hailey Gonna lock the version on all my systems (altough Debian, Void and FreeBSD might do that too and I don't even have to)

EDIT: FreeBSD has 3.4.3 and there's no easy way to downgrade – so I just manually got 3.4.1 tarball, configure/make/doas make install

@speaktrap @hailey What is the last slop-free version?

@daks has replied:
3.4.1. Although it has some not fixed CVE's. So there is no good alternative unless your distro's team back ports fixes.

@zillion
3.4.1. Although it has some not fixed CVE's. So there is no good alternative unless your distro's team back ports fixes.
@speaktrap @hailey
@speaktrap
That's why I love Gentoo, rsync-3.4.1-r3 is the last slop-free version marked 'stable' AND have back ported fixes for those nasty CVEs.
@hailey

@daks @speaktrap @hailey oh that's great!

I've been happily using debian since forever, but I'm slowly warming up to the idea of moving to gentoo..

@hailey

Fork that.

rsync-nai

Fork of https://github.com/RsyncProject/rsync at commit 236417cf354220669014317b1ba818b9d931afbb, just before the first obviously LLM-influenced commit

Codeberg.org
openrsync(1) - OpenBSD manual pages

@viq

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

@fogti @hailey

@zl2tod @viq @fogti @hailey Me too. TrueNAS Core (and presumably Scale) ships with a broken rsync with patches applied to tack on some NFS stuff in a way that prevents Linux xattr info from passing properly so stock TrueNAS is unable to backup properly from Linux clients.

@alexr
/me instinctively starts looking around for a cross

@zl2tod @viq @fogti @hailey

@viq @fogti @zl2tod @hailey OpenRsync will be really nice when it actually gets developed. Last time I checked it hadn't been touched in forever.
@jackemled @viq @fogti @zl2tod @hailey is that actually a concern here? I don't use rsync much but it seems like the sort of thing that could happily exist in a maintenance-only state almost indefinitely. (but I also haven't needed anything exotic out of it, so idk)
@gsuberland @jackemled @viq @zl2tod @hailey It is a concern as afaik openrsync lacks a lot —in terms of features— behind samba's rsync.
@gsuberland @jackemled @viq @zl2tod @hailey Besides that, I agree, except for security fixes, I doubt anyone really expects new features beyond those already established, in rsync.
@fogti @gsuberland @jackemled @viq @zl2tod @hailey Most alternative rsync implementations are stuck on the simpler protocol version 27, which is before many improvements such as the generation of the file list in parallel: https://github.com/gokrazy/rsync#existing-rsync-implementation-survey
Instead of trying to reimplement the undocumented rsync protocol, I would rather wish for an active community around a modern alternative file transfer tool based on content-defined chunking (as used by restic and borg backup). Google had a proof-of-concept with benchmarks for Stadia, but abandoned it: https://github.com/google/cdc-file-transfer
Following the ideas of FastCDC, resync looks promising on redefining the protocol, while keeping the command line interface familiar to users of rsync: https://github.com/vedLinuxian/resync-rs
GitHub - gokrazy/rsync: rsync in Go! implements client and server, which can send or receive files (upload, download, all directions supported)

rsync in Go! implements client and server, which can send or receive files (upload, download, all directions supported) - gokrazy/rsync

GitHub
@raimue @fogti @gsuberland @[email protected] @viq @zl2tod @hailey any more info on the project or author?, because popping up with a +9k lines initial commit in 2026 is very sus, particularly coming from a recommendation by someone with a slop PFP
@Ember Take the linked projects as examples of what will be possible if we leave the rsync protocol behind. I am not affiliated with any of these projects.
OpenRsync

the main OpenRsync page

@dieweltist @[email protected] That's..... They could have called it librersync, which is less problematic to say aloud.
@noodle Tried saying it aloud, do you mean that it sounds like "open arse sync"?
@dieweltist
Some transliterated it as 'arse ink'
https://aus.social/@ajft/116606417227815939
ajft [SEC=yferc ooxie] (@[email protected])

Content warning: mild lewd. Rstats. pun.

Aus.Social

@noodle @dieweltist Open Arse, Inc. :D

honestly I think this is a plus 🤣

@hailey FFS can we fork rsync and have a non-AI coded version?!

Why don't intelligent people get this: AI (LLM) coding takes vast amounts of power and resources and puts control in the hands of totally unethical mega-corps and billionaires. Not too mention the copyright infringement and lack of attribution that comes with LLM-coded slop.

@fionasboots @hailey
Also, is this even real snake in this oil?!
@fionasboots @hailey Already done a few years go due to some licencing issues to produce openrsync (https://github.com/kristapsdz/openrsync)
GitHub - kristapsdz/openrsync: BSD-licensed implementation of rsync

BSD-licensed implementation of rsync. Contribute to kristapsdz/openrsync development by creating an account on GitHub.

GitHub
@hailey @fionasboots @erik that’s a reimplementation though, not a fork
@mirabilos @hailey @fionasboots True, but in order to massively change the license regime that's the best option
@fionasboots @hailey @erik no complaint from me, I’m a BSD person. But pragmatic, openrsync documents it lacks functionality. (I’ll have to see what exactly. I just have no time or spoons, only fatigue.)
@hailey can someone with a github account go and dunk on the guy?
@hailey hurts. hurts to see.

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

@odd @hailey 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?

@odd @hailey

Given a choice between freezing all packages before vibe coding was "discovered" and packaging upstream releases, the former is not fully practical. The Gentoo social contract requires following council mandated policies about how one interacts with the Gentoo project, but doesn't control what other projects merge.

The kernel is slopcoded too, but we can't exactly do without that, now can we? Well, okay, we recently added experimental GNU Hurd support. :P

@odd @hailey

That doesn't mean we have to put up with horrid slop, it just means that blanket forbidding all LLM assisted software is in practice unenforceable outside our community (where we cannot analyze PRs and require assertion of non-use).

Inevitably the result of slop is that the software deteriorates and doesn't work, and Gentoo may respond by freezing updates or removing it entirely (see chardet being frozen).

We do what we can, and we make our disapproval clear regarding the rest.

@odd @hailey

I don't expect non-buggy versions of rsync to be dropped in favor of slopcoded ones.

@odd @hailey

The fact that Gentoo, unusually among distros, actually supports (unlimited) multiple versions of a package and for users to pick and choose their versions, means there is a *lot* of latitude for isolating the dangers of slopcoding destroying a package. It's generally always possible to discover that the project fell apart and stopped working, and just tell portage to reinstall the old version. Removing slopcoded trash from the distro is "simply" a matter of removing one choice.

@eschwartz does make me wonder if going for stable is an idea. I've been running ~amd64 for years as it has been pretty uneventful, but I'd imagine slop instability may take some time to surface.

@odd

That has always been a risk even before slopcoding, and the risk has indeed become greater now that people who formerly were known to be careful craftspeople have abandoned the notion of craft.

I don't run ~amd64 myself except for particular packages I'm interested in (including ones I maintain). Take that as you will. :)

@hailey fork it and call it rkink
@hailey what are the commits? Scrolling back they seem to be adding tests and some CI type stuff recently
Jeremiah Fieldhaven (@[email protected])

So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup. Revert to 3.4.1 and it works. So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog. Since 3.4.1, 36 commits by "tridge and claude" Oh for fuck's sakes.

Gamedev Mastodon
@hailey
what the fuck is wrong with this reality
@ki @hailey Looking around at pretty much everything for the last decade, I sometimes feel like we've discovered the Great Filter.
@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.
open-slopware

Free/Open Source Software choosing to use and/or support LLM usage/AI, as well as alternatives and tips to requesting better policies or forking.

Codeberg.org
isomoth (@[email protected])

@joriki I know this one for open source projects. https://codeberg.org/small-hack/open-slopware

Infosec Exchange
@hailey @auxonic <screams into digital void>
@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
@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/
Canyon Creek Ice Cave Hike Near Bragg Creek

If you want to explore a cave or you're after a different kind of outing do the Canyon Creek Ice Cave hike near Bragg Creek. Bike the road.

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