1/ 1st Impressions of the @readwiseio Reader Beta.
I have been testing the Reader Beta for about 2 weeks and I have to say I am super satisfied. It is just a beta, but has already entered deep into my psyche & something I see myself using for years to come.
2/ Reader is a new tool for all those passionate for reading and retaining the value of what you read.
Reader can be compared to tools like Pocket & Instapaper. I love those tools, but they fall short.
ReadWise delivers and I can’t wait for you all to get it.
3/ Reader when combined with the other ReadWise services delivers the features that a lot of us for a LONG time have been search for.
Acquiring knowledge and wisdom from reading is a more complex process than it appears on the surface.
4/ it involves finding material to read, then READING, processing what we read & resurfacing gems found in our reading later in different contexts.
I always fear losing what I obtained with reading, so a tool that covers this whole process is what I have been searching for.
5/ ReadWise is working to address the whole life cycle of reading and the purpose of reading.
Reader is a place to collect what to read, to read it in a beautiful interface designed for reading, for highlighting, annotating, categorizing, archiving and search.
6/ Then those gems found in reading can be resurfaced.
ReadWise offers a method for reviewing highlights using a spaced repetition technique. Spaced Repetition is a proven method for efficiently retaining & resurfacing information just as your mind begins to lose grip of it.
7/ The 2nd way to resurface your reading through Readwise is with one of their plugins for PKM tools to import those annotations. They can then be processed & melded with your own personal content.
Summarized, content we read becomes intimately intertwined with our own thoughts.
8/ Reader might become the most important tool in my arsenal. I may switch my PKM tool of choice from time-to-time, but ReadWise will always come along for the ride.
9/ Finally, in addition to my usual covering of Personal Knowledge Management and Tools for Thought, I will be covering ReadWise features. So if you are interested in ReadWise, keep tuned into my account. I will be tweeting tips, trick and some good old TfTHacker solutions.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ Over last 2 weeks been playing with @craftdocsapp while working on my newest @obsdmd plugin. For all you #roamans, it is Roam42 workBench, but tailored to Obsidian. I am calling it Text Transporter (for you Star Trek fans) since there is already a plugin with workbench name.
2/ anyhow @craftdocsapp is beautiful. For those looking for excellent block centric authoring with export MD support, this is amazing.
Some of my #roaman friends (@beauhaan) preach the gospel of Blocks. And I agree, blocks are the best unit for work. Craft supports them natively
3/ While Craft is amazing, I still can't see it's future. It is a little between Roam and Obsidian, but not a totally fair comparison. It is simpler and easier to learn. Uses more standard UX metaphors, which makes it a snap to learn.
2/ The word "Complex" sounds negative, but is not.
TfT tools enable new possibilities, but they require effort and commitment.
Is is not just about learning new software & features, but learning new things about ourselves.
We are the tool of thought, software is the helper.
3/ TfT tools are complex because we have to make changes to ourselves - the way we think, process & use knowledge. We have to be willing to invest time, energy & in some cases money to learn new techniques, processes & workflows.
In 1980, @TheTedNelson in one of his books coined the phrase transclusion and even demonstrated it in his own Xanadu Project. Transclusion says you have a single document assembled dynamically from separate sources.
3/ It is good to educate yourself on the transclusion as it helps you better understand the goal of block refs. I suggest this Wikipedia article. It’s not a new idea, the concept of compound documents have been around for a long time.
The Opinionated Short Guide for Switching from Roam to Obsidian
1/ Many have asked for advice on making the switch. While there is no "one size fits all" approach, I will share some practical tips that should help you.
Other switchers - feel free to hop in with your advice
2/ -- Give yourself time --
Over time, we build complex workflows & techniques in a Tool for Thought like Roam. There is no button to instantly transfer you to a new tool. You need to give yourself time to make the transition. Some say 2 to 3 weeks, I gave myself 2 to 3 months.
3/ -- Export from Roam using Flat Markdown --
Export your Roam graph to flat markdown files using the export tool in the menu. This will give you a zip with all your pages in Roam, in markdown format and with all block refs resolved to pure text.
1/ I submitted my 1st plugin to Obsidian for review. The process is nice. Not only is the dev experience good & support via the forums helpful, but the process of submitting a plugin makes you feel confident in @obsdmd leadership.
Here is the feedback I got with needed fixes
2/ You develop your plugin and then you submit it to review. Obsidian tests the plugin and then does a code review. The review is looking for a number of things that will improve the quality, reliability and secure usage of the plugin.
3/ First they make sure you are consistent with their User Interface features. This makes sure the user experience is standardized.