Ok, thanks for all the explanations.
I too have some not hidden .stfolder folders (bug, as mentioned above), but I always have hidden files/folders shown anyways, so now, there is a new folder in each of my local folder, which irritates my eyes and my usability: It is the first folder on top of all, it is always shown and therefore “in the way of my daily work.” (I administrate a lot of machines, so I need to show me all hidden files/folders to “see what happens”, but I like to have it tidy in my way)
I never liked the .stfolder files too or the files, which are stored inside a shared folder. I would prefere a configuration(folder) inside the syncthing folder, so the “original” data (count of files/folder locally seen, modification dates of root folder, when .stignores are updated, sizes of hole folders, etc.) is not touched or modified in any way. (also the .stversions folders, which are usefull, are not handy, when syncing those shared folders manually with other tools)
I now have 3 files in each of my shares (.stfolder, stignore and a global/local- stignore files) which are always visible as @DrSchnagels mentioned. (Plus a .stversions folder)
I understand the plans to move files into the .stfolder folder in the future,
but wouldn’t it be also possible to create subfolders in the syncthing configuration folder named like the shared folders and put all the configfiles into those folders?
One place for all the configs:
something like that.
(or, just an XML/INI, whatever config-file for each shared folder into the syncthing config-folder, instead of dumping “random” files into original and sensitive folders of the users machines)
of course, synching the (user generated “global”) .stignore-files would need some extra thinking
Anyway, thanks for the effort to make synthing better and flexible, -for me- this new folder makes my daily work more complicated. I like the idea of a sync-service, which just runs on the users data, but not change that data or changes the way users work.