- Roadmap
-
Idées
Section Encryption
Add the ability to encrypt a section. To view notes in the encrypted section, one must enter a password each time that section gets selected. Switching away from an encrypted section requires to input the password again, when coming back. As long as the section is active, all notes can be opened without requiring a password.
Solution
With CN 2.0 powerful section implementation the suggestion offers more flexibility and (imo) supersedes the following requests http://roadmap.cintanotes.com/topic/3189-individual-note-encryption/ and http://roadmap.cintanotes.com/topic/95254-encrypted-tags/
Even though we often agree - this time I have to disagree (sorry).
I will NOT vote against this request because the basic idea (encryption based on sections) is not a bad one.
BUT I strongly disagree that such a feature would supersede an encryption based on tags.
Here is my reason:
One note can only be stored in exactly 1 section - that's the concept behind it - and that makes the sections very special. We must think twice before we decide to use a tag or a section.
I for instance use them to separate private and work related notes. Now I will have the need to encrypt both, private notes and work related notes. And I am not willing to put them into an extra section for this purpose.
It would be much more convenient (for me) to assign a tag that will cause the note to be encrypted.
Maybe you could edit your request to make it an additional one to the tag based encryption.
thanks
chris
Hi Chris,
no need to be sorry :) There are four different requests on encrypting notes. It was my intention to open a discussion on this, so that it will be clear, at which level they are distinguishable. You made your point. Thank you for clarifying this! Imo, it is important to be able to allow discussions and to convey them. I have made the experience that this is a very constructive process in CN's community.
As for editing my request, i don't see a need for this. My request is written as an open request without interfering to other requests. It was on purpose that i added my thought on "superseding" as a separate "comment" to my request. This way it can be reckoned as an issue on its own.
Thomas
Service d'assistance aux clients par UserEcho
