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

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

          • 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

            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