16-Jul-22: Logseq Namespaces, GTD, Building a Second Brain, Plugins, Workflows

This week seems to have flown by. Wimbledon has been and gone, The Open is currently being played, the start of the new football seasons is nearly up us, people are complaining of the heat – Feels like summer is well and truly underway.

Of course if you are in the southern hemisphere, hope you are not feeling too cold.

Let’s wipe those sweat beads from our brows, or grab an extra layer of clothing, and see what Logseq has in store for us this week.


No updates as of yet this week, but there have been some musings in the Discord about a few improvements in the filtering and properties. Will be interesting to see what comes out.

Logseq News / Events

  • The first Learning Sprint is up and running. Be sure to check out Learning Sprints even if you are not taking part. Ramses and the group are showcasing interesting aspects of learning and queries.
  • For those that prefer not to / cannot log into Discord, you can now use Element / Matrix as these have been bridged. You can join the Logseq’s Matrix space via: https://matrix.to/#/#logseq:matrix.org

Logseq Mobile

To access the mobile apps, please use the respective link for your OS below.

Logseq Workflows

@aryansawhney17 provides us with a great video on Namespaces and how we might go about using them. Definitely worth checking it out in full.

Staying with videos, Productivity Toolsets presents to us video on Tips for effective note taking using the new Official Logseq Readwise Plugin

Ramses confirmed that Logseq Sync is being internally tested between the team and should be released in closed beta this summer.

Mike Jones did ask an interesting question which I am sure if on a lot of peoples mind “If we donate can we get into the closed beta? If so do we have to donate before a certain date?” No responses yet, but be sure to keep an eye out.

Brian Sunter has a really col public Logseq graph that is worth checking out here. He showcases his learning and managing projects, as well as a Newsletter about his undertakings.

Definitely worth having a peek.

A very interesting thread on how best to structure meeting notes, Looks at doing it on the meeting page or the daily notes page, and how best to structure the notes to ensure you can capture, and retrieve, all the information required. Thanks Aeonik and danzu for this discussion.

LazerGonzo is wondering: are there a recommendations of how to implement for the following:

1. Capture to-do items and take notes. Basically a digital inbox for the style of the GTD system I’d like to implement. Capture items, organize into projects with sub-tasks, create to-do list of next items. Currently using Todoist and I like it, but part of developing my tech skills beyond novice is moving to open-source and FOSS environments.
2. General collection of personal knowledge: the things I know and want to mine for insights.
3. Take targeted notes on works I am currently reading or content I am creating. Examples would be reading notes on a book about sociology or an article about philosopy. Outlines of articles, essays, or other writing I might be doing (fiction and non-fiction).
4. TTRPG development. Specialized use for a hobby of mine. Writing both supplemental items such as campaign settings such as ruleselts, item lists, bestiaries, and adventure modules. Also writing notes, adventures, and so on for active games that I run.

In general, would I use one graph? I’m pretty much drowning in information with no way to store, organize, or use it. All the types of things I described (and MANY more) are spread out over multiple platforms and file formats. Not looking for a one-app-to-rule-them-all, but rather trying to build up a system and work environment that I can integrate each of these areas. I will admit that the more of these that can get centralized the better.

Thread with responses to the above thought provoking points available here.

Would a rich commitment to hierarchies and classification be an anathema to Logseq culture? I appreciate hierarchy as a way of clarifying thought. I don’t mind if it breaks down or goes stale from time to time. Cleaning it up, when I feel the need to, restores clarity in an important way.

I especially don’t mind if hierarchy is partial, in connected-thought environments like Logseq. I view hierarchies as lists of saved queries that provide me with a clean way into my graph. I appreciate them as a tool, alongside chronology (Journals), favourites, search, query, hyperlink traversal, graph examination, scanning the linked and unlinked references, and looking at tag clusters.

Hierarchies are filters over some of the graph that help me get close to 100% signal and 0% noise, at the cost of excluding interesting adjacent ideas. However, with a bunch of other access pathways in the mix, you can use hierarchy to find your starting point for a work session, then shift to other strategies of traversal. The Journals page is used the same way in many people’s workflows.

The post and the comments and worth reading if you are interested in hierarchies.

For more fun with Logseq and “Banner” plugin (or “Solarized Extended” theme background), you can use Unsplash random image API! Just set in settings for the default page/journal banner:

Interested in Tiago Forte’s book “Building a Second Brain”? – This may be the summary for you. I love how James also teases us that a video implementing PARA and the like in Logseq is coming up.

Tip about namespaces (thanks Sawhney): Let’s say I’ve got a page called Python/Functions and also one called Clojure/Functions.

I can actually query for both of the pages together using “{{query “functions]]”}}”

Logseq Feature Requests

You can check out the full list of Feature Requests here.

  • Improve Graph Functionality – Clicking and holding a node brings its neighbours into view. Right now, it moves things around but doesn’t really pull them into view. Have a way to zoom in on a node and its neighbours without just bringing up the node in isolation. Right now, if you search for a node and bring it up, you just get a blue dot hanging there, and if you click it, you go right into the text view. Two nodes having links in the same block should create a link between them. This is especially important for people who like to use the journal but don’t want to rely on journal entries in the graph view. Have a sidebar which shows the graph view and automatically zooms in the current page whenever you switch pages. Kind of like Joplin’s graph view plugin.
  • Icon property for blocks – Since Logseq is more around blocks and pages are just collections of blocks with a name I think it would be nice to have the icon:: property for blocks too. I suggest to render it as the bullet point of the block (There is need for some effect for collapsed blocks though. Also, it would be better if the icon:: ... line is not displayed when not editing a block (like title:: for pages)

  • PDF Annotation: plain link to logseq block – I would find it useful to be able to make plain links between logseq blocks and pdf locations. This is kind of doable today with highlight/region but it would be more clean I think to have this possiblity directly. This is usable if you want to map a pdf but not using directly words from the pdf (like argument-1, argument-2, …) I would imagine a mouse drag from an arbitary location in the pdf with a line to a block in logseq (and opposite way). Some small symbol could indicate the location in the pdf and the “PXX” symbol in the block could indicate there is a link.
  • Hide icon:: property like title:: – When you are not editing the properties of a page the title:: property is conveniently hidden. I think this would be appreciated for the icon:: property too, since it looks redundant:
  • Nested (Conditional) flashcards – It would be great if card-B was only shown to me once I had successfully remembered card-A. I think this is feature would take flashcards to the next level and allow people to build knowledge STRUCTURES in their memories. I’ve shown two ways to do this in the images, I’d be fine with either.
    Screenshot 2022-07-12 at 14.27.05

Logseq Plugins

  • block Calendar Have you wanted to have a calendar on the right sidebar in @logseq like Obsidian? Now you can!! I am thrilled to announce Logseq Block Calendar was just released! Now you can render a calendar in blocks and put it wherever you want. Will be in the Marketplace soon
  • Omnivore – We’ve updated the Omnivore plugin to 1.6.0. This version makes it easier to choose your syncing options when importing your Omnivore library into Logseq. We’ve added a dropdown that allows you to choose between importing all your saved articles, only your highlighted articles, or using our advanced search syntax to customize (for example, you can use label:logseq has:highlights to import all your highlighted articles with the logseq label attached. This also fixes syncing issues for users that have multiple graphs.
  • Anki Sync – Major update to Logseq Anki Sync (V3.1.1) – Anki cloze macro support – experimental active cache for logseq api – enhance: dependencyHash Calculation algorithm.

Many thanks as always for reading this latest edition of Logseq Weekly.