Syncthing

Syncthing is written in Go and implements its own, equally free Block Exchange Protocol.[8]

It is a BYO cloud model where users provide the hardware it runs on. It supports IPv6 and, for those on IPv4 networks, NAT punching and relay. Devices that connect to each other require explicit approval (unless using the Introducer feature) which increases the security of the mesh. All data, whether transferred directly between devices or via relays, is encrypted using TLS.[9][10]

Conflicts are handled with the older file being renamed with a "sync-conflict" suffix (along with time and date stamp), enabling the user to decide how to manage two or more files of the same name that have been changed between synching.[11] GUI Wrappers can use these files to present the user with a method of resolving conflicts without having to resort to manual file handling.

Efficient syncing is achieved via compression of metadata or all transfer data,[12] block re-use[13] and lightweight scanning[14] for changed files, once a full hash has been computed and saved. Syncthing offers send-only and receive-only folder types[15] where updates from remote devices are not processed, various types of file versioning[16] (trash can, simple or staggered versioning, and handing versioning to an external program or script) and file/path ignore patterns.[17] Two different SHA256 hash implementations are currently supported, the faster of which is used dynamically after a brief benchmark on startup.[18] Moving and renaming files and folders is handled efficiently, with Syncthing intelligently processing these operations rather than re-downloading data from scratch.[19]

Device discovery is achieved via publicly-accessible discovery servers hosted by the project developers,[20] local (LAN) discovery via broadcast messages, device history and static host name/addressing. The project also provides the Syncthing Discovery Server[21] program for hosting one's own discovery servers, which can be used alongside or as a replacement for the public servers.

The network of community-contributed relay servers allows devices behind different IPv4 NAT firewalls to communicate by relaying encrypted data via a third party. The relay is similar to the TURN protocol, with the traffic TLS-encrypted end-to-end between devices (thus even the relay server cannot see the data, only the encrypted stream). Private relays can also be set up and configured, with or without public relays, if desired. Syncthing automatically switches from relaying to direct device-to-device connections if it discovers a direct connection has become available.[22]

Syncthing can be used without any connection to the project or community's servers:[23] upgrades, opt-in usage data, discovery and relaying can all be disabled or configured independently, thus the mesh and its infrastructure can all be run in a closed system for privacy or confidentiality.

Syncthing must be configured via a web browser either locally or remotely (and supports access via proxy server), the REST and Events APIs or one of the community-contributed wrapper programs.[24] Links to Docker images are also provided on the community contributions page, as well as links to supported configuration management solutions such as Puppet, Ansible and others.

• In episode 456 of SecurityNow!, host Steve Gibson praised Syncthing as a potential open-source replacement for BitTorrent Sync,[25] and again referenced it in episodes 603,[26] 698,[27] 727,[28] and in more detail in episodes 734 and 781.[29][30]
• A reviewer in LWN writes[31] "Syncthing leaves a favorable impression. The developers seem to have done the work to create a system that is capable, reliable, secure, and which performs reasonably well. But they have also done the work to make it all easy to set up and make use of — the place where a lot of free-software projects seem to fall down. It is an appealing tool for anybody wanting to take control of their data synchronization and replication needs."

The initial public binary release (v0.2) was made on 30 December 2013.[42]

In October 2014 it was announced by the original author that Syncthing was being rebranded as "Pulse".[43] However, on November 17, the developer decided not to change Syncthing to Pulse and is no longer working with ind.ie. Ind.ie's Pulse is now an officially sanctioned fork of Syncthing.[44]

On 22 April 2015, 0.11.0 was released and it introduced conflict handling, language selection in the UI, CPU usage and synching speed improvements, Long filename support on Windows, automatic restarting when there is a problem for example the drive being inaccessible, and support for external versioning software.[45] 0.11 is not backwards compatible with older versions of Syncthing.[45] Because of changes to the REST API Syncthing clients that were on 0.10.x wouldn't automatically update to 0.11 as it wasn't compatible with a lot of the 3rd party integrations at the time of its release.[45]

0.13.0 like many of the older releases of Syncthing is incompatible with clients that are running version 0.12.x and below. 0.13.x separates the folder ids from folder labels. It also now has the ability to serve parts of the file that have already been downloaded to other clients while it is still downloading.[46]

1.0.0, codenamed Erbium Earthworm,[47] didn't really bring any major changes to the table. It was more of a reflection by the developers on the widespread use of the program and the fact that it had already been in development for almost 5 years at that point.[48][49] Despite the change in the major number Jakob Borg, the lead developer, stated that it was otherwise identical to 0.14.55-rc.2[47]

Alongside the 1.0.0 release the team introduced a new semver-like versioning system with the following criteria:[50]

• A new version which is protocol incompatible with the previous one would constitute as a major version.
• A new version which has changes in the REST API or has database or configuration changes which would not allow downgrading would constitute a minor version.
• If there are no specific concerns as above, it is a new patch version.

In 1.1.0 syncthing adopted Go 1.12 and as such loses compatibility with Windows XP and Windows Server 2003[51]

1.2.0 introduces support for QUIC, can now perform automatic crash reporting and deprecates small / fixed blocks. 1.2.0 also dropped support for communicating with Syncthing clients that are running 0.14.45 or older.[52]

1.8.0 adds an experimental folder option that allows users to specify how file changes should be saved on Copy-on-write file systems and also adds TCP hole punching support.[53]

1.9.0 introduced the option caseSensitiveFS that allowed users to disable the newly added handling for case insensitive filesystems.[54]

The 1.10.0 release gave users the ability to toggle whether they would like LAN IPs to be broadcast to the global discovery network.[55]

• Comparison of file synchronization software

• Official website