244
you are viewing a single comment's thread
view the rest of the comments
[-] vagrancyand@sh.itjust.works 14 points 9 hours ago* (last edited 9 hours ago)

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.

[-] bryndos@fedia.io 1 points 41 minutes ago
[-] dan@upvote.au 1 points 1 hour ago* (last edited 1 hour ago)

Clean-room slopimentations

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:

  1. Someone that reverse engineers the original program and writes a spec specifying how it behaves
  2. 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.
[-] ImgurRefugee114@reddthat.com 13 points 8 hours ago

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.

[-] Captain_Patchy@lemmy.world 1 points 6 hours ago

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.

[-] ImgurRefugee114@reddthat.com 1 points 6 hours ago* (last edited 6 hours ago)

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

[-] Aatube@lemmy.dbzer0.com 9 points 9 hours ago

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.

[-] vagrancyand@sh.itjust.works 3 points 9 hours ago

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.

this post was submitted on 20 Nov 2026
244 points (98.8% liked)

linuxmemes

33506 readers
1107 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 3 years ago
    MODERATORS