I’m not entirely sure if i consider proprietary software worse than FOSS slop, but i have at the very least started to treat them the same way, as in i only use it if there’s no good alternative.
Then you misunderstand the point of FOSS. Clean-room slopimentations of proprietary software, assuming it is released on a FOSS license, is the very essence of the FOSS philosophy. Make free and open what those that would oppress you do not want free an open.
Don’t get me wrong it’s better to not have slop than have slop, but FOSS Slopware, FOSSlopware, or as I’ve recently taken to calling it, FOSS plus slop is a good thing.
A lot of the recent AI slop software aren’t actually using proper clean room techniques though.
With clean room reverse engineering, you need two completely separate parts:
Someone that reverse engineers the original program and writes a spec specifying how it behaves
Somebody else, who has never inspected the original program in any way, writes a new program based entirely on the spec.
For the recent AI slop reimplementations, some of them are essentially one person using two different AI models and agents for these two roles. Some of the potential problems are that:
If the person was ever exposed to data from the original app, or has ever inspected or reverse engineered the original software in any way, even just by looking at debugging output or temporary artifacts from the reverse engineering agent, then it’s not a clean room any more.
There’s no guarantee that the implementation agent won’t inspect the proprietary software, violating the clean room contract. Telling an agent not to do something won’t actually stop it from trying.
There’s no guarantee that the implementation agent didn’t have leaked code from the original program in its training data.
Related to this, there’s no guarantee that the model didn’t ingest data from original developer because they used an agent that trained on their data.
This. One of the big concerns from AI, especially in the early days, was ‘license laundering’; taking copy-left code (e.g. GPL), pumping it through an LLM, and putting it into a proprietary close-sourced product. Slop can’t be copyrighted, under most definitions; but (where applicable) putting slop under such a license reduces those concerns.
More or less, you’re correct. It’s a bit nuanced and the lines get blurry. These are things that get argued out in court and are upheld on a case-by-case basis. If I see slop with a GPL license, I’m probably not going to risk violating it on a hope that it isn’t covered…
The use of AI tools to assist rather than stand in for human creativity does not affect
the availability of copyright protection for the output.
• Copyright protects the original expression in a work created by a human author,
even if the work also includes AI-generated material.
• Copyright does not extend to purely AI-generated material, or material where there
is insufficient human control over the expressive elements.
• Whether human contributions to AI-generated outputs are sufficient to constitute
authorship must be analyzed on a case-by-case basis.
• Based on the functioning of current generally available technology, prompts do not
alone provide sufficient control.
• Human authors are entitled to copyright in their works of authorship that are
perceptible in AI-generated outputs, as well as the creative selection, coordination,
or arrangement of material in the outputs, or creative modifications of the outputs.
• The case has not been made for additional copyright or sui generis protection for AI-
generated content
Repo licenses, for example, apply where ever they may be applicable; they aren’t necessarily a blanket claim that everything in the repo strictly falls under that license (e.g. vendored dependencies may have their own licenses. Modules, components, files, or even individual functions or lines of code may have differing licenses. Its messy when you get pedantic about it)
So you can slap a license on slop… But whether or not it holds, and to which parts specifically, is variable
i’ll agree with you that anti-slop philosophy and pro-FOSS philosophy happen to not necessarily contradict. but i would like to respect both at once and value resource efficiency (i.e. not supporting the extreme resource waste that slop causes) over FOSS principles.
That is fair stance to take, and understandable as at the moment as especially with American models the token rate for even trivial decompliation is quite silly, but like image and video generation that’ll get reduced drastically soon and you’ll be able to run it on a 2090 in reasonable timespace.
I would use non-FOSS software over FOSS slopware
I’m not entirely sure if i consider proprietary software worse than FOSS slop, but i have at the very least started to treat them the same way, as in i only use it if there’s no good alternative.
But how would you know that your non-FOSS software isnt slop?
📈
Then you misunderstand the point of FOSS. Clean-room slopimentations of proprietary software, assuming it is released on a FOSS license, is the very essence of the FOSS philosophy. Make free and open what those that would oppress you do not want free an open.
Don’t get me wrong it’s better to not have slop than have slop, but FOSS Slopware, FOSSlopware, or as I’ve recently taken to calling it, FOSS plus slop is a good thing.
FLOPSS
A lot of the recent AI slop software aren’t actually using proper clean room techniques though.
With clean room reverse engineering, you need two completely separate parts:
For the recent AI slop reimplementations, some of them are essentially one person using two different AI models and agents for these two roles. Some of the potential problems are that:
This. One of the big concerns from AI, especially in the early days, was ‘license laundering’; taking copy-left code (e.g. GPL), pumping it through an LLM, and putting it into a proprietary close-sourced product. Slop can’t be copyrighted, under most definitions; but (where applicable) putting slop under such a license reduces those concerns.
I am under the impression that only humans can create anything that can be copywritten.
There is a picture taken by a monkey that set the precedent.
Maybe be should redefine copyright to remove human and in stead use person.
More or less, you’re correct. It’s a bit nuanced and the lines get blurry. These are things that get argued out in court and are upheld on a case-by-case basis. If I see slop with a GPL license, I’m probably not going to risk violating it on a hope that it isn’t covered…
https://www.copyright.gov/ai/
https://en.wikipedia.org/wiki/Artificial_intelligence_and_copyright
Quote from the former
Repo licenses, for example, apply where ever they may be applicable; they aren’t necessarily a blanket claim that everything in the repo strictly falls under that license (e.g. vendored dependencies may have their own licenses. Modules, components, files, or even individual functions or lines of code may have differing licenses. Its messy when you get pedantic about it)
So you can slap a license on slop… But whether or not it holds, and to which parts specifically, is variable
i’ll agree with you that anti-slop philosophy and pro-FOSS philosophy happen to not necessarily contradict. but i would like to respect both at once and value resource efficiency (i.e. not supporting the extreme resource waste that slop causes) over FOSS principles.
That is fair stance to take, and understandable as at the moment as especially with American models the token rate for even trivial decompliation is quite silly, but like image and video generation that’ll get reduced drastically soon and you’ll be able to run it on a 2090 in reasonable timespace.
You can only choose between closed source slop or FOSS slop.
I’d use whatever best enabled me to achieve what I was trying to accomplish with the computer
Not all FOSS software is slop.
thats not what I said
My bad, didn’t realize you were talking about AI slop FOSS software.
they meant AI-slop OSS