Probably only if this implements a similar roaming concept as mosh by using a nonce or something along that line vs. ssh session keys that are mapped to an IP. Mosh was designed by MIT folks not just for high latency but also mobile networks which can change IP and lose connectivity frequently. Perhaps the code author is here on HN?

It doesn't have to be this piece of software implementing MP-UDP for roaming to work though. Nevertheless I doubt it has such functionality right now.

Mosh was designed for a great number of things, including what you mentioned.

To me, mosh is "careful and impressively pedantically correct UTF-8 terminal emulator" + "careful and impressively pedantically correct state synchronization protocol". :)

Mosh has latency-hiding mechanisms. I used mosh for a bit on while riding a bus. Latency-hiding helped quite a bit to keep the UI responsive.

Do you mean UI as in X forwarding? I thought this wasn't possible, which kept me from using mosh so far.

They mean UI as in for command lines, like vim/emacs/shells

TUI, better?

UI is just plain ol' things for user to interact with computer.

The "G" in "GUI" stands for "graphical". Some people use "TUI" to mean "Terminal User Interface". It therefore follows that someone using merely "UI" has not specified the type of interface.

Mosh is closer to tmux than to ssh.

Any similarity with tmux is purely because it's connectionless. It's mostly certainly more like ssh than it is like tmux. Both are remote shell protocols, while tmux is simply a terminal multiplexer.

Mosh is a terminal emulator itself and sends the diff of the output from the server to the client. Ssh just passed the terminal data through. I think that is why mosh is like tmux, because tmux is also a terminal emulator.

Mosh is not at all like ssh, tries hard to avoid duplicating ssh functionality, and this is by design.

If it were like ssh the authors would have had to then handle security/authentication and all that jazz perfectly. It was written to "stand on the shoulders" of ssh, except handle terminal emulation and UTF-8 correctly. By using ssh, you don't have to trust "some new thing" as long as you trust ssh.

It's not even a shell protocol if you think about it!

Mosh bidirectionally synchronizes the state between the terminal window on the client and the virtual terminal on the server. It runs at a frame rate, which results in not filling intermediate network queues, which is where the low latency comes from. :)

> It's not even a shell protocol if you think about it!

Nor is SSH. Feel free to take a read over the RFCs. There's next to no 'sh' in SSH as a protocol. What mosh adds to SSH is the ability to securely resume a session. SSH is fundamentally protocol for setting up a secure connection and then ping-pong messages back and forth.

tmux runs locally. It's not a network daemon. The complexion of a daemon and protocol meant to operate over a network is very, very different from one intended to run over Unix domain sockets or on the loopback interface.