kos13

We had removed time diff from the Sync, it just compares time between two machines to find the right file during the collision. Could you please try to give us a clue what went wrong in your case?

Yes, we plan to turn autoupdate since all major changes are in product.

Try new build 1.1.22

1.1.22 will be available in few hours.

Sync just can't get to a maximum on small files. Try something bigger like 100 Mb files.

Sure it is. Fully agree with you.

Never say never We still consider this option.

I want to apologize for being silent for quite a while. Team was extremely busy working on new version of Sync. We had an option to release minor update earlier or go with something bigger. We decided to put all possible efforts to excite you again and make something big. New build is in testing and we should release it quite soon. Sync mobile builds performs really well, thank you for your help in testing. Thanks Kos

Sorry guys, we really needed to change the protocol and making it backward compatible would require quite a work.

Just want to check that your are not mixing Mbs (megabit per second) and MBs (megabyte per second). Sync shows speed in Mega Bytes per second.

Thank you, we will ask for a help, when we will be ready.

Please wait for the build after 1.1.15. We will fix that.

We will add option to add secret without need to scan a QR.

Could you please try new build 1.1.15. We made a lot of fixes since 1.0.132

PM me with your email

Can you please send us logs from the machine that changes IP? And please refer to this thread. Steps are

Until we have official BitTorrent Sync twitter, you could follow me at @klissounov where I will post all updates to Sync.

We do have specific plans for Sync for business. This version of Sync will cover some of your concerns and will have features that is required by enterprises and SMB. At the moment Sync is pure consumer product that might be used in some business cases.

Why this is important to you?

Thanks.

This was issue in 1.1.15 please wait for next build.

100% CPU happens when there are nodes with older versions trying to connect to your machine. This is fixed. Please wait for next build.

I just leave it here http://www.keylength.com/

We had fixed this issue, will be in next build.

Try 1.1.15 we fixed few crashes on 1.1.12