The wording is weird. But the project (openslop) defines permissive as basically having a path for AI to enter the code. This lumps together both measured approaches like NetBSD's and fully embracing slop contributions in the same category.

I think this only makes sense if you view AI contributions as a taint, something that threatens the licensing of a project. In that optic, it really is an all or nothing. But it doesn't help users choose among the options as much.

Personally, I think any output from these models must be for noncommercial use only, as its impossible to track down exactly whose rights are being violated for any given output, yet guaranteed that's its a non-zero number every single time.

They want it to worm its way into every corner of our lives as quickly as possible so that when a non-criminal administration and congress come into power, they'll be hesitant to prosecute something that touches the entire economy.

Don't let them win.

Biggest problem is proving where the code came from. Trying to pick out what software vibe code comes from is loke.trying to pick out a single hay strand from a pile of sharp broken glass and used needles. Can you do it? I'm sure with enough time you can, but at that point was the time spent worth it instead of learning how to be an actual programmer and/or developer?

I think you're right. Hopefully FSF will win some lawsuits and we'll get all the models made public

Indeed it would/does

You are disallowed from building a commercial product on top of it or tweek/fix it without publishing said changes. There may be systemic reason that prevent that.

This is going to be the next Arch, isn't it?

That's a lie, you simply run "sysinst" and select "install pkgin" from a curses menu. sysinst can also help you setup a wifi connection and other basic user config things from the comfort of a TUI. But good job in trying to scare people of from trying a good alternative OS.