No support for encryption? It would be interesting to support HTTPS, even if the initial setup would be harder than "nc".
Seashells – Pipe output from command-line programs to the web in real time
31–40 of 45 posts
Re: Seashells – Pipe output from command-line programs to the web in real time
#32 telnet towel.blinkenlights.nl | nc seashells.io 1337Re: Seashells – Pipe output from command-line programs to the web in real time
#33I think this is a great idea, like others said it's the first time I've seen it. The problem is that almost any use case where this is useful for, is almost surely data that people wouldn't want publicized. A self-hosted version of this is ideal (for businsesses). At the very least, allow for API tokens and require a login to see your output (for personal projects uses) instead of just relying on a short random strin…
Re: Seashells – Pipe output from command-line programs to the web in real time
#34Re: Seashells – Pipe output from command-line programs to the web in real time
#35Re: Seashells – Pipe output from command-line programs to the web in real time
#36I created something similar years ago and it's open source: https://stream.ht/ Try it out, you can pipe your terminal: exec > >(nc stream.ht 1337) 2>&1 Or just pipe a file: tail -F file.log | nc stream.ht 1337 Pipe htop (delay is required to see share url) (sleep 5; htop) | nc stream.ht 1337 Doesn't require installing anything! Requires netcat which is installed on most *nix systems but you can use a plain tcp socket…
Re: Seashells – Pipe output from command-line programs to the web in real time
#37Earlier quoted context omitted.
I wonder if that could get registered for this purpose somehow?
Ports get registered? I just assumed we were all picking whatever open ports we could find.
I don't think you can do this anymore..., or if you can it's not easy.
Re: Seashells – Pipe output from command-line programs to the web in real time
#38I think this is a great idea, like others said it's the first time I've seen it. The problem is that almost any use case where this is useful for, is almost surely data that people wouldn't want publicized. A self-hosted version of this is ideal (for businsesses). At the very least, allow for API tokens and require a login to see your output (for personal projects uses) instead of just relying on a short random strin…
How is random string not a password?
Re: Seashells – Pipe output from command-line programs to the web in real time
#39No support for encryption? It would be interesting to support HTTPS, even if the initial setup would be harder than "nc".
Re: Seashells – Pipe output from command-line programs to the web in real time
#40I created something similar years ago and it's open source: https://stream.ht/ Try it out, you can pipe your terminal: exec > >(nc stream.ht 1337) 2>&1 Or just pipe a file: tail -F file.log | nc stream.ht 1337 Pipe htop (delay is required to see share url) (sleep 5; htop) | nc stream.ht 1337 Doesn't require installing anything! Requires netcat which is installed on most *nix systems but you can use a plain tcp socket…