Except Syncthing is not centralized. It's basically a webhook between your own computers or others whom you authorize. If you sneakernet a file, that is discontinuous whereas Syncthing provides continuous file syncing over UPnP. The underlying protocol is open, the source code is open...

Like, are you not aware the default roadmap for this shit is be nice and free till people rely on the service, then become greedy and shitty.

Let's absolutely be wary of enshittification, but Syncthing ain't it. If they enshittify, I'll eat my humble pie, fork the code, and go back to my merry synchronization between my computers all over the place. All without having to run a file server. Well, I'd probably just pull my most recent, non-shitty Docker image, but that's running off into the weeds.

Centralization in this context would require the Syncthing Foundation to run servers hosting your files, which they don't. My question was why/how you think Syncthing is a centralized service,