Which is best for google drive and why? base32 base64 or base32768?
I struggle to comprehend which would be best, because I don't really understand the situation that well, googledrive is case sensitive, yes, but uh, I have no idea why UTF-16 googledrive might support...
Google file names can be 8000 bytes long so you can use either, or the default base32 it will make no difference.
Hmm, is there anyway to migrate from a crypt that uses filename obsfucation to a crypt that uses base32 encryption as a serverside move?
or is the only way to do it to copy from remote1: to remote2: and download all the files then upload all the files consuming massive amounts of bandwidth?
Yes you can do that.
You copy the crypt config in the config file but change the base32 setting and also the remote so it doesn't overlap the original say from drive:crypt to drive:crypt2
You then do a rclone move from old crypt to new with --server-side-across-configs and this will server side move from old encoding to new.
Let me know if you want more details.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.