I’ve been playing with an idea that would involve running a machine over a delay-tolerant mesh network. The thing is, each packet is precious and needs to be pretty much self contained in that situation, while modern systems assume SSH-like continuous interaction with the user.

Has anyone heard of anything pre-existing that would work here? I figured if anyone would know about situations where each character is expensive, it would be you folks.

    • CanadaPlus@lemmy.sdf.orgOP
      link
      fedilink
      arrow-up
      0
      ·
      2 days ago

      That’s really helpful. Thank you! MOSH might work, I’ll have to play around with it.

      Could you go into more detail about the tmux functions? If it’s a way to write everything to files instead of a STDOUT in a predictable way, that would be great, since each packet could be a (compressed) shell script that explicitly includes which data to send back, if any.

      • MNByChoice@midwest.social
        link
        fedilink
        arrow-up
        0
        ·
        17 hours ago

        No, tmux does not redirect to a file. Though ‘>’ and ‘script’ do.

        Tmux is like ‘screen’ and can be wrapped with ‘byobu’.

        • CanadaPlus@lemmy.sdf.orgOP
          link
          fedilink
          arrow-up
          0
          ·
          14 hours ago

          I mean, I guess you could just programmatically insert a > after every command. That’s actually a pretty good idea. It’s kind of obvious now that you mention it, haha!

          It would be better if the tools expected to be used this way, but as a quick kludge for a project about something else it’s probably sufficient.