Earlier 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 always find it by searching ‘iana port list’
41–45 of 45 posts
Earlier 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 always find it by searching ‘iana port list’
- 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.
Earlier quoted context omitted.
Ports get registered? I just assumed we were all picking whatever open ports we could find.
Way back in the idealistic days of the internet you could apply for and reserve a port for your protocol. I don't think you can do this anymore..., or if you can it's not easy.
I 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…
I 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…
Your TLS certificate has expired and is throwing an error.