a) There is no functionality to "upgrade" a folder from 1.4 to 2.0
b) Sync 2.0 completely clutters the namespace. I don't necessarily want all "sync'ed" folders to show up on all machines.
c) I used to be able to define where Camera Backup from an iOS device went. Now it forcibly makes me use "<devicename> Camera Backup"
d) The ability to dynamically change "sync'ed" folder names as well as folder paths still does not exist.
a) 1.4 and 2.0 folders are different cryptographically. They are not mathematically compatible, so one can not be changed in any way to be another (and by the way 2.0 folders can not be turned into 1.4 folders either). 1.4 folders can just be disconnected and reconnected to become 2.0.
b) Through the MyDevices, linkages you are able to access all of the information you have added to any of your instances of Sync. This is a major user benefit - you no longer have to hunt down the originating machine to get your data. In order to remove a folder from this device, click on Folder Options > Disconnect and Disconnect from this copy of Sync.
c) Your devices are all named by you during install - you are able to change the device name in Preferences. You are now able to choose where your iOS backups are able to go from within the iOS app. Click on Camera Backup > Device List — which allows you to backup your iPhone to your computer and your NAS at the same time.
d) The application is constantly watching your file system for changes you make. If you want to change the name of a folder in Sync, change it in Windows Explorer or Finder, and in Sync it will be changed. The folders also follow your changes, move the folder where you want it to go, and Sync will follow your movements automatically. We feel that this is the best user experience as they are already familiar with moving folders and renaming folders in this manner.
I want to be able to hide the folder at least. For example, with 1.4, I was able to define shares between different sets of machines/devices.
Now, as I mentioned, all folders are visible, which is not ideal.
d) Here's a use case:
I connect a iOS device to a VM running BTSync. Folder shows up on VM as "<iOS device> Camera Backup" on a local filesystem.
I can't easily switch this to point to a network folder (over CIFS) with a name of <iOS device>
Worse, "<iOS device> Camera Backup" shows up on all machines with no easy way to rename. This is not good UX. Consider enabling functionality to switch names/locations in both BTSync UI and in Explorer/Finder.
D) There are a couple approaches here:
—> You can rename the folder - double click in the Sync folder list and it will show you the folder it Syncing. If you rename the folder, it will be renamed in Sync.
—> You can move the folder — double click in the Sync folder list and it will show you the folder it is Syncing. If you grab the folder and drag and drop it - you can move it to anywhere in the file system.
You can manually rename Camera Backup on your device, but we keep the "Camera Backup" name as it's often requested by name by our users.
I updated a machine that is usually off to 2.0 today, several days after updating other machines (total 6 devices) and the straggler promptly recreated the 1.4 folder on all the other machines. Now I have to go through and do cleanup.
Let me be clear: THIS IS HORRIBLE UX.
Dropbox is much better at the UX up to this point but I don't trust/need a copy in the cloud. But BT, please do not delude yourselves in thinking the current iteration or anything leading up to this point has been a good user experience. I've had to on multiple occasions needed to do cleanup on different machines because of this automagical behavior. Automagic is all fun and games until it does something unexpected. I'm much more in favor of predictable, repeatable behavior, particularly in an app like this.
Also, there does not seem to be a way to reset the identity.
For a more detailed explanation (and other helpful troubleshooting tips): http://help.getsync.com/customer/portal/articles/1902361-dis...
When you upgrade to 2.0, all 1.4 folders will still exist. You can continue to sync your 1.4 folder with both 1.4 and 2.0 builds of Sync. The only difference is that your 1.4 folders will not gain any of the new 2.0 functionality like permissions changes and syncing on-demand.