In this week’s episode, which is a couple of days later than planned due to a holiday (and getting on a plane for the first time in about 18 months), there has been a further release of Logseq, new plugins, and discussions regarding task management and linking.
- Officially released to the public and includes a lot of new additions and bug fixes.
- The most notable improvement was fixing a lag issue that affected users who had many linked and unlinked references on a page. The fix seems to have resolved this issue, but it will be interesting to see what happens long-term as your second brain (and pages and links) grows
- We were also introduced to an updated search which included search history. The default keyboard shortcut is a little odd (ctrl+k), but this can easily be remapped in the settings.
- Full image viewing to see your images in all of their beauty in full screen.
- Unfortunately, a critical bug was introduced, which meant that 0.4.1 was released shortly after. The good news is that the Devs fixed the bug but also added a couple of new additions.
- The new update fixed a few bugs and especially one related to Codemirror that would not save new additions
- Improved slash (/) smoothness was introduced to make the writing experience better.
- Improved query display
- PDF annotation enhancements
- Improvements to the document mode layout
A few new plugins were added to the Logseq marketplace, including:
- Hypothesis – Hypothesis.io plugin developed by @c6p that allows you to retrieve your online web annotations and insert them directly into Logseq. All you need to do is enter your API key in the plugin interface and then you can easily add all your annotations to your second brain in Logseq.
- Habit Tracker – Another great plugin by @c6p. Ever wanted to keep a tracker of the frequency and when you complete your habits? Well, now you can have this within Logseq at the click of a few buttons by adding the Habit Tracker plugin.
- This week we started with a very interesting discussion regarding To-dos/tasks and whether these should be included in Logseq or in a standalone app like Todoist/3things etc. @alan moved away from Logseq and into 3things as they found that Logseq was adding interference and lacked features available in a standalone task management app. On the other hand, @Luhman, went the other way, they have “moved from a dedicated task manager to logseq. For me it isn’t just context, but being able to directly link to my knowledge base. If I write
TODO email [[john]] about [[that project]]I can look to see John’s page, which will have backlinks to all the previous tasks involving him, and I can look at the project page and get what needs to be done.” Being a todoist user, this is a great point of view. Being able to quickly see the context and your other thoughts related ot the task all in one place may be priceless.
- @qwxlea explained their process of keeping tasks and notes in their workflow: From today’s journal page keep all simple tasks, marked as: LATER. Aim to limit this to no more then 10-15. If the list gets too long think about creating a separate project. Every task that is more than three sub-tasks long gets a project page, with notes attached either as linked tags, or written right there, and tasks, marked: LATER task1, LATER task2 etc. Projects are marked “active” as long as there are tasks left, otherwise I retire it, and it no longer shows up in any default searches (only in the archive). As Next Action (from GTD, as Logseq does not support Next), use #A #B or #C (in projects only). Add a search in the config file that shows these next actions on the journal page. At the end of the day, do a daily review
Please be aware that as Logseq is not a fully-fledged task management app, some expected features may not be available.
- Linking concepts in an Interstitial journal. @Aaron Powell explained how he links meetings on different days of the week with different people to have multiple meetings in a sequence and build on each other to see the progress in one place (i.e., the last meeting in the sequence). If by chance you encounter notes from a meeting earlier in the sequence, you will see that it’s referenced by later meetings. To do this there are two ways:
- The first is if I have, say, ongoing meetings on a similar topic or responsibility. For example, every couple of weeks, I have a meeting with the people in my editorial department. So on the day of the meeting, I’ll add a block called [[Editorial]] [[Meeting]] to the daily journal, and then indent my notes under it. In the future, I can go to the [[Meetings]] page, filter references by [[Editorial]] and see a list of all my editorial meeting notes from the various days.
- The second way, is more direct referencing. Today I had a follow-up meeting with a couple of colleagues about their feedback on a manuscript I wrote. The first meeting showed up in my journal as a block that was “[[Meeting]] about [[The Free Market Buddhist]] with [[Colleague A]] and [[Colleague B]]” and then my notes embedded under that. When I had the follow up meeting today, I did something similar for its block in my daily note, but then the first thing indented under it was a block embed of my notes from the prior meeting.
- The potential new additions for last week (Windows certificate and layout) are being worked on
- Data security and reduced conflicts with cloud and local storage are being looked into
- Stopping the / commands from appearing when pasting a link or text which ends with / – this is quite an annoying issue, so I am glad that it is being looked into