7ef2743964
Events API consumers rely on being able to detect that events were skipped by the fact that the event ID has increased by more than 1. This is documented, and is absolutely necessary when trying to maintain a local model of Syncthing's state. With the introduction of LocalChangeDetected, which is not exposed to the Events API, this contract was broken. This commit introduces separate concepts of a "Global ID" and a "Subscription ID". The Global ID of an event is unique across all subscriptions. The Subscription ID is local to a particular subscription, and always increments by 1. They are both exposed over the Events API, but the Subscription ID uses the key "id" for backwards compatibility, and the "?since=xx" parameter refers to the Subscription ID (making the Global ID for information only). GitHub-Pull-Request: https://github.com/syncthing/syncthing/pull/3351 LGTM: calmh
Syncthing
This is the Syncthing project which pursues the following goals:
-
Define a protocol for synchronization of a folder between a number of collaborating devices. This protocol should be well defined, unambiguous, easily understood, free to use, efficient, secure and language neutral. This is called the Block Exchange Protocol.
-
Provide the reference implementation to demonstrate the usability of said protocol. This is the
syncthingutility. We hope that alternative, compatible implementations of the protocol will arise.
The two are evolving together; the protocol is not to be considered stable until Syncthing 1.0 is released, at which point it is locked down for incompatible changes.
Getting Started
Take a look at the getting started guide.
There are a few examples for keeping Syncthing running in the background on your system in the etc directory. There are also several GUI implementations for Windows, Mac and Linux.
Getting in Touch
The first and best point of contact is the Forum. There is also an IRC
channel, #syncthing on freenode (with a web client), for talking
directly to developers and users. If you've found something that is clearly a
bug, feel free to report it in the GitHub issue tracker.
Building
Building Syncthing from source is easy, and there's a guide that describes it for both Unix and Windows systems.
Signed Releases
As of v0.10.15 and onwards release binaries are GPG signed with the key D26E6ED000654A3E, available from https://syncthing.net/security.html and most key servers.
There is also a built in automatic upgrade mechanism (disabled in some distribution channels) which uses a compiled in ECDSA signature. Mac OS X binaries are also properly code signed.
Documentation
Please see the Syncthing documentation site.
All code is licensed under the MPLv2 License.