GreatMarko

Right-click a column header

You're assuming though that all peers are connecting to the same 50 peers - in reality, this isn't the case, so the 52nd peer (or 53th... 54th... etc) won't be "alone in the darkness" - it'll still received files from other peers!

The "latest" public builds can be obtained via the links on http://www.bittorrent.com/sync/downloads - these links are "static" and persist between versions (i.e. http://www.bittorrent.com/sync/downloads/complete/os/windows will always get you the most recent public build of the Windows version of Sync, etc)

Indeed! ...and it can be any unused port, you'll just then need to make sure that Sync is set to use that port each time, and not try to map a new random one on each run.

@newcXL, UPnP has nothing to do with DNS. The message you're seeing is due to Sync attempting to open a port on your firewall/router, and it being unable to i.e. your router denied the request. Changing your DNS server setting will have no affect on which ports are open/closed/mapped on your router/firewall. Basically, it sounds like your campus (like many) has a restrictive router/firewall which prevents the opening/mapping of random ports.

Read-Only devices with the same Secret can share data between them also!

It means the files have not fully sync'd/were interrupted during sync. To resolve, stop Sync on all your devices, locate and delete any .!Sync files, and restart Sync It does happen from time to time, and Sync is only in "beta", but to reduce the risk of this, it can help to ensure your files/folders are in sync before exiting Sync/shutting down your computer.

You'll need to locate and open your Apache server's httpd.conf file, locate the "Listen" setting (which defines which ips/ports the server listens for connections on), and adjust according. Remember to restart your server for changes to httpd.conf to be applied!

Have you verified that they system clocks on your devices are in sync and correct? ...but it does! Sync "moves" deleted files on other devices into a hidden SyncArchive folder on your device rather than delete them outright. This is controlled by the "sync_trash_ttl" setting - Set this to "0" and Sync will never delete stuff from SyncArchive Please do bear in mind that Sync is currently "beta" software, and should be regarded as such.

I think you've answered your own question in your edits - Sync's count of files/file sizes won't take into account files it's not syncing (including .SyncIgnore and .SyncID files and anything in your hidden .SyncArchive folder). Your OS on the other hand will take into account these. There isn't much need really for Sync to display info on files/folders it's not syncing (although, there's a case to be made for showing the "size" of the .SyncArchive in the UI, so you can keep an eye on how big it's getting - but that's more a request for the Feature Request forum)

Step 1) Stop Sync on all your devices Step 2) Locate and delete any .!Sync file on all your devices Step 3) Restart Sync on all your devices ...the problem should be resolved!

You'd need to use the API

Chris, the request - as I understand it - is to "encode" or in some other way incorporate a list on pre-defined hosts within a Secret that you then go on to "share" with others, so that when they come to enter that secret into their own Sync, their Sync settings for that folder will be automatically have the "Pre-Defined Hosts" setting pre-populated with a list of IPs

I don't think it needs to - if my understanding of the OP's request is correct, he essentially wants to be able to encode and incorporate a list of pre-defined "hosts" into a Secret, so when that Secret is used on other devices, that folder's "Pre-Defined Hosts" options are already set. This would of course only be of use if the list of pre-defined hosts point to static IP's, rather than dynamic, otherwise those IPs are prone to change between the time when the secret containing the encoded "hosts" is created, and when it is subsequently used. ...and I think that was the point the OP was making in relation to static IPs.

You don't mention which Operating System you're using, but on Windows/Mac, etc, this is shown in the graphical interface for Sync - i.e. the "Devices" tab will show you when your devices are in sync, the "Transfers" tab will show you what's currently syncing, and the "History" tab will show you what's recently sync'd.

Please see: "If you have a Sync issue" - it tells you where logs are located, and where to send them.

Incorrect - Sync currently supports a maximum of 50 simultaneously connected devices by design - it's not an "OS limitation" - see this post. Given that the current Sync offering is intended primarily for "personal" use, it's unlikely that most "personal" users would need to connect to 50 other devices simultaneously (let alone own or have access to 50 other devices!). This does not mean that you can't share a file with more than 50 devices with the "personal" edition of Sync, though - you can! - see this post. I suspect that if the ability to raise this limit were to be introduced, it would likely be an "enterprise" feature, rather than something included in the "personal" edition of Sync.

Cent OS is a linux distribution - there are linux builds available for Sync - have you tried them?

It's not really a limitation of Sync - more a limitation of Windows. On Linux for example, you can have two files, one named "FILE.txt" and "file.txt" co-existing in the same folder. Windows doesn't allow this - it sees the two file names as being the same - and therefore the operating system itself (not Sync) generates a .conflict file/folder. That would likely be the best solution!

dabruna, You've now posted near identical posts 3 times - twice in the General Discussion forum, and once in the Feature Requests forum. Once is sufficient! Feature Requests go in the Feature Request forum. General Discussions go in the General Discussion forum. Troubleshooting goes in the Troubleshooting forum.

Because Sync can't just assume that because it's not running, nothing will have changed! Take for example a scenario where you're Syncing with say a network share/external folder/networked hard drive which other users also have access to - you could shut down your own computer completely, but the next time you power up, files on your network share may have been changed by someone else - thus necessitating a rescan. ...or a further example would be where you just "log off" your computer (rather than shut down) - Sync would still exit in the same way as when you shut down. So, if you just "log off", and then another user logs in and makes changes to files in a local folder you're syncing, your files would go out out of sync whilst you're not logged in - again, necessitating a rescan the next time you yourself login and run Sync. ...so that's just a couple of examples as to why its just safer for Sync to perform a rescan of the folders it's monitoring each time you start the program - it can't just automatically be assumed that nothing will have changed since the last time it was run, especially if other users have access to your computer too, and/or you're syncing "external" folders.

In a word - yes! Of course, the size of the files being sync'd and each device's available bandwidth, etc will also factor in - but generally speaking, the more devices you sync between, the faster your files will transfer. If you're familiar with downloading "torrents", Sync is essentially based on that technology - and so just like when you're downloading a big torrent (i.e. a movie - ..a legal one of course! ) - the more "peers" you're connect to, the faster the download will complete. The same principle is true of BitTorrent Sync.

Not currently - the devs & support hang out here in the forums instead

Try decreasing the "folder_rescan_interval" setting. This controls how frequently Sync re-scans folders for changes that can't be picked up in real-time. By default, this is set to 600 seconds i.e. 10 minutes.

Would it not just be better to rate-limit your up/down bandwidth, using the existing settings, or perhaps be able to sync on a schedule or have a selective pause function instead? Having Sync "cut off" entirely for the remained of a calendar month once a certain amount of data has transferred in.out would mean that your files wouldn't then sync with other devices for the remained of that month - they could be out-of-sync for days!! - somewhat defeating the whole point of file synchronization software!? Take, for example, the following scenario; you have two devices A and B, A is set to "cut off" once a certain amount of data has transferred in a given month. An important file already exists and is in sync on both devices. The file is then updated by A on the 20th of the month. Unfortunately, by that time A has already reached its monthly data limit, so the changes made don't propagate to other devices. Meanwhile, on the 30th of the month, the corresponding file is updated on B. When the 1st of the next month rolls around, the updates made on A on the 20th which never sync'd anywhere will be lost, as B has a newer copy of the file and will propagate that to A! So essentially, when you update a file on any device, you really want those changes to propagate to other devices as soon as possible ...and not have to wait until the start of the next month! That's perhaps why limiting bandwidth, having a "selective pause" function (so that you can pause non-essential syncing, but still allow some syncing to take place), or be able to sync on a schedule (i.e. only during certain hours of the day) may be a better option than a complete "cut off" each month?