3 ms·
> inherent in the tool > We wouldn’t blame the blade manufacturer in that case Well, said blades are inherently sharp, when said LLM implementation is inheren
by mdp2021 3y ago
> inherent in the tool
> We wouldn’t blame the blade manufacturer in that case
Well, said blades are inherently sharp, when said LLM implementation is inherently dull (unchecked, unreasoned, unvetted).
This remains valid if the input consisted of legitimate ingredients.
- gmerc 3y agoI think that’s word play missing my point - unaligned models are sharper in their edges and ability to produce undesired content. For example, Alpaca veering of into rape fantasies while performing financial report analysis is not safe for most audiences and will cause serious accidental hurt such as triggering PTSD in survivors. So protecting those unwanted edges is a necessity for production use. But this case ain’t that. This case allowed you to throw a razor blade into the cocktail recipe. It’s negligent and stupid by the the developer, not the juicer (LLM) but also, crucially, requires stupidity by the user. The LLM really doesn’t factor in here unless you think it’s the juicers job to stop when you add blade to your OJ
- mdp2021 3y agoI think I got your point: if you want to use this range of LLMs it is best practice to restrict the input to a valid set. But my point was: even if you restricted the input to a valid set ("whitelist chocolate celery ... diet-coke and Mentos; blacklist everything else; warn-fail on detergents etc."), the potential results have easily not been stress-tested, nor the training set, nor the internal process. "Works somehow" differs from "works well".