Yes, I was using the last version in all machines (some mint, some arch).
I was trying to sync seven machines in three different physical locations, some with slow internet connectivity; only one machine in each location had its syncthing ports open to the internet through NAT. I'm not sure it's a supported use case: syncing in the same LAN generally worked fine, but changes often didn't propagate correctly to other locations; for instance a folder name change sometimes was not propagated to the remote locations, and after some time the machine in which the rename had happened detected that the rest of the machines in the syncthing group had a folder which didn't exist locally (the folder with the old name), and downloaded it from its peers. The result was that the folder was duplicated everywhere, with both the old and the new name.
The same happened sometimes with deletions: sometimes they didn't propagate over LAN boundaries, and this resulted in the deleted files reappearing after some time.
A machine staying "syncing..." forever also happened sometimes, requiring a manual restart of the service. I couldn't reliably reproduce it though.
I like the project and I'm sure if I reported the issues in github they'd have given support. I wish I had the time for properly reporting and investigating, but I really needed a syncing solution I could trust for a small business and I needed it ASAP, so I settled for owncloud (which for the moment has not given me any surprises). I will try to find some time to reproduce the bugs in my personal machines and report them, but I really didn't have the time when I found them.
I was trying to sync seven machines in three different physical locations, some with slow internet connectivity; only one machine in each location had its syncthing ports open to the internet through NAT. I'm not sure it's a supported use case: syncing in the same LAN generally worked fine, but changes often didn't propagate correctly to other locations; for instance a folder name change sometimes was not propagated to the remote locations, and after some time the machine in which the rename had happened detected that the rest of the machines in the syncthing group had a folder which didn't exist locally (the folder with the old name), and downloaded it from its peers. The result was that the folder was duplicated everywhere, with both the old and the new name.
The same happened sometimes with deletions: sometimes they didn't propagate over LAN boundaries, and this resulted in the deleted files reappearing after some time.
A machine staying "syncing..." forever also happened sometimes, requiring a manual restart of the service. I couldn't reliably reproduce it though.
I like the project and I'm sure if I reported the issues in github they'd have given support. I wish I had the time for properly reporting and investigating, but I really needed a syncing solution I could trust for a small business and I needed it ASAP, so I settled for owncloud (which for the moment has not given me any surprises). I will try to find some time to reproduce the bugs in my personal machines and report them, but I really didn't have the time when I found them.