Live data from Hacker News

Introducing ChatGPT and Whisper APIs

openai.com

71–80 of 696 posts

Re: Introducing ChatGPT and Whisper APIs

#71
post #54

Earlier quoted context omitted.

You have to rebuild all your prompts when switching providers.

Do you? They're natural language, right?

You don't have to, but they will have been optimized for one model. It's unlikely they'll work as well on a different model.

Re: Introducing ChatGPT and Whisper APIs

#72

Earlier quoted context omitted.

This is actually a big deal. They erred on the side of caution, but as a result the responses are nerfed beyond basic "censorship" level. I saw someone describe this as "desperately posistive" and it really resonated with me. It produces underwhelming / unrealistic responses in negative scenarios.

It's just a matter of time before open source models show up with no limits whatsoever.

Hopefully so, would really like to know what else is lost by nerfing potentially offensive responses. Can't imagine a project I'd rather work on.

I think open-assistant.io has a chance to do exactly this. We'll see what kind of moves they make in coming months though, wouldn't be surprised if they go the safer route.

Re: Introducing ChatGPT and Whisper APIs

#74

Earlier quoted context omitted.

Is there though? It's just a matter of swapping out $BASE_API_URL.

You have to rebuild all your prompts when switching providers.

If the superlative LLM can’t handle prompts from another provider, it just isn’t the superlative LLM.

This area by definition has no moats. English is not proprietary.

Use case is everything.

Re: Introducing ChatGPT and Whisper APIs

#75

> It is priced at $0.002 per 1k tokens, which is 10x cheaper than our existing GPT-3.5 models. This is a massive, massive deal. For context, the reason GPT-3 apps took off over the past few months before ChatGPT went viral is because a) text-davinci-003 was released and was a significant performance increase and b) the cost was cut from $0.06/1k tokens to $0.02/1k tokens, which made consumer applications feasible wit…

How do these compare to the recent Default ("turbo") vs legacy" (for plus/pro) modes? If "turbo" is "gpt-3.5-turbo", how to access the (better?) "legacy" by API?

Probably bait and switch. They call both ChatGPT, so now people believe they will get the better old ChatGPT, but they get the new cheap and worse ChatGPT "Turbo" that they switched to recently. Fewer will realize if they no longer give you the option to use the legacy version in this API.

Re: Introducing ChatGPT and Whisper APIs

#76

Earlier quoted context omitted.

This. Despite how impressive the results are, there isn't a particular large moat to prevent competitors from entering the space. Basically just compute $ for training.

they likely do lots of tricks and data collection inside which makes quality better.

exactly. this isn't a leetcode problem where all you have to do is re-run the function, or do it iteratively vs recursively.

Re: Introducing ChatGPT and Whisper APIs

#79

Whisper as an API is great, but having to send the whole payload upfront is a bummer. Most use cases I can build for would want streaming support. Like establish a WebRTC connection and stream audio to OpenAI and get back a live transcription until the audio channel closes.

It's also annoying since there appears to be a hard limit of 25 MiB to the request size, requiring you to split up larger files and manage the "prompt" to subsequent calls. Well, somehow, near as I can tell, how you're expected to use that value isn't documented.

You split up the audio and send it over in a loop. Pass in the transcript of the last call as the prompt for the next one. See item 2 here: https://platform.openai.com/docs/guides/speech-to-text/promp...
Post reply on HN