Basically, I believe that BitTorrent Sync can never be a valid personal cloud service unless a 100% reliable machine, always on, is linked for every shared file. As a result of not having a reliable "server", I regularly get older file versions as a nasty surprise. If you can't rely 100% on one of your syncing machines always being up, you must check every time you save a file that it is actually syncing somewhere. I feel I have to repeat that: You either must have an EXTREMELY reliable machine that is always on, or you must check every time you change a file to know if it propagated (and remember if there are lots of files which did and which didn't). Otherwise (this is obvious, but I will lay it out anyway): - Three machines, A, B and C are supposed to sync a file, let's call it temp.txt - Machine, B, is supposed to be the "server" (i.e. always on) - B is down for whatever reason, C is typically down, so only A is operational - This "should" never happen, but of course, always will at the worst time possible - A changes temp.txt - A is shut down assuming wrongly that the temp.txt has been synced to B - B is now turned on again - C is turned on and temp.txt is modified there assuming it received the latest version from B - C syncs the mixed version to B - A is turned back on and receives the mixed version from B - A's original mods are lost This has happened to me MANY times. I am looking at creating a droplet at Digital Ocean to try to get something more reliable as a "server", but there doesn't seem any other solution. It seems to me that BitTorrent Sync could "know" that A never synced the file after it was modified. Knowing that A's version of the file is "hot" and needs to be synced, it could warn when receiving the file from B. Any comments?