Base32768 encoded filenames appear to contain characters that result in a 400 error

[Oval0149]

@azmi

The problem with base32768 is that Dropbox doesn't support newer unicode code points which seem to be used by b32k. E.g.,

azmi@stiorra:~$ rclone touch azmi-dbx:/good_stuff/foo
azmi@stiorra:~$ rclone ls azmi-dbx:/good_stuff
        0 foo
azmi@stiorra:~$ rclone touch azmi-dbx:/good_stuff/ꡀ
azmi@stiorra:~$ rclone ls azmi-dbx:/good_stuff
        0 foo

Is the implication not only that you can't store certain code points, but that you can also have a silent failure with base32768 for paths that contain certain code points, wherein a write would seem to complete without error but in fact not be committed?