Shackles
Joined 3 years ago
Karma
36
Submissions
8
Member since
Mar 27
Recent submissions
Comment · 3 years ago
Got it, it's a bug and happens because of the token calculation. We'll fix it. Thanks for reporting.
Comment · 3 years ago
You're right. Fixed wording in our README on Github, can't edit HN post. Thanks
Comment · 3 years ago
Okay, this shouldn't happen. Please create a GitHub issue, I'll investigate.
Comment · 3 years ago
It's a userfriendly web client for the latest OpenAI chatCompletion API with additional features compared to the official chat.openai.com client (mainly: "Share chats" & better param customization), it's Open Source and can be run locally or self-hosted easily. It's built in one of the most popular frontend tech stacks of the last years. Not more and not less than that.
Comment · 3 years ago
SlickGPT passes message history including a "context" or "system" message which it clearly explains to the user at the start of every chat. This is probably the most important thing the official chat.openai.com client fails to explain or expose to users directly.
Comment · 3 years ago
Do you mean if you type something or if you retrieve the answer/completion from ChatGPT? Which model are you using?
Comment · 3 years ago
I get that fear and it's fair. SlickGPT is OS, self-hostable and just runs locally, so you can check the code and run your own instance if you don't trust that ours running on Vercel is on-par with the one in the repo. You can also put a soft and hard cap on your API quota on the OpenAI page and monitor it to verify that only you are using it.
The key is passed (see https://github.com/ShipBit/slickgpt/blob/main/src/lib/ChatIn...) to a Vercel edge function (see https://github.com/ShipBit/slickgpt/blob/main/src/routes/api...) that does the actual call to the OpenAI API. This function is stateless and doesn't store anything. I also put it in your localStorage using a store (see https://github.com/ShipBit/slickgpt/blob/main/src/misc/store...) so that you don't have to enter it over and over again.
As for the "what is this trying to solve" - read our documentation in the GitHub repo over at https://github.com/ShipBit/slickgpt.