[HN Gopher] Show HN: Chie - a cross-platform, native, and extens...
___________________________________________________________________
Show HN: Chie - a cross-platform, native, and extensible desktop
client for LLMs
I'm submitting this before going to bed, so by the time it hits
front page (if it does at all) I'll likely be asleep, so I won't be
able to answer questions in time.
Author : zcbenz
Score : 48 points
Date : 2023-07-28 13:26 UTC (9 hours ago)
(HTM) web link (chie.app)
(TXT) w3m dump (chie.app)
| hedgehog wrote:
| I tried it and got the error "You exceeded your current quota,
| please check your plan and billing details."
| stavros wrote:
| This looks nice! It says it's not an Electron app, but GitHub
| says it's written in TypeScript, so what UI toolkit does it use?
|
| EDIT: Never mind this is mentioned in the technical details link,
| thanks!
| ricklamers wrote:
| The UI toolkit it uses is Yue which I hadn't heard of:
| https://libyue.com/docs/latest/js/
| iFire wrote:
| GPL3 License https://github.com/chieapp/chie/blob/main/LICENSE
| homarp wrote:
| Chie is currently licensed under the GPLv3, it will be
| relicensed to the MIT license on March 20th, 2028 (5 years
| after the first commit). I take this approach to discourage
| closed-source software from taking advantage of my work before
| it gets enough impacts.
|
| Due to the future relicense, contributors will be asked to sign
| an agreement.
|
| https://github.com/chieapp/chie#license
| broast wrote:
| I like how it's now a feature to not be an electron or webview
| app.
| iamjackg wrote:
| 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 wrote:
| > 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). The
| latter seems to be using 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,
| but it's not ChatGPT anymore when you use it, so the naming is
| a bit confusing as you said.
| buu700 wrote:
| I haven't read the terms of service, but would headless
| browser automation be a safer solution?
| capableweb wrote:
| The 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.
| steeve wrote:
| I advise you not to look up what it means in french.
| cbenz wrote:
| Sorry, too late, I'm french.
| qwerty456127 wrote:
| Hi. This is the first time I'm trying an external app. I created
| an ChatGPT API key and configured it in Chie.
|
| Once I tried asking ChatGPT it immediately replied "You exceeded
| your current quota, please check your plan and billing details"
| which I can't believe is the case.
|
| I then tried to press the copy button over this reply to paste it
| here but that raises an error: "TypeError: Cannot read properties
| of undefined (reading 'content') at #copyTextAt
| (chieapp.exe\asar\dist\view\chat-view.js:1:11362).
| nickthegreek wrote:
| Your 'future plan' section says you want provide a subscription
| plan for gpt-4. Why would I pay a subscription to access my other
| subscription, especially when its a feature you currently offer
| for free. I feel like a one time fee to unlock access to premium
| models could be a better option. You will need to differentiate
| from your main free competition, chatboxai, to get a meaningful
| userbase like you have stated you want.
| pjmlp wrote:
| Kudos for taking the effort of not being yet another Electron
| app.
| hruzgar wrote:
| [dead]
___________________________________________________________________
(page generated 2023-07-28 23:02 UTC)