15-Apr-22 – Logseq iOS App, Workflow and Discussion Videos, New Plugins, Feynman Technique, Reading List

Well, it is that time of year again when we can justify eating way too much chocolate on Easter. Can you believe it is nearly already May! Might be getting ahead of myself as it is really only mid-April, but you get my point.

As much as I try and stay away from the latest social media trends, it seems impossible to ignore them completely, given they are everywhere, the Never Let Them Know is actually a very funny one. If you do not know what it is, then lucky you, but here is a video to make you part of it.

In light of the above, and to keep everyone on their toes, the latest LogseqWeekly post does not stick to a schedule and is available a day (or 2) early. Now that I feel like part of the gang and included myself in the latest trend, here are the important Logseq matters.

Releases

Although no releases for the desktop app, the devs have surprised us with an announcement that Logseq is available to download on the app store. Be sure to download it (if you have an iPhone / iPad) and please do leave a review.

Image

The iOS app includes the following noteworthy updates since the beta version:

  • Added a voice recorder (saves as .mp3 to /assets/)
  • Document view is now available on mobile
  • Added a quick capture button
  • The mobile toolbar is dynamically reordered by usage frequency
  • The startup speed is much faster than before

For fellow Android users out there, fear not, I am sure approval to the Google Play store will be gained soon enough. Remember you can already download the Android (and the latest Desktop version) from here.

Logseq News / Events

  • The Logseq Office Hours episode 2 hosted by Ramses is available here. In this episode, Ramses showed the two fundamentals of Logseq (linking and indentation) and why it matters to find back your notes. He then demoed how to write a query, going from a broad question to progressively more specific search terms. Really good watch if you are interesting in learning more about queries.
  • The Official Logseq Blog is about to be launched. The blog will look to share regular updates on the product, but also enable content creators to share their knowledge directly via the blog. If you have an idea for content or want to republish your existing Logseq content, please send Ramses a short pitch via DM (on Discord). No link to share yet but I am sure this will be announced in good time.
  • Logseq are looking to start their next-step mobile apps development for new feature integrations, workflow enhancement, etc, and would like to know your opinions on what you would like to have in the Logseq future apps. Please join this Discord thread for discussion and sharing your ideas. The devs would appreciate any feedback offered. If you are not on Discord, I am sure they would not mind a Twitter post.

Logseq Workflows

  • Not really a workflow point, but this image and user (@Cannibalox) certainly deserves a mention. 13k pages, nice going!
Image
  • With the release of the IOS app, a few users have asked: Do you guys know a way in which I separate a certain group of notes not allowing them to upload for my cloud or synchronization? I want some of my private notes, such as therapy ones, to be part of my web of knowledge, but I wouldn’t like to synchronize them to my portable devices, since I live in a city where lots of robberies happen every day, and I depend on public transport. So, that’s it, on my notebook and smartphone I would like to have only my university notes. On my desktop, at home, I would like to connect everything. Possible Solutions: 2 graphs, check with sync service to block certain files.
  • NOW tasks – I find it really useful that journal tasks tagged NOW appear on today’s journal page, but NOW tasks on non-journal pages don’t. Surely the rationale for having them on todays page at all counts wherever in the graph they are found? Is this how it’s meant to be or am I doing something wrong? Add the following to the config.edn to pull in NOW or DOING tasks from any page (I use project specific pages)
  {:title "🟢 ACTIVE"
   :query [:find (pull ?b [*])
          :where
          [?b :block/marker ?marker]
          [(contains? #{"NOW" "DOING"} ?marker)]]
   :breadcrumbs-show? true
   :collapsed? false}
  • Feynman Technique anyone? Another brilliant video by Josh who walks us through his implementation of The Feynman Technique with Logseq and Obsidian.

  • Project Management – I asked the following question on the Discord and got some fantastic responses. Does anyone have a suggested flow / structure when dealing with projects? For example, I am working on 5 projects this week, next week I get another one, At the end of April 2 close but another one comes in. What I would like to achieve is that I can see the active projects (and closed) quite easily but also have access to the closed projects for prosperity and in case I need to look back on them. I am thinking namespaces eg. work/project1, work/project2 and then a tag such as #live, #dormant, #closed, so that I can then query and get what I need. An alternative would be work/live/project1, work/closed/project2 – Bonus would be a bit more structure, but more time consuming and needs more thought. Any suggestions very welcome.
    • Sawhney – I’m a big fan of namespaces and in this case, what makes the most sense to me is having a tag. One thought that quickly comes to my mind is the usage of the icon:: page property. You can perhaps have like a stop sign or like a green traffic light or something to signify that a project is either in motion or cancelled or has been completed. The benefit of this is that you can easily query, but also and arguably more importantly, you can easily and visually see the status of a Projects by looking at it or a link that’s referring to it
    • Zyrohex – I tried the namespaces approach for projects but found it polluted my graph and became too noisy. Instead I use related and parent property keys on my project pages to link back and forth, along with type to classify the page and status to set the current state of the page. Below is an example of my problem solving template that starts off in a journal page. Once I have finished filling it out I use the “turn into page” plugin to suck everything up into a page. Another thing I do sometimes is if I have related projects that I am aware of during a meeting I will drop a page-ref to the already existing project to take some notes, then start a new template for my new project(s) nested under the existing projects page-ref to show the relation.
    • LarryK – Most of my work projects are related, so I set up what I call a “dashboard page.” The projects fall into three major buckets, and each project has links to requirements and epics, milestone dates, anchor features, and whatever notes I might need to add. A recent addition, since many of the projects are in my backlog category, is a /Scheduled date to pull them from backlog and start working on them. I use it for two purposes: First, for each core team call, I expand the appropriate bucket and expand the projects inside that bucket. I add notes if needed, update milestone dates, then close it when they move to the next project.
    • Luhmann – First of all see my old post on this: https://discuss.logseq.com/t/my-logseq-workflow/2278 But I’ve updated it recently, by having a page of queries like so: {{query (and (page-tags project) (page-property status doing))}} {{query (and (page-tags project) (page-property status ongoing))}} {{query (and (page-tags project) (page-property status waiting))}} {{query (and (page-tags project) (page-property status done))}}
  • @Rocket asked “When you input copy in your journal do you enter the next item , ie topic or meeting below the last one or above? I’ve been doing it above and then realized I may be making it harder for myself doing it that way. I suppose I thought when I’m reading back through journals I wanted to read the most recent item first on each day. Anyway interested to know what others do?” Consensus Add blocks below to make adding content as smooth as possible.
  • Readwise recently released a RemNote plugin – from what I can tell, a Logseq one is coming soon. I appreciate I have said this before (and most likely more than once) but the below gives me hope that it really will be soon.
  • How stable is Logseq these days? I’m thinking about switching from Obsidian to Logseq for note-taking and writing purposes. But I am a little hesitant because the last time I used Logseq, which was like 6 months ago, it was extremely buggy. Pages would go missing, files wouldn’t be properly deleted, etc. I’m wondering how much better is it these days. What I like about Logseq is its minimal interface and its emphasis on writing without the hassle of creating files, choosing a location, etc. But if it’s still having issues, I might just stick with Obsidian. If anyone could give me a quick overview of Logseq’s performance these days, I’d truly appreciate it, thanks. Consensus: Stable :)!
  • Alex gives us great insight into his flow for book notes. What I like to do for books is:
    • one note per book
    • Copy TOC to the note
    • Make my own notes in the note, tagging highlighting, but quick
    • Go over the notes again tagging, highlighting all the best stuff
    • Now I will take the best parts and split those of into atomic notes, first seedlings, then when I’m happy permanent notes, they get their own page
    • Those seedlings get all linked in a forest of atomic thoughts, this is parallel/separate from the book-notes, which are just by-the-book. The book part is just work, it is the most boring part, just fuel for the rest. The cool part is writing the atomic notes, and linking them to other notes.
  • Query / Property table to track what is important?
  • Parent Property Usage – @ Zyrohex8 says: There’s nothing special being done by logseq for the parent property. It’s intended purpose are for my queries. So an example of how I may use it is I add a query on the parent project page {{query (page-property parent <% current page %>) }} which allows me to see all of my child projects that tie back to the existing page. Or I could do {{query (and (page-property parent <% current page %>) (not (page-property status done)) ) }} to see open child projects for the existing page.. For my customers index page I can have a dedicated section that covers all of their problem tickets like so {{query (and (page-property customer "customerA") (page-property type "problem")) }}.
  • I also use these properties in daily task items.. Such as I work in a escalation type of role where I support a specific set of accounts. I’ll engage with various teams across my company to tackle and resolve XYZ issues. So when I engage on these tickets I will add a block-ref for “[[incident]]” to the incident I engage on, and tag some metadata like the component, customer name, and symptom that relate to the incident. I can then later use this data to feed into my problem pages which helps me build evidence to escalate defects back to the appropriate teams. This is also done by adding a query to the problem page to find all my incidents that has a relation to the problem I am working, the follow would be very simple example: {{query (and [[incident]] [[!/mce errors]]) }} .. But it kinda gives you the idea behind it. And a screenshot to show how it all looks from the problem page
Image
  • Have a reading list but don’t really know what to do with it? Why not turn it into something beautiful like the Felipe’s. It is simply namespaces, properties and a little bit of CSS (All available in the tweet and here). Great work,
  • Namespace pages automatically get an alias? Interesting concept by Gforcedev who asks if a page such as [People/Isaac Newton]] is created, it would automatically get the alias:: Isaac Newton in the first block of the page. Definitely worth a feature request as that would make linking a lot smoother.

Logseq Feature Requests

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

  • Support epub format ebooks – It’s very nice if logseq can support epub ebooks like PDF. I am cheating a little as this is a request from some time ago but really looking forward to it being implemented, so hoping that it can get some more votes.
  • Reminders plugin – I’m moving my task management from Notion to Logseq, but I miss something: the remind function. It would be great a native or a plugin solution. To get something similar, I’d be very useful the same notification system implemented in Pomodoro plugin by @Aryan (amazing plugin) but on scheduled and deadline dates.
  • Local (on-server) storage for self-hosted Logseq – As the Github backend has been deprecated, I’d love it if we had the option to use local storage (self-hosted only). This would get rid of the need to sync between different devices for people running Logseq on their own server. It would also allow us to use Browsers that don’t support the File System Access API (Firefox, IE, Opera, WebView).
  • Sort the flashcards – I have used flashcards for a while. When I have 500+ cards, I cannot review all the cards one day, so I have to review part of it. The problem is that the cards at the bottom of the review card set which I left for tomorrow, still seem to be at the bottom of the card set tomorrow. If I cannot review all the cards once, it seems that the bottom part of the card will never be reviewed.
  • More scrolling options for PDFs – I don’t have a scroll wheel because I use a stylus, and the arrow keys can’t be used to scroll a PDF even if it’s in focus (it always moves the outliner selection), so the only option left is to drag the scroller, which is very imprecise in long documents. Can you allow scrolling PDFs with middle-click dragging? Or allow scrolling with the arrow keys?
  • Task notifications – When adding a task or todo with a date(time) and it’s due, the app should send a notification
  • View and delete orphan asset – I would like to have the same feature that delete orphan pages to the assets. How it works now: Currently, if you paste an image into a block, Logseq generates a file with a non human name, for instance, image_1646019226269_0.png. If I remove the image from the page, the image file remains in the assets folder. It make me concerned about generating too much trash files. Desired Behaviour: It could have some form to easily query or view the list of orphan assets and decide to delete them in a batch action or selecting individual assets to delete, like we have now for orphan pages.
  • Export PDF with Highlights – I’d love to have a way to export PDFs with their highlights so that I can share the annotated version of the PDF with friends. Right now, the highlights are stored separately in the PDF’s .edn file, which isn’t a format in which I’d ever share the data (though it’s really nice for personal use!).

Logseq Plugins

  • Searchable plugin – A quick utility that allows you perform OCR on an image and insert the text as metadata that can be hidden. This then allows you to navigate to the image using search and query for that image using queries. Supports 100+ languages!!!! Inspired from a plugin request that Aryan had submitted almost 6 months ago, back when he didn’t make plugins.
  • Github File Getter – This plugin allows the user to easily import the contents of files from any Github repository that the Github user has access to. The main goal is to enhance the ability to document code development and final code using Logseq. Once a file is imported you can update it to the latest commit version by clicking on the refresh icon.
  • Cinematograph “writing in movement” — a Youtube note taking helper: It hides all but the last line while making notes
  • Move Block – A Logseq plugin to help you manage block movement.
screenshot
  • LogStats – Analyse your Graph for peace of mind (and quiet bragging rights).
Image
From @Luhmann in the Discord – impressive stats.
  • Harmony Theme – is now available in the marketplace! A lot of minor bugs were fixed for the release.
  • Logseq Interstitial heading has been updated Configurable (new!) keybindings for gorgeous timestamps, Random quotes for your morning ☕️/🍵/🥛, Note to self for en💡enment
  • Logseq Anki Sync v2.2.0 – It adds namespace support for naming decks (for better organization of cards).
    Also, adds a scrollToClozeElement toolbar button in anki, nested decks support, and several bug fixes
  • Logtools v0.0.3 – 2022-04-13 new: #.v-gallery-col[2-7] add option -col[2-7] to force the number of columns for image grids (works best with images of the same width), eg: #.v-gallery-col2 will make 2 columns, #.v-gallery-col5 will make 5 columns ,etc… each ![image](link) should be in its own block under the #.v-gallery tag
  • Link Preview v2.2.0 now has a new command to generate static link card. This may enable rendering link card in the exported/published graphs later, but it seems logseq will not render with the generated link markup at the moment.
  • Unfinished business – Updated plugin for busy lazy people: Unfinished Business 0.1.5. Now you can sort your procrastinating tasks: Sort order: Alphabetical, by Marker then Priority, by Priority then Marker, or Not at all.
  • Export to PDF – Updated to Support a lot more languages, Supports markdown highlights, Supports markdown tables, Fixes images issue on windows, Uses native print windows, Less janky export with formatting and spacing errors, WYSIWYG Export, Supports inheriting aspects of current theme, like typefaces for a much cleaner look of PDFs, Output generally looks much better and more professional
  • Media Rendered – Updated media-ts, added a media renderer that supports both video and audio files. Path supports URL, absolute local file path or relative to Logseq file path (for uploaded assets). Please check the updated gif on README for the workflow of uploading a video asset and have it rendered properly.

Many thanks as always for reading this latest edition of Logseq Weekly and happy weekend all.