• Content Count

  • Joined

  • Last visited

About mdovey

  • Rank
  1. The MyDevices\Identity thing only meets one specific use case, which is unfortunate as it is pretty much forced upon you by Sync 2.0 Pro (unless you use multiple identities but then the licensing costs increase). As a raised during the beta, a better approach would be to have the concept of a device group - a device can belong to multiple groups. When you share a folder you can choose to share it with a particular device (or devices) or with a device group (or multiple device groups) or a mixture of both. However, I don't think they allowed the beta to run long enough to consider all of this.
  2. The only way I can see to not use the "My Devices" feature is not create a new identity for each individual device (as linking a device to an existing identity automatically adds it to My Devices) - but, as far as I can tell, if I do that, I will then require a separate Pro license for each device (I have five devices so the cost would be $200 per annum!).
  3. I'm interested in the download on demand feature of BTSync 2.0 but not the automatic sharing of folders across all linked devices. I understand that the free version will disable both features. Is there anyway to have the download on demand feature enabled but the automatic share of folders disabled in Pro? The only other way I can think is to have a seperate identity for each device but that would make the license cost excessive.
  4. To share a folder between two devices in sync 1.4 you had to share a text key between those devices. As the key was completely self contained you had complete control over the transfer of this key and so could do so in a way which you could be sure was not eaves dropped. In sync 2.0 when you manually share a folder it now creates a link (beginning Surely this means that as well as being a single point of failure, the server also knows everytime you share a folder (information which could be shared with NSA etc?) Is the encryption key (or certificate) transfered via that server (which means that if that server was compromised it would also compromise anyone using sync 2.0)?
  5. Any update on this - I've been patiently waiting for btsync 1.4 as it was supposed to fix this problem, so it is very disappointing that it still persists. Matthew
  6. 1.4.75 still prevents hibernate because it still writes sync.dat every 10 minutes as outlined above. More precisely, every 10 minutes it creates a new file removes sync.dat.old renames sync.dat to sync.dat.old renames to sync.dat As the minimum threshold on the synology is 10 minutes idle before the disks hibernate, this disk access to sync.dat (etc.) every 10 minutes prevents hibernation. Neither changing the config_refresh_interval value nor the folder_rescan_interval changes the frequency btsync writes to sync.dat Matthew
  7. BTSync 1.3.94 still prevents disk hibernation on Synology NAS's. It looks like it is still writing every 10 minutes regardless of the setting of the rescan interval. Any chance of a resolution or a configuration setting for when btsync writes sync.dat Matthew
  8. Yes, I've increased folder_rescan_interval to 6 hours, but this doesn't change how often sync.dat and settings.dat get updated. Matthew
  9. I've installed ZFS on a server running btsync, and scheduled regular snapshots. All the folders I'm sharing via btsync are shared with this server. That way if things go wrong I can roll back to a known good snapshot. Matthew
  10. I have (to 6 hours), but that does not seem to influence how often btsync automatically saves settings.dat or sync.dat (which is still 30 minutes and 10 minutes respectively). Matthew
  11. btsync (1.1.48 and 1.1.70) still doesn't allow my synology box to hibernate the HDD Switching on the debugging option in the synology box and checking the logs. btsync seems to write and sync.dat new every 10 minutes (the minimum disk idle time before the synology hibernates the HDDs is 10 minutes) even if sync.dat hasn't changed. Also it seems to write settings.dat every 30 minutes, again even if these haven't changed. I assume that these timed writes are just a precaution and these files are also saved should change actually happen. Could the times when btsync automatically saves these failed be configured? Matthew