Hey Helen, Oh really? Sorry, im new to BTSync, i didnt actually realise that the old .SyncIgnore file didnt actually sync between the clients. When i googled around, i came across few comments implying that it was synced across the clients, thus my assumption. You have a fair point, but i think one of us understands the ignore file (the current .sync/IgnoreList) incorrectly (likely me, but clarify for me if you can). You, and I have a share folder. If you add "bob" to your IgnoreList on your computer, does that mean: 1. if you create a folder called bob in our shared folder, bob and its content will NOT be shared/synced to MY client/computer. 2. If I added folder called bob in to our shared folder, bob and its content will not sync to YOUR client/computer. Assuming the answer is 1 (i hope), then your example seems invalid. Because adding *.txt to B's ignore list means If B creates txt files, A and C will not see them, and adding "my secrets" to C's list means, A and B wont see "my secrets" folder and its content if added/created by C. But if the answer is 2, then well... Shouldn't the point of an "Ignore List" is a list of stuff you dont SEND, not a list of stuff you refuse to RECEIVE/DOWNLOAD? If a client doesnt want to download these folders, shouldnt this be a feature of selective sync and not added as an "ignore list"? I might be wrong, but im under the impression that if you look at almost all file share platforms (lets take git/svn/seafile as an example), the ignore list is a list of items that the client does not send (outgoing), not a list of items that the client rejects (incoming). Does BTSync really does it the other way around?