- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
You can also make a torrent very easily, which is the better method.
If you care about security, OnionShare beats all these webRTC implementations
Is this Firefox Send thingy centralized? Also I’ve read that it’s actually a dead project.
ffsend targets Send which is an actively maintained community fork of Firefox Send.
It’s not centralized, you can host your own or choose from the public send instances.
The Thunderbird team is actually looking to bring it back as part of their new (paid I believe) services along with Thundermail.
This is the community fork that is still maintained. There are multiple instances like invidious and from what I understand it is relatively easy to self host. Since it is only for short term file storage and its E2EE I do not really mind using one of the public instances.
Any difference between croc and this?
If I’m not mistaken, ffsend generates a link that you can share with non-tech people (which is a big difference in my book).
It says on the github page that this is limited to 1gb only
I’ve not heard of “Firefox Send.” Why would I use something like this instead of
scpor Nextcloud?Because the other person might not have ssh or access to your nextcloud
I always liked the concept of blaze, but it seems like development stopped 2 years ago.
https://github.com/blenderskool/blaze
Using webtorrents for multi-peer transfers & being able to UL/DL from a URL.
I’m confused, is this different than?
This site states “⚠️ Send will be terminated on May 24th. ⚠️ Costs are getting too high to keep hosting this service. Find an alternative instance here or host your own.”
It literally says “Firefox Send client” in the title.
