magic-wormhole.rs

Sounds like Magic Wormhole (https://magic-wormhole.io/). The readme acknowledges Warner at the end. Key differences seem to be resumable transfers and proxy support. Another is a single binary, whereas MW is in Python, but there’s now https://github.com/magic-wormhole/magic-wormhole.rs I appreciate that the project acknowledges its inspiration. I wish it were more common for projects to provide detailed comparisons with similar ones for people trying to choose.

I saw some time back that a productionalized attempt came out: https://github.com/magic-wormhole/magic-wormhole.rs The one I mentioned was much more primitive, meant as a demo (you can look at the branches for different approaches): https://github.com/estebank/rusticwormhole

Just noticed by coincidence there's also: "Rust implementation of Magic Wormhole, with new features and enhancements": https://github.com/magic-wormhole/magic-wormhole.rs

> if you want a non-Python runtime for some reason [...] Magic Wormhole project has its own alternate implementation https://github.com/magic-wormhole/magic-wormhole.rs, which is also used by delightfully designed GNOME and Android apps; [Warp](https://apps.gnome.org/Warp/), and [Wormhole](https://play.google.com/store/apps/details?id=eu.heili.wormh...), respectively.

> Downloading 3GB of dependencies is not a thing that happens in the Rust ecosystem. Reality is orders of magnitude smaller than that. Assuming they're talking about the built size of dependencies that are left lying around after cargo builds a binary, they're really not exaggerating by much. I have no difficulty of believing that there are Rust projects that leave 3GB+ of dependency bloat on your file system after you build them. To take the last Rust project I built, magic-wormhole.rs [1], the source code I downloaded from Github was 1.6 MB. After running `cargo build --release`, the build directory is now 618 MB and there's another 179 MB in ~/.cargo, for a total of 800 MB used. All this to build a little command line program that sends and receives files over the network over a simple protocol (build size 14 MB). God forbid I build so

The main thing I use for ad hoc file transfers is Total Commander for Android (https://www.ghisler.com/android.htm). It can copy files to and from a WebDAV inbox on the local network as well as my home directory (although the SFTP plugin I use for that is fiddly to set up and a bit buggy). For copying the same things on a regular basis, I run rsync scripts in Termux (https://termux.dev/en/). They push photos from my phone to my computer and pull essential backup from my computer to my phone. They also synchronize themselves and Termux configuration. For exchanging files without a direct network connection, I have croc and the Rust version of Magic Wormhole (https://github.com/magic-wormhole/magic-wormhole.rs) installed in Termux. It may seem arcane and archaic, but I have found this setup better (more predictable and more reliable) than a

I didn't know about https://bashupload.com. Thanks for mentioning it. There is also https://chunk.io/ in the https://transfer.sh category. It requires free registration by emailing the owner. It has some interesting features, like uploading multiple files in one HTTP request and syntax highlighting for source code. Files are associated with your account, so you can delete them without a per-file token and list them. https://github.com/schollz/croc is like Magic Wormhole but can send multiple files and resume transfers. It is written in Go. It releases official static binaries, including for Free/Net/OpenBSD. (Magic Wormhole has alternative implementations with static binaries: https://github.com/psanford/wormhole-william, https://github.com/magic-wormhole/magic-wormhole.rs.)