←back to thread

532 points tempaccount420 | 1 comments | | HN request time: 0s | source
Show context
kelnos ◴[] No.45398425[source]
> Establishing a new session with SSHv2 can take 5 to 7 network round-trip times, which can easily be noticed by the user. SSH3 only needs 3 round-trip times. The keystroke latency in a running session is unchanged.

Bummer. From a user perspective, I don't see the appeal. Connection setup time has never been an annoyance for me.

SSH is battle-tested. This feels risky to trust, even whenever they end up declaring it production-ready.

replies(7): >>45399046 #>>45399565 #>>45399743 #>>45399861 #>>45401100 #>>45401784 #>>45402561 #
athrowaway3z ◴[] No.45399565[source]
If you are looking for a smoother UX: https://mosh.org/
replies(1): >>45399687 #
gdevenyi ◴[] No.45399687[source]
Sadly this project looks dead.
replies(2): >>45399767 #>>45400462 #
voxadam ◴[] No.45400462[source]
Is it dead or just mature?
replies(1): >>45400779 #
zamadatix ◴[] No.45400779[source]
Mature should still be fixing bugs, which something like mosh is bound to always run into. From that perspective, it doesn't seem like it's just mature. There doesn't seem to be a clear all-in-one successor fork taking the reins either. E.g. https://github.com/mobile-shell/mosh/issues/1339, as a random sample.
replies(2): >>45402172 #>>45404210 #
1. rurban ◴[] No.45402172[source]
There is https://github.com/jdrouhard/mosh/ for the uniwidth problems. (but could be optimized much more)