i plan to package openrsync this weekend in alpine as an alternative to rsync (and probably switch the default rsync implementation in future)
-
sidebar: given that there is interest in alternatives to GPL software that is now being vibecoded, and these alternatives largely tend to not be copyleft...
will vibe coding mean the death of copyleft?
@ariadne Possibly, there seems to be problems from multiple sides; with some vibecoded re-implementations and LLM-generated code effectively licence-washing GPL'd code,
while other GPL'd projects voluntarily drown themselves in slop code.Though, there's also GPL projects taking more restrictive stances about how or if LLMs can be used, to avoid the latter problem,
and hopefully new copyleft projects starting (though, The Industry
seems to favour permissive licenses like MIT lately?) -
@ariadne Quite the opposite I think. I think it leads to a resurgence in interest in copyleft, since these are largely the projects not embracing slopware and the fraudulent "non-copyleft" "rewrites" are pandering to techbro asshats and the corporate AI-slop program.
@dalias @ariadne I said different, but I suppose I assumed that the GPL projects @ariadne was thinking about are those that have given into slop coding; GPL code that isn't GPL, essentially.
I think if people are the ones developing the codebase, we are still stuck with the problem of derivative works not complying with the GPL (as the slop coded projects are derivatives of the GPL projects that have been trained on).
Copyleft becomes less of a cudgel - I don't think it is anything but weaker.
-
sidebar: given that there is interest in alternatives to GPL software that is now being vibecoded, and these alternatives largely tend to not be copyleft...
will vibe coding mean the death of copyleft?
@ariadne That's definitely a concern of mine. AI might be the greatest enclosure act in history.
-
@dalias @ariadne I said different, but I suppose I assumed that the GPL projects @ariadne was thinking about are those that have given into slop coding; GPL code that isn't GPL, essentially.
I think if people are the ones developing the codebase, we are still stuck with the problem of derivative works not complying with the GPL (as the slop coded projects are derivatives of the GPL projects that have been trained on).
Copyleft becomes less of a cudgel - I don't think it is anything but weaker.
@yoasif @ariadne The derivative works are going to have wildly unclear infringement status that varies by jurisdiction and perhaps by short-term political winds. That is an incredibly precarious thing for anyone to be depending on. We need to be amplifying this narrative to make potential users terrified of legal consequences that might befall them in unexpected locations even when they think they have certain countries' legal systems under their thumbs.
-
that is also not relevant, but i am not sure that your assertion is true anyway, as at least one debian developer has suggested that the regressions are bad enough to revert back to the last non-LLM version.
@ariadne @AmyZenunim LOL, LMAO
-
that is also not relevant, but i am not sure that your assertion is true anyway, as at least one debian developer has suggested that the regressions are bad enough to revert back to the last non-LLM version.
@ariadne @dysfun @AmyZenunim Fedora, yes, that Fedora, the one pushing MCP nonsense and whatever else either held rsync back at the last non-slop version or rolled back
-
i plan to package openrsync this weekend in alpine as an alternative to rsync (and probably switch the default rsync implementation in future)
@ariadne Thank you!
-
sidebar: given that there is interest in alternatives to GPL software that is now being vibecoded, and these alternatives largely tend to not be copyleft...
will vibe coding mean the death of copyleft?
@ariadne copyleft didn't predict the creation of software that could trivially launder the functionality of the software through a process judged to be transformative...
...but Marx did!
-
i plan to package openrsync this weekend in alpine as an alternative to rsync (and probably switch the default rsync implementation in future)
@ariadne Oh, I was actually considering packaging openrsync myself in response to the recent release's bug reports (as a fail-safe for pmOS), but nice to see you beat me to it. I don't know enough about openrsync other than it is an OpenBSD version to really make any solid statements other than thanks
-
@ariadne Oh, I was actually considering packaging openrsync myself in response to the recent release's bug reports (as a fail-safe for pmOS), but nice to see you beat me to it. I don't know enough about openrsync other than it is an OpenBSD version to really make any solid statements other than thanks
@ariadne It is also very interesting reading the comments on this post with people explaining the entire ecosystem to you as if you know nothing about it...
-
i plan to package openrsync this weekend in alpine as an alternative to rsync (and probably switch the default rsync implementation in future)
@ariadne I haven't been paying particular attention. What's the problem with rsync? -
@ariadne I haven't been paying particular attention. What's the problem with rsync?
@me its now being coded by Claude and there have been regressions
-
@me its now being coded by Claude and there have been regressions
@ariadne Ugh. I use rsync daily. Thanks for the heads-up. -
i plan to package openrsync this weekend in alpine as an alternative to rsync (and probably switch the default rsync implementation in future)
@ariadne It'd be useful for them to update the "please wait" page with more detail.
It'll be nice having a more heterogenous ecosystem. Thanks in advance for your planned port.
-
i plan to package openrsync this weekend in alpine as an alternative to rsync (and probably switch the default rsync implementation in future)
@ariadne thank you
-
@ariadne
Bug#1138239: rsync: Consider reverting to pre-LLM version
https://bugs.debian.org/1138239@billchenchina @ariadne and avoid the latest security release with 6 CVE? 🤯
-
sidebar: given that there is interest in alternatives to GPL software that is now being vibecoded, and these alternatives largely tend to not be copyleft...
will vibe coding mean the death of copyleft?
@ariadne I don't know, but I've thought about this exact scenario way too much and it seems like it's at least a real concern.
I guess we'll see how the next few years play out.
-
that is also not relevant, but i am not sure that your assertion is true anyway, as at least one debian developer has suggested that the regressions are bad enough to revert back to the last non-LLM version.
interesting
-
sidebar: given that there is interest in alternatives to GPL software that is now being vibecoded, and these alternatives largely tend to not be copyleft...
will vibe coding mean the death of copyleft?
@ariadne I'd be a bit surprised, since copyleft is in theory a lot more legally resistant to being *used* for vibecoding. Not that courts will likely care, because when a corporation does it it's generally legal (though maybe I'm being too cynical, or not cynical in a complex enough fashion—the ongoing lawsuits from the NYT and such haven't been decided yet). But, it does seem like in the longer term this could naturally lead to people against LLMs using licenses that attach *more* stipulations rather than fewer.
As a random internet commentator, my specific prediction: by the end of this decade, we'll see reasonably wide and/or notable adoption of a software license that breaks the traditional taboo against having clauses like the CC NC clause where field of use is restricted. -
i plan to package openrsync this weekend in alpine as an alternative to rsync (and probably switch the default rsync implementation in future)
@ariadne I think about replacing rsync for several years.
Now I try to see how far I've got with the prototype of a pre-generated git-like bundle of metadata and http as transport protocol. Okay, only for non-chunked transfers.
