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.
So they are not deleted, but rest in peace here without bothering you in other places in Readwise.
Now lets consider he other buttons in the review process.
4/
Keep button - keep this highlight in your Readwise database and its likely to resurface in the future when Readwise determines its a good time.
Mastery - is for making Clozed flashcard (Question/answer style reviews)
5/ Feedback button, or perhaps in other Spaced Repetition systems would be called "Score"
This is where you tell Readwise if you want the highlight to come back sooner or later. You might compare this to scoring the highlight as easy to remember or hard to remember.
6/ By learning how to use these buttons properly, you can finetune the way highlights are resurfaced for reviewing.
Lots of value to this system: your highlights don't disappear into a void, but are resurfaced for review in a smart way.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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.
1/ FLEXIBLE SYSTEMS - Structure with the rewards and not the pain.
So many of us when starting our PKM journey want the perfect tool & perfect system for how we will take notes, resurface / reuse knowledge.
Sorry to tell you, there is no perfect tool and no perfect system.
2/ We should not expect perfection, rather be in the pursuit of a good, flexible & adaptive system.
The fact is our lives change, interests, priorities, needs & desires. If we had a perfect system, it would require freezing our lives into a period of time. None of us want that.
3/ Therefore, a long time ago I got over the illusion that there is a perfect system and embraced the concept of a flexible system.
A flexible system should help us to accomplish our PKM needs, but not lock us into a rigid way of doing things.