Best of luck to the author! My understanding is that anything that makes large file sharing easy and anonymous rapidly gets flooded with CSAM and ends up shuttering themselves for the good of all. Would love to see a non-invasive yet effective way to prevent such an incursion.
For local network sharing between my devices I tend to use LocalSend [0] which is absolutely brilliant, pretty much replaced my USB stick for transferring files/folders between devices on the same network.<p>[0] <a href="https://localsend.org/" rel="nofollow">https://localsend.org/</a>
The title heavily implies that Mozilla's is closed-source. It isn't: <a href="https://github.com/mozilla/send">https://github.com/mozilla/send</a><p>Actually since it says forked it implies that Mozilla maintains a closed-source version. No, it was cancelled.
What I'd love to have is a <i>deposit</i> of files to be shared within a group of people.<p>Say we're 8 friends traveling through the middle of Greenland (read: no niceties like WiFi), and on the evening we want to share the photos of the day with everyone else.<p>In short, an evolution of the myriad of file sending copycats that exist: the same idea but for a shared bucket of files (I don't think doing N individual shares fits the bill, that'd just be a poor man's solution for the lack of a proper alternative)<p>Commenting this in hopes that the HN popular wisdom knows about something similar! :)
This is cool, sharing files larger than 1GB still remains challenging these days.<p>How easy is it to self-host? I don't see any Docker instructions.<p><a href="https://gitlab.com/timvisee/send" rel="nofollow">https://gitlab.com/timvisee/send</a><p>P.s. Kind of odd that the site links to Github, but the GH repo is only a mirror of the official Gitlab.
There is also filebin.net: <a href="https://github.com/espebra/filebin2/">https://github.com/espebra/filebin2/</a><p>And pwndrop: <a href="https://github.com/kgretzky/pwndrop">https://github.com/kgretzky/pwndrop</a><p>And lots of others.
As others have said, I use a combination of LocalSend on all my devices (Win64, Linux, iOS…) and a Syncthing folder that I call QuickSync and added as a shortcut to all of my file managers a few years ago. Syncthing, in particular, works so well that you don’t even notice it, until you have a file conflict. It’s a great solution to have files synced easily.
Is there a version of this, where i can allow emailadresses to upload things/download things/share things with other emailaddresses?<p>Like firefox send but some version of authentication via email? I am aware that i would need a way to send emails so the emailaddresses get authentication
If you don't want to self-host and you don't want to trust someone else's service (I don't know anything about this server) you get Bitwarden Send with the $10/year premium plan.
For those of you with a server on their hands, please consider hosting ProjectSend[1] to share files with friends. I haven't used it extensively but it's great for sharing files here and there. (I'm not affiliated in any way, just a happy user)<p>[1]: <a href="https://www.projectsend.org/" rel="nofollow">https://www.projectsend.org/</a>
Even if Mozilla retired the service, they should've at least kept the repository active so people can send patches.<p>I find this applications like this very useful to self-host. Sometimes I need to send someone a file quickly and this can come in handy. I don't need to allow uploads from everyone and I can just whitelist IPs for the upload URL.<p>At present I'm using Project Send.
Slightly off topic: I'm a fan of solutions like <a href="https://webwormhole.io/" rel="nofollow">https://webwormhole.io/</a> - which lets you send the file directly from one computer to the other via webrtc instead of uploading to a middleman server... at the expense of not being able to generate a link that you can send to someone else and forget about.
As a side note, you can also simulate various network problems in the linux kernel via tc: <a href="https://www.baeldung.com/linux/network-failures-simulation" rel="nofollow">https://www.baeldung.com/linux/network-failures-simulation</a>
I recently launched www.64.surf that uses the URL to send files, obviously a much smaller file size, but was fun to build regardless.<p>Basically, base64 encode the file, inject it in the URL and then allows you to share it with other people.
I self host this and probably the best looking and working file sharing app. Works well for me as the files are ephemeral and the upload is protected by cloudflare access.
A command line version by the same author: <a href="https://github.com/timvisee/ffsend">https://github.com/timvisee/ffsend</a>
In my opinion, the idea behind Firefox send was a real step towards a more greener IT. The elephant in the room here that no one is talking about is the impact of the email with attachment on climate change. In 2018 (that's the best I could find) nearly 600 billion emails are distributed every day around the world. Im' pretty sure this is a lot more nowadays. No matter the truth, this colossal figure is not without impact on the environment. From the PC to the data center to the small lithium battery of a smartphone, email consumes electricity and its consequences on greenhouse gas emissions are far from negligible.<p>Studies on the subject (very few actually, if you have intel on that matter, let me know) have already been conducted and reveal that a simple email with an attachment of 1MB produces around 15 grams of CO2[1]. Obviously, this figure increases with the size of the email. This is the case, for example, when the email includes large attachments or if the email is sent to several recipients.<p>With the use of the IMAP protocol, one email sent has at least 6 permanent copies (from the sent item in the sender email client to the inbox of the recipient, through sender and recipients email server which hopefully have long term archiving).<p>A solution like firefox send with automatic shredding of the file after an expiration period to replace email attachment would drastically reduce the consequences of email usage on greenhouse gas emissions. It would also resolve other issues related to sending files by email, but that would make this post waaaayyy to long :-)<p>[1] <a href="http://www.helixee.me/limpact-ecologique-des-e-mails/" rel="nofollow">http://www.helixee.me/limpact-ecologique-des-e-mails/</a> (in French)