News for hackers. Stuff that matters.
Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by oxplot on Sunday March 20, 2016 @03:58AM (#11322194)
It'd be cool to have the ability to pipe stuff over the Internet from shell in real time like you would with SSH for instance. So I could do:

A$ curl --upload-file - http://blah < /proc/kmsg

B$ curl http://blah/uYsfVX

and see live stream of data on B.

Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by Retr0spectrum on Sunday March 20, 2016 @05:08AM (#11322315)
You can do that with netcat if either A or B are listening.
Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by Symbiote on Sunday March 20, 2016 @06:05AM (#11322408)
I do this fairly regularly.

    A$ tar cv * | nc -l -p 1234

    B$ nc a.example.net 1234 | tar xv
Or I might remove a 'v' and pipe through 'pv' to see the transfer rate and amount.
Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by oxplot on Sunday March 20, 2016 @06:46AM (#11322474)
Well over the "Internet" kind of implies behind a firewall so the service would be a convenience to avoid setting up port forwarding etc.
Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by lolidaisuki on Sunday March 20, 2016 @07:39AM (#11322573)
VPN are a thing.

I recommend just installing cjdns and forwarding the home end. It also encrypts your traffic. You wouldn't want to netcat in cleartext over the internet.

Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by voltagex_ on Sunday March 20, 2016 @10:17AM (#11322981)
You could always just pipe it through ssh or some other thing. Setting up openvpn or similar is nontrivial - even if you're lucky enough to have a static IP and enough spare time to make it work.
Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by lolidaisuki on Sunday March 20, 2016 @11:45AM (#11323331)
> Setting up openvpn or similar is nontrivial

Setting up cjdns is less work than setting up SSH.

Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by zackboe on Sunday March 20, 2016 @05:10PM (#11324686)
Someone else in this thread mentioned chunk.io which offers this http://chunk.io/#stream_content_beta
Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by javajosh on Sunday March 20, 2016 @04:42AM (#11322269)
That would be cool, but the devil is in the details. For one thing, does the "upload" wait for at least one "download" to connect? Or does "upload" go to a cache that is re-used for all subsequent downloads? What are the timeouts? E.g. how long would blah.com hold the upload connection open until (at least one) download opened up?

The other thing that makes it less cool is that it's a hack that would be better off not existing. The ideal case is that every device should have a unique ID, such that we can directly "subscribe" to anything on any device without using an intermediary (well, an application level intermediary anyway; you'll always be using link-level intermediaries). Such an ID might be IPv6, in which case such a service is trivially replaced with ordinary every day ssh/scp.

Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by oxplot on Sunday March 20, 2016 @06:51AM (#11322481)
I think it should be as dumb and simple as possible and do nothing deviating from normal unix behavior (ie pipe). So it would cache only one chunk of data sent by A and start streaming to the first download request.
Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by gbin on Sunday March 20, 2016 @05:45AM (#11322376)
Re:$ cat ~/myfile | curl -X PUT --upload-file “-” https://tr... by lmm on Sunday March 20, 2016 @05:06AM (#11322310)
You can use netcat for that. Or Bash has built-in TCP support.