Live data from Hacker News

What happened to Firefox Send?

support.mozilla.org

181–190 of 267 posts

Re: What happened to Firefox Send?

#181
post #64

Earlier quoted context omitted.

We still have Magic Wormhole though and it's awesome! (at least for techies) https://magic-wormhole.readthedocs.io/en/latest/welcome.html

"We" as in "the people who knows how to use the command line". Unfortunately very few of the people I send files to knows that. There's https://webwormhole.io/ and https://file.pizza/ , but can I know what they really do behind the scenes? Native open-source software for this would be a dream come true. It's 2020 and I still wrestle with sending files between devices. And no, don't take this as a wish for creating ju…

If you're just sending files between devices that you own, KDE Connect [1] is cross-platform and works pretty well.

[1] https://kdeconnect.kde.org/

Re: What happened to Firefox Send?

#182
post #166

Earlier quoted context omitted.

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?

Pretty much. They suddenly took it down for 'maintenance'. The relaunch was delayed. Mozilla released a statement on laying off 250 employees. That's when I figured it wouldn't come back online again.

I don't have any specific knowledge, but my general impression was that malware was a very real issue that nobody could come up with a realistic response to. Other than that, it seems like Send was a breakout success.

(I work for Mozilla, but mostly on the JS engine.)

Re: What happened to Firefox Send?

#183
post #168

The challenge I have is when someone non-technical needs to send me a very large file. I’ve resorted to spinning up a pureftp server in docker and having them drop it there.

jokes on you https://developers.google.com/web/updates/2020/09/chrome-86-...

I don’t think you could write FTP via Firefox...I think it was read-only?

Re: What happened to Firefox Send?

#184
post #64

Earlier quoted context omitted.

We still have Magic Wormhole though and it's awesome! (at least for techies) https://magic-wormhole.readthedocs.io/en/latest/welcome.html

"We" as in "the people who knows how to use the command line". Unfortunately very few of the people I send files to knows that. There's https://webwormhole.io/ and https://file.pizza/ , but can I know what they really do behind the scenes? Native open-source software for this would be a dream come true. It's 2020 and I still wrestle with sending files between devices. And no, don't take this as a wish for creating ju…

Couldn't someone pretty easily write a native GUI or browser app that wraps Magic Womrhole?

Re: What happened to Firefox Send?

#185
post #182

Earlier quoted context omitted.

Pretty much. They suddenly took it down for 'maintenance'. The relaunch was delayed. Mozilla released a statement on laying off 250 employees. That's when I figured it wouldn't come back online again.

I don't have any specific knowledge, but my general impression was that malware was a very real issue that nobody could come up with a realistic response to. Other than that, it seems like Send was a breakout success. (I work for Mozilla, but mostly on the JS engine.)

With the utmost respect, can somebody please tell if anyone thought of requiring a Firefox account? Or charge $2/mo and go from there? Products usually iterate on design and security, no? Not just give up right away?

Some of us recommended a Firefox+ service that bundles Firefox Send, the VPN, etc. and charge a monthly premium. I would've paid a lot of money. Nothing makes any sense looking from outside!

Re: What happened to Firefox Send?

#186
post #178
post #128

Earlier quoted context omitted.

It wasn't a "reasonable speculation". More like pure fiction, simply intended to denigrate the target.

You criticised their guess as baseless just to follow up by denying their numbers without sources. Only one of you two chose to present a fact without backing it up. There's also this gesture of assuming that the opponent is motivated by evil intentions, which is almost always wrong. On topic though: Our conversation could really benefit from some actual numbers. I made a quick search but didn't find anything.

A quick search turned up this for me: https://blog.mozilla.org/firefox/the-new-firefox-by-the-numb...

It's a bit dated, but at the time of the Quantum release,

> How many authors contributed code?

> More than 700 authors contributed code to Firefox ...

and I guess the majority of those code authors were working for Mozilla.

It seems unlikely there's been a 90% reduction in the engineering effort being put into Firefox in the last couple years.

Re: What happened to Firefox Send?

#187

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…

should be obvious what happened "malware" means it facilitated child porngraphy and far worse I mean what could possibly go wrong when you have such a public and easy to use service that "encrypts" on the client side and allows self destructive payloads? that or it was a honey pot and got enough of you perverts sort of like google 411

Re: What happened to Firefox Send?

#188

Earlier quoted context omitted.

You're assuming the good case of people sending naive users a virus. But think of two consenting parties sharing cp or something else. It's a legal hell hole.

Why would it be mozillas fault? If someone sends cp via snailmail, will the postal service get sued?

I wonder how mega.nz managed to withstand what killed send.

Re: What happened to Firefox Send?

#189
post #182

Earlier quoted context omitted.

Pretty much. They suddenly took it down for 'maintenance'. The relaunch was delayed. Mozilla released a statement on laying off 250 employees. That's when I figured it wouldn't come back online again.

I don't have any specific knowledge, but my general impression was that malware was a very real issue that nobody could come up with a realistic response to. Other than that, it seems like Send was a breakout success. (I work for Mozilla, but mostly on the JS engine.)

2 questions:

1) how?

2) how did you know?

I can't quite see how malware would be sent with this? An exploiter uploads a file, then gets someone to download it - where's the secret sauce, why does this work better than hosting the file; each file is only downloadable once IIRC?

Next, how were Mozilla able to determine the contents of files shared (but not able to just drop by hash known malware, or run antivirus heuristics)?

Post reply on HN