Edit. It was rejected for "Cloud synchronization clients" as well, probably because it is not a pure client/server architecture, but more of a peer-to-peer setup. There is no server where data is stored for multiple users, each syncthing instance is only able to sync data for a single user.
]]>Your setup is like mine, which is not really a "cloud", at least not according to NIST.
Syncthing is under https://wiki.archlinux.org/index.php/Sy … ronization, which is the correct categorisation, imo.
]]>syncthing is not a cloud storage server
This surprised and confused me, as I've used Syncthing for a few years now, and in exactly that manner.
On Syncthing's Website it says at the top of the page:
Syncthing replaces proprietary sync and cloud services with something open, trustworthy and decentralized. Your data is your data alone and you deserve to choose where it is stored, if it is shared with some third party and how it's transmitted over the Internet.
While Syncthing does not function only as a cloud storage server/client, it does indeed have the flexibility to do so. As an example, I have a central Syncthing server (an old laptop) to which I have multiple devices (computers and my phone) connect directly in a wheel-spoke fashion, so they each connect to the server, yet not to each other, and any changes made on any client device are automatically synced to the server, which then syncs those changes to the other clients. This synchronization works not only within my network, but also from the internet. That, to me at least, falls within definition of cloud storage server/cloud synchronization client functionality.
I don't at all want or intend to cause conflict, especially with individuals, who, like myself, contribute their time and effort to help make Arch better, I'm just interested clarity about this. If I am incorrect, then I'll absolutely accept that (would not be the first time, of course).
]]>