Hello Roman,
In 2017 in this thread, we requested, and you agreed, that your company
would stop using "Mosh" to refer to Termius, and use a phrase like
"Mosh-compatible" if you want to explain its ability to interoperate with
mosh-server. (You have told us that Termius is a clean-room
Hi Keith,
On 9 August 2017 at 11:51:44 AM, Keith Winstein (kei...@cs.stanford.edu) wrote:
Roman,
In early May, we had this exchange (also below in this thread). I wrote:
(3) We've had bad experiences in the past with people (especially iSSH on iOS)
attempting to implement the Mosh protocol,
Roman,
In early May, we had this exchange (also below in this thread). I wrote:
(3) We've had bad experiences in the past with people (especially iSSH on
> iOS) attempting to implement the Mosh protocol, but with imperfect results,
> and users blaming Mosh for the problems. As with these past
Hello Roman,
As we requested earlier (below in this thread), could you please refer to
your software as "mosh-compatible" instead of calling it a mosh client (or
"Mosh in your pocket" as is on your website now)?
Thank you,
Keith
On Sun, Aug 6, 2017 at 10:56 PM, Roman Kudiyarov
Hello Roman,
Okay, but if we can't see your code, we don't have a good way to start to
know if your implementation is "fully compatible" with Mosh (it's not like
we have a compatibility test suite for new binary implementations). If you
didn't implement it with clean-room approach and were
Hi Keith!
On 2 May 2017 at 6:40:20 AM, Keith Winstein (kei...@cs.stanford.edu) wrote:
Thanks for letting us know!
(1) Could you please describe the process you used to develop a clean-room
implementation of the Mosh protocol? Did you write up a protocol
specification based on the Mosh source
Thanks for letting us know!
(1) Could you please describe the process you used to develop a clean-room
implementation of the Mosh protocol? Did you write up a protocol
specification based on the Mosh source code, and then have somebody else
implement the spec? If so, would you be willing to share
