Search the Community

Showing results for tags 'nesting'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. 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 sy
  2. 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 len