|
|
|
|
|
by Vermeulen
1771 days ago
|
|
It's laggy since it needs to do speech to text, gpt3 text response, then text to speech. Not sure what adds the most latency actually. They only allow gpt3 chatbots if the chatbot is designed to speak only about a specific subject, and literally never says anything bad/negative (and we have to keep logs to make sure this is the case). Which is insane.
Their reasoning to me was literally a 'what if' the chatbot "advised on who to vote for in the election". As if a chatbot in the context of a video game saying who to vote for was somehow dangerous I understand the need to keep GPT3 private. There is a lot of possibility for deception using it. But they are so scared of their chatbot saying a bad thing and the PR around that they've removed the possibility of doing anything useful with it. They need to take context more into account - a clearly labeled chatbot in a video game is different than a Twitter bot |
|
It's not unreasonable to have checks-and-balances on AI content, and there should be.
However, in my testing of GPT-3's content filter when it was released (it could be improved now), it was very sensitive to the point that it had tons of false positives. Given that passing content filter checks is required for productionizing a GPT-3 app, it makes using the API too risky to use, and part of the reason I'm researching more with train-your-own GPT models.