… and as long as I’m posting about fun-but-unnecessary website hacks I don’t have time for, I’d also love to redo the taxonomies and templates on my site to make it easy to navigate media reviews by author, title, series, etc. No one would use it but me, but I’d have a lot of fun with it.

One of the joys of teaching a class on content management is the way that the concepts we discuss and work with have seeped deep into my brain, making it impossible to consume web content casually ever again. I write that half jokingly, but it’s amazing how much ICT 302 affects the way that I see the web, and how much my everyday encounters with the web shape my teaching in that class.

Shortly after last week’s mostly-successful experiment with Hypothesis, I noticed Chris Aldrich posting to Micro.blog about the software and started up a conversation. I’d followed Chris a few weeks before in trying to get more into Micro.blog (perhaps my favorite indie social media platform out there, though I’m also enjoying getting into Mastodon) by following academia and academia-adjacent folks, and was pleased to see an area of common interest.

It wasn’t until a separate conversation on Mastodon this morning that I remembered that my Hypothesis setup was dependent on my manually checking annotations on my website. So, it was three days later that I realized that in addition to our Micro.blog conversation, Chris had been kind enough to leave some comments on my site, giving the Hypothesis comment layer a test run. The most helpful comment included a link to a post he’d written describing how to subscribe to a Hypothesis RSS feed that supported wildcards, something that I’d previously thought was impossible (and, at any rate, isn’t listed in the Hypothesis documentation I was checking).Thanks to this, I’ve now got a notification system for website comments, which is going to make life a lot easier; however, I did find that I had to use a variation of the format that Chris posted: