-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add OpenAI moderation #81
Comments
Is our org key something we need to keep private? |
I don't think it's as secret like the API key since member in the org can see it (you're a member of the org too) but just to be safe, I'd avoid posting it publicly. I've DMed you the value just in case you need it. |
From the email (below), it looks like BEFORE we make any calls to
|
I did a some testing, and it doesn't seem like feeding the whole prompt is always enough to identify issues (the query can get drowned out in sources), so I'm checking on both the entire prompt and just the query. Seems this way will always catch it. If moderation seems overly strict going forwards (easy to imagine on topics of politics, etc) we can be more selective than just checking |
That sounds like a good plan. I think we need to catch both whether the query is problematic and also the context blocks too. Hopefully, there's not a huge lag. Politics doesn't seem to a category specified in moderation api but yes, we should log and keep an eye out for the type of things get flagged. Given the circumstance, probably better to start off strict and slow relax as needed. |
There's been some potential misuse of the Stampy API key which puts our account at risk of being banned. It's unclear if the abuse was from stampy-chat or elsewhere. A few steps:
Should also set openai.organization so bill for devs using personal keys are charged accordingly.
The text was updated successfully, but these errors were encountered: