Post B6EtGBuClpMQSHPkrg by mirabilos@toot.mirbsd.org
 (DIR) More posts by mirabilos@toot.mirbsd.org
 (DIR) Post #B6Ce44ek0iXirs1eLI by kaidenshi@exquisite.social
       1 likes, 1 repeats
       
       Nearly six weeks later, and the question of whether "AI" generated code in tmux -- not tool-assisted bug finding, not refactoring, actual LLM-generated slop with questionable license(1) -- that was consequently merged into OpenBSD base, is considered acceptable by the lead devs, remains unanswered. Despite Theo de Raadt's concrete stance against any code of questionable license origin polluting the project -- and the tmux merge was indeed questionable -- it seems this is being swept under the rug. This makes me extremely uncomfortable; it's like seeing a fox in the henhouse but the farmers are all looking the other way and no one can convince them to admit they can see it and root it out. I really don't know what to do being just a user; I feel like even if I tried to chime in on the mailing list I would just be ignored like the others trying to raise the alarm. I hope, as they do, that this is being discussed internally, away from the public list, and that a positive outcome is near. Maybe they are waiting for the 7.9 release before setting anything in stone. Or maybe the "AI" disease has infected one of the last pure operating system projects we have left and there's no going back. https://marc.info/?l=openbsd-misc&m=177513420401322&w=2(1) As in, it could have been lifted from any GPL'd or otherwise encumbered code and there's no way to know for sure since LLMs are perfect plagiarism machines#OpenBSD #vibecoding #NOAI #stoptheslop
       
 (DIR) Post #B6D9lKP6QwnKjvoeQq by thomholwerda@exquisite.social
       0 likes, 0 repeats
       
       @kaidenshi Can I quote this verbatim on OSNews? Its an excellent summary, no need for me to redo your work. 😄
       
 (DIR) Post #B6D9lKjfCVF1lhR4To by kaidenshi@exquisite.social
       0 likes, 0 repeats
       
       @thomholwerda Absolutely! And I bookmarked it so it doesn't auto-delete.
       
 (DIR) Post #B6D9lKw4SNAMOBEyoq by thomholwerda@exquisite.social
       0 likes, 0 repeats
       
       @kaidenshi Up for tomorrow! Thanks bud 😄
       
 (DIR) Post #B6D9lL5zrT6csxsuI4 by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @thomholwerda @kaidenshi I’m more surprised you only noticed it now, when it was the talk of the Fedi ~four and ~five weeks ago…
       
 (DIR) Post #B6EA8y9f07qBqMpG76 by kaidenshi@exquisite.social
       0 likes, 0 repeats
       
       @mirabilos @thomholwerda I've been following the issue on the mailing list since it popped up, and I've talked about it here previously. This particular post is prompted by weeks of waiting to see a definitive response from the project.
       
 (DIR) Post #B6EA8ySRsGrymdcGOm by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @kaidenshi @thomholwerda yeah, I meant Thom, from the OSnews post.Thanks for keeping up with the mailing list. I’ve been looking every now and then, and…
       
 (DIR) Post #B6EcBhNqbrenPjYGG0 by be0ba@fedi.tcp80.org
       0 likes, 1 repeats
       
       @mirabilos @kaidenshi @thomholwerdaAnother issue I hadn't thought much about that affects (Open|Net|FreeSLOP)BSD is LLVM. All three include it; it's the base system compiler for OpenBSD and FreeSLOPBSD. LLVM is actively accepting slop; a very hasty search shows at least 25-30 commits.My understanding is that the LLVM in the OpenBSD tree is effectively a maintained fork specific to OpenBSD, but I don't know much extra labour this will end up adding to exclude the slop there.
       
 (DIR) Post #B6EtGBuClpMQSHPkrg by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @be0ba @kaidenshi @thomholwerda yeah, they’re caught between a rock and a hard place there.stick with GCC, no licence regresson: 4.1.2 was the last GPLv2 version, so anything newer is out, eliminating new architectures from basestick with GCC and upgrade beyond 4.1.2: out because GPLv3 would be a reduction of freedom on base and thus inacceptableClang+LLVM: now ensloppified, but the Apple takeover has already cast deep shadows before; also, huge C++ monstrosityPCC: basically didn’t materialise; the ragge renewal… built software, but it was neither fast enough nor small enough for the boot floppiesfew other maintainable options under libre enough licences, even leaving currently-supported architectures out
       
 (DIR) Post #B6EtO9JQIPSsjG0M7M by mirabilos@toot.mirbsd.org
       0 likes, 0 repeats
       
       @thomholwerda @kaidenshi at least, for now, TNF has confirmed they have not permitted any slop in so far