Hacker News new | ask | show | jobs
by zitterbewegung 1582 days ago
If you put your OpenAI key and start running this then they will ban your account because it will be against their TOS.

With some minor modifications you could port it to goose.ai and it isn’t against their TOS.

EDIT: Forking it here https://github.com/zitterbewegung/Goopt to add the functionality above.

3 comments

OpenAI engineer here. Cloning this project and running it locally with your own API key does not violate any policies. However the way this project is configured, publishing it to the web would expose your API key in the client-side source code, which violates our policies since it would allow your account to be compromised.
Sorry I should have read the TOS
I think that as long as you don't put a live version (where you don't require your own API Key) and you don't misuse the results, there shouldn't be a problem.

Even so, it is a good idea to adjust, I'll keep an eye on your fork. Thanks!

It’s fine for not being live but switching over to goose.ai allows you to make it live I have a home server I could host it on .
I would like to put it live, although it would be necessary to review the terms to launch it live.

If you can make any adjustments that respect the terms, contact me to see it together.

I also have GPUs that are mine so that will definitely have any TOS at all but I would have to mirror the OpenAI API.
Also, for GPT-3 an advanced query would be helpful maybe to give it examples.
hey, you beat me to it :D did you manage to get it to work? I tried on my own but got error messages
I’m getting error messages I think it’s an issue where the endpoint is in a configuration where it is using the old openai value I think I have to recompile it with typescript or something .
I made it work but GPT-J doesn't respond in the same manner to the template prompts for search. Goopt cannot use and display GPT output from there as a search result.
You might have to enable billing, that was the issue for me
No it’s a config error.
What did you change ?
I set the base and engine in openai-api for goose.ai completions return fine, I'm seeing them fine in the log. However they are unusable to make Goopt work. The end of search prompts mock JSON format.

I get this \"content\": [{\"name\": \"Keto Diet\", \n \"typeClass\": {}, \n \"description\":[],\n \"contentImageUri\": null }]}

GPT-J doesn't seem to compose similar broken JSON so formatResults returns empty.

Maybe giving more examples can give a better result, for the case of GPT-3 I kept it to a few examples because of the cost of the amount of tokens.

Another option is to improve formatResults to fix more cases of invalid JSON responses. If you get any improvement a pull request is welcome.

With GPT-J, search prompt works better if you don't try to get a JSON response. I don't know why but when you ask for technical formats/outputs, GPT-J heavily focuses on composing a technical document/code for you. It tends to start composing Javascript etc.

I'll come up with a pull request.