37fc42eb73
* GSoC root file This is the root file for the Google Summer of Code program * Fixed TOC * Introduction to GSoC with Joplin The first draft cloned from https://community.kde.org/GSoC * Joplin's Application at GSoC template Cloned from https://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2019/Organisation_application * GSoC 2019, idea #1: deeper Nextcloud integration * GSoC 2019, idea #2: sharing notes * GSoC 2019, idea #2: tag handling * GSoC 2019, idea #4: search improvements * GSoC 2019, idea #5: per note password protection * Update GSoC_Idea#1.md * Update GSoC_Idea#2.md * Rename GSoC_Idea#2.md to GSoC_Idea#2_sharing.md * Rename GSoC_Idea#1.md to GSoC2019_Idea#1_Nextcloud.md * Rename GSoC_Idea#2_sharing.md to GSoC2019_Idea#2_sharing.md * Update and rename GSoC_Idea#3.md to GSoC2019_Idea#3_tagging.md * Rename GSoC_Idea#4.md to GSoC2019_Idea#4_Search.md * Rename GSoC_Idea#5.md to GSoC2019_Idea#5_Password per Note.md * Update GSoC2019_Idea#1_Nextcloud.md * Create GSoC2019.md cloned from https://community.kde.org/GSoC/2019/Ideas * Rename Introduction.md to GSoCIntroduction.md * Rename GSoCIntroduction.md to GSoC_Introduction.md * Rename Application.md to GSoC_Application.md * first draft of a public introduction and project idea page, plus first (filled) template for ideas * added idea * started to update org details * Delete GSoC_Application.md moved to forum * Update summer_of_code.md put the template in a <details> block. little improvements where to publish ideas and applications * Update summer_of_code.md put application in quote
1.2 KiB
additinal protection per note
- [Feature request] Password or pin protection
- [Suggestion] Add instructions to generate app-specific password enhancement
- Turtl Documentation - Security and encryption
Password or pin protection: It’s very unclear what people want. It seems the threat model is you give your unlocked phone or laptop to someone, and you don’t want them to see your notes. But of course, the solution is to not do that. All devices these days support multiple accounts, so there’s no point giving their unlocked device to someone they don’t trust. I think we should remove this issue until it’s betted defined. Perhaps it should go to a different category like, “to be specified”. We need to know what’s the threat model, what people want. I’ve heard dozens of variations (locking the app, obfuscating the data, encrypting the data, encrypting a note, a notebook, encrypting a part of a note, etc.) so it’s unclear what needs to be done. I guess for me it seems so unnecessary that I can’t quite wrap my head around it.