←back to thread

SSH3: Faster and rich secure shell using HTTP/3

(github.com)
532 points tempaccount420 | 2 comments | 27 Sep 25 14:27 UTC | HN request time: 0s | source
Show context
ricardobeat ◴[27 Sep 25 19:20 UTC] No.45398629[source]▶
> the keystroke latency during a session remains unchanged

That’s a shame. Lowered latency (and persistent sessions, so you don’t pay the connection cost each time) are the best things about Mosh (https://mosh.org/).

replies(1): >>45398642 #
nine_k ◴[27 Sep 25 19:22 UTC] No.45398642[source]▶
Lowered perceived latency.
replies(1): >>45400095 #
ricardobeat ◴[27 Sep 25 23:04 UTC] No.45400095[source]▶
Mosh uses UDP in addition to optimistic updates, so there is an actual latency improvement.
replies(1): >>45400907 #
1. nine_k ◴[28 Sep 25 01:15 UTC] No.45400907[source]▶
HTTP/3 also rides on UDP, so the effect should be comparable.
replies(1): >>45402947 #
2. ricardobeat ◴[28 Sep 25 09:19 UTC] No.45402947[source]▶
> SSH3 only needs 3 round-trip times. The keystroke latency in a running session is unchanged.

If implemented with latency in mind, yes. After a quick look at the code, it seems they are buffering data on both sides with hardcoded buffer sizes at 1500 (TCP packet size) or 30Kb, which could be negating any latency improvements.