Slashdot Mirror
Mozilla's Send is Basically the Snapchat of File Sharing (theverge.com)
Mozilla has launched a new website that makes it really easy to send a file from one person to another. From a report: The site is called Send, and it's basically the Snapchat of file sharing: after a file has been downloaded once, it disappears for good. That might sound like a gimmick, but it underscores what the site is meant for. It's designed for quick and private sharing between two people -- not for long-term hosting or distributing files to a large group. It supports files up to 1GB, and after uploading something, it'll give you a link to send to someone else. That link will expire once they've downloaded it or once 24 hours have passed.
I'd bet people who "think of the children" would use a service like this a lot.
https://xkcd.com/949/
I know my parents want something like this.
Here's an alternate idea for Mozilla:
- Fix the browser; get back to the original mission of a fast no-bloat browser
- Fire everyone but the five developers it takes to do that and donate any excess money left in the Foundation to the EFF
I use to share videos of my wife
I really couldn't care less if you do or do not see the point, as long as you keep those videos of your wive coming.
CLI paste? paste.pr0.tips!
Do you know what else they use?
Phones! The postal service! Roads! Aircraft! Railways! Banks!
Better shut down the entire society! Think of the children!
I get...
Your browser is not supported.
Unfortunately this browser does not support the web technology that powers
Firefox Send. You’ll need to try another browser. We recommend Firefox!
...when I try to access the service.
If Mozilla's strategy is to lure back old users with web based services like Send, they are going to have to ensure that the service works seamlessly for the people that I exchange files with, without trying to force them to change their browser first. Even if I eventually make the switch to Firefox, I can hardly expect everyone that I exchange files with to do the same in order to be able to receive the files that I send.
FTP is set up to provide a remote file system access, with directories, subdirectories and different access rights to different areas.
And it has the ability to traverse restrictive firewalls through the secondary socket used for data being set up as active (PORT) or passive (PASV). And the ability to have data servers that serve the content, while the control channel server only handles the authentication and command parsing.
What it is not intended for is security. There are add-on extensions, but it's still not a good choice.
Nor is it suited for easy configuration. The great majority of FTP servers are incorrectly set up, especially regarding firewall rules, where the admins (and I use this term loosely) do not understand the difference between incoming and outgoing ports and directions, and now FTP is somewhat special here, in that it uses two sockets, not just one, and one of them might be in the other direction and needs a reverse firewall rule.
These days, sftp has all but taken over for ftp for automated / command line use, and web based upload/download for the masses.