I'm not saying it is hard to do, but it increases the scope a lot because if you encapsulate notes and notebooks in a vault, you need to hide all of those items from everywhere in the UI when locked, and there's a lot more testing which would need to be covered. This is already a large project and the project must be completed within the timeframe of GSoC
No no, I think you misunderstood it is not notebooks encryption. I meant to keep all encrypted notes in a single special notebook called Private Notes.
I'm just suggesting an Idea, consider this based on users feedback and of course if time permits.
That has all the same considerations as implementing an encrypted notebook to be honest. It was discussed about having the concept of encrypted notebooks which don't encrypt all content within the encrypted notebook (ie. note titles and sub notebook titles are not encrypted). But to be honest I think that gives a false sense of security. If a vault is locked behind a password, a user would reasonably expect everything within it is protected. But if you don't go all in and encrypt everything, what you're providing is more like a note lock hybrid rather than an encrypted vault
Ok, encrypting titles is not a big issue. But I see your point, It is programmatically possible to access hidden notes with Data API and possibly alter them as well.
And resource intensive as well, as you need to decrypt all encrypted notes at once, even though they are not required.
Don't get me wrong, I think supporting an encrypted vault would be great. This is just a big project and it needs to be a rock solid implementation, otherwise this might end up not getting released at all
yeah agreed, private notes sounds simple at first but it kinda changes the promise.
once it looks like a vault, people will expect everything inside to be private, not just the body. so i think for this project it’s better to get note locking + bulk lock actions solid first, and leave the full notebook/vault idea as something that can build on top later.