‹ BackHN Continuity

Thread

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

618 points · 145 comments · Ardakilic

  1. solaire_oa · · 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:&#x2F;&#x2F;ollaya.dev&#x2F;library&#x2F;laya" rel="nofollow">https:&#x2F;&#x2F;ollaya.dev&#x2F;library&#x2F;laya The examples suffer the same problem of why I&#x27;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&#x27;m not trying to be negative, I genuinely want to know about some practical examples (that don&#x27;t require tons of backwards maintenance).

    1. colordrops · · focus · HN ↗
      If you don&#x27;t want to spend a lot and want low latency, e.g. home automation. &quot;It&#x27;s cold and dark in here, do something about it&quot;, it will then turn on the lights and heater nearly instantly.
      1. maskedpirate · · focus · HN ↗
        sounds reasonable but doesn’t feel natural in a way that I can’t explain easily
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.