“At the end of each chapter write a few bullet points that summarize what you’ve read and make it personal if you can — that is, apply it to something in your life. Also, note any unanswered questions. When you’re done the book, put it down for a week.”
“Pick up the book again and go through all your notes. Most of these will be garbage but there will be lots you want to remember. Write the good stuff on the inside cover of the book along with a page number.”
“(Optional) Copy out the excerpts by hand or take a picture of them to pop into Evernote. Tag accordingly.”
I ran across a Chrome extension for highlights, annotations, and tagging tonight. It’s called Learning Paths. It works roughly as advertised for creating and saving highlights and annotations online. With a social silo log in process (I didn’t see an email login option), you’ve quickly got an account on the service.
You can then use the extension to highlight, tag, and annotate web pages. One can export their data as a .csv file which is nice. They’ve also got an online dashboard which displays all your data and has the ability to see public data from other users as well.
One of the interesting pieces they support is allowing users to tweet a thread from all their highlights of a piece online. Upon seeing this I thought it might make a useful feature for getting data into one’s personal wiki, website, or digital garden, particularly now that ThreadReaderApp supports posting unrolled Twitter threads to one’s Micropub enabled website.
So the workflow goes something like this (with links to examples of my having tried it along the way):
- Use Learning Paths to highlight an article;
- Use the sharing interface to share the highlights as a Twitter thread;
- Make any modifications to the Twitter thread and then post;
- Go to the thread and reply to one of the tweets with “@ThreadReaderApp unroll”;
- Log into your ThreadReaderApp account to see the thread;
- Go to your “My Authored Threads” tab;
- Click on the “Publish n Tweets to Blog” button for the appropriate thread (and handle any authentication/authorization workflow);
- The thread of highlights should now be on your website;
While this works relatively well, there are a few drawbacks:
- The UI for the annotations is a bit flaky at times and in my experience often disappears before you’ve had a chance to save them.
- The workflow misses out on any of the annotations and tags you might add to each of the highlights (unless you manually add them to the thread, and even then you may run out of space/characters).
- The appearance of the thread on your site is simply what you get.
While the idea works roughly in practice, it isn’t as optimal as the workflow or data fidelity I’ve found in using more robust tooling like that found in Hypothes.is for which I’ve also built a better UI on my website.
Still others, might appreciate the idea, so have at it! I’d love to see others’ ideas about owning their highlights, annotations, and related data in a place they control.
I suspect that a reasonable WordPress user could probably set up a free Hypothes.is account and use the RSS feed from it (something like
https://hypothes.is/stream.atom?user=username) to create an IFTTT.com recipe to post it as a public/draft to their WordPress website.
My version presented here has also been augmented by also using the Post Kinds Plugin to which I’ve manually added a custom annotation post type along with some CSS for the yellow highlight effect. These additional coding flourishes aren’t absolutely necessary for those who just want to own the data on their website.
If you want to get even fancier you could also do RSS to IFTTT to do a webhook post to an Micropub endpoint or custom code your own solution using their API. Lots of options are available, the most difficult part may be knowing that something like this could even be done.
I often pull my own annotations to my personal website similar to your own Memex and publish them there (example: https://boffosocko.com/kind/annotation/)
Incidentally you can also annotate documents stored locally on your computer, but viewed through a browser as well as collaboratively annotating with others.
Recently, I made my 100,000th annotation with Hypothesis. I know what you must be thinking: Doesn’t she have a life? Why would anyone make 100,000 annotations? Just a few short years ago, I would have dismissed this prospect as preposterous. I disliked reading online and abandoned most online tools at the first hurdle. Yet, here I am, a self-diagnosed annotation addict. (For those of you who don’t know me, I used to work for Hypothesis. Leaving to build open infrastructure didn’t mean that I left the tool behind — far from it!)
I hadn’t included it at the time, but private groups are also an interesting way to share ideas and private posts with small groups of people. You could also use those groups as taxonomies for keeping private notebooks as well. While the primary instance of Hypothes.is that many use would technically be considered a silo, keep in mind that it’s open source, so you could technically host it for yourself as an IndieWeb project! Now to get support for Webmention and Micropub! 😉
I’d also recently done a quick survey of some of the bigger accounts I was aware of and suspected that there must be one or two edge cases in the 10,000+ range. I knew a bot user or two were likely way ahead, but figured there was at least one person with a huge number of posts hiding out there. Great to know my hypothesis was right!
I’m still tinkering with mine and should have a Micropub based version using IFTTT and Webhooks done soon.
Since I only had 13 highlight posts versus 121 annotation posts (plus various additional annotations and highlights which I’ve rolled up into the body of some of my read posts) over the last year and a half, I felt it seemed redundant and bothersome to maintain two separate, but nearly identical post kinds. Semantically one may think of a highlight on some text as an annotation anyway, thus the idea of annotation subsumes that of a simple highlight.
As of this evening, I’ve changed all the custom highlight posts to be of the annotation kind. Other than the one word visual difference of the post kind text changing from “highlight” to “annotation” this change won’t affect much except for those who may have been subscribed to the highlight feed. Going forward you may consider subscribing to my annotation feed instead.
I had created highlight posts first, but in the end annotation posts have won the day. And for those that don’t have them, fear not, because honestly annotation posts are really just glorified bookmarks with custom text in the context. (The glorification only entails a highligher icon instead of a bookmark icon and a bit of CSS to color the text yellow.) I do find having them delineated for my personal research purposes useful though.
A great look at our new feature for saving highlights from physical books— Readwise (@readwiseio) January 10, 2020
This is one of the coolest apps I've seen in a long time from @readwiseio— Farza (@FarzaTV) January 7, 2020
1. Take a picture of a page from a book.
2. Drag and drop markers to literally highlight the passage right on the picture and extract the quote.
3. Store the quote, take notes, attach it to the book. pic.twitter.com/Dzb2x6NQIa
President Trump sent a letter on Tuesday to Speaker Nancy Pelosi expressing his “most powerful protest” against the impeachment process. The House is expected to vote on two articles of impeachment against Mr. Trump on Wednesday.
In general I don’t think for a moment that he actually wrote any of this. I suspect some of it was dictated or pulled from prior communication/thoughts. It definitely sounds like his “voice”, but I can’t imagine that it came from him in the same psuedo-logical structure, which I highly suspect was imposed on it after-the-fact by someone else.
He really used 8 exclamation marks in a six page letter?! Has any president used this many in an entire term I wonder?
–December 20, 2019 at 09:00AM
Impeachment Fever ❧
There are several instances in this document where words are improperly capitalized, presumably in an attempt to make them stand out and make them more memorable. Or possibly to provide them more emphasis than they deserve.
–December 20, 2019 at 09:17AM
American People ❧
Here’s another case of the mis-capitalization. American should be capitalized, but people should not.
–December 20, 2019 at 09:18AM
I started some research and work into creating a plugin to effectuate making “vias” and “hat-tips” easier to create on my site since I often use them to credit some of my sources. I was a bit surprised not to see any prior art in the WordPress repository. Sadly, there’s nothing concrete to show off just yet. I think I’ve got a clear concept of how I want it to look and what will go into the first simple iteration. It will be my first “real” WordPress plugin, so there’s some interesting learning curve along the way.
On a more concrete front, I made a handful of CSS tweaks and fixes to the site, and particularly to some of my annotation/highlighting related posts, that I’ve been meaning to take care of for a while. Now on read posts where I’ve aggregated some annotations/highlights, the highlighted portions should appear in yellow to better differentiate them in portions of text and represent them as highlights. This prevents me from creating a read post for the content and one or dozens of related, but completely separate, follow-up annotation posts. Now they’re combined, and I think they provide a bit more contextualization for the original, but still include the timestamps for the annotations. I’m sure there’s some more I can do to tweak these, but I like the result a bit better than before. Today’s post about a research paper I read on food is a good example of to highlight (pun intended) some of the changes. Ideas for further improvements are most welcome.
I also slightly tweaked and then further experimented with some of the CSS for my reply contexts. I’ve been considering reformatting them a tad to try to highlight the fact that the content within them is context for my responses. In some sense I’m looking at making the context look more card-like or perhaps oEmbed-esque. I still haven’t gotten it the way I’d ultimately like it, but perhaps one day soon? I played around with changing the size of the context with respect to my content as well as adding some outlines and shadows to make the context look more like cards, but I haven’t gotten things just right. Perhaps some more research looking at others’ sites will help? Which sites do you think do reply contexts incredibly well?
I’m glad there’s a holiday coming up so I can spend a bit of time catching up on some of the sessionsand notes and hopefully see some of the demos from the camp.
Dissenter acts as a workaround for people wishing to comment on websites, even those without a comment section. One user, Cody Jassman, describe the plugin as “like the graffiti painted in the alley on every web page. You can take a look around and see what passersby are saying.” The plugin was launched in beta at the end of February by Andrew Torba, who co-founded Gab, a far-right social network. Gab is well known for being the platform where Robert Bowers, the suspected Pittsburgh synagogue shooter, published anti-Semitic comments before he allegedly killed 11 people and wounded many others at the Tree of Life synagogue.