Trivial Sync Conflict: file names only differ in upper/lower case style

[tstreibl]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Expected behaviour

Different syntax between unix/windows file systems on web-interface/client side should not lead to sync conflicts.

Actual behaviour

no complaints in web interface when files are named according to unix style but not according to windows style
sync error in windows desktop client for those cases (guess on all windows machines)
guessed root cause: unix servers for the web interface use a case sensitive file system; windows file system is not case sensitive

Steps to reproduce

1. create a first file with the name "test1.md" in the web interface
2. create a second file with the name "Test1.md" in the web interface
3. use the desktop client on a windows machine
4. watch sync error from desktop client

Client configuration

Client version: 3.3.6

Operating system: Windows 10

Nextcloud version: 23.0.0

Storage backend (external storage): no

[marbx]

Whether this a bug, an enhancement or a design question, NextCloud should at least give more expressive messages, depending on the operating system:

• To Windows users: "There is another file that name only differs in case, please look it up under Unix or in the web interface.
• To Unix users: "Warning: this files cannot be synced to Windows because Windows cannot distinguish case in filenames".

Currently, users are left in the dark.

[marbx]

Actually only Windows users are left in the dark, which is kind of (not) a joke :-)

[marbx]

Similar to #3277