I love the Syncthing app, and I am grateful for the valuable contribution you have made to the free software world.
But as an Obsidian user who syncs a large number of files (thousands) in .md, .json, and similar formats across more than two devices, the strange out of sync errors I encounter are truly demoralizing.
Why not add a button that takes us directly to the out of sync item and even lets us delete it right there? Is that so hard? Yes, the exact path is shown in the details. I went to that path on all my devices and tried deleting the file, yet that stubborn error keeps popping up.
Please consider pairing your brilliant, complex thinking with some simple fixes and additions as well.
Please show a screenshot of the specific error you’re seeing. This isn’t that simple, e.g. there may be different reasons why a file cannot be synced. Being able to delete a file once won’t really help if the errors keep popping up again and again.
Just to be clear, having to deal with out of sync errors constantly means that something is wrong. Normally, Syncthing should just do its job with no need for a manual intervention from the user.
I usually get errors like this. I also checked the logs but couldn’t find any information about the issue.
As for the cause of the error, I think it may be due to Unicode characters that Syncthing doesn’t support.
It’s not just the out of sync items problem, but also the creation of “sync-conflict” files that is a serious issue. Even when the file has the same name and “size,” sync-conflict files still get created. Preventing this would be wonderful.
I stick out my neck and claim that when @tomasz86 wrote “something is wrong” he did not mean that Syncthing is doing something wrong. Search the forum för “Obsidian" and you will find several threads on this subject. I believe these things are important here:
Same name and size of a file in two devices is no guarantee that they are equal. If they have both been edited in some way since the devices last synched, Syncthing cannot resolve the conflict by itself. That is when Syncthing creates the sync-conflict file, which is also synched so that you as user can investigate and resolve.
I argue that the creation of sync-conflict files is not the issue, but rather the situation which caused Syncthing to detect the conflict.
