Document E2EE: Advantages and limitations

[tbsbdr]

We urgently need to document E2EE, as incorrect usage can result in data loss. IMO, the following needs to be clear at least:

• Web scope: E2EE is currently focused on Web. There is no "batteries-included" solution for desktop and mobile yet. The alternative for experts is to use rclone, but we need to clearly state that this is a manual, expert-only option.
• Advantages: Nobody without the password can access the contents of a vault. (As of now, system-level admins can still access all files without E2EE!)
• Limitations: No collaboration, search, etc. No out-of-the-box decryption in mobile and desktop clients.
• Usage:
  • First create an E2EE folder, then put the files to be encrypted into that folder.
  • Make clear that you cannot right-click a resource and select "Encrypt".
  • The password cannot be recovered. Be careful! Losing the password means losing the data. This makes E2EE a reliable way of shredding data.
• Clients: What do desktop and mobile clients see? What happens if you use rclone and try to work collaboratively on text files?

[tbsbdr]

in case you are unsure @Svanvith I or @dragotin can help

[Svanvith]

First question:

• I create a encrypted folder
• click on it an get access after enter the password
• create a file in it
• go back to "Personal"
• click after a few seconds again on the encrypted folder and got access without typing again the password

Is this correct? @dragotin