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

[mrjo118]

FYI I’m not sure how far through you got with implementing the latest changes to the proposal, but in the save section of 3.2, make sure the following sections are removed

@keshav0479

• extract resource IDs from the plaintext body via Note.linkedResourceIds(body) and call NoteResource.setAssociatedResources(noteId, resourceIds) directly. this must happen while the body is still plaintext because ResourceService.indexNoteResources() (L82-91) populates note_resources by parsing note.body in a background task - with an encrypted body it would find no resource IDs and mark all resources as is_associated = 0, eventually orphaning and deleting them. populating at save time keeps note_resources accurate. performance-wise this is lightweight: linkedResourceIds is a regex parse on the in-memory body, and setAssociatedResources is a single local SQLite write with known IDs, not a table scan. (from discussion with mrjo118, post #37)

@keshav0479

• on initial lock transition (unlocked -> locked): call RevisionService.deleteHistoryForNote() (RevisionService.ts, L378) to wipe existing plaintext revisions. subsequent saves of already-locked notes skip this step

Setting resources is not relevant anymore, and deleting revisions will be done on gated load instead (for an encrypted note only), but just deleting unencrypted revisions