zlacker

Send: Open-source fork of Firefox Send

submitted by leonry+(OP) on 2024-10-19 12:17:15 | 278 points 133 comments
[view article] [source] [go to bottom]

NOTE: showing posts with links only show all posts
1. metada+gm[view] [source] 2024-10-19 16:26:33
>>leonry+(OP)
This is cool, sharing files larger than 1GB still remains challenging these days.

How easy is it to self-host? I don't see any Docker instructions.

https://gitlab.com/timvisee/send

P.s. Kind of odd that the site links to Github, but the GH repo is only a mirror of the official Gitlab.

◧◩
5. ranger+Lo[view] [source] [discussion] 2024-10-19 16:53:57
>>metada+gm
https://github.com/timvisee/send-docker-compose
◧◩
6. ranger+bp[view] [source] [discussion] 2024-10-19 16:56:22
>>mlok+Mn
There doesn't appear to be a technical reason, it appears to just be a default configuration setting that was a holdover from Mozilla's imposed limits when Firefox Send was still around.

https://old.reddit.com/r/selfhosted/comments/1bwqxit/is_ther...

7. deskr+dp[view] [source] 2024-10-19 16:56:32
>>leonry+(OP)
As a side note, you can also simulate various network problems in the linux kernel via tc: https://www.baeldung.com/linux/network-failures-simulation
13. chme+5w[view] [source] 2024-10-19 17:56:14
>>leonry+(OP)
There is also filebin.net: https://github.com/espebra/filebin2/

And pwndrop: https://github.com/kgretzky/pwndrop

And lots of others.

16. benatk+9y[view] [source] 2024-10-19 18:13:21
>>leonry+(OP)
The title heavily implies that Mozilla's is closed-source. It isn't: https://github.com/mozilla/send

Actually since it says forked it implies that Mozilla maintains a closed-source version. No, it was cancelled.

18. gpm+Xy[view] [source] 2024-10-19 18:20:04
>>leonry+(OP)
Slightly off topic: I'm a fan of solutions like https://webwormhole.io/ - 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.
◧◩
19. LWIRVo+LA[view] [source] [discussion] 2024-10-19 18:35:33
>>mlok+Mn
There are other variants with different file size limits https://github.com/timvisee/send-instances Maybe performance based or something depending on those hosting these instances?
21. CT4u87+gD[view] [source] 2024-10-19 18:57:07
>>leonry+(OP)
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.

[0] https://localsend.org/

◧◩
22. promis+SD[view] [source] [discussion] 2024-10-19 19:03:01
>>benatk+9y
The Thunderbird team is working on a fork!

"The Thunderbird team was very sad when Firefox Send was shut down. Firefox Send made it possible to send large files easily, maybe easier than any other tool on the Internet. So we’re reviving it, but not without some nice improvements. Thunderbird Send will not only allow you to send large files easily, but our version also encrypts them" - https://blog.thunderbird.net/2024/10/thunderbird-annual-repo...

◧◩◪
23. cpeter+cF[view] [source] [discussion] 2024-10-19 19:13:34
>>promis+SD
Firefox Send used E2E encryption. The key was generated on the web client and not shared with the Send server.

https://web.archive.org/web/20200226024845/https://www.wired...

◧◩
29. blacks+RJ[view] [source] [discussion] 2024-10-19 19:47:51
>>gpm+Xy
I am partial to croc[1] which will send directly on your local network, or encrypted through a relay across the 'net.

1: https://github.com/schollz/croc

◧◩
34. loveth+RO[view] [source] [discussion] 2024-10-19 20:27:43
>>Arubis+3s
For Firefox Send, it was actually malware and spearfishing attacks that were spread.

The combination of limited file availability (reducing the ability to report bad actors), as well as Firefox urls being inherently trusted within orgs (bypassing a lot of basic email/file filtering/scanning), was the reason it became so popular for criminals to use. Like we've seen in the spearfishing attacks in India[1].

[1]: https://www.amnesty.org/en/latest/research/2020/06/india-hum...

39. leonry+xR[view] [source] 2024-10-19 20:52:39
>>leonry+(OP)
A command line version by the same author: https://github.com/timvisee/ffsend
◧◩◪◨
55. benatk+Uf1[view] [source] [discussion] 2024-10-20 01:35:42
>>Vinnl+VF
I wouldn’t be surprised if that hash fragment is sent to URL previews in otherwise encrypted chats. I did that too in my own program and it felt wrong. https://codeberg.org/macchiato/encshare-app I think I’ll change it, if not in my old project then in the next one.
◧◩
56. qudat+jg1[view] [source] [discussion] 2024-10-20 01:39:40
>>Arubis+3s
Checkout https://pipe.pico.sh which is a system for networked Unix pipes using ssh.
◧◩◪
83. nanna+r02[view] [source] [discussion] 2024-10-20 13:01:02
>>promis+SD
The excellent FileLink plugin for Thunderbird already makes it a sinch to transmit a file via a Next/Owncloud instance instead of as an attachment to an email. Worth running a *cloud instance just for it imo.

https://gitlab.com/joendres/filelink-nextcloud

◧◩
87. j1elo+o32[view] [source] [discussion] 2024-10-20 13:35:09
>>deskr+dp
I based off someone's quick notes and made it a ready to use script, in case it's useful for anyone:

https://github.com/j1elo/slow-network

Your article is very interesting and details some practical use cases, thanks! I will read it to see if there are any new ideas to incorporate.

89. melice+o42[view] [source] 2024-10-20 13:47:31
>>leonry+(OP)
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.

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.

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).

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 :-)

[1] http://www.helixee.me/limpact-ecologique-des-e-mails/ (in French)

◧◩◪◨⬒⬓
97. jamal-+I62[view] [source] [discussion] 2024-10-20 14:09:47
>>beepbo+662
No I'm offering that it's incredibly wrong to go bean counting email co2 usage when this is a dead end solution blaming end users for a problem caused by large corporations. It causes people to take environmentalism less seriously and doesn't change a thing for the greater good.

It's not letting me reply to your further comment but here's some links for you to really 'get it'

https://www.clf.org/blog/the-truth-about-carbon-footprints/

https://www.theguardian.com/commentisfree/2021/aug/23/big-oi...

106. Pooge+U82[view] [source] 2024-10-20 14:33:39
>>leonry+(OP)
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)

[1]: https://www.projectsend.org/

◧◩◪◨⬒⬓⬔⧯
107. snowe2+Ja2[view] [source] [discussion] 2024-10-20 14:54:07
>>immibi+9H1
The fbi literally only investigates if the ncmec tells them to.

https://www.fbi.gov/investigate/violent-crime/vcac

◧◩◪◨
111. lenova+Ri2[view] [source] [discussion] 2024-10-20 16:01:45
>>_-_-__+9j1
https://github.com/localsend/protocol

Defaults:

- Multicast UDP for discovery

- HTTP for file transfer

Will work in an office, but not for a email transfer to a customer

◧◩
121. mainfr+DX2[view] [source] [discussion] 2024-10-20 21:48:13
>>CT4u87+gD
I love Snapdrop [0] for that use case, since it doesn't require downloading/installing an app.

[0] https://snapdrop.net/

◧◩◪◨⬒⬓⬔⧯
126. dragon+Fr3[view] [source] [discussion] 2024-10-21 04:11:11
>>halJor+4h3
Note that this is specific to CSAM, not crimes in general. Specifically, online service providers are required to report any detected actual or imminent violation of laws regarding child sex abuse (including CSAM) and there are substantial fines for violations of the reporting requirement.

https://www.law.cornell.edu/uscode/text/18/2258A

[go to top]