• 8orange8@lemm.ee
      link
      fedilink
      arrow-up
      24
      ·
      1 year ago

      They have different usage scenarios.

      LocalSend is for the occasional sending of files/folders from A to B or B to A (One direction only).

      Syncthing’s primary usage is for keeping the exact same copies of files on A and B automatically.

      • Leraje@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        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.

        • sonnenzeit@feddit.de
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          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.

        • blueConifer@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          1 year ago

          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?