5 ms·
Is it just me or is this the least intuitive format imaginable? The type def is something like: type Message = string type Speaker = 'system' | 'user'
by explaininjs 4y ago
Is it just me or is this the least intuitive format imaginable? The type def is something like:
type Message = string
type Speaker = 'system' | 'user' | 'assistant' | 'system name=example_user' | 'system name=example_assistant'
type CML = ('\n' | '${Speaker}\n${Message}' | {token: '<im_start>'|'<im_end>'})[]
I'd expect something more like...
type Message = string
type Speaker = 'system' | 'user' | 'assistant' | 'example_user' | 'example_assistant'
type CML = {message: Message, speaker: Speaker}[]
- gdb 4y agoWill all make more sense with upcoming releases, we have a lot of extensions in the works :).
- mwint 4y agoSomehow, seeing OpenAI employees adding smilies just makes the sense of impending doom even stronger
- EGreg 4y ago:-P
- yieldcrv 4y agoBecause they're being a good user, for their good Bing.
- warent 4y agoThey are a good OpenAI employee :) You are a bad user
- pokoleo 4y agoIt's a nice way to say "Hello there :)"
- monkeydust 4y agoI am trying to work out the odds of the OpenAI employee not being human.
- ralusek 4y agoJust say you think it's human. Saying you think it's not makes them add 50 million parameters, each time.
- alexwebb2 4y agoWhen this is extended to have multiple system roles as designated agents, with mechanisms for the assistant to ping a specific agent for more information or completion of a subtask so devs can route that to secondary AIs or services, that’s going to be a very big deal. Is that what you’re building toward here?