Using send.vis.ee as default host
ffsend
uses send.vis.ee as default host (in v0.2.65+).
I am hosting this instance myself. That way I can ensure best performance, availability and security.
You may choose to use any other host when uploading with the --host <URL>
flag or FFSEND_HOST
variable.
See a list of public Send instances here: https://github.com/timvisee/send-instances/#instances
The send.vis.ee instance
- The instance has been running for 1+ years, without any real issues.
- The instance runs a Send fork, which I maintain: https://github.com/timvisee/send
- The instance is hosted in the Netherlands (Amsterdam), people from the USA might experience ~130ms of latency.
- The instance does log IP addresses as part of an access log, these are kept for 24-hours.
- I may block suspicious/malicious IP addresses, when uploading 100's of GBs for example.
- I'll try to keep the instance running as long as I'm able to.
Hosting this isn't free. I'm paying this myself with the help of some generous donators.
If you'd like to show your support for this, please consider a donation: https://timvisee.com/donate
In case have to stop hosting the service, I'll try to do the following:
- I'll show a warning banner on the webpages noting the instance may shutdown.
- After a while, I'll disable the ability to upload.
- I'll keep the instance running so that uploaded files can still be downloaded, until all uploads have expired.
Security
If case you're wondering what this means from a security standpoint, note that Send uses end-to-end encryption so this isn't a real concern. See security.
Additional info
On first release, ffsend
used the original Mozilla Send instance (https://send.firefox.com/
). This has been down for a while, and so a different default host had to be chosen. The first intention was to do this temporarily until it came back up again. This is now a permanent thing.
Feel free to comment on any of this within this issue.
Related #100 (closed), #101 (closed)