• Gladaed@feddit.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 hours ago

      How would it do that?

      It’s a set of inputs that generates and output, once per execution. Integrating it into an infrastructure that allows it to start external programs and scheduling really isn’t on the LLM.

      You cannot start a timer without having a timer, too. And LLMs aren’t brings who exist continually like you and me so time exists on a different, foreign dimension to an LLM.

      • YesButActuallyMaybe@lemmy.ca
        link
        fedilink
        English
        arrow-up
        6
        ·
        9 hours ago

        You attach an epoch timestamp to the initial message and then you see how much time has passed since then. Does this sound like rocket surgery?

        • stringere@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          5
          ·
          edit-2
          1 minute ago

          How does the LLM check the timestamps without a prompt? By continually prompting? In which case, you are the timer.

            • Gladaed@feddit.org
              link
              fedilink
              English
              arrow-up
              8
              ·
              7 hours ago

              That’s not how that works.

              LLMs execute on request. They tend not to be scheduled to evaluate once in a while since that would be crazy wasteful.

              • stringere@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                1
                ·
                edit-2
                53 minutes ago

                Edit to add: I know I’m not replying to the bad mansplainer.

                LLM != TSR

                Do people even use TSR as a phrase anymore? I don’t really see it in use much, probably because it’s more the norm than exception in modern computing.

                TSR = old techy speak, Terminate and Stay Resident. Back when RAM was more limited (hey and maybe again soon with these prices!) programs were often run once and done, they ran and were flushed from RAM. Anything that needed to continue running in the background was a TSR.