[jwarden]

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 when I was speaking (perhaps by saying "hey YakGPT"). But I see how that might be hard to implement.

Would love to hook this up to some smart glasses with a heads-up display where I could speak and read the response.

[anonzzzies]

> Most people can talk faster than they can type

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.

[chenxi9649]

Normal/average talking is ~150 WPM. Average typing speed is about 60-70. Is a 150+WPM a requirement to become anonzzies' friend?

[MikePlacid]

The only person that could type as fast as I can speak and whom I met in real life was an immigration officer taking my naturalization interview. The sound of a keyboard going: trrr-trrr! And he was amazingly accurate too: all unnecessary things that I said for conversation sake were there, and exactly as I said them. But I think my wife would beat him easily though…

[quickthrower2]

Or a really slow talker?

High WPM might be achievable with shorthand though.

[thelittleone]

The advantage of course is your not tied to a keyboard / desk. So one could potentially be doing Internet research while hiking.

[tluyben2]

Yes, and that with smart glasses seems interesting.

[xupybd]

It wasn't so smooth for me.

I gave up at

Creating an optimized production build ...TypeError: Cannot read properties of null (reading 'useRef')

[johnchristopher]

Oh, my install failed at:

    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)

[kami8845]

Haha, I'll set up a docker image that people can pull down!

[johnchristopher]

Thanks but FWIW, I'd also be interested in why it doesn't build. Shouldn't yarn/npm/gulp/whatever manage dependencies ?

[xupybd]

I've not found a dependency manager that works reliably across multiple operating systems and operating system versions.

[uh_uh]

I did, just not in the JavaScript ecosystem.