189
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Sep 2023
189 points (99.5% liked)
Open Source
28943 readers
350 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 4 years ago
MODERATORS
Also has the huge advantage for me that it actually works. I could never get Syncthing to work no matter how much I tweaked it. This worked instantly.
And the interface is not a mess too.
For Syncthing I had to add a bunch of rules to my firewall to allow the necessary connections between my PC and smartphone. And for that I had to find, install and familiarize myself with a fire wall first. And after that ensure that the fire wall service is running always. Summa summarum: it's not something that is likely to work out of the box.
The great thing about Syncthing is that once you have it set up properly it really does work. It silently does its thing in the background and I never think about it
Haven't used LocalSend yet but I imagine it's going to be much less of a pain if the traffic is all routed through the Brower.
I agree on Syncthing's UI, and it did take me some time to understand it and get it working right. But I could only get LocalSend to accept files on my Pixel from my PC when I had the app open. Even with quick save turned on, it wouldn't accept the file without having the app open. But maybe that's the point of LocalSend? More deliberate file sharing?