Hi Untrusem,
Untrusem <[email protected]> writes:
So I saw there So I saw there was a update for waybar in guix
repo
and then I checked the release notes and saw that it was using
co-pilot and claude both and I personally don't like to use
software
that have LLMs if I can avoid that.
I would have not known that waybar author started using LLM or
not if
I didn't visited the repo myself.
So that's why I wanted a way to know when a guix package updates
or
gets added. It should explicitly mention that LLMs is being used
in
the software to let the users know that the software they are
using is
slop or not.
I completely agree with you: users should have the freedom to run
software which doesn’t contain LLM output. However, the subject
is complicated, and I think requires a GCD. I don’t think commit
messages are the best way to accomplish that, since they are
difficult for users to find. I also have some reservations about
it being a package contributor’s responsibility to do this; it can
be difficult to know if an LLM is used in the first place[1]. Are
folks contributing version bumps responsible for auditing the
changes in the new version for the presence of LLM use?
Perhaps a tool could be written making use of the Open Slopware
list[2], which could audit packages in a profile and report which
contain LLM code.
Unfortunately, the Linux kernel is now accepting LLM-authored
patches, so unless you want to strip those out or use an older
version, it’s not possible to run a Linux machine free of this
output.
-- Ian
[1]: Some maintaners deliberately obscure presence and extent of
LLM tools in their projects.
[2]: https://codeberg.org/small-hack/open-slopware
