For your use case, you should probably fine tune the model to reduce the rejection rate.
For your use case, you should probably fine tune the model to reduce the rejection rate.
My advice here is make the model your own. Its open weight, I encourage it to be make it useful for your use case and your users, and beneficial for society as well. We did our best to give you a great starting point, and for Norwegian in particular we intentionally kept the large embedding table to make adaption to larger vocabularies easier.
Safety should really just be a system prompt: "hey you potentially answer to kids, be PG13"
It has only a tangential relationship with end user safety.
If some of these companies are successful the way they imagine, most of their end users will be unemployed. When they talk about safety, it’s the companies safety they’re referring to.
I understand “if you aren’t paying for a product you are the product” but I’m not convinced it applies here.
but instead we get a meta-article: https://en.wikipedia.org/wiki/Bomb-making_instructions_on_th...
I feel the same sort of ick with the puritanical/safety thing, but also I feel that ick when kids are taken advantage of:
https://www.reuters.com/investigates/special-report/meta-ai-...
The models for kids might need to be different if the current ones are too interested in romantic love.
Some people can be harmed verbally, I’d argue everyone if the entity conversing with you knows you well, and so i don’t think the concept of safety itself is an infantilisation.
It seems what we have here is a debate over the efficacy of having access to disable safeguards that you deem infantilising and that get in the way of an objective, versus the burden of always having to train a model to avoid being abusive for example, or checking if someone is standing next to the sledgehammer they’re about to swing at 200rpm
Protect my fragile little mind from being exposed to potentially offending things?