On 8/27/2023 7:32 PM, Andrew Hyatt wrote:
> After following Jim Porter's suggestion above, here is the new function,
> and you can see the advice we're giving in the docstring:
>
> (cl-defgeneric llm-nonfree-message-info (provider)
> "If PROVIDER is non-free, return info for a warning.
> This should be a cons of the name of the LLM, and the URL of the
> terms of service.
>
> If the LLM is free and has no restrictions on use, this should
> return nil. Since this function already returns nil, there is no
> need to override it."
> (ignore provider)
> nil)
For what it's worth, I was thinking about having the default be the
opposite: warn users by default, since we don't really know if an LLM
provider is free unless the Elisp code indicates it. (Otherwise, it
could simply mean the author of that provider forgot to override
'llm-nonfree-message-info'.) In other words, assume the worst by
default. :) That said, if everyone else thinks this isn't an issue, I
won't stamp my feet about it.
I agree that it'd be nice to have that property. That's the way I had it initially, but since you need info if it's non-free (the name / TOS), but not if it is free, the design where free was the default was the simplest. The alternative was one method indicating it was free/nonfree and the other, if non-free, to provide the additional information.
As for the docstring, I see that many models use ordinary software
licenses, such as the Apache license. That could make it easier for us
to define the criteria for a libre provider: is the model used by the
provider available under a license the FSF considers a free software
license?[1] (For LLM providers that you use by making a web request, we
could also expect that all the code for their web API is libre too.
However, that code is comparatively uninteresting, and so long as you
could get the model to use on a self-hosted system[2], I don't see a
need to warn the user.)
I agree that it'd be nice to define this in a more clear way, but we also can just wait until someone proposes a free LLM to include to judge it. We can always bring it back to the emacs-devel list if there is uncertainty.
The hosting code is not that relevant here. For these companies, there would be restrictions on the use of the model even if there were no other unfree software in the middle (kind of like how Llama 2 is). Notably, no company is going to want the user to train competing models with their model. This is the most common restriction on freedoms of the user.
(Also, if you prefer to avoid having to say '(ignore provider)', you can
also prefix 'provider' with an underscore. That'll make the byte
compiler happy.)
TIL, that's a great tip, thanks!
[1] https://www.gnu.org/licenses/license-list.en.html
[2] At least, in theory. A user might not have enough computing power to
use the model in practice, but I don't think that matters for this case.