3 ms·
Looks great! Very excited to try this out. At first glance I have one concern and one suggestion: Concern: you mention it supports the actual ChatGPT Web API -
by iamjackg 3y ago
Looks great! Very excited to try this out. At first glance I have one concern and one suggestion:
Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs.
Suggestion: I would rename what you call the "ChatGPT" (non-web) part of the backend to "OpenAI API" instead. There is already enough confusion in the world between ChatGPT and API access to the underlying GPT models.
- capableweb 3y ago> Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs. There seems to be two extensions, one called "chatgpt" and one called "chatgpt-web" (https://github.com/chieapp/chie/tree/main/src/extensions https://github.com/chieapp/chie/tree/main/src/extensions). The latter seems to be using https://chat.openai.com/backend-api/conversation https://chat.openai.com/backend-api/conversation which is OpenAI's private API for ChatGPT. Using this (as a user) seems to be able to get you banned, as far as I can tell by some reddit posts as of late. However, the extension called "chatgpt" seems to correctly use the right endpoint: https://api.openai.com/v1/chat/completions https://api.openai.com/v1/chat/completions, but it's not ChatGPT anymore when you use it, so the naming is a bit confusing as you said.
- buu700 3y agoI haven't read the terms of service, but would headless browser automation be a safer solution?
- capableweb 3y agoThe only thing that would keep you safe, if OpenAI bans people accessing the API outside of their client-side application, is if you make those requests from a different IP than what you normally use ChatGPT from.