@tflidd Seems it’s been discussed plenty. The dev’s are aware of issue/feature going on a few years now. Whatever their reasons they have decided not to add/address it. I will though make another issue and link this post.
I think most basic user’s use case is they just want to sync their entire “home” directory . That way as they work they don’t have to think “did I just put/backup that in the cloud?”. In a perfect world of unlimited free cloud storage and giant bandwidth that’s what we’d all do. But like me they have maybe a folder of huge video files or a folder of sensitive stuff, whatever they don’t want to/can’t sync.
Since I saw no post of my work around only pain I just offered this here for new/noob users who probably just assumed this feature existed (i.e. ignore one or more folders in a parent folder being synced) and were instead surprised that they just deleted a folder for which they may not have had a backup (poor planning on their part!) by mistakenly clicking apply despite the warning.
For new users reading this you should know that it is possible to set a sync up for each individual sub folder in a parent thus effectively “ignoring” some. Yet if you had say a dozen or more it gets ugly having to make a remote folder for each and the client window gets crowded and confusing. Of note any file in the parent root will not be synced by this approach.
Clearly at a certain point it’s easier/better to sync the whole folder and then indicate which folders/files to ignore like for example a videos folder with HUGE video files. When you do that nextcloud makes all those (sub)folders for you on the server (very convenient)
I personally would like to see this feature mostly for others (like my family members who use the cloud I set up) because they may not understand all the limitations or best practices for managing their files nor when to take a serious warning seriously. When I set each of them up I had to do it personally because of the danger that they would delete files. The lack of this ignore feature (or the uncheck = delete “anti-feature” if you will) is a tech support nightmare (as has been pointed out). Several sysops posted they decided to pass on nextcloud only because of the super headaches created by this dangerous client “anti-feature”
I suppose the lesson like most coding lessons is code to how users use it not to how they should use it.
I chuckle a bit at the warning message “local file system” most users have no idea what a “filesystem” is let alone the nuances of a “local” vs “remote”. They will just click “apply” because well they thought (and maybe rightly) that unchecking it would simply not put that in “the cloud”. They are used to checking a check box and then clicking delete (which is what you do in the browser interface) not unchecking something and having it be deleted.
Well in the end this is not a problem for me. I have my work around and I only need support a few users. Still I hope they do something as having a community edition is dependent on having a viable enterprise version and this “anti-feature” isn’t helping the bottom line IMHO.