warp

What a coincidence, I wonder if this other dude got $17 mil: https://github.com/spolu/warp > warp lets you securely share your terminal with one simple command: warp open. When connected to your warp, clients can see your terminal exactly as if they were sitting next to you. You can also grant them write access, the equivalent of handing them your keyboard. > warp distinguishes itself from "tmux/screen over ssh" by its focus and ease of use as it does not require an SSH access to your machine or a shared server for others to collaborate with you. > Despite being still quite experimental, warp has already proven itself useful especially in the context of: > - Interaction with remote team-members > - New engineer onboarding (navigating code in group without projection) Installation

It isn't peer to peer. It is connecting to a 3rd party (warp.link, port 4242). It appears you can run your own server though. See https://github.com/spolu/warp/blob/4d045e7cac70c1af1fcb0abef...

How many times is it reasonable to submit the same URL to HN? This link is to https://github.com/spolu/warp?attempt=8. 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. Here's a few prior identical submissions by the same person: 1: https://news.ycombinator.com/item?id=14398392 (ie, https://github.com/spolu/warp?attempt=1) 4: https://news.ycombinator.com/item?id=14407813 6: https://news.ycombinator.com/item?id=14452505 If 8 isn't too many, what is? 20? Submit the same link every day indefinitely until it reaches the front page?

This is false. There has to be some way to resolve the name used (e.g. in the example, `warp connect goofy-dev` is used) to an IP address. Looking through the source code, I've found these lines: https://github.com/spolu/warp/blob/master/client/command/con... https://github.com/spolu/warp/blob/master/client/command/con... https://github.com/spolu/warp/blob/master/protocol.go#L13 It looks like it defaults to connecting to `warp.link:4242`. I can't tell if it's routing the entire connection through warp.link or if it's just resolving the name to an IP address that then connect directly (I don't know Go very well).

Looking at the source code suggests it is peer to peer. The code for daemon indicates you need to specify what address and port to listen on when starting up, and there is code about receiving incoming clients. https://github.com/spolu/warp/blob/master/daemon/cmd/warpd/m...