<div dir="ltr"><div>I think that's a good observation. I think this conflation has also happened because there are very few compatible clients and servers. (Actually, I'm not aware of any other implementation of the mosh-server component besides mosh). </div><div><br></div>Would "mosh protocol" be an appropriate compromise between accuracy and clarity? Statements like the following would be, I suspect, pretty easily understood by people looking for remote access clients:<div><br></div><div>"Run multiple concurrent terminal sessions on any device you own, using the SSH, Telnet and Mosh protocols"</div><div><br></div><div><br><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 8, 2017 at 8:15 PM Jim Cheetham <<a href="mailto:jim.cheetham@otago.ac.nz">jim.cheetham@otago.ac.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Part of the broader miscommunication here (assuming good faith, of course) seems to be around the use of protocol names vs product names; using "SSH" and "Telnet" to refer to protocols and not products. The protocol name SSP isn't well-known, and currently the public recognise only the name of the canonical server software, which is Mosh.<br>
<br>
In practice, people set up "an SSH server" and don't tend to remember the name of the actual server software ... OpenSSH for example, or OpenSSH-Portable, which most Linux distributions are actually using :-)<br>
<br>
Mosh's own website says "Mosh is a replacement for SSH", which conflates the software with the protocol. Perhaps "SSP is a replacement for SSH"? Of course, SSP is capable of more than that as far as I can see, SSP isn't actually a replacement for SSH, but the Mosh application uses SSP in order to replace users of SSH ...<br>
<br>
Naming things seems to be one of the hardest things in computer science :-)<br>
<a href="https://martinfowler.com/bliki/TwoHardThings.html" rel="noreferrer" target="_blank">https://martinfowler.com/bliki/TwoHardThings.html</a><br>
<br>
And "mosh" is such an excellent name :-)<br>
<br>
-jim<br>
<br>
Excerpts from Keith Winstein's message of August 9, 2017 11:51 am:<br>
> I'm happy to explain our position further, and maybe you can understand why<br>
> this is important to us. Mosh is a piece of software, like OpenSSH or<br>
> Chrome. The protocol is called SSP (State Synchronization Protocol). You<br>
> have told us that your program is not derived from Mosh, so we really don't<br>
> want your company to call it Mosh. It's nothing personal -- but users are<br>
> better served knowing the difference. We had a bad experience with somebody<br>
> writing what they thought was a compatible implementation, and users<br>
> getting confused and blaming us. So we don't want users to think they are<br>
> running Mosh when they are running somebody else's application.<br>
><br>
> We would be fine with you making statements like, "Termius is<br>
> mosh-compatible" or "Termius has a mosh-compatible client" or even "Termius<br>
> works with Mosh servers." They key thing here is that it's fine for Termius<br>
> to claim mosh-compatibility, or to work *with* Mosh servers. It shouldn't<br>
> claim to *be* or to include Mosh, because it doesn't.<br>
><br>
> Yes, the text "SSH, Telnet, and Mosh in your pocket" and "... with SSH,<br>
> Telnet, and Mosh." appears on your current website, <a href="https://termius.com" rel="noreferrer" target="_blank">https://termius.com</a>.<br>
> You can visit it yourself to see.<br>
<br>
--<br>
Jim Cheetham, Information Security, University of Otago, Dunedin, N.Z.<br>
✉ <a href="mailto:jim.cheetham@otago.ac.nz" target="_blank">jim.cheetham@otago.ac.nz</a> ☏ <a href="tel:+64%203-470%204670" value="+6434704670" target="_blank">+64 3 470 4670</a> ☏ m <a href="tel:+64%2021%20279%204670" value="+64212794670" target="_blank">+64 21 279 4670</a><br>
⚷ OpenPGP: B50F BE3B D49B 3A8A 9CC3 8966 9374 82CD C982 0605<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>