- cross-posted to:
- selfhost@lemmy.ml
- cross-posted to:
- selfhost@lemmy.ml
Heard about his on the self hosted podcast and just installed it and it works great. Dont use the given compose file just make your own with the linuxserver image. Here’s mine and it works over tailscale and through my reverse proxy.
version: "3"
services:
snapdrop:
image: "linuxserver/snapdrop"
volumes:
- /nasdata/docker/volumes/snapdrop/:/data
ports:
- "8090:80"
- "4430:443"
You must log in or register to comment.
I actually like PairDrop better, as it allows also linking devices that fail to find themselves on the network (for example if you run it behind a reverse proxy). It is obviously pretty similar though.
Just looked at that and might have to try that. had a couple issues with devcvices finding eachother at first, but a reboot of thee container fixed it. Might be handy for sending my gf something when out and about.
I just heard about this on the podcast and wanted to try it but pairdrop may be better. Thanks
I’ve always found snapdrop very very inconsistent. When it works is amazing, but it often as not doesn’t see other devices.
LocalSend, on the other hand, is excellent. It’s an app so needs to be installed but it available for about every platform desktop and mobile and is my go-to now.
Another recommendation for Localsend. But it’s cool that Snapdrop manages to do almost the same thing and does it in the browser. I can definitely see where it would be useful.
What’s the point of self-hosting Snapdrop though? Does it need a discovery server in there for WebRTC? Or does this just end up serving the same static files but now from a local server?
The main reason to self host snapdrop is that a good 60% of the time, when I really need it to work - it’s down.
This seems similar to KDE Connect? Am i missing something?
It’s quite a different use case, it’s meant to facilitate wireless transfer between any device through a browser tab without having to have any local software installed first. So think more like sharing full resolution photo to a friend’s device who is connected to the same wifi as you by just both of you opening the same url, snapdrop.net or pairdrop.net (fork with more features) or your own selfhosted url.
Ah, thank you! That makes sense.
The browser has to support WebRTC though.
😐😐😐
I woul recommend LANDrop, apart from some fiddling with my unusual firewall, it has apps for whatever phone os, sharing menu integration on mobile, works flawlessly locally
Awesome. Thanks for sharing.
Hah, just heard about it on the same place as well. I’m floored I’d never heard of it before, such a neat implementation. Planning on giving it a go sometime soon.
Also see pairdrop, it is a snapdrop fork that allows connecting devices on different networks using a numeric code and has other improvements.
Snapdrop is great. I don’t need it often, but when I do, it’s so simple and easy to use.
I didn’t know I needed this, I’m going to set this up right away Thanks for sharing!
this is cool, i’d love something similar that replicates the Firefox send-to feature which i often use to leave a tab waiting for me on another device.
What is the self-hosted podcast you mentioned?
https://selfhosted.show/ literally the self hosted podcast it’s pretty good imo.
