silverwind
Unable to manipulate file with a name containing colon.
Colons (and a number of other characters, see here) are forbidden as filenames on NTFS, and colons specifically also cause issues in the macOS Finder. These limitations don't apply when the server runs on Linux with a typical filesystem like ext4.
Right now, I forbid all characters that could get problematic, but if there's a cross-platform way to detect the file system in use on the server, I can communicate that fact back to the web client and allow those characters.
@silverwind Thank you for your comment. The thing is, I do not think having Droppy support those special chars in filename really depends on underlying filesystem in a sense that if colon is not permitted on that filesystem, we can never create it and view any filename containing colon in any way. If user want to create such filename via Droppy, just return a creation error (because OS will return that error) instead of making assumption on file naming rules.
If we remove all these restrictions in Droppy, at least ext4 users will not find themselves helpless when they trying to delete a file via Droopy, because Droppy API will prohibit it in the first place. And NTFS users will not run into this problem anyway because they do not need to.