GSoC 2026 Proposal Draft - Idea 7: Local Note Encryption - keshav0479 Links Project idea: Idea #7: Local Note Encryption GitHub: github.com/keshav0479 Forum introduction: Welcome to GSoC 2026 with Joplin! Joplin PRs: PR Description Status #14776 Mobile: Fix OneDrive auth code dou…

Hello, we've recently updated the template for GSoC draft proposals. Please update your post as described here: [image] GSoC 2026: How to Submit Your Proposal Draft sun_with_faceGSoC Before submitting a draft, please read the GSoC guide on writing proposals: h…

Thanks for the template pointer, i've updated the first post to follow it. A couple of design questions as i work through this: for the body-field challenge, i'm weighing two approaches: keep the current option-gated body approach and enforce safety through integration tests use a separate trans…

[image] keshav0479: keep the current option-gated body approach and enforce safety through integration tests use a separate transient property for decrypted content in editor/viewer paths, so plaintext never sits on the serializable body field at all I’d lean more towards the second option b…

You will still need to include testing of conflict scenarios, even if direct changes are not required. So I’d say you should mention this in the proposal. For example in handleConflictAction.ts, this will duplicate the note using Note.load and then clear some of the fields before saving as a new not…

Thanks, that helps a lot. i traced a few paths for option 2. on desktop, initNoteState() in useFormNote.ts pulls n.body into FormNote. for encrypted notes, editor/viewer paths could read from a transient field instead of the serializable body. since FormNote is separate from NoteEntity, this stays …

yeah that makes sense, i'll trace through handleConflictAction.ts to make sure the note duplication path handles is_locally_encrypted and local_cipher_text correctly, and that the transient field doesn't leak into the duplicate. i'll cover resource conflicts there too and add conflict scenario testi…

for encrypted notes, editor/viewer paths could read from a transient field instead of the serializable body I think it would have to be for all notes using the transient field, not just for encrypted ones? The React / React Native component to display the note contents would have to map to just o…

Unless it would work to set this value to a variable with a conditional underlying value I guess the issue with that might be when you toggle encryption on the note, it would need to switch which column it is writing to. You could drive the value by a state variable instead, but then you would ha…

yeah the toggle case is a good point. switching which column the UI writes to mid-session would be messy to keep in sync. I think a thin layer outside Note.save/Note.load is the cleanest approach. something that: after load: populates a transient display field from the right source (body for norm…

Hi, I'm Aravind, author of Secure Notes Plugin. Sorry, I didn't go through complete Draft. But here are a few things I would like to add: Some people prefer to have different passwords for different notes, not single master vault password (Survey few people about which model, proceed with the maj…

GSoC 2026 Proposal Draft - Idea 7: Local Note Encryption - keshav0479

GSoC Projects Encrypted Notes

laurent 15 March 2026 13:13 2

Hello, we've recently updated the template for GSoC draft proposals. Please update your post as described here:

Topic		Replies	Views
Secure Notes Plugins	35	1812	27 March 2026
GSoC Idea - Password-protected notes Features gsoc-2020	17	1838	21 November 2020
Encrypting individual notes Features	27	8738	8 October 2025
Requesting encryption of local Joplin data (at rest encryption) Features	42	9002	28 May 2021
Vaibhav GSoC 2020 - Introduction GSoC gsoc-2020	13	711	12 March 2020

GSoC 2026 Proposal Draft - Idea 7: Local Note Encryption - keshav0479

Related topics