4 ms·

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 Mo

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 https://github.com/timvisee/ffsend I'm currently hosting a public Send instance myself to ffsend keep working. Let's see how long I can keep this going (and funded).

basilgohar 6y ago
I'm interested in knowing the infrastructure you've setup to continue this service.
- timvisee 6y ago
  It's rather simple actually. Currently hosting it on a clean DigitalOcean droplet with an additional disk, which has been running for ~2 months now. It runs Send in Docker. I set up this configuration for it: https://github.com/timvisee/send-docker-compose https://github.com/timvisee/send-docker-compose
  - basilgohar 6y ago
    I presume bandwidth and storage are the main concerns since I doubt compute dominates in this kind of service.
    - timvisee 6y ago
      You're right! Luckily files have a maximum lifetime of 1 day, which helps with storage. Almost no computing needed. Expensive en/decrypting operations are done on the client.
      - neolog 6y ago
        Do you know what you'll do when people start sharing illegal content?
        bfuclusion 6y ago
        Not worry about it? It's not like he can see it anyways, it's encrypted on the client.
        gilrain 6y ago
        That world certainly be the proper Silicon Valley approach: can this be used to harm people? shrug
        eertami 6y ago
        I'm confused how much responsibility you want to put on a service provider. If someone sends an encrypted email containing illegal content, is email then considered harmful?
        Spivak 6y ago
        I mean it's the dream, right? It's what we all wish we could build. You design a system that gives you (the hoster) zero ability to inspect, modify, block, censor, restrict any of your users' content and in doing so you're allowed to abdicate all responsibility for how the system is used because you're literally incapable of controlling it. Pure infrastructure with none of the messy real-world bits.
        timvisee 6y ago
        Good question. Simple answer: no. I've thought about it though, but haven't settled on anything yet. I can't inspect files. I'll add an abuse report notice soon, abuse@ is already live. I'll attempt to manually review cases. That doesn't prevent illegal sharing, but I think that's the best I can do. If things get out of hand, I might take the instance down. I don't want to support hosting illegal stuff. A newer Send version (yet to deploy) also shows a clear warning, and requires users to tick a confirmation box, when downloading through the webpage. I hope that helps preventing malware installations.
quyleanh 6y ago
Your tool is very useful for me. Have used it since a long time. First transfer.sh and now Firefox Send are closed. What service should I trust to send file quickly and securely.
- deleted 6y ago
  [deleted]
- Shared404 6y ago
  I've honestly fallen back to HTTP/SFTP. I just rent a VPS, temporarily host the file on there, and give whoever it is a link. Edit: If my threat model were to include protecting the contents of the file from the VPS provider I would probably encrypt it client side with GPG or something similar.
- timvisee 6y ago
  That's awesome to hear! You can still use ffsend for now, it still works and uses the Send instance I'm hosting (send dot vis dot ee). Some generous users started sponsoring me through GitHub, so that'll definitely help keep it alive longer. I haven't found a great alternative myself yet.
- rixtox 6y ago
  I started to used wormhole: https://github.com/warner/magic-wormhole https://github.com/warner/magic-wormhole There is also a Golang port: https://github.com/psanford/wormhole-william https://github.com/psanford/wormhole-william
cbkeller 6y ago
Thank you for building this and keeping it running!
- timvisee 6y ago
  Happy to do so!

basilgohar 6y ago

I'm interested in knowing the infrastructure you've setup to continue this service.

timvisee 6y ago
It's rather simple actually. Currently hosting it on a clean DigitalOcean droplet with an additional disk, which has been running for ~2 months now. It runs Send in Docker. I set up this configuration for it: https://github.com/timvisee/send-docker-compose https://github.com/timvisee/send-docker-compose
- basilgohar 6y ago
  I presume bandwidth and storage are the main concerns since I doubt compute dominates in this kind of service.
  - timvisee 6y ago
    You're right! Luckily files have a maximum lifetime of 1 day, which helps with storage. Almost no computing needed. Expensive en/decrypting operations are done on the client.
    - neolog 6y ago
      Do you know what you'll do when people start sharing illegal content?
      - bfuclusion 6y ago
        Not worry about it? It's not like he can see it anyways, it's encrypted on the client.
        gilrain 6y ago
        That world certainly be the proper Silicon Valley approach: can this be used to harm people? shrug
        eertami 6y ago
        I'm confused how much responsibility you want to put on a service provider. If someone sends an encrypted email containing illegal content, is email then considered harmful?
        Spivak 6y ago
        I mean it's the dream, right? It's what we all wish we could build. You design a system that gives you (the hoster) zero ability to inspect, modify, block, censor, restrict any of your users' content and in doing so you're allowed to abdicate all responsibility for how the system is used because you're literally incapable of controlling it. Pure infrastructure with none of the messy real-world bits.
      - timvisee 6y ago
        Good question. Simple answer: no. I've thought about it though, but haven't settled on anything yet. I can't inspect files. I'll add an abuse report notice soon, abuse@ is already live. I'll attempt to manually review cases. That doesn't prevent illegal sharing, but I think that's the best I can do. If things get out of hand, I might take the instance down. I don't want to support hosting illegal stuff. A newer Send version (yet to deploy) also shows a clear warning, and requires users to tick a confirmation box, when downloading through the webpage. I hope that helps preventing malware installations.

quyleanh 6y ago

Your tool is very useful for me. Have used it since a long time. First transfer.sh and now Firefox Send are closed. What service should I trust to send file quickly and securely.

deleted 6y ago
[deleted]
Shared404 6y ago
I've honestly fallen back to HTTP/SFTP. I just rent a VPS, temporarily host the file on there, and give whoever it is a link. Edit: If my threat model were to include protecting the contents of the file from the VPS provider I would probably encrypt it client side with GPG or something similar.
timvisee 6y ago
That's awesome to hear! You can still use ffsend for now, it still works and uses the Send instance I'm hosting (send dot vis dot ee). Some generous users started sponsoring me through GitHub, so that'll definitely help keep it alive longer. I haven't found a great alternative myself yet.
rixtox 6y ago
I started to used wormhole: https://github.com/warner/magic-wormhole https://github.com/warner/magic-wormhole There is also a Golang port: https://github.com/psanford/wormhole-william https://github.com/psanford/wormhole-william

cbkeller 6y ago

Thank you for building this and keeping it running!

timvisee 6y ago
Happy to do so!