Happy Friday, fellow lovers of knowledge!
Today's newsletter is special as I have two announcements: I've finally renamed RoamStack to Think Stack Club, plus I'm joining Logseq as Community Manager.
What does this mean, and what can you expect from my part? That's what I share in this edition.
If you're not interested in Logseq or the future of the community, come back for next week's newsletter which will be about other tools as well. If you are interested in the broader Tools for Thought space, read on and hit reply to share any of your thoughts with me.
Let's dig in!
Become tool agnostic with Think Stack Club
The RoamStack community is almost 16 months old and has seen lots of change in that time. As many members chose to move to other tools, there was also churn in the community as it was still fully focused on Roam Research.
In the past six months, I've increasingly been talking and teaching about workflows for thinking, learning, and creating. But still, the focus was mostly on Roam.
From this weekend onward, the domain RoamStack.com points to ThinkStack.club. That means the rebranding of RoamStack is complete (for now) and I will finally start to fully focus on the broader Tools for Thought space. In the coming months I'll spruce up the visuals some more.
To ensure that you keep receiving the newsletter, please add firstname.lastname@example.org to your contact list.
Coincidentally, after long talks with the Logseq team, I've decided to join this awesome open source project. I'm not married to Roam Research, but I am to networked thinking and privacy. That's why it was just a matter of time until I would shift my focus to this tool, as I've already been using it for some months now.
That I'm now also cultivating the Logseq community has no consequence for Think Stack Club. I'm still interested in tool agnostic workflows. Actually, it's one of the Logseq team's goals to make all networked note-taking tools interoperable.
Why I'm joining Logseq
Yesterday I announced on Twitter that I'm joining Logseq as Community Manager. The overwhelming positive reactions have warmed my heart, and I want to thank everyone for their encouragement.
It's great to see that so many people are interested in helping each other, instead of only being interested in them being successful with a tool. This shows me that the positivity in this community far outweighs the spores of toxicity. I cannot wait to learn and share more with you all.
In this Twitter thread I share my reasons for joining Logseq and what I hope to achieve with the community:
A complete introduction to Logseq
If you're proficient with Roam Research, you'll have no problem adapting to Logseq. But before you go switch up your tool stack, ask yourself: Do I really need to change tools?
My advice: don't switch if you don't need to. Changing your tool for thought is expensive, even when functionality is much the same and transferring data is easy.
In case you do feel the need to switch (because of privacy, data longevity, price, or simply because of community), here are some resources to help you get started.
🤔 Is Logseq Better than Roam Research?
Shu Omi has created the perfect video if you're already familiar with Roam and want to have a quick overview of the main differences between Roam and Logseq. In just 7 minutes, he shows what Logseq doesn't have, what it does bring to the table, and how to decide between the two tools.
📺 50 Logseq Tips: Beginner to Expert in 6 Minutes
Not all too familiar with Roam but you still want to quickly see Logseq's features in action? David has you covered with this 6-minute video in which he showcases the core features of the tool.
🧑🏽🎓 Logseq Intro Course
Convinced that Logseq is the thinking tool for you, but you have no idea where to get started? Dario from OneStutteringMind has you covered with this free intro course on YouTube.
In just one hour, he'll take you from setting up Logseq on your local machine to how to resurface exactly what you need. On the way, he'll teach you task management and learning workflows, as Logseq has wonderful features to support both use cases much better than Roam.
🤿 Overview of LogSeq, by Tienson Qin
If you want to take a deep dive into the history of Logseq and how it all works under the hood, I strongly recommend you watch this one-hour session with Tienson Qin (founder of Logseq).
In this session facilitated by Tools for Thought Rocks, Tienson gives a complete overview of Logseq's features, the vision behind the product, and why certain design decisions were made.
Make Obsidian and Logseq play nice
If you've started using Obsidian but miss Roam's outlining features, you should consider adding Logseq to your stack.
In September I wrote a thread about how I've set up Logseq and Obsidian in a way that they're compatible. My reasons for combining the two are that I use Obsidian Sync to have a versioned backup of my notes, Obsidian's data/graph visualization is more powerful, and because I prefer to write long form content in Obsidian.
I based my setup on this article by "Luhmann" on the Logseq forum. In case you get stuck setting up this stack, the forum is the best place to get support, fast.