Show HN: Open Message Format – a compact, vendor-agnostic spec for messages

Re:Show HN: Open Message Format – a compact, vendor-agnostic... by ianbicking on Monday September 09, 2024 @09:22PM (#41496240)

Huh, that's a different use case than I was imagining. I actually don't know why I'd want a standard API from a frontend and backend that I control.

In most applications where I make something chat-like (honestly a minority of my LLM use) I have application-specific data in the chat, and then I turn that into an LLM request only immediately before sending a completion request, using application-specific code.

[ Parent | on HN ]

Re:Show HN: Open Message Format – a compact, vendor-agnostic... by sparacha on Tuesday September 10, 2024 @12:55AM (#41497275)

Well, in the case of the front-end (like streamlit, gradio, etc) they send conversational messages in their own custom ways - this means I must develop against them each specifically, and that slows down any quick experimentation I would want to do as a developer. This is the client <> server interaction.

And then the conversational messages sent to the LLM are also somewhat unique to each provider. One improvement for simplicity purposes could be that we get a standard /chat/completions API for server <> LLM interaction and define a standard "messages" object in that API (vs the stand-alone messages object as defined in the OMF").

Perhaps that might be simpler, and easier to understand

[ Parent | on HN ]