GreatMarko

Simply remove "._*" from the .SyncIgnore file

There is currently no way to "select" which network interface Sync will use - essentially, it will use the first one it finds. To "force" it to use a specific interface, you would need to temporarily disable the other interfaces before running Sync, so that Sync is left with no choice but to use the one remaining interface that hasn't been disabled. Once Sync is running, you can then re-enable the other interfaces. The ability to be able to choose which network interface Sync connects through has been suggested a couple of times, so be sure to add your voice for this feature to the wishlist.

Use .SyncIgnore to exclude files with a ~$ prefix and prevent them syncing

Well, it's been tried before, and it doesn't work - .SyncIgnore files need to be identical at all ends - if they're not, you'll find files get deleted. As I say, at present, "nested" shares are not supported - and .SyncIgnore doesn't provide a "workaround" to this. If you wish to share some of a parent's sub-folders with certain devices, and other sub-folders with others - the only solution at present is to not Sync the parent folder, but create individual syncs for each sub-folder - that way you can individually share these sub-folders with your selected devices.

...it is, given that the protocol's currently changing all the time!! The OP's "research" is pretty outdated and isn't applicable to the latest builds!

Sync 1.1.27 installs & runs just fine on my WHS v1 (and also on WHS 2011) - so the WHS OS's ARE supported!

Whilst not RSS, there is apparently going to be an official BitTorrent Sync Twitter feed in the very near future!

I don't really see why you'd need a web UI if there's already a native UI? In order for Sync to be able to provide a web ui on Windows, it would need to also install/run a web server as well! - seems a bit over the top, considering you can already do everything via the native windows app!! ...you don't need to trawl through 20+ pages of the wishlist to find out if it's already been suggested, just suggest it there anyway! The developers are keeping tabs on how often certain features of requested... so the more times something's requested, the more likely it will be considered anyway.

You'll get far faster speeds if you transfer between your Android and your Computer over wi-fi, rather than over your Cellular Data connection! - this will likely explain your slow speeds. In addition, I have a feeling that currently the Android client can only handle files up to 2GB in size? (At least that was the case with 1.1.5 - I've not tested this with 1.1.7 yet - but I'm sure someone will chip in to confirm/deny!?) However, it does sound like a bug if Sync was transferring over your Cellular Data connection, even if you had this option disabled within Sync. Do use the "Send Feedback" option within the Android app to let the developers know!

Is the file in question currently open/locked by another application? If so, this will be why Sync indicates that there's data to be uploaded, which will only be transferred once the file in question is closed/unlocked/released by whichever other application is currently using it.

No, you need to update all your devices to 1.1.27 1.0.x builds are NOT compatible with 1.1.x builds - therefore 1.0.134 is NOT compatible with either 1.1.25, 1.1.26, or 1.1.27

Yes, but that's why there's a search function!! For example, search this forum for the word "android", and there are only 37 results! Please read the Unofficial FAQ in relation to the "Wishlist" - the developers ARE keeping track of the popularity of each suggestion made! ...besides, you don't have to read every post in the Wishlist thread in order to be able to contribute to it! - it's fine if you suggest something that's already been suggested... the more people that suggest the same feature(s), the more likely the developers will give them more consideration. In summary, please use the search function, and don't worry about the developers not picking up on suggestions made in the wishlist thread - they do!

You should be able to - it's only when a folder already has a read-only secret that the only way to change it is to remove the folder from Sync and re-add it again with the new secret. But if it has a full-access secret, you should be able to just change the secret at any time

Happy Birthday, Sync! ...it's come so far in just 12 months... I can't wait to see where we are in another 12 months!

Please read the Unofficial FAQ - there is no Web UI for Windows/Mac, as these have their own dedicated GUI's

You've made the folder "read-only" to Sync... that means that any changes you make to it, won't propagate to other devices, but other devices changes will continue to propagate to that device in order to keep that folder in sync. So if you have previously deleted a folder on Device A, this folder will be deleted on Device B. If Device B uses a "read only" secret, and you add a folder back to that with the same name as the deleted folder, then in order for Device A to keep Device B in sync, the folder will be deleted again from Device B (as it doesn't exists on Device A).

"versioned" files are stored in each folder's .SyncTrash folder. For example, when a file named "myfile.txt" is updated, the previous version will be stored in .SyncTrash as "myfile.1.txt". Upon the next update to "myfile.txt", the previous version will be stored in .SyncTrash as "myfile.2.txt", and so forth As versioning is a very new feature to sync, it's currently very limited in terms of allowing you to "manage" versions - essentially you can't control it at the moment, so you can't specify things like "only keep last X versions", etc ...but I'm sure improvements in this area will come in future builds! For now, as I say, you'll find your versioned files in their corresponding .SyncTrash folders

Yes, this is normal behavior for a "read-only" Sync folder! btw, 1.1.27 is the latest version, so do consider updating!

In addition to Kos' question - are you using a full-access secret on both devices... or is "Linux B" only using a Read-Only secret? (as this would explain the behavior you're seeing)

Issues/Questions surrounding security have previously been pretty much discussed to death - please search the forum to find the information/answers you require - the following threads will help you get started: 1 | 2 | 3 | 4 | 5 Given that BTSync & the protocol are, at present, closed source, writing your own app that reverse-engineers the protocol and/or attempts to communicate with Sync will likely be frowned upon, as it is in direct breach of the Terms or Use... it would also certainly be unwise to go down that route at the present time, given the very fluid nature of the "alpha" builds & the protocol (which has changed several times since the build you base your "findings" on). That said, there is an official API in development, which may be something of significant interest to you if you do wish to develop your own app/interface, etc, although please be aware that there is no timescale at present for the API's general availability (There's a dedicated "Wishlist" thread for the API here)

"nested" sharing isn't current supported. There's been quite a few topics on this subject already, including this one

Well, it's really up to people who start new threads to "tag" their threads with relevant keywords. That said, if you wish to find posts relating to say Sync on Android, you could just search this forum, or an individual thread for instances of the word "android", etc - where this does fall down, though, is if you want to search for say "TCP" or "UDP" or "NAT", etc, as the Search function doesn't allow search strings of less than 4 characters!

Manual download links for 1.1.27 may be found here

Yes, re-add your folder(s) to Sync again! Sounds like you were previously running an older, incompatible, alpha build of Sync! The auto-update does clearly warn you that "BitTorrent Sync 1.1.27 is not compatible with versions earlier than 1.1.25"

The auto-update does clearly warn you that "BitTorrent Sync 1.1.27 is not compatible with versions earlier than 1.1.25" You will therefore need to re-add your folders again if you were previously running 1.0.134. Welcome to "alpha" software! Protocol changes and incompatibility between alpha builds is to be expected! If that's not for you, you'd probably be best waiting until Sync migrates out of "alpha" and "beta" phases into a "stable" release!