<div dir="ltr">Frederick:<div><br></div><div>Thanks for your kind words about Mosh. For instant predictions (that might be wrong and get corrected by the server), please try the --predict=experimental option to mosh.</div><div><br></div><div>You can measure the latency with our term-save tool: <a href="https://github.com/keithw/stm-data/" target="_blank">https://github.com/keithw/stm-data/</a></div><div><br></div><div>Best regards,</div><div>Keith</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 24, 2015 at 12:13 AM, Frederik Eaton <span dir="ltr"><<a href="mailto:frederik@ofb.net" target="_blank">frederik@ofb.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Mosh Developers,<br>
<br>
Thank you for a great product. I have thought about the need for<br>
something like this for years, and was happy when I discovered 'mosh'<br>
(a bit late I know).<br>
<br>
Your mailing list is not indexed by Google, but I downloaded the<br>
archives and found there seems to be no mention of 'carpal tunnel<br>
syndrome' or 'tendonitis'. I wanted to say that the reason I think a<br>
product like mosh is so valuable, is that according to my own self<br>
observation, typing over high-latency connections causes tendonitis. I<br>
wonder that no one else has made this connection, perhaps it is my own<br>
imagination. (I guess the hypothetical mechanism would be that my<br>
brain sends a "work faster" signal whenever a nerve seems to be<br>
working slowly, according to the delayed visual feedback, causing some<br>
kind of damage to healthy nerves)<br>
<br>
In any case, whether for health or "minimum annoyance" reasons, I have<br>
an interest in eliminating latency as much as possible. I don't care<br>
if someone sees part of all of my password, or if control sequences<br>
briefly show up on my editor screen. What I want is for immediate<br>
visual confirmation when one of my fingers pressed a key. The man page<br>
says "The predictive model must prove itself anew on each row of the<br>
terminal and after each control character, so mosh avoids echoing<br>
passwords or non-echoing editor commands." Is there an easy way to<br>
turn this feature off in the source code? Is it a bad idea, for some<br>
reason I haven't anticipated?<br>
<br>
My other (related) question is how to measure the actual latency. I<br>
can imagine that someone may have patched xterm to log input and<br>
output characters with sufficiently fine-grained timestamps, so that<br>
the latency of ssh, mosh, screen, etc. could be calculated, as the<br>
user presses random keys. I saw a couple things on your github issue<br>
tracker which look like people are measuring these values. I'm curious<br>
how to measure them myself. My initial trial of mosh (on an Arch<br>
Linux, 800 MHz "Intel(R) Atom(TM) CPU N270" (32-bit)) seems to show a<br>
slightly higher latency than simply typing on a local editor, and I'm<br>
curious to know if this is real.<br>
<br>
Thank you again for your dedication and incredibly useful software<br>
contribution, and also for reading my questions.<br>
<br>
Please Cc on replies as I'm not subscribed. Thanks,<br>
<br>
Frederick Eaton<br>
_______________________________________________<br>
mosh-devel mailing list<br>
<a href="mailto:mosh-devel@mit.edu" target="_blank">mosh-devel@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/mosh-devel" rel="noreferrer" target="_blank">http://mailman.mit.edu/mailman/listinfo/mosh-devel</a><br>
</blockquote></div><br></div></div>