Purchase should have a Logseq/Entity/Time/Year and a Logseq/Entity/Time/Date. you'll need to define the later. Look at Logseq/Frontmatter attributes like date-created on pages to get a sense. Keep in mind that the date should be a journal reference, and it doesn't matter if the journal reference exists on disk. Also, in my logseq configuration, references that include the day of the week at the end resolve to a journal in either YYYY-MM-DD or the format that includes the weekday abbreviation suffix, e.g. 2026-09-24 or 2026-09-24 Thu resolve to the same file in Logseq.
file a Logseq/Entity/Question: generally speaking, what's the difference between Audio/Connector/Line/Out/Port and Audio/Connector/Headphone/Port? Specifically on Zoom H5, what's the difference?
file a Logseq/Entity/Question: how can I connect Zoom H5/Port/Line Out to Macbook/Port/Headphone or Macbook/Port/USB/C or iPhone/Port/Lightning so I can record audio on those devices while also using Zoom H5/Port/Headphone for monitoring? Assume that i'm in Zoom H5/Mode/Audio Interface/iPad. Assume that I know I can purchase a dedicated breakout box like the Focusrite/Saffire but I need a solution that's very small and lightweight since I need my whole setup to fit in a single backpack. I'd rather not have two dedicated audio interfaces unless there really is no other way.
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 PrivacyPerson/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.
create a Logseq/Entity/Trade-Off and Logseq/Entity/Trade-Off/Component. Basic characteristics: H2 for Summary, then H2 for The Trade-Off, H3 Headings for each of the sub-items that are being considered should be linked to sub-namespaces, with nested logseq page embeds for the Logseq/Entity/Trade-Off/Components. Page names like the ones below, for example, X/vs/Y with alias X vs Y Trade-Off. Entity must not stipulate that there are only two choices; it must handle n choices where n is approximately less than 10.
Create a new Logseq/Entity/Term/Acronym. This entity should be able to be added onto any page that already is a term page (it would have more than one entity). The subset of Term entity pages that have this acronym entity attached would have a page whose name is an acronym and has an alias of the fully expanded acronym, for example, TAM page would have Total Addressable Market. Like all entities by default, pages that are Acronyms can be at any position in the logseq namespace hierarchy.
Create a new Logseq/Entity/Field of Study to which should be applied to pages that represent a domain of human expertise. Those pages don't have any characteristics that define their page names or namespaces; they can appear anywhere. An example is Password/Manage/ment; Field of Study doesn't appear in the name. It's not required to be in conjunction with any other entity, though that example happens to be a Term entity.
look at the logseq-proxy rulesync skill, then push as much of it as possible and practical into the entity system by making Logseq/Entity/Proxy/Page as an entity definition. I want the behavior of the skill to remain functionally the same but to decrease the amount of text in it, assuming that the agent will read that logseq entity for the details. In general, I'm trying to converge on the Logseq Entity system as the place of record for things that would otherwise be located in Agent/Skills delivered by rulesync.
look at the /logseq-question command/skill in rulesync and move as much as possible for it into Logseq/Entity/Question to slim it out. If there is a command, remove it and port it to a skill. Submit a pr using a worktree after checking my preferences.
define Logseq/Entity/Feed/Subscribed as a way to describe feeds that I intend to subscribe to in my RSS/Reader of choice. Then a certain entity designation on a blog would mark it for my read-it later app, so that I can use Readwise automation in the browser or through the Readwise/CLI or Readwise/API or MCP to ensure it's in my subscriptions
file a Logseq/Entity/Question - does Obsidian have a Collapse All feature, and if not are there Obsidian/Plugins that support this? I'd prefer it if the collapse status of a heading could be in the markdown document (similar to Logseq/Block/Attribute/collapsed )
Have a worker in a worktree create a Logseq/Entity/AI/Model to replace logseq-encode-garden/.rulesync/skills/logseq-ai-model. That way the entity system is all that should be necessary to create these types of entities. Submit a pr when ready, opening it in tuicr in a tmux window appropriate named; also linked here:
refactor: replace the logseq-ai-model skill with an entity · PR #26 · codekiln/logseq-encode-garden — the entity absorbs the provider namespaces, the model-code alias, both page shapes and the upkeep rules, and adds what the skill left implicit: a family, a model kind and a product built on a model are each not instances. Open in tmux switch-client -t '=logseq-encode-garden:pr 26 ai model entity'.
file a Logseq/Entity/Question: in LazyVim is there a way to quickly see what PRs are open if my pwd is a git root right in vim? I know gh-dash can do this but I'm lazy
I need my AI agents to understand that they should not use the memory system specific to their harnesses unless I explicitly grant them authorization to do so. I switch between agents so frequently that doing that would be counterproductive, as a memory saved to one provider's harness location is not accessible to another coding agent. In general I work in git repos knowledge gardens, and those preferences should be stored in such a way that is provider neutral inside that repo or knowledge garden. To that end, create My/AI/Rule to capture this, as that namespace is read upon agent load. If agents want to, they can ask me where a memory should be recorded.
create Logseq/Entity/Question entity - when I enter :pwd in LazyVim, it pops up a message in a tiny box and I can't see the full path. How can I easily see recent messages in LazyVim?
please create Logseq/Entity/Article/Blog as a more specific entity. In general, I prefer Person/<Name>/Blog/<YY>/<MM>/<slug>, with a readwise-url if one exists.
please create Logseq/Entity/Series. A Series should be combined with another entity to represent a sequence. By default, Series should appear in the Logseq namespace after the entity type and before the entity, and the parts of the series will appear clustered by the series as well as in order on the filesystem when sorted Lexicographically. For example, while Logseq/Entity/Book would imply that Philip Pullman's book His Dark Materials should have a page at Person/Philip Pullman/Book/95/The Golden Compass, if a page is both a Book and a Series entity, it should then be rightly be placed instead at Person/Philip Pullman/Book/Series/His Dark Materials/<Appropriately Zero-Padded ordinal>/95/The Golden Compass, or Person/Philip Pullman/Book/Series/His Dark Materials/95/1 - The Golden Compass. If a page is both a Podcast and a Series entity, similar rules should apply, and similar combinations for other entities that form a series. 1 here is an optional appropriately zero-padded ordinal. If the series currently terminates in n digits of ordinal references, then all instances should be zero padded to n digits so that sorting them lexicographically does not perturb the intended order. The intention of the ordinal is to aid in memorization or identification. In the case of a podcast, an ordinal number should never be given unless the podcast's published feed and/or title references that ordinal number such that one can google "<podcast name> episode <number>" and reliable get to the episode in the top hits. Hard requirement: the entity definition for a series must not imply that "series" is particular to books and podcasts and must be stated in a way that generalizes across the garden to its applications elsewhere. Books and podcasts may be used in the entity definition as examples as long as they are accompanied by examples that are not Books and Podcasts.
please create Logseq/Entity/File/Format as a light-weight entity specifically for file formats, for example, docx, PDF, ePub. A page that is a file format entity should list things such as operating systems that support it, it's basic structure, the standards that it represents, the evolution over time, etc.
create Logseq/Entity/Time/Year as an entity meant to model a particular year, while also modeling decades and centuries. For example, 19/5/9 should be aliased to 1959 and represent the year 1959. Then 19/5 should be aliased to 1950s, and 19/0 should be aliased to 1900s and 19 should be aliased to 1900-1999.
update Logseq/Entity/Time/Year to indicate that logseq-created-time-year:: should be the logseq property that is used to point to a particular time and year. This is applicable broadly speaking - Books, Movies, Podcasts, Essays, Musical Compositions, Works of Art, etc. Update downstream entity definitions as well to mention this precedent. Create Logseq/Entity/Time/Year/Todos with logseq todos for pages to backfill and their explanation.
By adding prominent Knowledge Gardeners to the garden