18-Sep-21: Logseq 0.3.9 Release, New Plugin System and Lots of Other Updates

Welcome to the inaugural post on LogseqWeekly. In this week’s post, we have several items to cover.

Releases

  • 0.3.9 has been released with some very good additions including:
    • YouTube video timestamping. Easily navigate to certain sections in a video (Demo).
    • Fixes to Code Blocks which were inadvertently not storing recent additions and tweaks,
    • Git commits to have version history and more control,
    • Improvement to avoid overwriting data for users who use a cloud-based storage solution,
    • Initial build of the Logseq Plugin Marketplace.
  • Plugin Marketplace
    • The “store” where plugins will be showcased so that they can be easily installed in Logseq,
    • The easy process of adding and removing plugins and themes can the tool so much more scope for new features and addons. The marketplace is currently a little empty given that it has only been released but I hope that many plugins will find their way,
    • Installation process is very easy. Settings -> Advanced -> Enable Developer Mode. Once the app restarts, click the three dots in the top right-hand corner, then Plugin and install the ones you wish.
  • 0.4.0 (pre-release) has been floated out there to users.
    • This release aims to fix a few performance issues. A few users complained that the app suffered from significant lag on a page that has significant linked and unlinked references. Given the tool is meant to capture notes and being able to take quick notes is vital, any lag is a bit no-no. Luckily @tylerwince came up with a great suggestion which the devs implemented. So far so good.

Plugins

  • The first plugin I tried was the Journals Calendar plugin by @Charlie. A simple, yet extremely powerful, journals calendar plugin for Logseq where you can create new past/future journal pages or easily navigate to already created historical pages. This makes it so much easier than having to continuously scroll in the past, searching for a date, or going via all pages. The QoL improvement has levelled Logseq up.
  • Another very interesting plugin is the mindmap tool by vipzhicheng. The plugin allows you to visualise your notes in a mindmap format. I love seeing my notes differently and from another perspective so that I can get a quick overview. Here is a demo:

Workflows

  • How do you decide when to use #Tag vs [[Tag]]? Personally, like a few others in the discord and especially @cannibalox, who put it very well: “I use [[]] when the [[tag]] is part of a sentence and # when it’s a property or page-tag (or used as a label/category of sorts)”. I find that this makes a lot of sense and the reading of notes a lot more natural. Another excellent point raised by @Luhman is that “multi-word, tags, like [[that project about the thing]]” won’t work if using # to tag. You could of course use #[[tag with space]], but that just doesn’t feel natural, although can assist with custom CSS settings.
  • There was quite a lot of chat about users using the daily page as their main point and creating links to branch off to other pages. I personally like this approach as it allows me to see from a high level what I did on a particular day with the possibility of going deeper where required. @vicrerdgz on top of this makes a fantastic point “I like to do that, but I keep flushing content to pages. Since all the notes end up being a markdown file I would want to keep portability of my notes in case that for whatever reason I can’t use Logseq anymore. This lets me for example index notes with other tools like the terminal. If Logseq one day does not exist, I will just have a stream of dated notes with lots of non-indexed data that won’t be useful.”
  • Not sure how to use queries in Logseq? @qwxlea created an amazing step-by-step guide.

Appearance

  • I recently installed the Dev Theme by the very talented @pengx17 and have to say it is a real eye-pleaser. Lots of useful tweaks which make editing and reading notes a lot easier.
  • Have you ever wanted to use icons instead of bullet points Well now you can, with some clever wizardry from @Zyro. Details.

Up Next?

  • I am looking forward to the app having a Windows Certificate so that the Warning blue screen stops popping up. I think this is putting a few people off installing it but luckily it is being worked on, so who knows, maybe in the next few posts this will be implemented.
  • For those like me who crave a left-hand sidebar, I have some good news, this is being looked into by the fantastic @Charlie (Roadmap). Cannot wait to see what he comes up with.

Other Knowledge Management Apps

Whilst this blog is centered around Logseq, I also like to keep up with what is happening in other knowledge management apps. As I do not think I am the only one, here are a couple of significant updates I came across:

  • Obsidian – The devs have started working on the highly sought-after What You See Is What You Get (WYSIWYG) interface. I am looking forward to seeing what they come up with. Interestingly there are people who will outright refuse to use it, but I find it easier to see read my notes without the markings. It is a bit like Show Paragraph Marks in MS Word, bit too much going on. Some love it, others don’t
  • Athens – They are progressing with Real-Time Collaboration (RTC) with an initial build having been released. All the devs efforts are going on RTC which has however pushed back development of other areas of the app.