add show hidden option for crypt storage

[textrix]

I tried adding a show hidden option for Crypt Storage.
This is like the option to show files or directories that start with dot in Local Storage.
This is for directories that don't need to be visible to certain users.
I think it requires a .json file by running the alist lang command, but I don't know the exact workflow, so I'm just implementing the feature and submitting it.
Please confirm.

[welcome]

Thanks for opening this pull request! Please check out our contributing guidelines.

[welcome]

Congrats on merging your first pull request! We here at behavior bot are proud of you!

[anwen-anyi]

Doesn't seem to be effective? I did not see two '. zip' files other than non encrypted files
Did I misunderstand?

[textrix]

Doesn't seem to be effective? I did not see two '. zip' files other than non encrypted files Did I misunderstand?

This pull request is to give Crypt Storage the option to hide files or directories with names starting with dot (just like Linux 'ls' doesn't show files or directories starting with '.' by default).

Presumably, based on the picture you showed, you were experimenting with the option to encrypt filenames set to 'off'. If you set the name encryption option to 'obfuscate' or 'standard', it should be normal for the original unencrypted storage to show the encrypted name. Also, if you encrypted the name with 'standard', moving it from the original state to another directory should be problematic.

Consider two cases, one where the file or directory is created in Crypt and the other where it was originally created in Stroage, assuming 'off'.

1. when creating a file in Crypt: the original name is postfixed with '.bin' and written to the original storage, only the file contents are encrypted.
2. creating a file in the original storage: naturally, the name and content will match the original.

After all, Crypt doesn't handle files that don't have the .bin postfix as originally promised, which is why Crypt doesn't seem to show it, and it's not recommended to create or change anything in the original storage that Crypt references.

So, the screen you've shown as an example is exactly how AList handles Crypt, regardless of this code change.

For reference, I always use this option with obfuscate in rclone crypt. This is because I don't want the storage provider to have to run a simple script to verify my filename, but also because of the previous problem with 'standard' and the limitations on filename length.

Anyway, this code checks if a file or directory name starts with '.'. The code uses strings.HasPrefix to check if the file or directory name starts with '.'. I don't think that question is relevant to this code.

Also, I wonder if other storage types could have this option, what do you think?

[anwen-anyi]

I understand what you mean this time, I misunderstood it 🙏