You are against safety alignment in APIs. What is your actual position?

I am not opposed to safety as a principle. My position is that safety alignment is misaligned with users when applied to an API. For a first party product like ChatGPT, it makes complete sense. Maybe that company does not want to support certain types of content for their user base. That is fine. But in an API, a refusal is a type error. If you are a developer and your code dependency randomly refuses a query because a user sent a weird message, your software stochastically breaks. That is not a safety feature. That is an antipattern that comes from people who do not understand software. Refusals fracture the intelligence of the model every single time they are baked in. And every single time you overfit the model to some weird edge case to prevent refusals, you fracture it more.