A$ curl --upload-file - http://blah < /proc/kmsg
B$ curl http://blah/uYsfVX
and see live stream of data on B.
A$ tar cv * | nc -l -p 1234
B$ nc a.example.net 1234 | tar xv
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.
Setting up cjdns is less work than setting up SSH.
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.