piping-server VS send

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.

There is also Send.Vis.ee, which is a community fork of Firefox Send. It has always worked very well for me personally. There are many public instances available with varying sizes and expiring conditions.

- Website: https://send.vis.ee/

- Source: https://github.com/timvisee/send

- List of instances at: https://github.com/timvisee/send-instances

I've been using Send, which I really like: https://github.com/timvisee/send

Probably not what you are asking for, but if you would like to host on your own server, there is https://github.com/timvisee/send which is a fork of Firefox's Send.

You get a web interface where you can drag and drop files. It uploads the files to your own server and you will get a link to share them.

Send is a fork of Mozilla's Firefox Send. It's perfect for sharing files with friends with ease.

Send

Not much of a point to that. File upload forms are pretty trivial for one, and there already are plenty of good open-source solutions for that (e.g. send or pomf). Your main challenge is going to be finding the disk space/bandwidth for that sort of thing, but anyone with enough resources can already run a zippyshare "clone" with zero issues.

If it's just one time file sharing, try Send. Formerly Firefox Send, you can now self host it.