I self host a ff send instance. See https://github.com/mozilla/send
In Dropbox Transfermozilla
send
FreeMarker2017–2024
mozilla / send · Archived
send
Simple, private file sharing from the makers of Firefox
46Distinct people
46Mentions
0Explicit recommenders
13.2KGitHub stars
What to know before exploring
What it is
Simple, private file sharing from the makers of Firefox
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:01:40 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year46 dated mentions
Observed mentions: 2017-08-02 06:54:38 UTC to 2024-10-19 18:13:21 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 19 | 3 | 16 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Firefox Send
NOTICE - May 2021
Mozilla discontinued the Firefox Send service in September 2021. For more information about this, please see the Mozilla Blog.
Please note that the Mozilla Public License 2.0 does not "grant any rights in the trademarks, service marks, or logos of any Contributor." You may fork and modify the source code for Firefox Send pursuant to the Mozilla Public License, but you may not create a version of the service that uses Mozilla trademarks or logos.
This repository is archived. In May 2021, Mozilla removed Mozilla trademarks from some of the files in this repository so that developers using this code are less likely to inadvertently infringe Mozilla's trademarks and confuse users. You are welcome to copy and modify this code under its open source license, but please ensure that all use complies with Mozilla's trademark policy. In other words, if you create a new version of Firefox Send you must remove all "Mozilla" and "Firefox" branding to ensure that users are not confused about who is providing the service.
Docs: FAQ, Encryption, Build, Docker, Metrics, More
Table of Contents
What it does
Requirements
Development
Commands
Configuration
Localization
Contributing
Testing
Deployment
Android
License
What it does
A file sharing experiment which allows you to send encrypted files to other users.
Requirements
Node.js 12.x
Redis server (optional for development)
AWS S3 or compatible service (optional)
Development
To start an ephemeral development server, run:
npm install
npm start
Then, browse to http://localhost:8080
Commands
Command
Description
npm run format
Formats the frontend and server code using prettier.
npm run lint
Lints the CSS and JavaScript code.
npm test
Runs the suite of mocha tests.
npm start
Runs the server in development configuration.
npm run build
Builds the production assets.
npm run prod
Runs the server in production configuration.
Configuration
The server is configured with environment variables. See server/config.js for all options and docs/docker.md for examples.
Localization
Firefox Send localization is managed via Pontoon, not direct pull requests to the repository. If you want to fix a typo, add a new language, or simply know more about localization, please get in touch with the existing localization team for your language or Mozilla’s l10n-drivers for guidance.
see also docs/localization.md
Contributing
Pull requests are always welcome! Feel free to check out the list of "good first issues".
Testing
ENVIRONMENT
URL
Production
https://send.firefox.com/
Stage
https://stage.send.nonprod.cloudops.mozgcp.net/
Development
https://send2.dev.lcip.org/
Deployment
see also docs/deployment.md
Android
The android implementation is contained in the android directory, and can be viewed locally for easy testing and editing by running ANDROID=1 npm start and then visiting http://localhost:8080. CSS and image files are located in the android/app/src/main/assets directory.
License
Mozilla Public License Version 2.0
Read the full README on GitHubWhat Hacker News says
19 sources>They were building a free subscription service to check HIBP for your info. (https://monitor.firefox.com/) //
Wasn't HIBP a single person.
So presumably a checking system could have been churned out by, being generous, a team of 6 on a mean-average $100,000 wage. Lets say $1.2M per year (doubled to account for facilities, etc.) as a top end. Realistically surely that's a couple of months work for such a team?
Looking at the Send github (https://github.com/mozilla/send/graphs/contributors) it's essentially 2 people, about 1.5 person years in the commits.
The first and fourth items you list sound like absolute white elephants that management should have allowed only as "we'll give you a full time dev wage for it and spare facilities, show us what you can do and we might take it on".
So, what have we got left $240M?
In Firefox has lots of room to improve if it wants to beat Chrome> They spent $253 million (45% of revenue) on software development, presumably the bulk going to Firefox.
I'm curious if anyone can locate information on how much of that was spent specifically on Firefox, the browser. It seems like Mozilla was working on a bunch of peripheral stuff during that 2016-2017 period.
* Work on Firefox OS was still ongoing through 1H 2016. (https://groups.google.com/forum/#!msg/mozilla.dev.fxos/FoAwi...)
* They were building a free subscription service to check HIBP for your info. (https://monitor.firefox.com/)
* They were building a file-sharing service (https://github.com/mozilla/send/blob/master/CHANGELOG.md)
* They were building a new VR-first browser and content aggregator (https://blog.mozilla.org/blog/2018/09/18/firefox-reality-now...)
In Firefox has lots of room to improve if it wants to beat ChromeAnd, since it's a Mozilla product, you can self-host it: https://github.com/mozilla/send
In Mozilla and Firefox could be about to change the VPN and privacy marketSend: Simple, private file sharing from the makers of Firefox
1 points · Open discussionWhy not hack your favicon to show file loading progress, React-LoadCon
When it comes to a huge file (such as huge PDF or upload file to Cloud service) loading or download in a tab, a tiny progress indicator on favicon could be an interesting but also considerate UX experience.
This idea comes from a long time ago and has been realized by so many open-source developers, and it comes to me again when I try to solve this good first issue for the `Send` project from Mozilla https://github.com/mozilla/send/issues/803
Here is React-LoadCon for React community, welcome to play around and feel free to submit your feedback whenever encounters any issue.
https://foreseaz.github.io/react-loadcon/
3 points · Open discussionSimple, private file sharing from the makers of Firefox
1 points · Open discussionWe'll find out by the end of the year »
Secondary - In support of Revenue KPI
We believe that a privacy respecting service accessible beyond the reach of Firefox will provide a valuable platform to research, communicate with, and market to conscious choosers we have traditionally found hard to reach.
We will know this to be true when we can conduct six research tasks (surveys, A/B tests, fake doors, etc) in support of premium services KPIs in the first six months after launch.
https://github.com/mozilla/send/blob/master/docs/metrics.md
In Firefox Send: Free encrypted file transfer serviceAnother user pointed out that Firefox Send is written to use an Amazon S3 compatible API to run. That could mean that Mozilla is using AWS for the service.
https://github.com/mozilla/send#requirements
In Firefox Send: Free encrypted file transfer serviceRead here for the why: https://github.com/mozilla/send/blob/master/docs/metrics.md
In Firefox Send: Free encrypted file transfer serviceIf you're still interested in this type of tool, I'm sure Mozilla would welcome your contribution: https://github.com/mozilla/send
In Firefox Send: Free encrypted file transfer serviceIt looks like Mozilla publishes a container and has instructions:
https://github.com/mozilla/send/blob/master/docs/docker.md
In Firefox Send: Free encrypted file transfer service> Key Business Question to Answer: Is the value proposition of a large encrypted file transfer service enough to drive Firefox Account relationships for non-Firefox users.
The metrics section is interesting https://github.com/mozilla/send/blob/master/docs/metrics.md
In Firefox Send: Free encrypted file transfer serviceThe client encrypts the file that is uploaded, along with some metadata. The key is appended to the share URL provided by the URL, in the fragment/hash, and is never sent to the remote server. Only people having the URL including the secret will be able to download and decrypt your shared file. See https://github.com/mozilla/send/blob/master/docs/encryption....
In Firefox Send: Free encrypted file transfer serviceShowing the 15 most recent of 19 sources. Enable JavaScript to search and browse every indexed mention.