zlacker

[parent] [thread] 6 comments
1. killer+(OP)[view] [source] 2025-05-06 15:51:39
Why can't they just use version numbers instead of this "new preview" stuff?

E.g. call it Gemini Pro 2.5.1.

replies(2): >>lukesc+O4 >>mhh__+0b
2. lukesc+O4[view] [source] 2025-05-06 16:14:16
>>killer+(OP)
I take preview to mean the model may be retired on an accelerated timescale and replaced with a "real" model so it's dangerous to put into prod unless you are paying attention.
replies(2): >>lolind+Sf >>danena+Aj
3. mhh__+0b[view] [source] 2025-05-06 16:52:16
>>killer+(OP)
Are you saying you find model names like o4-mini-high-pro-experimental-version5 confusing and stupid?
◧◩
4. lolind+Sf[view] [source] [discussion] 2025-05-06 17:19:31
>>lukesc+O4
They could still use version numbers for that. 2.5.1-preview becomes 2.5.1 when stable.
◧◩
5. danena+Aj[view] [source] [discussion] 2025-05-06 17:42:03
>>lukesc+O4
Scheduled tasks in ChatGPT are useful for keeping track of these kinds of things. You can have it check daily whether there's a change in status, price, etc. for a particular model (or set of models).
replies(1): >>cdolan+fu
◧◩◪
6. cdolan+fu[view] [source] [discussion] 2025-05-06 18:48:34
>>danena+Aj
I appriciate that you are trying to help

But I do not want to have to build a network of bots with non-deterministic outputs to simply stay on top of versions

replies(1): >>danena+nv
◧◩◪◨
7. danena+nv[view] [source] [discussion] 2025-05-06 18:54:25
>>cdolan+fu
Neither do I, but it's the best solution I've found so far. It beats checking models/prices manually every day to see if anything has changed, and it works well enough in practice.

But yeah, some kind of deterministic way to get alerts would be better.

[go to top]