The purpose generally would be operate like a cache where “files you are actively using, recently created or frequently changing” would be sync’d to the client. And, thus, older files you don’t really use/touch much could be left out of the synchronization. This would help manage space on the client side - where you only need recent files.
My current workaround: set an “Archive/*” ignore pattern…and then I manually copy old files/folders into that sub-folder when I don’t want to sync them to the clients.
Other ideas I can imagine a few things:
-
on a new shared folder, only files that have been “recently updated” per the time specification. Like, only sync files/folders modified in the last N days.
-
on an existing shared folder, files that are beyond the time specification would be removed from the remote client and not synchronized in the future