News for hackers. Stuff that matters.
Re:SSH uses four TCP segments for each character you type by robinson-wall on Thursday May 30, 2013 @10:29AM (#5792700)
Are you thinking of Mosh? http://mosh.mit.edu/
Re:SSH uses four TCP segments for each character you type by markild on Thursday May 30, 2013 @10:41AM (#5792786)
I have used Mosh as my primary remote access client for a few months on my "on-the-go" laptop, and I must say that the user experience is very good.

In a lot of scenarios, the latency is not much of an issue, but on wlan/3g, this very fast become very noticeable. In the few cases since, I've used ssh on wireless, I suddenly find myself noticing how much of an issue the sudden feedback delay might be at some times.

Re:SSH uses four TCP segments for each character you type by eridius on Thursday May 30, 2013 @02:25PM (#5794230)
Not only is mosh great for latency, but it's also great for laptops because of IP roaming. These days I have a dedicated Terminal window with a permanent Mosh session to my Linode. The Mosh session never shuts down (unless I'm rebooting), no matter how often I put my laptop to sleep, or go between home and work.
Re:SSH uses four TCP segments for each character you type by markild on Friday May 31, 2013 @06:08AM (#5797677)
Indeed.

The only obvious downside to Mosh I've seen so far, is that a lot of enterprisy firewalls tend to block UDP traffic.

Re:SSH uses four TCP segments for each character you type by simias on Thursday May 30, 2013 @10:33AM (#5792727)
That's the one, and after watching the video again it's actually more clever than my "local echo" description even though it's part of it.