-
-
Notifications
You must be signed in to change notification settings - Fork 13
Design privacy-first local scan history #162
Copy link
Copy link
Open
Labels
appThe Tauri desktop appThe Tauri desktop apparchitectureWorkspace layout and engine designWorkspace layout and engine designenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededlevel: advancedCross-cutting or safety-critical design workCross-cutting or safety-critical design workpriority: mediumWorth doing, not urgentWorth doing, not urgentsafetyTouches the read-only / quarantine guaranteesTouches the read-only / quarantine guaranteesui/uxInterface design, usability, and visual polishInterface design, usability, and visual polish
Description
Activity
Metadata
Metadata
Assignees
Labels
appThe Tauri desktop appThe Tauri desktop apparchitectureWorkspace layout and engine designWorkspace layout and engine designenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededlevel: advancedCross-cutting or safety-critical design workCross-cutting or safety-critical design workpriority: mediumWorth doing, not urgentWorth doing, not urgentsafetyTouches the read-only / quarantine guaranteesTouches the read-only / quarantine guaranteesui/uxInterface design, usability, and visual polishInterface design, usability, and visual polish
Goal
Design a privacy-first local scan history.
Users may want to compare the last scan with the current scan, but Diskern must stay local, understandable, and safe.
Why this is advanced
A scan report contains file paths. Storing history needs a careful privacy design, not just a new array in local storage.
Possible shape
A first design could store only summary data by default:
{ "scanned_at": 1760000000, "root_label": "Downloads", "files_scanned": 12000, "total_reclaimable": 1800000000, "category_totals": { "browser_cache": 600000000 } }Full paths should require an explicit choice.
Acceptance criteria