DecsyncCC had been forked and was last updated 5 months ago.
1 Like
Yeah you’re right about the admin rights. Syncthing and Radicale shouldn’t have them all the time for security’s sake.
However, I do not yet understand your rights file approach.
Radicale docs (here and there), to me, sound like this access management only applies to users of Radicale (not those handled by the OS running on the same machine) who contact the server in some way. Be it the browser-based web interface or the CALDAV protocol.
In the Locking section (see my next post) —> [1] <—, the docs mention that “the storage is locked with exclusive access while the hook runs”. So Syncthing needs the hook state to be active to access the otherwise locked data.
Here —> [2] <— they describe how to use that hook mechanism to version the Radicale collections data with Git.
… Which leads me to another question. Can we somehow configure Syncthing to delay scanning / synchronization of specific folders until we notify it about the temporarily granted access rights?
I wasn’t allowed to post >2 links / post, so here they are…
[1] Radicale docs on locking
[2] Radicale docs on versioning with git
I see what you mean, and to be honest, I don’t remember the details, because I added that rights file a long time ago 
. I do remember that I needed it for some valid reason though. I’d have to do some testing to determine what’s actually required and what is not.
I also use type=multifilesystem_nolock (as stated in the original post). This option was required, in my case, on Android.
I must add that, on my systems, there is no problem accessing the Radicale folder using Windows Explorer (without administrative priveledges).
I misunderstood the Radicale docs on locking, it literally says that the storage is locked while the hook is run. So there should be plenty of advantages for Syncthing to access the storage unlocked when there is no hook specified at all.
type=multifilesystem_nolock was neccessary on my android, as well.
My synchronization between Windows 11 and Android seems to be working now (no continuous admin rights for both programs)!
I believe that what fixed my issues was a transfer of file ownership using icacls, more specifically the /setowner and /t (recursive) options as discussed here.
I just hope it’ll keep working from now on…
Thank you once again for your helpful post and answers!
The Syncthing / Radicale combo is… finicky and error-prone to the uncautious user but at least it relies on very actively developed and well-known projects.