There is one significant use case that I cannot yet use Syncthing for: keeping an off-site backup of my on-site backup. My backup is a simple filesystem sync made with rsync, and between snapshots, there are a lot of hard links. Using Syncthing as-is would multiply the size of the backup repository by … I don’t know … a lot. Of course, I could “just” do another rsync offsite, but … Any hope hard links could be a feature in a future release?
If it isn’t obvious: I won’t move off of rsync to be compatible with volumes that don’t support hard links.
I realize that adding a single volume that does not support hard links to the peers would break everything. I also realize I’m wishing, but I would like Syncthing to check if the local volume supports hard links and, if not, simply refuse to synchronize with a shared folder that has hard links enabled (so yeah, there would hypothetically be two kinds of folders now, with and without hard links). I’d even settle for running a hardlink-supporting-volume-only fork of syncthing. Maybe I’ll try vibe coding that someday.