Hmm so the problem still consist (1.1.48) I find the .ignore* thing a bit ugly. I would like to maintain the flexibility i have by sharing all my important data in one share, so sharing all the sub folders separat is not an option. A solution i though of would be to create a copy of the subfolder you want to sync, outside the main share. One can keep the copy in sync with the "original" using something like rsync+cron. Then you can create a secret for that "copy" of the subfolder and share it to whatever it is that you want to share just the subfolder to. So i have my main share "/filer" huge, contains all the files i need synced. All my PCs can handle it, but my phone does not, i still want to sync the subfolder "/filer/musikk" to my phone. I pick a PC i see fit (should be one that is online 24/7) and create a folder besides "/filer" called "/phone" Then i use rsync+cron to make "/filer/musikk" sync one way to "/phone/musikk" I create a secret for "/phone" and share to my phone, and there it is. The PC running the intern folder synchronization is so to say a bridge, from one btsync share to another. I could share the secret to my other PC's to increase speed/availability (of course putting the "/phone" share besides "/filer", not inside "/filer"), however the syncing/updating from "/filer/musikk" to "/phone/musikk" only works as long as the pc running the "bridge" (rsync+cron script in my case) is online. And no matter on which pc "/filer/musikk" changes, the changes will translate to "/phone/musikk". Not directly, but via the PC running the "bridge". This is just a theory, i don't have time to test this right now. also i'm not sure how this would work if you wanna do two way sync form the node that only has the sub-folder share, but i guess it is possible, just taking some precaution with who and what has write access.
