23-Dec-21: Logseq 0.5.4, Logseq Mobile App, Workflows and New Plugins

The timing of this episode is a little off, but as I have missed the last couple of weeks, I wanted to get back on track and provide you with an update before the holiday season.

In the past year, Logseq has undoubtedly come a long way. A lot of improvements have been made to the tool. The speed, stability and reliability have greatly increased, all while new and exciting features have found their way to us. The Devs have really “worked their socks off” to provide us with something incredible.

Of course, there are still many things that need to be improved and updated and at times, I am sure that it feels comments are falling on death ears. However, be sure that the devs take every comment on board seriously and are always looking at ways to provide us with the best possible notetaking app so that we can not only hoard our notes but actually make use of them in the long run. So during this festive season, all I would say is, have a little patience with the devs (and people in general) who are working tirelessly while potentially having many other things on their plates.

I also wanted to take the opportunity to let you know that we have reached a milestone of 400+ subscribers and have an average 76% open rate. Thank you so much to each and everyone of you that subscribes and reads my posts, this is very much appreciated.

Happy holidays everyone!



  • Today’s journal file is not recognized by Logseq when starting
  • Can’t embed some IFrame links because of x-frame-options
  • Handle code block with non-latin1 chars
  • Modal displaying on narrow screens
  • Graph view forces (more enhancements are coming)
  • Nightly release! (It’s unstable compared to the official releases, so please use it with caution!)
Example of the new graph view forces.
  • As part of the nightly releases, we can have some insight into the goodies that are coming up. Once which took me by surprise was the multiple windows possibility. Looking forward to testing this one out when released:

Logseq News

  • @Mono Wang joined the Logseq team recently as a full-time developer. My past experience is mainly in backend development, SRE and database. I’ve been using different kinds of note-taking software for years. As a team member, my main focus will be on optimization and data synchronization of Logseq. Glad to join this great community! Hope to have a good time here with you guys. Thanks.
  • @Junyi also joined as a software developer. I previously studied natural language processing at University of Southern California with interest in knowledge extraction, dialogue system and multimodality 🔍 I can not wait to enhance the LogSeq’s input experience while keep the privacy-first principle in mind 🚀
  • @Ramses joined as the community manager – Hi all! My name is Ramses Oudt and since this week I’m the community manager of Logseq. It’s my goal to help members of this community feel heard and get the most out of this wonderful tool. Apart from helping end users, I’ll also be reaching out to contributors and content creators. Maybe you’ve seen me around in the Tools for Thought space. I ran the largest community of Roam power users (RoamStack, now named Think Stack Club) and have coached hundreds of people to learn and use networked thinking. My background is in teaching and consulting, the latter mostly for Human Resource departments and small teams. I look forward to connecting with the bring people here. Never hesitate to DM me with ideas or concerns—I’m all ears.

Ramses hit the ground running and has set up an event which will take place on Tuesday 4th January 11:00 AM UTC and again on Thursday 6th January at 5:00 PM UTC:

  • An Introduction to Networked Thinking Using Logseq
    • Are you new to the idea of using an outliner like Logseq? Or are you a (former) user of Roam or Obsidian? We’re here to help you learn how to use Logseq!
    • In this hour-long workshop, you’ll learn all the fundamentals of Logseq to help you get most out of your notes.
    • We’ll not just look at Logseq’s features, but also how to build a system for Personal Knowledge Management. There will be room for questions and discussion.
    • Stop adding your notes to an idea graveyard and learn to turn them into a thriving garden of knowledge!
  • To join what sounds like a fantastic event, be sure to follow this link and click on Events to register your interest.

Logseq Mobile

  • The initial release of the Android app was well received and a few more bugs have been squashed, so we should see some improvement in the upcoming update. From what I can understand, the app is also being evaluated to be made available on the Play Store.
  • The IOS version of the app had a cloud issue which has hopefully bene resolved so the app should be available for testing soon.


  • @Tokio Mike talks about his daily set up here. I am really enjoying how Logseq handles tasks. For those interested in the Schedule section is the time of a meeting and then a link to the notes for that meeting. The name of the note is from a macro app I use to give me YYYYMMDDHHmmss so each time I execute the macro is prints a unique string of text, and when that text is between [[]] you can click it to create a page. On that page I then add #tags for what the meeting is about. Simple workflow – tasks all gathered – I have a page called TASKS in the Favorites that executes a couple of queries to pull all tasks in.
  • @Danzu presented us with how they would envisage a dream PKM task workflow:
  • @Bad3r presents us with a very good write up of changing / implementing hierarchy in Logseq. I like the approach suggested but it might go too far from the “everything in a flat structure” set up.
  • Notes structure – three seems to be a split of people taking notes on dedicated pages vs those taking notes on the journal page. I am like @Prashant and take my notes as follows:
    • I usually do that in a journal now. In the daily page, I would add a block named [[Meeting with John]] Nested under it I will take my notes. When you open the Meeting with John page later, you will the full history of your notes grouped by date in the linked references
    • The alternative would be that on the Meeting with John page you have a block with the date of the meeting and then take your notes under that.

I like the first approach as when I reflect on my week, I can quickly see what meetings I had, the tasks I had (and hopefully those I completed) and what still needs to be done next week. This also then allows me to do, is Shift + Click the [[Meeting with John]] page and see any background and the past meetings at a quick glance.

To conclude though, both systems work just as fine – as long as you are taking your notes somewhere and the system works for you, carry on.

  • My fellow Discord mod @Sawhney provided us with a very good video asking the question: “Is this the BEST Notetaking app for students? | Logseq Student Workflow”. Well worth a watch, and great work Sawhney.
  • @Danzu wowed us with another diagram of their workflow, this time on the subject of podcasts and ebooks. “Currently, I use Airr for Podcast, I can easily type a quick note on the audio frame. Otherwise, I just trigger Siri to create a note in the IOS note app, which allow me to convert to a permanent note in Logseq when I am on Logseq desktop. Here is an overview of the future state…when logseq for IOS is ready”
  • @LarryK talks us through a small change they made to their workflow that seems to have done wonders.
    • Recently, I had to make a small change in my work workflow. I document firmware for our products; it functions very similarly over three platforms and each platform has numerous releases being developed simultaneously. I had been taking core team notes in the journal, and tagging them with #OurProduct to pull them all together.
    • But soon, I realized, it wasn’t what I needed. The changes that come up in nearly every core team call are important, but when they happen usually aren’t. Thus, I turned the #OurProduct page into a dashboard of sorts. Each release is a child node of its platform; each release has links to specs, development epics, lists of features and changes I need to document, and (most importantly) milestone dates.
    • So, for each core team call, I open this page and update each release as needed. If dates change, I’ll strikethrough the old ones so I know to update my Friday report (then I can remove the strikethrough text next time). If a when does become important, I can tag the entry with /Today and it shows up in the journal. Everything else goes in the journal, but this one change made for a lot less friction for me.
    • The takeaway: if something isn’t working just right, try a different approach. You can always change it back if the new approach doesn’t succeed.
  • Zotero anyone?


As a reminder, to activate the plugins, you need to

  1. Click the 3 dots in the righthand corner and go to settings,
  2. Got to advanced and enable Developer mode,
  3. Restart the app,
  4. Click 3 dots and go to Plugins, then Marketplace,
  5. Install the desired plugin(s).
  • Readwise (unofficial) – This is a simple Readwise plugin to: 1) Pull in all your highlights from Readwise 2) For subsequent pulls, it only pulls in those not in the graph.
  • Table of Contents – Interactive (style-able), real-time rendering of Table of Contents from markdown headers
  • Merge Pages – This plugin helps to merge multiple pages into a single page. Links to previous pages are redirected to the page that they have been merged to.

I hope you found this latest edition of LogseqWeekly interesting and please do let me know if you have any questions or comments. Thanks as always for reading.

2 thoughts on “23-Dec-21: Logseq 0.5.4, Logseq Mobile App, Workflows and New Plugins”

Comments are closed.