foo

Your whole response can be summarized as "trust us," which I don't. My private data is too important to be left to closed source. Moved on to syncthing a while back, and I encourage others to do likewise.

I'd like to see proof of this as it's absolutely a dealbreaker for me. I'm getting the same error. I already have directory /nas/sync/foo shared, and I cannot add directory /nas/sync/foo/bar as a separate shared directory. 1.0.134 Linux x86-64 (I also tried 1.1.15 and still get the same error)

The best fix would be for btsync web daemon to default binding to 127.0.0.1 instead of 0.0.0.0. In the meantime you can manually set that in the json config file: { "webui": { "listen": "127.0.0.1:8888" } }

Ah, now I understand. Yeah I totally agree, my low-end Synology NAS would not be a good choice if you need massive storage, consistently high throughput, tons of services/daemons running all the time etc.

The DS212j only costs $200 without the drives. I actually downgraded from a massive fileserver like you seem to be implying, that had 8 750GB hard drives (largest size at the time) in a hardware RAID controller with an i5 CPU, 4GB ECC RAM, etc. because it was way overkill (you don't need much CPU or RAM to run a file server) and used way too much power. The Synology NAS is already low power but it will go into sleep mode when there's no network access, which was important for me. Being able to do RAID-1 was also important. These two features alone would be very hard to implement with somet