4 ms·

I'm crushed to see Firefox Send go away. It was an amazing tool. In the "This is why we can't have nice things category" it's sad to see yet another encrypted

I'm crushed to see Firefox Send go away. It was an amazing tool. In the "This is why we can't have nice things category" it's sad to see yet another encrypted file-sharing service that is inevitably shut down when someone starts abusing it to host malware or child porn.

AsyncAwait 6y ago
I've found croc[1] to be a good alternative, but not ideal for async unless you have a NAS. 1 - https://github.com/schollz/croc https://github.com/schollz/croc
Macha 6y ago
It's the one service of the new wave of Mozilla products I actually liked. Well, maybe lockwise might be ok, but I already have a password manager.
- zymhan 6y ago
  I use Lockwise since I'd been using Firefox Password manager for years. I keep my important passwords (Financial, etc) in Keepass, but for the myriad websites I use that require logins, Lockwise is a great solution. I'm also very impressed by it's iOS integration.
nine_k 6y ago
There is no way around it. Either [insert technology name] works for bad guys and good guys alike, or it does not work for bad guys and good guys alike. You can't make technology follow morals. The moral panic almost inevitably tilts the scales towards [insert technology name] not working for anyone, rather than allowing bad guys use it publicly. So bad guys use it privately, and good guys... well, they can also use it privately, if they are tech-savvy enough. Otherwise, tough luck.
- Spivak 6y ago
  Like it’s a pseudo-public file storage system. If you’re not going to put up the moderation effort and block the spread of malware, cp, phishing attempts, and spam then the people who would get kicked off of, say Dropbox, will migrate to your service and now you’re the company whose links are inherently sketchy. It’s not really a moral panic so much as it’s damaging to Mozilla’s reputation.
  - Reelin 6y ago
    You're missing the point. Dropbox isn't E2E encrypted. Send was. The technology is E2E encrypted file transfer via a central server. It doesn't matter whether the response is due to a moral panic or an attempt to protect their reputation. The end result is the same - reduced public availability of <insert technology here> while the bad guys generally continue using it the same as before.
    - nine_k 6y ago
      The parent comment had a good point, though: trust. If you run a public file sharing service, trusting a link shared through it becomes hard if it's overfilled with phishing and virus-laden fakes pretending to be legitimate things. Often you don't want the risk as a user, and definitely you don't want an association with a cesspool as a brand. Until trust is solved, running and using such a service remains problematic. It needs not be solved via content inspection, though; if I could verify the sender, I won't care about phishing links (and such links would cease to be useful for scammers and disappear). But this is a separate significant undertaking.

AsyncAwait 6y ago

I've found croc[1] to be a good alternative, but not ideal for async unless you have a NAS. 1 - https://github.com/schollz/croc https://github.com/schollz/croc

Macha 6y ago

It's the one service of the new wave of Mozilla products I actually liked. Well, maybe lockwise might be ok, but I already have a password manager.

zymhan 6y ago
I use Lockwise since I'd been using Firefox Password manager for years. I keep my important passwords (Financial, etc) in Keepass, but for the myriad websites I use that require logins, Lockwise is a great solution. I'm also very impressed by it's iOS integration.

nine_k 6y ago

There is no way around it. Either [insert technology name] works for bad guys and good guys alike, or it does not work for bad guys and good guys alike. You can't make technology follow morals. The moral panic almost inevitably tilts the scales towards [insert technology name] not working for anyone, rather than allowing bad guys use it publicly. So bad guys use it privately, and good guys... well, they can also use it privately, if they are tech-savvy enough. Otherwise, tough luck.

Spivak 6y ago
Like it’s a pseudo-public file storage system. If you’re not going to put up the moderation effort and block the spread of malware, cp, phishing attempts, and spam then the people who would get kicked off of, say Dropbox, will migrate to your service and now you’re the company whose links are inherently sketchy. It’s not really a moral panic so much as it’s damaging to Mozilla’s reputation.
- Reelin 6y ago
  You're missing the point. Dropbox isn't E2E encrypted. Send was. The technology is E2E encrypted file transfer via a central server. It doesn't matter whether the response is due to a moral panic or an attempt to protect their reputation. The end result is the same - reduced public availability of <insert technology here> while the bad guys generally continue using it the same as before.
  - nine_k 6y ago
    The parent comment had a good point, though: trust. If you run a public file sharing service, trusting a link shared through it becomes hard if it's overfilled with phishing and virus-laden fakes pretending to be legitimate things. Often you don't want the risk as a user, and definitely you don't want an association with a cesspool as a brand. Until trust is solved, running and using such a service remains problematic. It needs not be solved via content inspection, though; if I could verify the sender, I won't care about phishing links (and such links would cease to be useful for scammers and disappear). But this is a separate significant undertaking.