ltning
Michael W Lucas 
@ltning where do you see that?
@mwl https://codeberg.org/small-hack/open-slopware#operating-systems - links to offending commits and to standing policy on the matter.
@ltning well fuck
@mwl Very very fuck. I am sick to my stomach right now. Don't know what to do with this information.
In desperation I started writing an email to the Foundation, but will sleep on it; I don't want to burn too many bridges until I fully understand where this came from, if it is final, what it actually means, etc.
But for fucks sake...I started looking at making an #evi port to replace Vim everywhere - and I'm not even a bloody Vim user!
NerdNextDoor 
@ltning @mwl Ohp, hello! Found this because I follow the EVi hashtag.
Yeah, I'm really pissed about FreeBSD as well, I had always known them as the no-AI system.
And before you think about switching to another BSD, there is no guarantee that isn't slop-free either. BSD's like to exchange code a lot.
In fact, I was discussing potentially making a kernel and OS with no slop software in it with some peeps in another thread.
On the other hand, nice to see people still working on EVi ports! :D
cloudskater@mwl @[email protected] @mrmasterkeyboard
Fuck, I wish I could code. I'd be all over this, you have no idea. I already procrastinate on school, the least I could do would be something useful with that time. If you make that OS tho, I'll be the first to be a monthly donator, and heck, if at some point it can run the latest version of Ardour (my digital audio workstation), even if I rely on Linux for other things, I can have an open source music making station that is 100% verifiably slop free and that'll be awesome. I know Ardour isn't friendly to AI at all, but if any of my FLOSS plugins start to… yeah I'm not thinking about that rn.
Wanting a computer with no slop code and, by extension, with a dev team that actually gives a damn about the issues AI causes, is not much to ask.
@cloudskater forgot to respond to this, but it’s never too late to start learning ;3
I… technically am! It's very clearly not my forte, but I long for the moment I can contribute a single solitary bug fix to anything hahaha
That said, if you need some help writing documentation for something… maybe I could be of assistance there.
Eugene 
@mrmasterkeyboard @ltning @mwl
> I had always known them as the no-AI system
Yes, the same. But at the past month I saw a rise of toots, even in Mastodon, with instructions about how to integrate FreeBSD machines with some LLMs. Also, I read about issue in the Claude (IIRC) GitHub repo with request to add FreeBSD support to some of their tool.
So, looks like "AI"-believers know about FreeBSD, use it and come for it 
If you have something to write to FreeBSD Foundation, please do it.
Also, since FreeBSD has some sponsorship from corporations, possibly this was the reason of adding slopcode in the FreeBSD source tree:
as400 🇵🇱 🇪🇺 :openbsd: (@[email protected])
@evgandr I guess one of the corpos sponsoring #FreeBSD told them "guys, either you use LLMs or you loose money".
Aydan@mrmasterkeyboard @ltning @mwl Something I just learned is that NetBSD does at least have a no AI code policy (for a while now) and is very clear about it
post they made: https://mastodon.sdf.org/@netbsd/112446618914747900
NetBSD Foundation 🚩 (@[email protected])
New development policy: code generated by a large language model or similar technology (e.g. ChatGPT, GitHub Copilot) is presumed to be tainted (i.e. of unclear copyright, not fitting NetBSD's licensing goals) and cannot be committed to NetBSD. https://www.NetBSD.org/developers/commit-guidelines.html
be0ba
Graham Perrin@ltning I am not "offended" by the five characters in this screenshot.
Also, I trust the Senior Director of Technology for The FreeBSD Foundation to do what's appropriate in extreme cases such as this.
ben@grahamperrin @ltning that second one (kinfo_file) seems to say it's 'reported-by' anthropic, not that it's generated by claude. Or am I just misunderstanding the terminology?
In any case I'm sort of in two minds here. Small changes like those can be easily reviewed by humans and verified as trustworthy — but in that case, what value is 'AI' actually adding?
@benjamineskola thanks. True: there's no evidence of code generation by AI.
<https://github.com/freebsd/freebsd-src/commit/25cc459286a02b646751541ccde5a33319471c73>
"Reported by: Calif.io in collaboration with Claude and Anthropic Research"
<https://calif.io/company#why-us>
Committer: Ed Maste. <https://freebsdfoundation.org/about-us/our-team/>, author of 6,991 commits: <https://freshbsd.org/freebsd?author[]=Ed+Maste+%28emaste%29>.
Reviewer: John Baldwin, author of 14,540 commits: <https://freshbsd.org/freebsd?author[]=John+Baldwin+%28jhb%29>.
@ltning human slop worries me more than AI slop in cases such as this.
Why does the page not describe OpenZFS as tainted?
That's just careless.
Incidentally, I'll continue to use OpenZFS. I don't plan a fork.
@grahamperrin That is indeed an inaccuracy - or perhaps even a failing, but since they rely on things being reported to them I can see why. In this case it is a distinction without a difference: OpenZFS is tightly integrated in FreeBSD to the point where one can hardly tell where one stops and the other begins. Especially from a users perspective.
And these are FreeBSD commits, so ..
That said: I care who wrote the code. I care less how the bug was found. It is among potentially legitimate uses, and simply finding the bug with AI does not in itself taint the code or challenge the license. How the LLM was able to find the code in the first place is a question that is outside the scope of this discussion.
And these are FreeBSD commits, so ..
That said: I care who wrote the code. I care less how the bug was found. It is among potentially legitimate uses, and simply finding the bug with AI does not in itself taint the code or challenge the license. How the LLM was able to find the code in the first place is a question that is outside the scope of this discussion.
@ltning it has been reported to them.
They describe FreeBSD as tainted with slop whilst ignoring the obvious origin: OpenZFS.
Incidentally, I don't think of OpenZFS as tainted.