Peer subdirectory ".stsync"

[Andy (Andreas Kaelber)]

The name .stsync was just an idea of me. By default in every peer I suggest for all operational files and directories, e.g.

.stfolder
.stversions
.stignore
.syncthing. *. *. tmp
~ syncthing ~ *. *. tmp
.
.
.

to set up a system directory with the suggested or another name. This would have the advantage of a clear location or easier handling, e.g. in IgnoreLists etc., etc.

[Nummer378 (Max)]

Related:

Should "meta"-files use .syncthing instead of .st as prefix?

Original comment: can you please include syncthing in the name of the file if you choose to go that route, as it’s not entirely clear what these extra files are for if you’re not intimately involved with the project. Edit after split: imsodin has split this topic from a previous thread (thanks). The idea I am getting at is changing files like “.stignore” to be “.synthingignore” or something along those lines. This means that the name of the software responsible is able to be found by users who …

[calmh (Jakob Borg)]

Yeah. I think a .syncthing directory with files in it would be better than the current setup. Migrating to it without screwing up existing setups isn’t completely trivial.