Interview Ramses Oudt: The future of Logseq and Personal Knowledge Management
Вставка
- Опубліковано 9 лип 2024
- Had an awesome day talking future of Logseq with community manager Ramses Oudt in my studio, where we talk in-depth about a lot of questions we got asked over Twitter.
Podcast version for those that want to listen on the go
www.podbean.com/eas/pb-vv9a9-...
🌎 BLog toolsontech.com/posts/
💌 Join my mailinglist - toolsontech.ck.page/
💖 Let me know you want more, subscribe
#logseq
TOC (Thanks Ramses)
00:00 Introduction
01:05 What's Logseq vision for the future (mainstream versus power user)?
11:10 Collaboration between paid contributors and volunteers in the Logseq community
20:00 No note-taking versus lots of note-taking
28:55 In the next 5 years, Logseq will become a personal knowledge browser
45:30 Logseq versus (and in combination with) other note-taking tools
55:20 How does Logseq aim to be a better tool for professional users and enterprises?
1:15:10 Personal versus work graphs (and combining the two)
1:28:20 Why (and when) to combine tasks and notes in one system1
1:40:10 How it'll be easier to structure information in Logseq
1:48:28 What makes Logseq different from other (personal) knowledge management tools? - Навчання та стиль
I like the statement Rames made about how important it is to keep files local. Aligned with the second brain and brain extension discourse
For sure, I got lots of emails if I want to try out app X or Y and nearly all fail on this crucial step.
This is a great jam! I need to meet Ramses.
You definitely should, Ramses is amazing!
Thank you for this interview. It's very interesting. There is almost no material like this on Logseq in video format. I can't wait for Query builder and the migration to Database
Even though I'm working on the concept for a good basic query primer video right now, the query builder will be such a huge improvement for people to get more out of the data they put into Logseq.
Supertags is very interesting. In the meantime I think I'll add a property to each template so it'll be easy to find all previous uses of that template and do the necessary maintenance.
My current workflow as well, add the properties to the template so I don't forget them. But feels like a hassle after you experience how apps like Tana solve it.
I think the concept Ramses is looking for when he was talking about different dashboards and such is contexts. Most don't just need to split tasks by "work" or "private". But also other contexts like "at home", "garden", "cabin", "errands" and more. The Getting things done(GTD) methodology has quite an interesting approach to this.
Yup, this is why I have tags like #@laptop #@phone etc...
And then filter my tasks for context
Ramses around minute twenty refers to the importance of sharing their way of using Logseq and I thought of meta models. How can i have a model that allows me to build on top of the main building blocks. Think of it, the XML schema equivalent in Logseq. So we can govern the structure of fields and pages within properties. I wonder if RDF or any simpler equivalents for the semantic layer can be used to let some meta modeling. I also think that meta modeling can also be a good use case for the new Whiteboard feature. What I’m missing is to be able to refer to a page that represents page itself, so we can use it in our meta models
Around minute 43, letting the structure of your templates grow is also related to the underlying meta model and its evolution
An integration with the command like is also key I think. In a way, I expect it to become a web-aware Emacs
I’m ALL-In with Apple Notes. And still the very best notes app in my opinion. Not in terms of features perhaps, but in terms of smoothness, and everything just works every single time. But again, I really don’t have any use for much of the backlinks etc. or graph view. I’m also a paid user of Obsidian, but haven’t been using it for a long time. And Logseq almost always seems to give me problems and I don’t like how the plugin system/design is. And another major issue is the fucking Electron every where. I understand it’s easier to develop with Electron, but damn, some should really make a smooth PKM-like app, developed natively for macOS/iOS.
Try Craft.
Logseq is the kind of platform that could use a workflow engine that is capable of running user defined workflows. The plug-in system is too complex when most of the time, all we want is to execute a particular workflow, which would orchestrate user actions, scripts or timer-based activities
I don’t “take notes” in the PKM sense… never have and never will. But I do take some notes during the day… to remember some things or if I just need to write something down. But never to build something. In my opinion, I don’t see the point at all. As long as I find my notes, I’m all good.
Building something feels more towards the "templates" of Notion, with Logseq it's more "how I take notes". Not sure if marking a block as "meeting" would already be considered building.
Metamodeling is something I miss in Logseq. When a page is associated with a type, then we should be able to use that type to filter the scope of a query for instance
While I can query on type, do you mean having a fixed amount of properties for a specific page like say type: project or type: book
Please just re-write (design) the whole plugin system/design. Make it so it actually feels its built-in. And make it so every plugin looks the same (design principles, colors, etc.)
This one is high on my wishlist as well. It would require making components that can be re-used so it would definitely take time.
Man, logseq is already perfect. Just make it faster...
Faster and more keyboard driven and would totally rock it.
Sorry but there will never be a maintsteam user the whole point about these apps is to get your barin out of the mainstream.... cause itd so uninspiring
I agree that it will never be fully mainstream, it's still a bit technical and I like it that way. But making it easier to use so the bar of entry is lower is always good in my book. And looking at the new query builder that's exactly the right direction, make it easier to do something but allow for switching to code for power moves.
This community manager has less carisma that a groundhog