Search the Community

Bittorrent Sync is a really interesting concept - hoping it will be wildly successful (and that encrypted nodes provides will provide the same convenience we have with non tin-foil had proof services these days). Migrating my stuff to Bittorrent Sync I am however running into an issue. I have a ~/Sync folder, which is the replacement for what was ~/Dropbox before. In that folder I have shares with different people e.g. ~/Sync/Shares/John Doe/ - that's all working fine and dandy. Now I am trying to set up ~/Sync/Camera Uploads/ with the secret that the iOS app gave me for the Camera-Roll sync. But strangely I am getting the error message "You don't have enough permissions to share part of a read-only folder. Please choose another folder". That error message doesn't make any sense to me - I have no whatsoever read-only shares. If I choose a target folder outside of ~/Sync/ it works fine, but that's not what I want. Migrating from ~/Dropbox I want everything neatly organized under ~/Sync/ Any feedback/pointers are very appreciated. B.t.w. (a bit unrelated) is Bittorrent (as a company) planning to offer "encrypted nodes" (for offline syncing) as a commercial service, or is the stance that third party companies should offer these services? Recently got our developer api key - seriously interested in hacking a nice service (mainly because we also need an offsite backup - and it would make sense to build in such a way that it's useful for others, too), but depending on where Bittorrent as a company is going this may make less sense. Thanks!

It's not altogether clear how BTSync deals with deeply nested subfolders and long file names that exceed the maximum path length of different systems. For instance, I'm syncing between my Android mobile, tablet, Windows, Ubuntu and Apple clients and a BTSync server under FreeNAS. Each OS has a maximum path length that, with a shallow directory structure and reasonably short filenames, are unlikely to cause an issue. However, with deep folders and long filenames, the chances of exceeding the maximum path length are higher. Several questions arise: 1. How does BTSync deal with maximum path length issues? 2. Should something be tabled in the FAQ guide on maximum path length for different OS's? 3. Does the BTSync sending or receiving app flag an attempt to exceed the maximum path length when syncing between systems?