YuukiJyoudai

Well written. I completely agree with you.

The Matrix got me into programming, so honestly this was inevitable.

Agreed. IDs feel like the right starting point — names before verbs.

From there, I could imagine thin protocol layers emerging above — renderers, voice interfaces, AI agents each binding their own behavior to the same IDs. Markdown stays plain text. Complexity through composition, not bloat.

Thanks for the reply — first time posting on HN, so this really means a lot.

Just checked out Voiden. Same philosophy, different layer: plain text, git-native, composable. You made API requests executable Markdown. We made dev workflows executable Markdown. I'm also building a cross-platform `.md` viewer (Tauri + Mermaid). All-in on this format.

I think `.md` is quietly becoming an *interactive runtime* — not just docs. Your work is proof of that.

Excited to see where this direction goes. If there's ever a way I can help or collaborate, I'm all in. What a time to be building. Let's see what unfolds.

Thanks for being my very first HN reply — genuinely appreciate it.

The short answer: I cheated by staying in the Apple ecosystem.

The sync has two layers:

- *macOS ↔ iOS*: iCloud handles it natively. Obsidian's iCloud vault is just a folder, both devices read/write the same files, syncs in seconds. - *macOS ↔ GitHub*: A launchd job runs `git add + commit + pull --rebase + push` every 5 minutes. That's the entire mechanism — it's in `scripts/sync.sh`.

So there's no magic — iCloud does the heavy lifting for mobile, Git handles versioning and cross-platform backup.

Your Android problem is real and hard. Android doesn't give apps transparent filesystem access the way iCloud vaults work on iOS. I haven't solved that yet. The closest path I can think of: Termux + git clone + symlink into Obsidian's storage, but that's far from "zero effort."

This is worth thinking about more deeply. If I find a clean solution, I'll come back and share it here.