19-Feb-22: Logseq 0.6.0, Taking Notes from YouTube Videos, Logseq for Research Event, Plugin Updates

It certainly was a wild and windy day yesterday in the UK with trains being cancelled, people being told to work from home, schools being closed (I used to love these unexpected “days off”) and damage being caused to buildings.

The most impressive I thought though was pilots landing planes in very strong crosswinds at London Heathrow airport. If you ever questioned a pilot’s skill, check this video out:

Now that we have battened down the hatches, let’s look at this week’s LogseqWeekly post.

Releases

The devs have been hard at work and have presented us with a great release that includes several performance improvements.

0.6.0

  • New commands to switch between graphs (Cmd/Ctrl+Shift+G), add a graph, remove a graph and copy current file
  • Shift+click to select multiple blocks
  • Upgrade Excalidraw to 0.10.0
  • Updates to various languages including Russian, Portuguese, Chinese and German
  • Performance improvement while saving files
  • Performance improvement via incremental queries
  • Performance improvement of long pages and queries
  • Reduce memory usage
  • Add default right click context menu
  • Refine page search autocompletion
  • Refine page title renaming dialog
  • Enhance settings UI of plugins
  • Fix querying integer properties
  • Title property is not added when creating or renaming
  • custom.js not works
  • Block collapse state not being saved

NOTE for Windows Users: re-index is required to fix the search cache bug.

  • To download the latest version, check here.

Logseq News / Events

  • A very successful Intro to Making Logseq Plugins ft. @aryansawhney17 took place last week. Well done Aryan on taking us through what us quite a complex topic. The recording is being prepared and as soon as available I will post a link. Also be sure to check the Logseq YouTube Channel and subscribe to be notified of new videos.
  • This coming week, on the Wednesday 23 February at 3:00 PM, we have an exciting episode on How to Use Logseq for Research ft. Cara Antonaccio. ​Cara is a PhD candidate in the public health field and will look at covering how she uses Logseq (and related tools) to carry out her research. The talk with Ramses will cover the following:
    • What is Cara’s PKM story?
    • What are her current PKM use cases? •
    • What does her daily process and Journals structure look like?
    • ​How does she use Logseq to do research?
    • ​What other tools does she use besides Logseq? •
    • What are your top tips for researchers starting with Logseq?
  • Cannot wait to see what Cara has in store for us. To register please follow this link. A recording will be available after the session.
  • Ramses is starting a project to rewrite the current documentation (https://docs.logseq.com/) and is looking for people who want to give feedback or contribute. “I’ve already written a started guide which is pending review (https://github.com/logseq/docs/pull/37), so now is a good time to tackle the documentation about individual features.” Be sure to check it out and give your thoughts. For those that are not familiar with GitHub a Loom video is being prepared and will be shared on the Discord.

Logseq Mobile

To access the mobile apps, please the the respective link for your OS below. Also, please keep in mind that the mobile apps are relatively new releases so may have some performance issues. The devs are working hard to sort this out and squash as many bugs as possible.

  • The Android app of 0.6.0 had a critical bug so you may not see an .apk file on GitHub. As soon as a fix is found, the devs will re-implement. For the time being it is saver to stay on 0.5.9.

Logseq Workflows

  • @HDanzu once again wows us with their mind mapping skills by presenting what they consider to be a cheat sheet on note taking fundamentals. For those interested, the diagram was created with XMind.
Image
  • Use case for the A|B button; [#A] / [#B] / [#C] tags – What are your use cases for the abc tags? I’m toying between; priority,fleeting/permanent/project note and family/friends/work. @Alex assists us with “It’s useful for queries (searches) that result in long lists. For example, every time I see something I might want to watch later, I just dump it in my journal. But if I really want to watch it, I add a priority to it. Then, when I look at the list, those tagged with a priority are sorted first. This can be used for basically any long list. Example query:”
#+BEGIN_QUERY
{:title "🎥 Watch later"
:query [:find (pull ?b [*])
:where
  [?b :block/marker ?marker]
  [(contains? #{"TODO" "LATER"} ?marker)]

  [?b :block/ref-pages ?p]
  [?p :block/name ?tag]
  [(contains? #{"cdrama" "ydrama" "kdrama" "tv" "towatch"} ?tag)]]
:breadcrumb-show? false
:result-transform (fn [result]
      (sort-by (fn [h]
          (get h :block/priority "Z")) result))
  }
#+END_QUERY
  • Staying with @Alex, if you are interested to understand queries further, be sure to check out his fantastic guide.
  • A quite common issue of late is the conflicts created with sync and using Logseq on the mobile and computers. Rocket writes “I’ve been using logseq for a for a few days now and I frequently find that a few of my pages have been deleted. I’m using syncthing to sync my database across 2 pc and an android phone. I usually don”t create pages manually but instead just click on the tags. Because they’re usually lowercase, I then rename the page to start with an upper case letter. This often results in logseq deleting the file (I assume it’s logseq deleting it since I’ve been using syncthing for years and never had those problems before).” I have not encountered any issues when using Logseq across 2 laptops and the majority of issues seems to stem from introducing a mobile (iOS or Android). Hopefully a fix can be found to give users the ability to safely store their notes no matter what medium is used.
  • Difference between #pages [[pages]] and using UI to create a page with heading “pages”So I’ve spent 3 days on this and even with all the youtube videos I find that people know something that I don’t fundamentally understand… still unfortunately. Goal: What I am trying to achieve: take my Obsidian/Joplin markdown university notes and convert to this format of thinking. So if I start out with clearly defines headings which already exist… and I copy a block; the reference is this cryptic long alpha-numeric code… are you guys converting each heading into a page for easy referencing? @Miranda provides a very thorough response here which touches upon: “So, one good approach to Logseq would be to not be strict about “page vs block” as the equivalent of the traditional “document vs paragraph” scheme. If a block becomes referenced, the block is that more important and may deserve to be a unique node in the graph, to be what Logseq happens to call a “page”, and we may consider it to be essentially still a block containing other blocks. To harness the power of Logseq, you want your headings to each contain the paragraphs as children blocks rather than just preceding them as parallel blocks; each heading text is then what summarises its children blocks, just like a page name summarising its content blocks.”
  • @pchalasani asks am trying to figure out the best way to satisfy these requirements for URL Dumping and whether to include all in a block, in a page or another manner. A popular response was 1. If you create a file under pages, you should still link it to your daily journal. Logseq does not automatically create hierarchies, you have to make them yourself. 2. opinion: I dump all my link (well, basically everything) in my daily note. You should just use a subheading that is folded, then it’s invisible, yet in the default location
  • A question from @mrclark: How do people deal with “stale labels”. For example, I created #Stuff to Check Out when I find an interesting link, software product, etc that I should look at later. Over time I could end up filling this label up with a lot of crap thats stale, leads to dead sites, etc. What sort of process people follow to not have this happen? Just simple once every few months review? Something else? @gestaltists provides a great response: “Reviewing your notes regularly is the most critical activity for any note system to be useful, in my opinion. My most important stuff is in an analog Bullet Journal and I have a set 20 minutes every morning where I review my journal. Logseq I still have to find a similar workflow for.”
  • Publishing query in relation to regenerating block references: One downside of having bunch of blocks in one page is the ability to reference them in the exported graph later. Consider the following scenario: You have a page with 10 blocks. You export it and now it available in some public wiki (company shared directory). When you want to refer someone to block 9 (e.g. best practices for names convention) – For having a link to it, you search in logseq web wiki and copy address bar link. This link works like a charm, whoever click on it, gets into the page and it scroll down and highlight block 9 automatically. Now, and this is the boomer, if you re-index your graph and export again – the url is no longer valid (you will redirect to the page, but not scroll to block 9, as re-index produce be block IDs…)… So in case of referencing stuff, atomic parts has some advantages.
  • For those that are wondering how to resize embedded YouTube videos, you can write the following in your custom.css file:
iframe[id^="youtube-player"]{
width: 800px; 
height: 450px; 
}  
  • Talking of Youtube, here is a fantastic video on taking notes on YouTube videos in Logseq:
  • For those wondering of the sync protocol that is likely to be used in Logseq, Tienson provided this response: For the coming file sync service, all the files will be end-to-end encrypted on local devices and then uploaded to aws s3 servers, which are located in the US too. Nobody including us can decrypt any files because only the users will have the key to decrypt the files. As a reminder, Logseq,Inc. is a US company, currently, we have 6 team members in China and 4 members in US and Europe and we’re going to hire more globally soon.

Logseq Feature Requests

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

  • Ability to lock a page as read-only/view-only – I have several pages that consist of tables of values for reference. It works really well as a curated guide. The only thing that makes it iffy for me is when scrolling through, particularly on the mobile app, I’ll accidentally end up tapping into edit mode and things go glitchy. I’m afraid I’ll inadvertently change a value and not notice it. A tick box to lock a page into view-only mode would make this a rock solid tool forever and always.
  • Create a title preview to quickly adjust the title of the line when writing – When watching videos and reading articles, taking notes often needs to jump under different title levels in my writing notepage, but there are many lines resulted not to quickly find the previously titles of outline. Therefore, a quick call out subwindow of Outline Title Preview on the writing line is needed to facilitate the adjustment of the outline title level of the current writing line.
  • Add more event hooks/subscriptions for plugins – When writing plugins it helps to be able to react to the app’s events, changes to the data, namely the Logseq primitives like blocks and pages. It would be great to subscribe to changes on a page or on a block, for example
  • Introduce custom workflows as a primitive to replace TODOs – I love Logseq TODOs but they could be better. There are two nomenclatures for the same thing: TODO/DOING/DONE and LATER/NOW/DONE. Thus the app supports a single workflow. Why not allow multiple workflows (state machines) to be defined within the config.edn?
  • Hide aliases circles in Graph View – If not by default, it would be good to have an option to hide them. It makes no sense to me showing them as different circles once they are just another way of naming the original ones.
  • Add option to remove Orphaned Bullets/Blocks – I often find that there are a bunch of empty bullets (blocks) at the end of a page/journal. I’d like an option that removes “extra” orphaned bullets. Potentially with a selectable number of bullets per level to keep. E.g. allow one blank per level. Likely this would be something you’d want to happen after some action (leaving the page or something) and not just as you were editing.

Logseq Plugins

  • VIM shortcuts by @vipzhicheng updated to v0.0.8. It’s about case changing which is bound to mod+shift+u to toggle upper/lower case. Original VIM shortcut gu and gU are also supported. Bonus is combo action also supported for more case styles. It also includes VIM-like mark feature is supported now, but a little bit different with VIM. shortcuts: NUMBER+m: mark a page or block Number+’: jump to saved page or block Number+[mod+’]: put saved page or block to sidebar
  • Readwise (unofficial) by @hkgnp updated to v4.0.0.  1. Greater customisation for titles, additional page metadata, image sizes, highlights section headers. 2. Supports org-mode for your page/highlights metadata. 3. Highlights are sorted by recent ones below (no longer an option). 4. Slightly more efficient in getting highlights. If you do want to update your version, please note that any changes will only apply to new synchronised highlights.
  • Logseq Kanban Board by @hkgnp updated to v2.6.0. It now supports queries that produce task items (TODO, DOING, NOW, LATER, DONE).
  • logseq calendars plugin by @aryansawhney17 updated to v1.2.1. fix: issue w/ some outlook calendar names feat: you can now insert location of a task by putting it in your template feat: add past events to past daily notes (clicking the button on past DNP will automatically add past events).
  • Logseq Anki Sync by @Lightink updated to v1.1.1. This is a minor bug fix release. which fixes a font size issue.
  • Need we say more on this great plugin by @aryansawhney17 (not yet available in the Logseq MarketPlace but will be soon).
  • logseq-wide-eyed by mlanza. Toggles the visibility of DONE and CANCELED to-dos. An eye—appearing in the toolbar—has opened and closed states which can be toggled by clicking it. Its state determines the appearance of select blocks. It is useful for showing/hiding content such as completed/canceled to-dos, but it can be configured for other purposes.

Many thanks for reading this week’s LogseqWeekly episode.