Thread

Ollaya – Ollama for open-source, Jev-style decision models

618 points · 145 comments · Ardakilic

solaire_oa · 1790372935 · focus · HN ↗
I installed it, I tried the examples, it works.... But forgive my lack of imagination... what is this useful for?
Like, their example is of classification for a support interface.... `refund_requested`. Pretty convenient bool given the example is about a refund- what if 99% of submissions don't ask about a refund? Also, is that user not a `churn_risk`? What could possibly qualify as a churn risk if not a user asking for a refund?
<a href="https://ollaya.dev/library/laya" rel="nofollow">https://ollaya.dev/library/laya The examples suffer the same problem of why I'd prefer to use a string column vs an enum. Changing an enum means you need to update the db, using a string you can do whatever.
I'm not trying to be negative, I genuinely want to know about some practical examples (that don't require tons of backwards maintenance).
1. devttyeu · 1790374164 · focus · HN ↗
  I have a lot of semi-practical examples of how you can use this model wrapped in unix-ish tools - <a href="https://github.com/aurorainfra/grev" rel="nofollow">https://github.com/aurorainfra/grev (readme links to docs of each tool with some more or less practical examples)
  Really I think "smart grep" is a pretty good one ('look for an error looking vaguely like this'). Also I think sql-based shell history + decision model is quite good to make the last 'which one of those choices is best fit given users past few commands' etc.
  1. solaire_oa · 1790374913 · focus · HN ↗
    Ok, those are pretty decent examples, and clears up the utility a bit: speed and tokens. Some of it's still a bit iffy (e.g. `cutv 'email address' 'phone number' < examples/users.csv`, csv is already in columns), but I can see using it for some niche queries. Neat tool.
    I very much appreciate your to-the-point, non-vibed README as well, ty for that.
    solaire_oa · 1790375727 · focus · HN ↗
    I still think that `churn_risk` above is incorrect and unacceptable (perhaps there are sensible fixes, but saying "no churn risk" about a refund, in a leading example on their homepage, flabbergasting).
    But if that were solved, I could see giving ollaya/grev to LLMs themselves, giving LLMs their own massive token-saver.
    cobanov · 1790411075 · focus · HN ↗
    [dead]

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.