billerr

(Sorry if this has already been reported, but I couldn't find any reference.) Since updating to 1.3.87 on Windows 64-bit (Windows 8.1), btsync pops up a UAC prompt on every system boot. This wasn't the case in earlier version. Did I mess something up with the 1.3.87 installation or what? EDIT: Sorry, my bad. Looks like something had indeed gone wrong with the installation and it was loading up the setup file on each boot.

For the development of "dumb" clients (i.e. clients that only function as a UI for a remotely installed server), the current implementation is a no-go. End users shouldn't be expected to apply for a developer API key just to access their btsync servers remotely. A more elegant implementation would be to either rely on just a username/password combination for access control (if an app goes rogue, just change password) or on an API key generated by the btsync server providing access to GUI clients (think SickBeard/CouchPotato - revoking access by re-generating the API key). The second way could be implemented in an even more granular way: generate and manage different API keys for each client wanting to connect and revoke their access independently. This could even be hidden behind a more user-friendly "Authorize/Revoke" UI.

Until recently, I too had a never-ending sync of just 52.5 KB pending (plus a file count difference of 1). Removing and re-adding folders didn't help, so I investigated. After checking each folder's file count one-by-one, I found the culprit! At some point, I had renamed a folder on my Windows machine, changing only the case of some letter (let's say from 'contest_winners.xls' to 'Contest_Winners.xls'). However, I found two identical files on my Linux NAS: 'contest_winners.xls' and 'Contest_Winners.xls' side-by-side. It seems that the difference in case-sensitivity from Windows to Linux threw off the indexing engine, and it created the duplicate. So, the 'contest_winners.xls' file tried to sync back to the Windows machine (after some changes) and found no counterpart, staying in limbo I guess. Whether this is an issue to be fixed, or a one-case scenario, I don't know. I'm just putting it out here.