Live data from Hacker News

What happened to Firefox Send?

support.mozilla.org

161–170 of 267 posts

Re: What happened to Firefox Send?

#161

I really don't understand it. - Content was used to spread malware/illegal content - It was not profitable How are those two things something you find out after the fact? What was the reasoning for launching the product in the first place?

I thought Mozilla was a non-profit.

And couldn't they have added a malware scanner to deal with the problem directly?

As for illegal content that's true with any private communication but maybe DCMA or similar got involved. I can accept that fighting for private large file transfer detracts from the main goal.

Re: What happened to Firefox Send?

#162
post #117

I was under the impression Firefox Send was one of the upcoming paid service offerings. At least, that we were seeing the free service and waiting some premium features to be released later on. It will be missed, it was a really easy and intuitive solution for file sharing,

I was really hoping this would be the case. Sync + Send + Lockwise would be a bundle of services worth paying a subscription for. Provided that they also made them available on Chrome rather than using them as lock-in features.

But there seems to be zero plans towards financial independence for Mozilla Corp. The management board appears to be all too cozy with Google funds lining their pockets. A financially independent Mozilla Corp. would probably mean less money for them.

Re: What happened to Firefox Send?

#163
post #109
post #101

Earlier quoted context omitted.

> how many working on Firefox? 50? and 950 doing various (useless) side projects? You have a source for those numbers? It looks to me like you're just making them up because you want to sling mud.

There were question marks along with the numbers. Clearly it’s a rhetorical device, presenting a reasonable speculation that matches the evidence (number of projects, and quality), as part of the natural flow of the writer making their point.

The comment was not asking out of curiosity, because when you do that you don't frame it in a way (50 out of 1000) that matches the larger point you're trying to make.

Re: What happened to Firefox Send?

#164

I really don't understand it. - Content was used to spread malware/illegal content - It was not profitable How are those two things something you find out after the fact? What was the reasoning for launching the product in the first place?

I thought Mozilla was a non-profit. And couldn't they have added a malware scanner to deal with the problem directly? As for illegal content that's true with any private communication but maybe DCMA or similar got involved. I can accept that fighting for private large file transfer detracts from the main goal.

The files were encrypted, Mozilla didn't have access to the contents.

Re: What happened to Firefox Send?

#165
post #130

Tangentially, I wonder what's happening with Lockwise. [1] It also seems to be languishing without significant improvements. I was expecting it to be a competitor, at least on mobile, to the likes of Bitwarden, 1Password, and other solutions. [1]: https://www.mozilla.org/en-US/firefox/lockwise/

I'm so happy I decided to move away from Chrome's password manager and Firefox Lockwise and instead use Bitwarden.

Re: What happened to Firefox Send?

#166

Sad! Developer of `ffsend` here. I've built `ffsend` as CLI tool for Send to securely share files from the command line. It has been a great success! Thanks Mozilla, for building and providing this amazing service! For the interested: https://github.com/timvisee/ffsend I'm currently hosting a public Send instance myself so ffsend keeps working. Let's see how long I can keep this going (and funded). It's available at…

Was this shutting down as surprising and out-of-left-field to yourself as someone more closely connected to the project, as it seems to me?

Re: What happened to Firefox Send?

#167
post #106
post #80

Earlier quoted context omitted.

But it tarnishes their name. People who get malware through Firefox Send will associate Firefox or Mozilla with viruses because that's where it's being served from. It doesn't matter to them that it's fully the fault of the person sharing the malware, they expect that if a site is serving them content then that site can ensure that it's safe.

I wonder if renaming the domain from send.firefox.com to fileshare.com or something like that would have helped with that

untrustedusercontent.com

Re: What happened to Firefox Send?

#169
post #95

Earlier quoted context omitted.

Nearly all their "side projects" look like greenfields used by the project teams to boost their CVs so they can land better jobs. Those teams know very well that those projects have no use case, but they dont care. Foundation does not care either, since it is busy with increasing own remuneration and politics. Meanwhile their core product lost around 10 percentage points of market share (from 15% marketshare to 5%):…

If you think Firefox has stagnated you clearly aren't aware of the substantial and complex improvements that have been made to the firefox core over the last couple of years: * Faster Quantum Engine (multi-process architecture, etc) * Faster CSS rendering with Stylo * GPU-based rendering with WebRender Any Moz engineer who worked on the above will have boosted their CV's substantially. They don't need to work on tang…

As an engineer I see the value in these projects, but as a user my biggest gripe with FF is the lack of proper multilingual spellchecking.

This has been on their Bugzilla for 20 years:

https://bugzilla.mozilla.org/show_bug.cgi?id=69687

Re: What happened to Firefox Send?

#170

I wish we could get every major OS to work on an open standard for file transfer from device to device (locally).

+1 AirDrop is pretty cool but proprietary.

Android Beam looked promising but Google killed it for something proprietary. Samsung had an updated version that used WiFi Direct, but I don't know if it was open.

It seems that something that was somewhat plugable would be very useful.

- NFC or bluetooth for setup. - Bluetooth, Wifi Direct or Internet for transfer.

Mesh networking would be cool as well but I don't think it is actually needed for the MVP.

Post reply on HN