Open P2P Symbol Launches Syncting 2.0 Files

synthing 2.0, in which synchronized data are not loaded into cloud storage, but directly replicated between the user’s systems when they appear online, using the BEP (Block Exchange Protocol). The SynCging code is written in GO and is distributed under the free license mpl. Ready-made assemblies prepared for linux, windows, macos and freedsd. Users can create large decentralized networks for storing jointly used data that are distributed through the systems of participants. Funds for accessing access and creating exceptions for synchronization are provided. Users can determine hosts that will only receive data, meaning that changes on these hosts will not affect copies of data stored on other systems. It also supports several modes of file verification, saving past versions of changed data.

During synchronization, files are logically divided into blocks that are indivisible when transmitting data between systems. When synchronizing a new device, if there are identical blocks on several devices, the blocks are requested from different nodes, similar to the operation of the Bittorrent system. The more devices involved in synchronization, the faster the replication of new data will be carried out due to decompitaling. Only the changed data blocks are transmitted during synchronization of changed files, while only metadata is synchronized during renaming or changing access rights.

Data transmission channels are formed using TLS, with all nodes authenticated by certificates and device identifiers using SHA-256 for integrity control. The UPNP protocol can be utilized to determine synchronization nodes in the local network without manual input of IP addresses. A built-in Web interface, CLI client, and GTK-based GUI are provided for system configuration and monitoring, enabling control over synchronization nodes and repositories.

Key changes in the new branch:

  • Backend of the storage is transferred from the LEVELDB database to SQLite. Data migration is automatically performed at the first launch after an update, simplifying support and data management.
  • The format of logs is changed, now structured in a key-value format. A new level of Warning logs has been added, providing more detailed information than Info but broader coverage compared to Error. Different levels of logs can be assigned to different packages.
/Reports, release notes, official announcements.