Asinine nonconfigurable feature-disabling has never been on the table. The issue you’re referring to begins with the subject “case insensitive by default” and ends a year and a half later with me saying literally “there will always be an option for case sensitivity”. So read either the first sentence or the last and take either on faith please.
- symlinks within a folder should be forbidden?
- versioning is incompatible with symlink targets as they’re outside the folder.
- what happens when following is disabled (everything is deleted on the other side)? (a followed symlink would look like a normal directory to the other side)
- “Only symlinks to directories are supported - not symlinks to files. We could support that on the scanner side, it’s not super difficult, but it’s a little bit more involved on the puller side as we don’t want to replace the symlink when pulling and we need to create the temp files on the other side of the symlink etc.”
- having to name the symlinks to follow was a “usage disaster”, but …
- … following all symlinks enables all kinds of shenanigans given that the other side can also add symlinks to the folder
and so on. It’s complex. None of the complexities are due to Windows or some lowest common denominator nonsense. The main problem with symlinks on Windows is that it’s difficult to not follow them under some circumstances.
Dropbox appears to do precisely what we do: sync the symlink as a symlink, and if it happens to point to something that was already in your folder then yes that also gets synced (because it would have been synced anyway). Probably this behavior has changed since you used it (the article says mid-2019). Maybe they ran into complexities.
Oh, and getting back to the case insensitivity thing – so that noone is mislead, it is much more difficult to implement a case insensitive system than a case sensitive one, whether at the filesystem level or at the application level. Case insensitivity is not a “reduced feature set”, it’s the OS & application bending backwards for the user in order to present something closer to how humans normally work. In our case we will need to be both case sensitive and insensitive and translate between the two worlds, which is another level of annoyance. None of this is trivial. Some of it is made worse by having the file name be the unique identifier of a file, but we don’t always have something better to work with.