Yes, i understand that the keyword “encryption” sounds more important than some wording related to file structures. But, I’m interested to details and how these relate to the existing system. Even if you can improve just 1% of a system - nothing is nothing, and something is something.
The word vault has multiple meanings, essentially it’s a place and not just a simple shelf… And mostly, a safe place, broken down in simple words.
A good definition, imo, to store large amounts of objects, in our case digital data.
Since our work is valuable, the definition of a safe place is more than desired but this promise wasn’t yet fulfilled, because our nameless genetic “vault” doesn’t support encryption.
When we first create our vault - we assign a name to our top/main/root folder, (call it as you like, to indicate, you can’t navigate outside that folder, everything is stored inside this folder) so we don’t assign a name to our vault. Vault is always called vault.
This top/main/root folder is visible on the very top of the file explorer
- What’s the use of that top/main/root folder in our file explorer ? Of course, it stores all our data but it sits just there as a name placeholder and does nothing (visual clutter)
- why is our vault called vault instead to use the name we assigned to our vault ? our vault needs a name.
I know, there’s a plugin in the community repos, called meld encryption - a good step forward to what a vault should be.
