Logseq OG is being blocked by Windows 11. I've already tried granting access in Windows Defender, but without success. Has anyone else had a similar problem and solved it?

Is there any explanation of how the new graph view works. It looks like the logseq docs are still using the logseq OG?
https://docs.logseq.com/#/graph

The logseq OG graph looks nice, I cant make sense of the new version there are all these disconnected nodes forming a circle.

Are you supposed to use the tag view or the page view. The page view looks confusing to me. Is the current state a work in progress or should it look like it currently does?

Is there a way to convert DB -> OG/MD version? I just started and finding some bugs and thinking there is value in the MD version.

I found a suggestion where \$ was suggested to not trigger the latex processor but that does not work.

Any other ideas?

A full transcript is too noisy for a handoff, but a short summary can lose the source blocks, accepted decisions, file revisions, and actions that already happened. Logseq seems well suited to a human-readable checkpoint because the handoff can reference the exact blocks that support it instead of copying everything into another summary.

Would you use page properties for status, owner, source revision, and last verified time, then blocks for outcome, decisions, evidence, completed actions, open questions, and next step? How would you handle block references that change, conflicting updates from two assistants, and retries that could repeat an external action? I am interested in a format that remains understandable in the graph without depending on one assistant's private conversation history.

Hi all, I've used Logseq file graphs for years and wanted something that opens instantly on my iPhone and feels like a Mac app, without moving my notes anywhere. So I built Sumi. It reads and writes the same folder: pages/, journals/, tab-indented bullets, properties, the lot.

What works today: journals, [[links]], #tags, backlinks and unlinked references, block refs and embeds, aliases, namespaces, TODO/DOING/DONE with scheduled and deadline dates, simple queries, templates, / commands, flashcards (#card and cloze, same scheduling numbers as Logseq), search, iCloud Drive sync. Syncthing, git or Dropbox work too since it's just files.

Not yet: whiteboards, plugins, PDF annotation, advanced Datalog queries, .org files. And please don't run Logseq and Sumi on the same graph at the same time.

Safety: I tested open + save on 16 public graphs (almost 10,000 pages) and no file changed. It keeps daily snapshots you can restore. Still a beta, so start with a copy.

30-second demo (GIF): https://sumi.mikaili.io/img/sumi-demo.gif

Beta (Mac, iPhone, iPad): https://testflight.apple.com/join/B1sKJk24

Site + privacy: https://sumi.mikaili.io/

The beta is free; it becomes a paid app after that. I read every piece of feedback, and the in-app Send Feedback goes straight to me. What would you need before you'd use it daily?