Firefox Send - Simple, private file sharing from the makers of Firefox
-
I use Send a lot, would love to have this as well. As @mehdi said, the use cases are a bit different. I haven't had any practical use for FilePizza but it's great for some p2p data transfer testing Whereas with send, there is a firefox extension using which you can upload screenshots, clips automatically.
-
@jdaviescoates said in Firefox Send - Simple, private file sharing from the makers of Firefox:
I guess someone could conceivably pick up and run with the source code, but I'm not going to hold my breath
Someone did - https://github.com/timvisee/send
-
While more options are good, I feel like with file pizza, jirafeau, and now bitwarden send, we have a lot of very solid options in this space. Still, I'm glad someone revived the project!
-
Community fork of Send:
https://github.com/timvisee/send
https://send.vis.ee/EDIT: Sorry, I see this has been posted by @girish already
-
@atridad Absolutely agree. Jirafeau working nice and stable and Bitwarden is perhabs the best hardened Solition with Rust.
-
Hey folks, I like Send because it integrated with Thunderbird, etc and saves me the step of uploading something to my Jirafeau (also, I can never remember how to spell it).
What's involved in taking their Docker compose file and turning it into a Cloudron app? It looks like if it were easy, somebody would have done it already and I wonder if I am missing something.
Thanks for letting me comment on an ancient post
-
Thanks @girish. I am using https://addons.thunderbird.net/en-US/thunderbird/addon/filelink-provider-for-send/ with Betterbird/Thunderbird.
-
@3246 I remember looking into this project before. Issue is that it has no concept of authentication. Essentially, you have to set up something where anyone can upload anything. This is dangerous especially for Cloudron because some DMCA notice or equivalent will ban your entire server and not just the send instance.
See also https://github.com/timvisee/send/issues/32 and https://github.com/timvisee/send/issues/108 . IMO, best to just host this outside Cloudron in a separate server.
-
@3246 said in Firefox Send - Simple, private file sharing from the makers of Firefox:
Jirafeau (also, I can never remember how to spell it)
Why do you need to know how to spell it? e.g. I have my instance installed at https://fileshare.domain.tld
-
@girish said in Firefox Send - Simple, private file sharing from the makers of Firefox:
@3246 I remember looking into this project before. Issue is that it has no concept of authentication.
Surely on Cloudron that wouldn't be a problem as it could use Cloudron's built in proxy auth or whatever it's called? (like you already do with lots of other apps without auth)
@girish said in Firefox Send - Simple, private file sharing from the makers of Firefox:
Via that I found this similar tool which does have simple authentication options:
https://github.com/psi-4ward/psitransfer/
https://psi.cx/2017/psitransfer-installation/It's a dockerized node app so should be simple to package for Cloudron, I'd guess.
-
@jdaviescoates said in Firefox Send - Simple, private file sharing from the makers of Firefox:
Why do you need to know how to spell it? e.g. I have my instance installed at https://fileshare.domain.tld
It was meant as a bit of a joke, yes I have called it wetransfer.domain.tld because most folks here know what that means
-
@3246 said in Firefox Send - Simple, private file sharing from the makers of Firefox:
@jdaviescoates said in Firefox Send - Simple, private file sharing from the makers of Firefox:
Why do you need to know how to spell it? e.g. I have my instance installed at https://fileshare.domain.tld
It was meant as a bit of a joke, yes I have called it wetransfer.domain.tld because most folks here know what that means
-
@girish Interesting point I never considered as I'd be using the Send app for known users and not publicising it. Although I am not stopping anyone who finds it from using it... something I should really curtail, but the risk of that is low.
I think the DMCA issue can be tackled with a disclaimer before users install the app?
-
@3246 said in Firefox Send - Simple, private file sharing from the makers of Firefox:
I think the DMCA issue can be tackled with a disclaimer before users install the app?
Yeah, and we already have Jirafeau and Surfer and Calibre Web and Emby and Jellyfin and SickChill and loads of other apps that could easily be used to share files you're technically not supposed to be sharing! (and frankly, almost certainly are being used to do exactly that)
-
@jdaviescoates Apparently, none of the client side works if you put an auth wall in the front (from my reading of the github issues I linked previously). It's meant to be a public site as it stands it seems.
To be clear, I have nothing against this on Cloudron, but it's low priority atm since I suspect it's quite dangerous to run this on a Cloudron instance (maybe I am not understanding how it's deployed). You might think your instance is private, but your file link will get passed around and anyone can upload anything.
-
@girish said in Firefox Send - Simple, private file sharing from the makers of Firefox:
it's low priority atm
Yeah that doesn't bother me since Jirafeau does the job (at least for me)
since I suspect it's quite dangerous to run this on a Cloudron instance (maybe I am not understanding how it's deployed). You might think your instance is private, but your file link will get passed around and anyone can upload anything.
I think lots of us are already running public instances of Jirafeau tbh. I don't get what is so different/ more dangerous about Firefox Send?
-
@jdaviescoates said in Firefox Send - Simple, private file sharing from the makers of Firefox:
I think lots of us are already running public instances of Jirafeau tbh. I don't get what is so different/ more dangerous about Firefox Send?
You can restrict uploads in Jirafeau - https://docs.cloudron.io/apps/jirafeau/#restricting-uploads . These things are usually only a problem only when it hits you and then it's very hard to "fix" since the service provider won't listen. For example, there have been many posts here in the past about insecure website warning from Google Chrome because of bad content hosted (by mistake) or A records pointing to some other server.