PKM/Log/26/09/23 Wed - Stacked Discussions in Multi-Tier Gardens

• 2026-09-23 Wed
  • Yesterday, I wrote a bit at Music/Composition/Log/26/09/21 Mon - iPad Microfreak Session 2. A bit earlier, I wrote in a similar namespace in my higher Privacy Person/codekiln/GitHub/logseq-garden, a private Logseq garden of mine that "descends" from this one (meaning that it inherits all the skills and entities, and proxies some of the pages) at Music/Making/Log/26/09/19 Sat. This morning I wanted to unify these namespaces.
  • I was considering migrating Music/Making to Music/Composition, so I could maintain Logseq/Entity/Proxy/Page with logseq-url:: and logseq-proxy-last-sync-date:: frontmatter in the higher Privacy garden. I haven't yet created that proxy entity, but I do have a rulesync/Skill called logseq-proxy which does this today in my repos, making it possible for the main version of a page to exist in one Gard/en and "descending" (to use ancestry) or "downstream" pages to exist in other Gard/ens.
  • That made me imagine that maybe I should make a way to "layer on" a private comment onto page that was proxied. I already have the convention that a .../XYZ/Discussion page was is a discussion of XYZ. This is used my principles, for example, My/Principle/Simplify/Fewer and Deeper/Discussion is a discussion of My/Principle/Simplify/Fewer and Deeper. What if this could be enriched such that if there was a Logseq/Block/Reference from the parent page in the child page, then that node and descending nodes were considered to be commentary on the parent page?
  • I'm interested in systems that have layered representations of the same entity. For example, I might represent a specific Mozart Sonata entity in a public knowledge garden, then in a more private garden I might reference that Mozart Sonata entity but put it in the context of my private memories of when I performed it, my struggles while practicing it, etc. I suppose one could compare this to Chess/3D.
  • Anyway, if I had Discussion pages that referenced blocks in the parent page, then I could see and expand those block references in logseq, and see the comments, allowing a sort of metanarative layer sort of akin to
  • The challenge in achieving metanarrative fluency in linked, proxied logseq pages is making a shortcut to creating and copying a block reference in the upstream page. In a single garden, I can press Cmd+C to generate and copy a UUID block reference that gets expanded elsewhere. But if I'm in the "downstream" representation of a page and I click Cmd+C in Logseq, it creates a Logseq/Block/Reference that doesn't propagate to the "upstream" representation easily. So, I'd like to make a way that if a page is a Logseq/Entity/Proxy/Page and it points to a remote garden, then the Cmd+C keyboard shortcut or another affordance would create a block reference that would originate in the upstream page, so subsequent syncs of the page would bring it down, creating a stable reference.
  • This is all very related to an idea from earlier this year, using two fuzzy hashes to represent a range for discussion. In general, markdown documents don't generally provide the best method of providing rich commentary on discussion. That's actually one of the core motivating features for Logseq: if markdown consists of Logseq/Blocks that are unordered lists in Markdown, then one can nest as deep as you practically could need in order to satisfy the ability to go deeper into the topic and provide metanarrative. But with logseq proxies, one can't comment on the upstream page easily ... but one could get around this with the hack mentioned above.