Cool tool but in the Readme you should probably explain a little bit 'how it works' rather than just 'how to work it'. In this case, I imagine it needs to connect to and trust some outside coordinating service run/owned by someone (you?).
I recently built <a href="https://debug-me.branchable.com/" rel="nofollow">https://debug-me.branchable.com/</a> which also does quick and easy terminal sharing, but with the addition of a cryptographically secure proof of what was done in the session, rooted at the gpg key of the person who connected to it.
Another good open source terminal sharing service is <a href="https://tmate.io/" rel="nofollow">https://tmate.io/</a><p>This gives you 2 ssh addresses (read only and read write) that you
can send out.
I've been using <a href="https://www.teleconsole.com/" rel="nofollow">https://www.teleconsole.com/</a> from the team behind teleport. It has Linux, MacOS, FreeBSD, x86_64 and ARM7 support.<p>This looks like a great project and I'll be keeping my eye on it, but there's no reason for me to switch to this and lose out on features.<p>It's open source, and you can even set up your own proxy so you don't need to rely on gravitational's servers.
Can someone explain the actual use of sharing a terminal with someone while not being in person with them (in which case they could just watch you and shotgun the keyboard?)? I can't imagine watching someone else's terminal session without them talking about what they're doing and why would be particularly informative or help with onboarding. Maybe it's just one of those things that work for some people and not others?
The feature I'd suggest for any peer-to-peer application such as this is some kind of firewall punching. It generally requires a 3rd-party on the internet. To avoid running services for a low-bandwidth application like this, maybe it could tunnel through a public IRC server or other public chat system.
Does it relate somehow to Joey Hess's debug-me[1]?<p>[1]: <a href="https://joeyh.name/blog/entry/announcing_debug-me/" rel="nofollow">https://joeyh.name/blog/entry/announcing_debug-me/</a>
How many times is it reasonable to submit the same URL to HN?<p>This link is to <a href="https://github.com/spolu/warp?attempt=8" rel="nofollow">https://github.com/spolu/warp?attempt=8</a>. If one needs to add an "attempt" HTTP parameter to track submissions of the same URL, and this is the 8th attempt, that seems like way too many.<p>Here's a few prior identical submissions by the same person:<p>1: <a href="https://news.ycombinator.com/item?id=14398392" rel="nofollow">https://news.ycombinator.com/item?id=14398392</a> (ie, <a href="https://github.com/spolu/warp?attempt=1" rel="nofollow">https://github.com/spolu/warp?attempt=1</a>)<p>4:
<a href="https://news.ycombinator.com/item?id=14407813" rel="nofollow">https://news.ycombinator.com/item?id=14407813</a><p>6: <a href="https://news.ycombinator.com/item?id=14452505" rel="nofollow">https://news.ycombinator.com/item?id=14452505</a><p>If 8 isn't too many, what is? 20? Submit the same link every day indefinitely until it reaches the front page?
I really like that it goes against the current cancer we are experiencing on the internet. That is,<p>* You don't need to rely or surrender to the cloud.<p>* Neither you nor the clients need to create an account (or worse, require a google/facebook account).