Hello Dean,<div><br></div><div>I noticed that the in-app purchase at <a href="https://itunes.apple.com/us/app/issh-ssh-vnc-console/id287765826?mt=8">https://itunes.apple.com/us/app/issh-ssh-vnc-console/id287765826?mt=8</a> is described as "Mosh".</div>
<div><br></div><div>Could you please rename this to "Mosh compatibility" as per below? Mosh is the name of our program and I don't want there to be any confusion about what is being distributed, as we discussed earlier.</div>
<div><br></div><div>Thanks much,</div><div>Keith<br><br><div class="gmail_quote">On Tue, Sep 11, 2012 at 2:50 AM, Dean Beeler <span dir="ltr"><<a href="mailto:canadacow@gmail.com" target="_blank">canadacow@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff" text="#000000">
Keith,<br>
<br>
Thanks for the clarification. As it stands mosh is being added as a
supplemental purchase inside of iSSH. This is generally due to
licensing and legal costs. As such, the purchase is for "Mosh
compatibility." Where mosh is activated it's simply a switch on an
otherwise iSSH standard terminal connection. Again, I'd be very willing
to either give you a demonstration or send you a beta copy if you
happen to have an iOS device.<br>
<br>
I've stayed pretty active with the development of iSSH over the last
four years and don't have any intention of slowing down. I fully intend
to keep pace with augmented features of mosh so long as they're
documented well enough I can replicate them.<span class="HOEnZb"><font color="#888888"><br>
<br>
Dean</font></span><div><div class="h5"><br>
<br>
On 9/10/2012 11:03 AM, Keith Winstein wrote:
<blockquote type="cite">Hi Dean,
<div><br>
</div>
<div>Thanks for reaching out! I worry that users will confuse your
independent implementation of the Mosh/SSP protocol with Mosh itself,
especially if you use images from our Web site.</div>
<div><br>
</div>
<div>Could you please describe iSSH as having a "Mosh-compatible
terminal client" or "Mosh-compatible secure terminal"? The point being
that you have implemented your own client. It needs to be clear that
this is a clean-room implementation and isn't Mosh or derived from the
Mosh codebase. Along the same idea, we'd ask you to use your own icon
instead of using the images from the Mosh Web site, since I think that
will just confuse people.</div>
<div><br>
</div>
<div>If you want to use the Mosh codebase, that's a different story
and I'd be thrilled to help make that happen, especially as we add
features (like scrollback) to the protocol in the future. But for an
independent program that speaks the same language, we would want it to
have its own name.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Keith</div>
<div><br>
</div>
<div>
<div class="gmail_quote">On Sun, Sep 9, 2012 at 11:39 PM, Dean Beeler
<span dir="ltr"><<a href="mailto:canadacow@gmail.com" target="_blank">canadacow@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204,204,204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div bgcolor="#ffffff" text="#000000">
Keith,<br>
<br>
Mosh doesn't really have a logo though I need something to brand its
appearance inside iSSH. Would you mind if I took the terminal screen
shown below and used it for branding and around the text describing
mosh?<br>
<br>
<img alt="" src="cid:part1.02080102.06000205@gmail.com" width="477" height="427"><span><font color="#888888"><br>
Dean</font></span>
<div><br>
<br>
<br>
On 8/13/2012 12:23 AM, Keith Winstein wrote:
<blockquote type="cite">
<pre>Howdy,
I'm the author of Mosh.
</pre>
</blockquote>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>