-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change filename_encoding in crypt config #5080
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
you can find some answers in https://alist.nn.ci/guide/drivers/Crypt.html#advanced-usage |
Sure I noted that "base64" is used as default in alist. For one thing, if you need to specifically state the default change there, it is not "a rarely used parameter". At least you are changing it every time using the rclone. For another, aligning the default settings can improve the compatibility to rclone (and also the users of TrueNAS like me). Currently, there is no way to setup alist crypt with TrueNAS Cloud Sync Tasks to survive future updates due to the mismatch of defaults in encoding type. I think it is better to add an option with defaults as "base64" and a comment to show that it is an advanced option. Non-professionals are still able to get noticed and use "base64". |
with that being said, i'll put filename_encoding in config page in next version. but please note that only default option "base64" is tested/supported. |
That will be good enough. Looking forward to the new version. |
Please make sure of the following things
Description of the feature / 需求描述
Currently, filename_encoding uses base64. However, this is not supported by some old versions of rclone. For example, in Truenas scale, the default version is
which does not support changing filename_encoding. Even though we can update rclone, Truenas GUI does not support such a configuration. Also, base64 is not the default choice of rclone.
Why does Alist use a different default setting? Can Alist support changing filename_encoding in the configuration?
Suggested solution / 实现思路
No response
Additional context / 附件
No response
The text was updated successfully, but these errors were encountered: