1/ So I have been deep diving on @logseq. Let me just say its brilliant and has so much potential. It really is a local @RoamResearch, but in some ways better (and in a few not so).
One thing I really like is this hybrid blend of a graph database with markdown under the hood.
2/ You really own your data and you can easily change your data in the markdown format and LogSeq crunches it into the graph database.
LogSeq is an outliner. Find out about the advantages outliners here, written for Roam but applies equally well to LogSeq
3/ Roam really deserves praise when I compare it to LogSeq.
+ Roam is cloud based, no setup, no local file management
+ Roam has fine tuned UX for many features. On surface it doesn’t look special, but it is all in the polish, yes in its nuances and finesse — Roam has this.
4/ LogSeq really appeals to those who want Roam like features (outlining, block refs, embeds) with additions:
+ Markdown (own your data)
+ Powerful query features
+ Page level and block level attributes
+ Task management support
+ PDF Highlights
+ Flashcards
+ Drawing tools
5/ One big advantage with LogSeq is control over where your data lives. It can be on your hard disk (using any sync service you want) or in a GitHub repository. You can open the data with their desktop app or via the browser.
I am really impressed with the level of control.
6/ Disadvantages with LogSeq
+ LogSeq is in beta. It is reasonably stable, but you need be ready to deal with bugs
+ Since LogSeq gives you more control over your data, it requires a little more understanding of how it works and a plan for managing your data (Syncing, backup)
7/ So which is better, Roam or LogSeq?
Simply put they are both outliners, based on graphs, with great block reference support. I found the experience similar in both tools with subtle UX/implementation differences.
When evaluating, you need to consider different factors.
8/ When to use LogSeq over Roam?
+ Storing your data as Markdown and control of where the data lives
+ If you prefer an integrated theme & plugin store
+ If you prefer to use open source tools
+ When multiuser graph editing is not needed
9/ When to use Roam over LogSeq
+ When you don’t want to mess with files and data management
+ You need multiuser graph editing
+ Basically you prefer pure cloud based solutions
+ Block embeds seem further developed
+ You don’t want to deal with beta software
10/ These are my notes from my deep dive.
Do you agree? Disagree?
What other decision making factors would you include?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ Reviewing highlights in a smart way is one of the benefits of @readwise using their Daily Review feature. However, it is important to understand what the review buttons do, so as to efficiency of the process. For example, what does the "Discard" button do during a review?
2/ Some might think it is designed to ignore it in the reviews. But in fact it does something different.
You use this when you decide a highlight doesn't have value to you.
Consider it a friendly delete. It removes the highlight from being reviewed and not to appear elsewhere.
2/ This was also an interesting comparison of the use of block references in other systems and how they slowly become a standard way to do translusion.
1/ Readwise Tip - Use highlight_id in your exports
The @readwiseio export feature allows you to export your highlights to various tools like @obsdmd, @RoamResearch, @NotionHQ and more. The export can be configured to export these highlights in a format that works best for you.
2/ One possible issue when exporting highlights is that you can lose context of where they come from. Each TfT tools might have their own way of creating references to a source (example: block references).
How can we connect our TfT back to its source consistently?
3/ Readwise’s highlight_id to the rescue.
Use highlight_id in your export configurations.
It is Readwise’s internal identifier for that highlight. This means that every highlight you create gets its own unique identifier and is globally unique to the Readwise system.
1/ Today I to start officially cover @craftdocsapp. Craft is a beautifully “crafted” app for iOS, Mac & the Web. They define themselves as “a fresh take on writing & collaboration”for the modern era of digital devices that brings back the joy of writing. craft.do
2/ It isn’t necessarily a PKM or TfT tool, so a bit outside my focus area, but has many of the core features in place to compete in this space over time.
I have to thank @calhistorian for brining this app to my attention last year.
So what do I like?
3/ It is block based. So very natural experience for Roam and Logseq users.
It supports backlinks. Who doesn’t? But crucial!!!
Excellent collaboration features - multi-user editing
A beautiful WYSIWIG experience with great markdown support (import/export)
I have been doing some work to integrate my iOS devices with Obsidian. the iOS Shortcuts tools is amazingly powerful and well designed.
Many in TfT community are using this to integrate workflows with @obsdmd and @RoamResearch, and probably other tools.
2/ If you haven’t used it before, it is a tool for non-developers and developers to build commands that automate various workflows. For example, in my current Shortcut, I am extracting all my calendar agenda items for today and dumping them out to Obsidian in my DNP.
3/ Though I have to say on iOS 15 the Shortcut building tool is super buggy. Constantly constantly crashing. I think @viticci mentioned this during the 15 beta…. Seems its not better.
ReadWise is a “Stealth Tool for Thought”, under the surface at periscope level, working away at their ideas & steadily bringing great tools to the surface.
2/ Reader which is currently in private beta is proof.
I use “stealth” because they are perhaps underrated and overlooked since they seem niche.
Reader will change that. We are getting a set of tools that help us with our workflows from capture to reuse of what we read.
3/ They are not stealth though in community engagement. The opposite! They are proving to be partners in the Tool for Thought community.
Partnership is crucial while TfT space develops.
Partnership should be a criteria in any tool we choose to put into your TfT toolbox.