File editing inside mounted encrypted vaults – one tiny fix away from becoming a game‑changer! #516
EGGGOOSE
started this conversation in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi dear developer,
First of all, thank you for Zettel Notes. It's an amazing piece of software, and I genuinely think it has the potential to become the only Markdown editor on Android that truly respects both privacy and usability.
Let me explain why I'm writing this with such passion – and why this feature request is not just for me, but for many others.
The problem I'm facing (and dozens of others)
I store all my personal notes, journals, passwords, and plans in an encrypted vault using gocryptfs.
On my PC, I mount the vault and use Obsidian for work with it.
On Android, I use DroidFS (which implements gocryptfs).
I sync my notes via Syncthing – only the encrypted files are synced between devices.
The vault is decrypted only when I need to work on a specific device. As soon as I'm done, everything is encrypted again.
This is true Encryption at Rest – even if someone steals my phone or laptop, they can't read a single word without my strong 20+ character password.
I work on a shared office computer sometimes, and colleagues could potentially access my files.
Leaving my notes unencrypted on that machine would be a nightmare.
With this setup, I can mount the vault, work, and dismount – leaving no readable traces.
Now, the challenge on Android: almost no Markdown app can open a whole folder inside a mounted virtual drive.
What I've tried (and failed)
I tested more than a dozen apps, including:
Logseq, Simple Markdown, JotterPad, WriterP, BeautyTyXT, Markor, Epsilon Notes, Open Markdown Markdown Editor, Quillpad, Material Files, Joplin, Obsidian, and many others.
So the situation is:
Then I found Zettel Notes – and it was a revelation
What already works (and it's 95% perfect):
ACTION_OPEN_DOCUMENT_TREE).[[wiki links]].But one thing is missing – and it's the final step:
Editing existing files. When I open a file, make changes, and hit save – nothing happens. The changes are lost. No error message, just silent failure.
(For comparison, Material Files can edit files inside mounted vaults, but it's a general file manager, not a dedicated Markdown editor like Obsidian with wiki links, search, and folder navigation.)
I am attaching a video that clearly demonstrates the problem:
https://github.com/user-attachments/assets/2451e5c9-c276-4cee-8206-6ab92418f895
Why this is critically important (not just a "nice to have")
If you add this, you will instantly attract everyone who has been struggling with Obsidian's security blind spot.
I've seen dozens of threads on Reddit, GitHub, and forums asking exactly for this:
And the typical answer from the Obsidian crowd is always a mix of 'nobody needs this', 'it's technically impossible', or 'it breaks the concept of plain markdown files' – even though dozens of real users have asked for it, and it would be trivial as an optional toggle.
You have the chance to prove them wrong.
What I'm asking for (technically)
takePersistableUriPermission(uri, Intent.FLAG_GRANT_WRITE_URI_PERMISSION).I believe the fix is relatively small:
takePersistableUriPermissionfor that file's URI.This would make Zettel Notes fully compatible with any virtual filesystem (DroidFS, Cryptomator, Solid Explorer's mount, etc.).
What I'm willing to do to help
I understand you might be busy, and I respect that.
But please consider that implementing this would give Zettel Notes a unique selling point that no competitor has. Not Obsidian. Not Logseq. Not any of the generic editors.
Thank you for reading this long message. I hope you share the vision.
With respect and hope, EGGGOOSE
All reactions