Maybe they can fix it with a prompt that makes the model check if the ingredients are safe. Chances are that every prompt can be circumvented but they can probably find instructions for self poisoning somewhere else with less effort.
Maybe they can fix it with a prompt that makes the model check if the ingredients are safe. Chances are that every prompt can be circumvented but they can probably find instructions for self poisoning somewhere else with less effort.
It's used here in Argentina to make pumpkin "sweets". (I'm not sure the correct translation.) It's a lot of 1 inch cubes of pumpkin, boiled for some time in sugar syrup. [1] Without treatment the cubes will disintegrate while boiling. If you put them for one day in water with quicklime, the cubes get a hard wall and they keep their integrity while boiling, but the interior is soft.
Drinking the water with the quicklime is dangerous and it's discarded. Eating directly the quicklime is even worse. But quicklime is useful for cooking.
[1] Some random recipe I got in Google (autotranlation) https://cookpad-com.translate.goog/ar/recetas/94999-zapallo-... (spanish) https://cookpad.com/ar/recetas/94999-zapallo-en-almibar
A teaspoon of quicklime in your mouth first reacts with water to produce a lot of heat that will burn you, and then the result is very basic (anti-acid), and make new burns in a different way. Definitively don't try it at home.
Just sanitize the input and remove products belonging to categories that aren't edible.
Tampons aren't great in salads, and toilet paper is not a good garnish.
That seems like a job for a database, not a language model. Every problem is not a nail.
TBH, there's often a huge chasm between product planning and real world users at companies and organizations like this.