Harold Feit

At the earliest would be when we have a release build.

Specifically, only if the changes are early in the file. If they're late in the file or simply appending to the file, only the last chunk and any changed chunks would need to be (re-)downloaded

If offsets change, you download the whole thing, if you only append and/or only change segments without changing offsets, you only get the changed chunks.

does the account running btsync have permissions on the folders?

Does the web interface show the devices connected to each other? It's BSD based platforms (freebsd, macos) that have this limitation, not Linux.In the future, there may be configuration options to completely disable the searching for relay servers and/or define your own.

upnp and nat-pmp are separate, and likely covered under separate directives. Relay servers are checked regardless due to the possibility of you wanting to add a secret that is otherwise firewalled.

Simply put, it's not just a case of being able to plop the regular code into a compiler and have it work. There are platform-specific tweaks that are required to get it to work.

The news I gave IS the actual news. We don't have fixed timelines.

It'll be out when it's ready

mimmo3, you are now on official notice. The next time you open a new thread on this topic, your posting privileges WILL be revoked.

It does. It requires that 4mbyte pieces of the files be downloaded though.

There's a dedicated GUI that isn't the webui. Just double click the BTSync icon in the notification area.

Log attachment missing.

Is "Use relay server when required" enabled?

DHT in Sync, like in the main client, runs on every client that is active, regardless of what torrents and secrets they actually run. If the destination ports on these are all seemingly random, it's probably DHT initialization.

What IP ranges are you dealing with on those?

Relay servers help get around firewalled states on one or more nodes. DHT helps when the tracker servers are down.

If you want a star layout, BTSync is NOT for you. BTSync is pure mesh.

The assumptions you're making in regards to this are flawed, because BT Sync is multi point to multi point capable. This means that EVERY system with part (4mbyte) of a file can also spread those parts around (just like regular BitTorrent transfers). There is actually zero benefit to only downloading files from the central server over from all the member systems because you are also given the member systems' upload bandwidth to your downloads. You're assuming that all downloads of a given file come exclusively from a single source when they start. They don't.

How long after placing files in the shared folder are you waiting?

Are you causing changes in files' internal offsets when you change the contents?

There are plans to offer a configuration option for the timed checks of the folders. On some platforms, like Linux and Windows, there are mechanisms in place for the operating system to pass file and folder change notifications to programs so they can go to work instantly.

How long are you waiting after adding the files in the shared folder? Some platforms have restrictions that require you to wait up to 20 minutes.

It doesn't appear to at this time based on my tcpview check. You may be able to force things by turning off discovery and using dynamic dns hostnames to attempt to exclude the cloud relay function, but I make no promises as to the effectiveness of that. Port forwarding on both ends and making sure everything is properly internet reachable is still ideal.

The easiest way to get off of the relay connection is to forward and make exceptions specifically for sync. Also, it WILL work better if the listen port is open on both sides. Additionally, some routers' SPI firewalls cause major slowdowns and even outright block traffic by bittorrent products and should be turned off)