By way of experiment I have added, where they exist, annotations of my postings to the posting itself. Such annotations are made in Hypothes.is an online annotations tool, with social features.

Hypothes.is uses the W3C standard for annotations, and the service has an API. That opens it up for experimentation. For instance there is a Obsidian plugin that pulls in my annotations and brings them to my notes.

I now experimentally use the API to check for annotations that exist for a single posting. If such annotations exist, a page with a single blogposting will mention the existence of annotations just above the comments, and provide a link to them. For this I adapted the template for single postings in my WordPress theme. See the image.


The number of annoations, if any, is shown beneath individual postings above the comments.

Like with comments this opens up a surface for people to interact with my blog and have that interaction made visible on my site. As with comments and trackbacks of old, this also opens up a possibility for spam, especially as there is no way yet for me to moderate such annotations to be shown, nor a way to prevent them in general.

Hypothes.is has existed for a decade and reached 2 million annotated articles early this year. It’s relatively unknown, and not commonly used. This at the moment should be enough ‘protection by obscurity’ for now. Maybe in time I will reconsider, there are valid reasons to do so.

Existing users of Hypothes.is don’t need a link like I added to my postings, they see that in their browser already (depicted below). However it may encourage other readers of this blog to check out those annotations and perhaps create their own.

In a next step I may aim to list the existing annotations, and their authors, not just link to them, but not immediately. First I’ll think some more about how I might use the Hypothes.is API for other things in my personal workflow.


A screenshot of how a logged-in Hypothes.is user in their browser sees a post on this site that has annotations.

1 annotations of "Added Hypothes.is Annotations Link To Posts"


This blogpost has 1 annotations in Hypothes.is! See annotations

5 reactions on “Added Hypothes.is Annotations Link To Posts

  1. Here are some impressions of my increased usage of Hypothes.is, a social annotation tool, in the past few days.
    I follow Chris Aldrich his Hypothes.is RSS feed, and his usage has been both a good example and source of learning in the past months, as well as a nudge to experiment and adopt Hypothes.is myself.
    What follows is a list of some early impressions that I formulated earlier today in an email. I thought I might as well post them here.

    I played with the API to get a grip of how I might interact with the annotations I make, and with those of others I’m interested in. Added the existence of annotations to my blogposts in WordPress through the API too.
    The Obsidian plugin to get annotations into my notes is an absolute prerequisite, because I need those notes in my own workflow.

    I find working in browser for annotations somewhat distracting and uncomfortable (and I need to remind myself that they will end up in my notes, I feel the urge to also download it directly to my notes.)
    I try to add an Archive link to the annotated article as the first link. It is slowly becoming habitual.
    I mention existing notes in my annotations when I make them in Obsidian. Because it is one context that is a matter of starting a link [[ and I have forward search through all note titles. In hypothes.is being browser based this is a bit harder, as it means switching tools to retrieve the correct note titles. They do then work when they end up in Obsidian of course. At the same time, in my earlier use of a markdown downloader I would just mention those associations in the motivation to save a link, which is worse. Hypothes.is sits in the middle of saving a bookmark with motivation and annotating in Obsidian itself.
    I do have some performative urges when annotating publicly. Maybe they will disappear over time.
    The firefox hypothes.is bookmarklet I use doesn’t seem to play nice with archive.org. There’s another I haven’t tested yet.
    I notice that any public annotations are licensed CC0 (public domain). Not sure what I think about that yet. It’s a logical step as such, but I don’t fully see yet what it may mean for subseqeunt learning processes internally and further down the process of creating insights or outputs. Is CC0 also applied to closed groups (educational settings e.g.)? Private annotations are just that, and don’t have CC0, but then you miss out on the social aspects of annotation.
    My thoughts keep wandering to interacting with hypothes.is without using it directly to annotate webarticles through the browser. Are there any tools or people who build on or share with hypothes.is using the W3C standards / API, but don’t necessarily use hypothes.is themselves? Or run their own instance, which should be possible? I suspect that would open opportunities for a more liquid experience between this blog, my notes, and annotated articles.

  2. I’ve now added over 100 annotations using Hypothes.is (h.), almost all within the last month. This includes a few non-public ones. Two weeks ago I wrote down some early impressions, to which I’m now adding some additional observations.

    100 annotations (in a month) don’t seem like a lot to me, if h. is a regular tool in one’s browsing habit. H. says they have 1 million users, that have made 40 million annotations to over 2 million articles (their API returns 2.187.262 results as I write this). H. has been in existence for a decade. These numbers average out to 20 annotations to 2 articles per user. This to me suggests that the mode is 1 annotation to 1 article by a user and then silence. My 100 annotations spread out over 30 articles, accumulated over a handful of weeks is then already well above average, even though I am a new and beginning user. My introduction to h. was through Chris Aldrich, whose stream of annotations I follow daily with interest. He recently passed 10.000 annotations! That’s 100 times as many as mine, and apparently also an outlier to the h. team itself: they sent him a congratulatory package. H.’s marketing director has 1348 public annotations over almost 6 years, its founder 1200 in a decade. Remi Kalir, co-author of the (readworthy!) Annotation book, has 800 in six years. That does not seem that much from what I would expect to be power users. My blogging friend Heinz has some 750 annotations in three years. Fellow IndieWeb netizen Maya some 1800 in a year and a half. Those last two numbers, even if they differ by a factor 5 or so in average annotations/month, feel like what I’d expect as a regular range for routine users.
    The book Annotation I mentioned makes a lot of social annotation, where distributed conversations result beyond the core interaction of an annotator with an author through an original text. Such social annotation requires sharing. H. provides that sharing functionality and positions itself explicitly as a social tool (“Annotate the web, with anyone, anywhere” “Engage your students with social annotation“). The numbers above show that such social interaction around an annotated text within h. will be very rare in the public facing part of h., in the closed (safer) surroundings of classroom use interaction might be much more prominent. Users like me, or Heinz, Maya and Chris whom I named/linked above, will then be motivated by something else than the social aspects of h. If and when such interaction does happen (as it tends to do if you mutually follow eachothers annotations) it is a pleasant addition, not h.’s central benefit.
    What is odd to me is that when you do indeed engage into social interaction on h., that interaction cannot be found through the web interface of my annotations. Once I comment, it disappears out of sight, unless I remember what I reacted to and go back to that annotation by another user directly, to find my comment underneath. It does show up in the RSS feed of my annotations, and my Hypothes.is-to-Obsidian plugin also captures them through the API. Just not in the web interface.
    Despite the social nature of h., discovery is very difficult. Purposefully ‘finding the others’ is mostly impossible. This is both an effect of the web-interface functionality, as well as I suspect because of the relatively sparse network of users (see observation 1). There’s no direct way of connecting or searching for users. The social object is the annotation, and you need to find others only through annotations you encounter. I’ve searched for tags and terms I am interested in, but those do not surface regular users easily. I’ve collated a list of a dozen currently active or somewhat active annotators, and half a dozen who used to be or are sporadically active. I also added annotations of my own blogposts to my blog, and I actively follow (through an RSS feed) any new annotation of my blogposts. If you use h., I’d be interested to hear about it.
    Annotations are the first step of getting useful insights into my notes. This makes it a prerequisite to be able to capture annotations in my note making tool Obsidian, otherwise Hypothes.is is just another silo you’re wasting time on. Luckily h. isn’t meant as a silo and has an API. Using the API and the Hypothes.is-to-Obsidian plugin all my annotations are available to me locally. However, what I do locally with those notes does not get reflected back to h., meaning that you can’t really work through annotations locally until you’ve annotated an entire article or paper in the browser, otherwise sync issues may occur. I also find that having the individual annotations (including the annotated text, in one file), not the full text (the stuff I didn’t annotate), feels impractical at times as it cuts away a lot of context. It’s easily retrievable by visiting the url now, but maybe not over time (so I save web archive links too as an annotation). I also grab a local markdown copy of full articles if they are of higher interest to me. Using h. in the browser creates another inbox in this regard (having to return to a thing to finish annotation or for context), and I obviously don’t need more inboxes to keep track of.
    In response to not saving entire articles in my notes environment, I have started marking online articles I haven’t annotated yet at least with a note that contains the motivation and first associations I normally save with a full article. This is in the same spot as where I add a web archive link, as page note. I’ve tried that in recent days and that seems to work well. That way I do have a general note in my local system that contains the motivation for looking in more detail at an article.
    The API also supports sending annotations and updates to h. from e.g. my local system. Would this be potentially better for my workflow? Firefox and the h. add-on don’t always work flawlessly, not all docs can be opened, or the form stops working until I restart Firefox. This too points in the direction of annotating locally and sending annotations to h. for sharing through the API. Is there anyone already doing this? Built their own client, or using h. ‘headless’? Is there anyone who runs their own h. instance locally? If I could send things through the API, that might also include the Kindle highlights I pull in to my local system.
    In the same category of integrating h. into my pkm workflows, falls the interaction between h. and Zotero, especially now that Zotero has its own storage of annotations of PDFs in my library. It might be of interest to be able to share those annotations, for a more complete overview of what I’m annotating. Either directly from Zotero, or by way of my notes in Obsidian (Zotero annotatins end up there in the end)
    These first 100 annotations I made in the browser, using an add-on. Annotating in the browser takes some getting used to, as I try to get myself out of my browser more usually. I don’t always fully realise I can return to an article for later annotation. Any time the sense I have to finish annotating an article surfaces, that is friction I can do without. Apart from that, it is a pleasant experience to annotate like this. And that pleasure is key to keep annotating. Being able to better integrate my h. use with Obsidian and Zotero would likely increase the pleasure of doing it.
    Another path of integration to think about is sharing annotated links from h. to my blog or the other way around. I blog links with a general annotation at times (example). These bloggable links I could grab from h. where I bookmark things in similar ways (example), usually to annotate further later on. I notice myself thinking I should do both, but unless I could do that simultaneously I won’t do such a thing twice.

  3. A summary overview of changes I made to this site, to make it more fully a indieweb hub / my core online presence. The set-up of my WordPress installation also has been described.
    Theme related tweaks

    Created child theme of Sempress, to be able to change appearance and functions
    Renamed comments to reactions (as they contain likes, reposts, mentions etc.)
    in the entry-footer template and the comments template
    Removed h-card microformats, and put in a generic link to my about page for the author in the Sempress function sempress_posted_on. Without a link to the author mentions show up as anonymous elsewhere.
    Removed the sharing buttons I used (although they were GDPR compliant using the Sharriff plugin, but they got in the way a lot I felt.
    Added a few menu options for various aspects of my postings (books, check-ins, languages)
    Introduced several categories to deal with different content streams: Dutch, German for non-English postings, Day to Day for things not on the home page, Plazes for check-ins, Books for ehh books, RSS-Only for unlisted postings, and Micromessage for tweets I send from the blog. This allows me to vary how I display these different types of things (or not)
    Displaying last edited and created dates to (wiki)pages
    Added a widget with projects I support
    Added to the single post template a section that mentions and links the number of Hypothes.is annotations for that post, where they exist.

    Functionality related tweaks

    Started creating pages as a wiki-like knowledgebase, using page categories to create the wiki structure
    To show excerpts from webmentions I changed the template for a webmention in the Semantinc backlinks plugin, class-linkbacks-handler.php
    Added a plugin to display blogposts on the same date in previous years.
    Added plugin Widget Context to remove recent posts and comments from individual posting’s pages, as they cause trouble with parsing them for webmentions.
    Using categories as differentiator I added language mark-up to individual postings, category archives. Also added automatic translation links to non-English postings in the RSS feed (not on the site). On the front page non-English postings have language mark-up around the posting.
    Added a blogroll that is an OPML file with a stylesheet, so it can be equally read by humans and machines.
    Added an extra RSS feed for comments that excludes webmentions and ping/trackbacks
    Added a /feeds page
    Added a Now page
    Added a Hello page
    Added a way to share book lists / feeds.
    Stopped embedding slide decks, and stopped embedding new Flickr photos (as well as removed older embeds, currently 23 postings between January 2013 and July 2018 still have them, and 22 postings from June 2006 to July 2009)
    Removed all affilliate links to Amazon books as it entails tracking
    Added an Index (using a plugin)
    Added my own basic check-in and Dopplr style posts

    Other tweaks

    Set up 2 additional WordPress instances for testing purposes (Proto and Meso)

  4. Today at 14:07 twenty years ago, I posted my first blog post. Well over 3000 posts later, this blog has been an integral part of quite a stretch of my life, to the point where it is unavoidable that if you’ve read along you now probably know more about me than I think I’ve actually shared in writing.
    In the past few years I’ve taken this blog’s anniversary as a moment to reflect on some of my blogging practices. That yearly reflection started 5 years ago when I was just leaving Facebook. This time it coincides with #twittermigration, where many people are exploring federated options now that Musk has taken over Twitter. Whether that is something that will stick is uncertain of course, but it is interesting to watch playing out. Other earlier such reflections: 2018, 2019, 2020, 2021.
    Last year I wrote:

    For the coming time this note-to-blog pipeline, and making it easier for myself to post, will be my area of attention I think. Let’s see next year around this time, when I hit the two decade mark with this blog, how that went.

    Indeed, that is exactly what I did from early this year: ensure that I could post directly to this blog in different ways. The key to that was create a Micropub client, which posts to this site. Once I had that I could create different paths to feed a post to that Micropub client. From inside a feedreader, directly from my notes in Obsidian, or through a simple web form. More recently I created different versions of that web form, to also post check-ins, and announce travel plans. In all fairness, my habits in how I post things haven’t fundamentally changed yet: I’m writing this in the WordPress back-end. But increasingly I am using those other paths to get content into this site.
    Making it easier to post, puts the friction of blogging where it needs to be: wanting to write something.
    Connecting things up into flows, blurring the lines between my site, online interaction and my notes for instance, stays an interesting thing to experiment with. In the past months I started using Hypothes.is more intensively, to annotate things I read on the web. Already all those annotations seamlessly end up in my local notes, from where I can work with them, and where they concern my own site I’ve made them visible here.
    But most of all, aside from all the more nerdy things of tweaking this site and my information flows, this blog has been a source of conversation for twenty years now. It was my original hope, and my ongoing motivation to keep blogging.
    Which brings me back to the earlier mentioned #twittermigration. Musk declared the bird is freed, but it seems quite a few people think the bird was caught and rather take wing on their own. Quite a few of those are the people I early on conversed with through their blogs too. If there’s a key difference between ActivityPub/Mastodon and Twitter, it’s that the federated version only ‘works’ if you actually interact with other people. Likes don’t matter in highlighting a message. Boosts do only share a message with your own followers, and has no other effect. It doesn’t mean it will be put higher in the timeline of others, it’s all in the now. There’s no amplification. Conversation is the key, if you interact then others may also see it and join the conversation. Twitter used to be like that too.
    Conversation is key, and that is why I blog.
    Here’s to another year of blogging and conversation.

Comments are closed.

Mentions