A podcast nearing its tenth year still relies on a surprisingly manual handoff: each guest records audio locally, usually with Quicktime Player or Windows Voice Recorder, and ends up with a file of roughly 100MB to get back to the producer. Local recording is what lets the editor do the most with the raw material, but moving that file is where things get inconsistent.

How the files actually arrive

When a guest happens to share a Slack workspace with the team, Slack handles files of that size. Boosted Discord does not — even with Nitro it falls short of 100MB. In practice about 70% of guests put the file in their own Dropbox and send a sharing link, another 20% use Google Drive, and the remaining 10% is a grab bag: uploading to a web server or file storage service the guest controls is the common variant.

The request to guests is deliberately open-ended — send it however you normally send large files — because people can have strong aversions to particular services or companies. Two things would improve the process: using File Request links on Dropbox or Box instead of asking for a generic share.

The gap Firefox Send left

Firefox Send was the natural recommendation for one-off transfers. It was built for exactly that purpose, and people generally trusted Mozilla to run it. It is gone. Mozilla's own explanation:

Unfortunately, some abusive users were beginning to use Firefox Send to ship malware and conduct phishing attacks. When this problem was reported, we stopped the service. Please see the Mozilla Blog for more details on why this service was discontinued.

The shutdown is understandable as a response to abuse, though abuse is a constant on any service that accepts uploads. The likelier read is that Send was a side project with no revenue behind it and nobody wanted to fund the work of defending it. Either way, it costs trust in Mozilla's other experiments.

Wormhole as a candidate replacement

Wormhole is the closest thing to a direct replacement. It encrypts end to end and has thoughtful UX details, such as issuing a share link before the upload finishes. What it does not state is a long-term business or support plan; file hosting appears limited to 24 hours, which suggests low running costs. Nor does it say how it will handle abuse. Encryption doesn't prevent link blacklisting: if Google or Twitter found many wormhole.app URLs pointing at malware, the domain would get blocked, which wouldn't stop existing users but would keep new ones from finding it. The team has said it has ideas for fighting abuse if that becomes necessary.

Email clients that quietly do the work

It's a surprise that more files don't arrive through the email provider itself, given how often email rejects large attachments. That has shifted among the big providers: when a Gmail attachment exceeds 25MB, Gmail offers to upload the file to Google Drive and share it with the recipient automatically. Apple's Mail Drop does effectively the same thing for iCloud mail.

Personal habits

Dropbox sees a lot of use, but rarely for one-off sends. When a permanent copy matters, an Amazon S3 bucket is an option. Day to day, the default is Droplr, kept around for years for precisely this kind of transfer.