Show HN: YakGPT – A locally running, hands-free ChatGPT UI
51–60 of 123 posts
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#52Make it easier to try
Before you comment something like this, ask yourself "How would I make this easier to try?" The only reasonable answer is providing the OP's own API key, which is undesirable.
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#53It's pretty bad to ask people to enter e private secret key in a web site (any, I mean)
Why? OpenAI keys can be revoked at any time, and OpenAI allows you to set soft and hard limits for billing as well. You can also generate multiple keys, so if one app misbehaves, you don't need to rotate all the keys, just the one that misbehaves. This is assuming the API keys can only do generation. If it can access billing details or something it's very different of course.
Because it's bad practice to provide sensitive information to untrusted sources, and if you are an ethical developer, it's an anti-pattern to write software that encourages bad practices.
Your credit card company will reverse any authorized charges. Will you email me all your credit card info?
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#54One feature I am missing from all these front ends is the ability to edit your text and generate new response from that point. Official chat gpt UI is the only one that seems to do that.
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#55Earlier quoted context omitted.
Why? OpenAI keys can be revoked at any time, and OpenAI allows you to set soft and hard limits for billing as well. You can also generate multiple keys, so if one app misbehaves, you don't need to rotate all the keys, just the one that misbehaves. This is assuming the API keys can only do generation. If it can access billing details or something it's very different of course.
> Why? Because it's bad practice to provide sensitive information to untrusted sources, and if you are an ethical developer, it's an anti-pattern to write software that encourages bad practices. Your credit card company will reverse any authorized charges. Will you email me all your credit card info?
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#56Nice. It took about a minute to clone it, run it, enter my API key, and get started. The speech-to-text worked flawlessly. Most people can talk faster than they can type, but they can read faster than other people can talk. So an interface where I speak but read the response is an ideal way of interfacing with ChatGPT. What would be nice is if I didn't have to press the mic button to speak -- if it could just tell wh…
I gave up at
Creating an optimized production build ...TypeError: Cannot read properties of null (reading 'useRef')
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#57I love the concept of this and other alternate ChatGPT UIs, but I hesitate to use them and pay for my calls when I could use chat.openai.com for free. Any chance you could integrate the backend-api, and let me paste in my Bearer token from there?
You can try the extension I built [0] which uses your existing ChatGPT session to send requests. [0] https://sublimegpt.com
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#58Interesting note: I tried speaking mandrain chinese to the mic and it auto translated what I said into English.
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#59This is fast. And talking to it is a nice touch. Consider adding text to speech too :) One feature I am missing from all these front ends is the ability to edit your text and generate new response from that point. Official chat gpt UI is the only one that seems to do that.
Re: Show HN: YakGPT – A locally running, hands-free ChatGPT UI
#60Nice. It took about a minute to clone it, run it, enter my API key, and get started. The speech-to-text worked flawlessly. Most people can talk faster than they can type, but they can read faster than other people can talk. So an interface where I speak but read the response is an ideal way of interfacing with ChatGPT. What would be nice is if I didn't have to press the mic button to speak -- if it could just tell wh…
It wasn't so smooth for me. I gave up at Creating an optimized production build ...TypeError: Cannot read properties of null (reading 'useRef')
Failed to compile.
pages/index.tsx
`next/font` error:
Failed to fetch `Inter` from Google Fonts.
> Build failed because of webpack errors
Apparently because it can't fetch a font from Google. There should be assets that are critical (js/ts code, templates,css) and assets that are not (freaking fonts) to a yarn build.edit: hacketyfixey, let's punch the thing in the face until it works:
./pages/index.tsx:
2: // import { Inter } from "next/font/google";
12: // const inter = Inter({ subsets: ["latin"] });
(I am sorry)