streamhut VS piping-server

Maybe try streamhut: https://github.com/miguelmota/streamhut

Of course, both of them are not ready for security-related tasks such as terminal sharing. So treat them like a "console" streaming service there you broadcast your terminal to the world.

Streamhut can be made more secure with some configuration tricks, namely, don't expose it's TCP port to the public, instead, only expose it's HTTP service. Then you can create a back tunnel (with SSH -L for example) to feed data into it's TCP port in a safer manner.

However, I'd imagine a better option is to beg miguelmota to add support for websocket in the cli client, that way the connection can be protected by TLS rather than just a raw TCP.

You can self-host easily on Heroku, Replit, Glich, etc. See https://github.com/nwtgck/piping-server/wiki/How-to-self-host-Piping-Server for detail.

I found a higher transparent way that uses existing and widely used commands: nc and curl. The original idea of a port forwarding with socat, curl, and Piping Server was proposed in a Japanese article by @Cryolite. Meanwhile, this post introduces a way using nc (netcat), which is more widely used and installed than socat, and the way allows simple integration with other commands using Unix pipe. It is very helpful when using an untrustable server because we can integrate it with an encryption command such as openssl.