Handling of long filenames in Cryptomator 1.5.0

[dHFH84H33]

Thank you for clearing up the misconceptions and providing clarifications, looks like everything is under control. Just one minor clarification from my side, the invisible/disappearing files that I mentioned above that are caused by long file paths are these:

Files invisible in long path names if WebDAV but not Dokany

Files and folders disappear (but still exist!) if the path name exceeds a certain length under WebDAV. The files will show up again, if the path name is shortened (e.g. by shortening one of the parent folder names). The files will also show up if the drive is mounted using Dokany. When does it occur: Main cause is when files or folders are copied or moved into too long folder paths - the data seems to completely disappear (but actually is still there). Other cause is renaming parent folder …

This is indirectly related to:

@overheadhunter

As long as the internals of the ciphertext directory is not touched, you can move it around as you like, it will not harm any contents.

I.e. the above is true, as long as moving the vault does not inadvertently cause the path length to exceed 260 characters, in which case files could temporarily disappear from explorer and be accidentally deleted (as described in the link above).

That’s why I mentioned doing anything to reduce path lengths (including any file names) seems to be a good thing. If we can avoid this scary issue then all is good. But is there any chance the proposed change allows longer file names that could make the disappearing file issue more frequent? The closer to 260 characters we get, the easier it is to move/rename a folder outside a vault and cause some vault files to exceed 260 characters and potentially disappear until the path is shortened.