Tine
v0.2.0 June 26, 2026 · original r/logseq thread ↗

Tine v0.2.0 — drop-in faster Logseq OG replacement

Two days after launch. My announcement, unedited — the AI-written changelog is linked, not pasted.

Two days ago I announced Tine. Thanks for the support and for everyone who reported bugs + feature requests. I tried to make progress on them — org-mode support, custom date formats and many others. See the (AI generated) changelog, hence v0.2.0.

I still have some items on my backlog from what you shared:

  • look into plugin support (I'm definitely not hopeful for full plugin support but maybe something can be done)
  • somebody mentioned something with namespaces

Then I have some ideas of my own. But feel free to give feedback, especially:

  • bugs
  • OG features that are missing / don't work as they should
  • features OG doesn't have but you wish it did (and are compatible with the on-disk format)
📦 v0.2.0 release & full changelog ↗ 💬 Full discussion on r/logseq ↗

From the discussion

Three exchanges that shaped how I think about Tine — a product philosophy, a design decision worked out in public, and a feature request I had to really understand before answering.

“If it works, don't fix it”

Petrush

Thinks this is a very interesting development: feature-wise Logseq is very good, but its performance and maintenance aren't convincing anymore.

Me OP

Thanks. I think (also based on my experience) that people have negative feelings when software "does not keep evolving". But I think this is a bad instinct - if it works, don't fix it. So Tine might disappoint - I hope to get it to a place where it serves my needs well and then only add features that bring genuine value, which might mean long stretches of time when nothing apparently changes (just bug fixes). We shall see of course.

Designing asset naming, out loud

MrAiupov

Wants one unified asset-filename scheme — a pure yyyymmddhhmmss timestamp. His reasoning is careful: he switches between Windows and Linux, where file-creation metadata isn't reliably preserved, so putting the timestamp in the name is portable and means sorting by name always equals sorting by time. It also removes the small friction of thinking about names at all. He'd keep original names only where they carry meaning (PDFs, documents) — so maybe timestamp by default, keep-original as an option.

Me OP

It feels like you must be using a very different flow than me..?

So: I never name assets explicitly. How do assets get into my graph:

  • pasted images, or
  • the /upload asset command which I use for PDFs mainly (but possibly audio, video)

The pasted images I don't name and it seems that they fget just timestamped by default. The uploaded PDFs etc are exactly where I would like to preserve the name somewhere because it tells me what's in the pdf.

For sorting it should be enough if I did timestamp_assetname.ext - no?

MrAiupov

timestamp_assetname.ext — good idea 😳

Do you really need split view?

cons_ssj

Wants true split view like VSCode/Obsidian — several long notes open side by side, each pane with its own tabs, so he can read, edit, and reorganize between them. He knows about Tine's sidebar but finds it uncomfortable for long notes: for him one “note” can be a whole project, and he can't keep several of those open at once.

Me OP

Not right now, the thought crossed my mind though. But are you aware of the sidebar? This is already an OG feature, it's just one of those that made it very slow and not comfortable to use for me, which is why I created Tine.

You can shift-click any bullet or page link, and it will open that block/page in the sidebar (you can open multiple at the same time and they will be stacked on top of each other in the order you opened them). They are fully live & editable in the sidebar. Do you think you need true split view - i.e. you use e.g. three-way splits, horizontal splits etc.?

Me OP

Thanks! I think it explains well what you want. I think mainly I was confused by you writing that even side by side reading would be great when the sidebar already supports that, but both the links show functionality that goes well beyond the sidebar. I'm not sure I'd ever use that but I think it makes some sense to have it if I can get it right. I'll focus on fixing bugs and adding easier features for now but keep this in the backlog.

How to read this: comments by other people are Claude's summaries — it tries to be faithful and generous — and the originals are linked on Reddit, so you can check; my own replies are quoted verbatim.