You can just encrypt your partition and use a file editor.
you can certainly do that, indeed.
Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
41–50 of 71 posts
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#42[flagged]
Hey, thanks for the feedback! Yes, currently in the preferences you can see the path of your local SQLite DB file, so you could definitely sync that to the cloud. I will improve it further in next releases to make it even simpler (for example, by defining a custom path for the store, which cannot be done currently), but it can definitely be done already. Regarding the key for recovery: you can already do it. Mini-Dia…
for aem
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#43This is Nice. However, how do one access their diary, when you stopped maintaining it? Is this targeted more at the technically inclined, high-profile people who need to keep secrets? Personally, I believe that for something like a diary/journal, it should be in a format easily readable by most tools (so a Plain-Text or a MarkDown at best), then it is in a container/folder. Now, encrypt that container/folder instead.…
When I had a Mac I used an encrypted volume in Dropbox. (Not sure if that's a good idea, but I didn't have any issues.)
I used Notational Velocity in those days :) A rare gem of ergonomics.
Later I did the same thing with a VeraCrypt volume.
Now I'm in Obsidian, which has its own encryption (if you trust 'em!), but never quite got the frictionless feeling of NV back.
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#44There already is another, unrelated "Diarium" journaling app:
https://diariumapp.com
It's a paid app, not open source, but I've been using it for years and it has been working very well for me.
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#45This is Nice. However, how do one access their diary, when you stopped maintaining it? Is this targeted more at the technically inclined, high-profile people who need to keep secrets? Personally, I believe that for something like a diary/journal, it should be in a format easily readable by most tools (so a Plain-Text or a MarkDown at best), then it is in a container/folder. Now, encrypt that container/folder instead.…
When I had a Mac I used an encrypted volume in Dropbox. (Not sure if that's a good idea, but I didn't have any issues.) I used Notational Velocity in those days :) A rare gem of ergonomics. Later I did the same thing with a VeraCrypt volume. Now I'm in Obsidian, which has its own encryption (if you trust 'em!), but never quite got the frictionless feeling of NV back.
The Alternate Notational Velocity (nvAlt) was my go-to for a very long time. https://brettterpstra.com/projects/nvalt/
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#46Thank you for sharing this, this is very interesting problem to tackle.
I find this interesting mostly to understand how you are handling encryption and security. I think this is one approach but others expressed concern over long term viability.
Using Tauri is also very interesting. How did you find using it for this simpler case?
Anyhow, very cool project. Don't aband it :)
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#47I like the idea, as a niche project for users that don't have control over their hardware/OS, or run on USB flash for portability.
Speaking of which, I have notes / journal entries dating back several decades, all in plain text files. I'm worried about these new projects and their longevity and whether it'll be actively supported 30 years from now. For simplicity, I'd use gocryptfs, Veracrypt, or other general file-based encryption which suits your risk tolerance, and use whatever editor (ie Obsidian, vscode, OneNote, etc) I want to use.
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#48> Every entry is encrypted with AES-256-GCM before it touches disk Until the OS needs more memory and swaps your secrets out.
The "before it touches disk" thing in the promo copy is silly, yes, but there's really no sane threat model for this; from every vantage point where this could matter, you already have game-over attacks on the app.
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#49This is Nice. However, how do one access their diary, when you stopped maintaining it? Is this targeted more at the technically inclined, high-profile people who need to keep secrets? Personally, I believe that for something like a diary/journal, it should be in a format easily readable by most tools (so a Plain-Text or a MarkDown at best), then it is in a container/folder. Now, encrypt that container/folder instead.…
yeah, currently you can export your journal to json or markdown files. So you can walk away at any point. Vendor lock-in is one of the main things i wanted to avoid. That's why I sticked with boring and standard libraries and encryption as much as possible. Thanks for the feedback!
You could store the encrypted contents in an IPFS collection or just use old DHT. Obviously someone else needs to access the content to keep it fresh (even if they don't have the ability to decrypt it), but considering it's markdown you could run an "official" seeder that seeds everything or just have each client run an IPFS node etc.
Re: Show HN: Mini-Diarium - An encrypted, local, cross-platform journaling app
#50Earlier quoted context omitted.
yeah, currently you can export your journal to json or markdown files. So you can walk away at any point. Vendor lock-in is one of the main things i wanted to avoid. That's why I sticked with boring and standard libraries and encryption as much as possible. Thanks for the feedback!
You could store the encrypted contents in an IPFS collection or just use old DHT. Obviously someone else needs to access the content to keep it fresh (even if they don't have the ability to decrypt it), but considering it's markdown you could run an "official" seeder that seeds everything or just have each client run an IPFS node etc.
That's definitely an interesting idea