Try it out, you can pipe your terminal:
exec > >(nc stream.ht 1337) 2>&1
tail -F file.log | nc stream.ht 1337
(sleep 5; htop) | nc stream.ht 1337
exec 3<>/dev/tcp/stream.ht/1337 && head -1 <&3 && exec &> >(tee >(cat >&3))
The window for viewing streams appears to even have commenting (and file/image sharing?). I also like how you lead with the "stream the whole terminal" example which lets me see how I can continue streaming a terminal instead of just piping a single program like htop to it.
Another plus is you've open sourced the server-side unlike Seashells/OP:
Nice work and thanks!
I always find it by searching ‘iana port list’
I don't think you can do this anymore..., or if you can it's not easy.
This is the first I see software like this, has anybody seen other similarly useful utilities? I think it's invaluable to be able to share your console output with coworkers in real time so they can also help to troubleshoot.
* https://github.com/yudai/gotty - actually gives you a tty in a browser
You can use tmux's shared sessions via ssh for that, no?
I built a similar tool a while ago, but to share your entire (read-only) shell session interactively: https://shellshare.net/. Might be useful for some looking at this.
telnet towel.blinkenlights.nl | nc seashells.io 1337
- an open-source client that symmetrically encrypts the output with a random key before sending it to the server (obviously, the key is not being sent),
- the key is appended after # in the URL, so it’s only available to the browser,
- client-side decryption in JS.
* oho is the best ANSI CLI->HTML tool out there (If I'm wrong file a ticket ;) )
* fenestro takes HTML output generated by your command line and displays it (macOS only). If you shove multiple things into it quickly it'll display the list of them in the sidebar. Later requests for display will be in new windows.
This could be quite useful to demonstrate/teach/explain simple stuff to people but I am not so sure if I would like to expose anything else from my console in this way.
In all seriousness, isn't the use case here more temporary? You're running a script that you want some else to see the output of without the faff of copy & paste to a gist.