piping-server VS localsend

You can self-host easily on Heroku, Replit, Glich, etc. See https://github.com/nwtgck/piping-server/wiki/How-to-self-host-Piping-Server for detail.

I found a higher transparent way that uses existing and widely used commands: nc and curl. The original idea of a port forwarding with socat, curl, and Piping Server was proposed in a Japanese article by @Cryolite. Meanwhile, this post introduces a way using nc (netcat), which is more widely used and installed than socat, and the way allows simple integration with other commands using Unix pipe. It is very helpful when using an untrustable server because we can integrate it with an encryption command such as openssl.

I agree and get your point.

But localsend has worked well for me. Yes, it requires an app but if we could get vendors to bundle that rather than a boatload of bloatware.

I know that it would be to optimistic to hope for Google.

See https://localsend.org/

Spread the word.

https://github.com/localsend/localsend

Something to consider, although I'm not sure how much it practically matters.

It works like a charm, and is really easy to use

https://github.com/localsend/localsend

Use local send to send files and folders.

I've recently discovered and can recommend LocalSend. It's FOSS, cross-platform, and it just works. Github page with more details here

Edit: This is very simple implementation, even a POC, for personal use between our own devices at home or other personal private network. Even works on hotspot. But no HTTPS, so don's use on non-private networks. LocalSend, as suggested by u/Fede777 seems to be better for every other use.