r/logseq

Logseq stores everything as plain .md files, but if you ever open one of those files directly on iOS (from Files, iCloud, Dropbox, a backup, etc.) you just get raw text. I built a small viewer to read them rendered on a phone.

Md Preview:

• Renders GitHub-Flavored Markdown — headings, tables, task lists, footnotes

• Code blocks with syntax highlighting, plus LaTeX math and Mermaid diagrams

• Opens .md / .markdown / .mdx / .rmd / .qmd from Files or the Share Sheet

• 100% on-device — no account, no uploads, no ads, no subscriptions

Free on the App Store: https://apps.apple.com/app/id6760341080

Details: https://markdown.cybergame.ai/

Not a Logseq replacement at all — just a quick way to read loose .md files when you're away from the desktop app. Curious how you all read your graph on the go.

I'm releasing Tine v0.3.0. This one took longer than I wanted, but I hope it's worth it. There are many nice small improvements and bug fixes, see my take on it below, and the full changelog after that, as usual.

But the big change was this. I periodically run an audit loop on Tine: have Claude+Codex look for places where data safety is in danger, or where performance is hit. During one of those I started to smell something fishy: I realized there's a bunch of bugs that look like the way Tine is parsing markdown is ... just a bunch of regexes, or something like that? This turned out to be true; while OG has a proper parser (mldoc), Tine had something either slow, incorrect, or both.

After some consideration, I decided to have Claude build a mldoc-compatible parser for Tine, which I'm calling lsdoc (for "logseq doc"). Anyway, this was the idea: the first iteration Claude came up with, despite the clear motivation, turned out to be... not quite a regex mess, but also not a properly designed, linear-time parser. It was, mostly, compatible -- a lot of the work went into quite serious differential testing wrt mldoc; and on "typical inputs" quadratic time may not bite you. But that's not what a computer scientist does, so I kept pushing Claude to do it right. That's what v0.3.0 was waiting for, and I think it's mostly done, so here goes. (On my very short subjective experience, I think it IS noticeably faster? but I'm not sure, and this is probably attributable to several other performance fixes, too.)

Other notable items:

• media niceties -- waveform view for easy audio navigation, draggable corners for images and videos, etc.
• web: tine.page
• native window controls
• multi-language spellcheck
• configurable asset name templates

...and many others.

If you want to contribute, I'm very thankful for anyone who tests and reports bugs on github! You can also take a look at CONTRIBUTING.md

The usual AI disclaimer: the only non-AI generated text is the above, everything else (code, docs, web) is AI. Take it or hate it :)

---

Full CHANGELOG.md

Claude's summary:

Beyond-OG features in Tine (0.2.0 → 0.3.0)

1. Genuinely beyond-OG (OG has no equivalent)

• Waveform audio player — OG's audio is a plain inline <audio>; the dimmed overlay with a waveform scrubber + ±5/15s skip + speed is Tine-only.
• Image/Video resize grip and the audio "⇔ widen" toggle
• Multi-language, live spell-check — basic spell-check is OG parity (Chromium's native checker), but checking several dictionaries at once, the auto-discovered dictionary tick-list, and applying it with no restart are all beyond-OG (Logseq needs a relaunch and one language).
• Configurable asset-filename templates (%yyyy %MM %assetname …) — OG has a fixed scheme; the token template is Tine-only.
• "Open in default external player" button — a WebKitGTK codec workaround; OG (Electron/Chromium) decodes inline and has no such button.
• Smooth scrolling (Lenis, opt-in) — a Tine feel experiment; no OG equivalent.
• Configurable [[/# autocomplete default — the link-first-match option is an extra Tine knob (the default still matches OG's "create unless exact match").

2. Beyond-OG by default — the "Differs from Logseq" family

(each can be toggled back to OG; the divergence is the default)

• Copy only the selected blocks, not the whole subtree (OG always drags the sub-tree).
• Strip collapsed:: when copying (OG keeps it).
• Click a block-ref → scroll-to-it-in-place, not zoom-in (OG zooms).
• The "Differs from Logseq" settings pattern itself (amber badge + "↩ Match Logseq" button) is a Tine-only concept.

3. App-shell / diagnostics — Tine-specific, no OG analog

• Native window controls — macOS compact overlay traffic-lights + the Linux/Windows "system frame vs Tine's compact controls" toggle. OG just uses standard Electron chrome.
• Startup debug mode (TINE_DEBUG / --debug trace file) and the software-rendering warning banner — both exist because Tine is a Tauri/WebKitGTK app; OG has neither.

Hi! I vibecoded Tine, a drop-in Logseq OG replacement mainly built to be faster, but also with some features I missed.

The why: I loved using Logseq, but at some point realized I can't use queries because they are slow / make logseq use a lot of CPU even when idle (yeah weird). Then every summer my laptop starts overheating and it is partially because of the electron apps. When CPU throttles, the apps get slow. Surely there must be a way to do this faster.

The what:

• I first just wanted logseq, but faster. I don't use whiteboards, flashcards etc., so these are currently unavailable. I focused on features that I use.
• It just works over your OG graph -- reads and writes the same files. It should be safe and compatible but it was only ever tested by one person, on one platform, one graph, so be warned. (On the other hand yes, I am actually using this on my real graph worth 5 years of life, and I'm syncthing-ing it to my Android phone and there editing it using the logseq app, and nothing has broken yet.) Also, there are automatic backups.
• I added some features that I liked -- some I knew from OG plugins (tabs), some just seemed like a (really) nice thing to have: tabs, focus+dim mode, quick-capture, carry tasks to today, etc. Look at the readme.

AI: full disclosure, everything except this text is completely vibecoded, including the README.

Let me know what you think / any ideas for changes / features etc. If you find bugs, let me know via github issues. This is still beta at best, so bugs are expected.

They said the stable DB release would be out around May–June, but it’s not happening.
We’ve been hearing about DB version release since last June and still no release date, just more delays.

At this point I have no idea when it’ll actually land. Maybe next year.
Honestly, I’m starting to think it’s time to move on.

Just Markdown files, edited through a live table.

Still early, but this is one of my favorite parts of Yamlink.