I actually have a production use-case that GPT3 solves: a nsfw filter for chat messages. Although there are open-source filters out there for Nodejs, all the on

I actually have a production use-case that GPT3 solves: a nsfw filter for chat messages. Although there are open-source filters out there for Nodejs, all the ones I tested fail in various ways. For example, famous emoji combos that indicate sexual activity and semantically sexual text that seem inoffensive enough based on the words. For example, “I bet you have the tastiest hot pocket”. Unless the chat is about cheap grocery food, it is probably a sexual reference. I’m assuming there are existing solutions: paid services or Python libraries undoubtably. But it is a lot easier for me to take 10 minutes of my time to put together a prompt and add the API endpoint to my Nodejs app. As far as cost goes, our needs are low-volume so it doesn’t really matter. I see GPT3s great utility here as a replacement for Mechanic Turk type tasks. MT is a real headache to setup and manage programmatically. GPT3 is pretty simple once you integrate it into your system. And the fascinating thing is that whole new realms of functionality are opened up to product ideation. I haven’t tried to do anything beyond low-volume tasks that are Mechanical Turkable, but with GPT4 I think we’ll see cost and performance drop to the point where these things can be done at scale. At that point, software engineers would be foolish not take make GPT4 just another standard library they have at their disposal — kind of like how jQuery opened up web development by providing a generic interface to DOM manipulation across all browsers. It is just as hard for us to imagine what kind of development GPT4 will enable as it was for people to imagine an internet of web-apps before jQuery. But it certainly will.