81–90 of 123 posts
It uses 2 external calls to a javascript CDN for the microphone package and something else. It would probably be best if it was localhost calls only since it handles an API key
This seems to be a contradiction. Am I running it locally, or is it running on someone else's server?
So if you add audio output to it so I can talk to my computer like in Star Trek, I'll venmo you $100. Then, I want to have a command line module so I can ask it to write files to the local disk and run them, so I can deploy code it's just written to AWS, that's worth at least another $100.
Nice. 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…
Most people I know type faster than they can talk. Also more accurate. I find talking a horrible interface to a computer while sitting down. On the move it is another story entirely of course.
By the way, chatgpt is not very fast either, so usually I type something in the chat and continue working while it generates the response.
> smart glasses
I just tried that; it works quite well, however, pressing the mic button kind of messes up that experience.
This 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.
Chat-with-gpt has that, we use it in our org as an alternative chatgpt Interface: https://github.com/cogentapps/chat-with-gpt
> Run locally on browser – no need to install any applications This seems to be a contradiction. Am I running it locally, or is it running on someone else's server?