snakes.run: rendering 100M pixels a second over ssh ·
18 points by eaj
18 points by eaj
Excellent.
I've been using Charm's wish for building an SSH command line interface for my ActivityPub services. Basically instead of having to run control commands on the server where the server runs, I just login through ssh and am able to run the same commands.
I haven't found a clean way to read the standard input that respects raw mode (for password entering) but it's still a cool concept. Another ActivityPub application Stegodon tipped me to the idea, and they're using it for a full blown TUI which is even cooler.
I have seen a few projects in recent months that use SSH for very cool, creative purposes. All I've seen use wish, which appears to be a framework for making these kinds of apps (this posts uses wish too). What do I need to read to understand how this works internally. Like which role does wish play, which role does the SSH server play, etc. I asked myself these questions when I saw the the SSH-based coffee shop, but I didn't know where to start, so my curiosity went nowhere.
One thing you might not realize is that there isn't a separate SSH server. Go has an implementation of the SSH protocol, and wish is reusing that. So the binary is listening on a port for SSH clients and then instead of spawning a subprocess like OpenSSH would typically do, it's instead interacting and sending terminal commands itself.