piping-server
streamhut
piping-server | streamhut | |
---|---|---|
4 | 1 | |
2,860 | 866 | |
- | - | |
8.4 | 0.0 | |
8 days ago | about 2 years ago | |
TypeScript | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
piping-server
- How to copy a file between devices?
-
Secure TCP tunnel from anywhere with curl and nc for single connection
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.
- Seashells: Pipe output from command-line programs to the web in real-time
streamhut
-
Seashells: Pipe output from command-line programs to the web in real-time
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.
What are some alternatives?
mediathekviewweb - Eine Weboberfläche als Alternative zum Java-Client
cointop - A fast and lightweight interactive terminal based UI application for tracking cryptocurrencies 🚀
yamux - Golang connection multiplexing library
go-websockets - I don't know .... learning golang and websockets ☠️
go-piping-server - Piping Server written in Go language (original: https://github.com/nwtgck/piping-server)
anycable-go - AnyCable real-time server
scripts - scripts from pixelbeat.org
gotty - Share your terminal as a web application
piping-vnc-web - VNC client over pure HTTPS via Piping Server on Web browser
ascii-movie - 🌌 Star Wars SSH + Telnet server written in Go
controller - A simple controller design pattern for curveballjs
kazy-go - Highlights, filters and extracts string patterns from STDIN