Microsub reader clients and unread entries

I’ve become inextricably ensnared by the wealth of awesome Microsub feed readers out there. However, one small piece of UI keeps rearing its ugly head as I move variably from one to another either to move from mobile to desktop or just to enjoy the variety of user interfaces available.

While they all do a fantastic job of keeping track of what I’ve read or left unread, many of them are missing the ability to explicitly ask for just the unread items in particular channels. Invariably, I’ll find one or two pieces that I want to leave unread to revisit later, but then finding them in a stream of hundreds later becomes an impossible task.

Aaron Parecki‘s model version in Monocle has a handy menu item to request just the unread items in a channel.

Screencapture of the Monocle UI
Monocle has a simple dropdown to allow me to see just the unread entries.

 

Either it’s missing or I’m not able to easily find the same functionality in Kristof De Jaeger‘s Indigenous for Android or Grant Richmond‘s Together. (I’ve yet to have time to try out some of the others.)

I suppose I should simply start bookmarking those pieces I still want to read later and rely on my site for the memory. Of course this also then makes me itch for having private feeds in these readers to find my unpublished bookmarks for reading via my favorite Microsub clients on a future date.

Read settings page in Indigenous

I’ve noticed that Indigenous for Android does have the ability to create an additional channel for all unread items. This seems useful while I’ve only got a few dozen feeds and a handful of channels, but I don’t expect it to be quite as useful when I’ve moved over several dozen channels with hundreds of feeds. The benefit is that it does replicate the sort of functionality that most social silos like Facebook and Twitter have of an unending stream of unread posts. 

Indigenous also allows one to either manually mark items as read individually or automatically mark them read a page at a time. The page at a time seems to clear out the entire channel rather than marking things read as they’re scrolled, so it’s a bit too broad for my taste. Monocle does a much better job at this marking read while scrolling functionality. Indigenous also says it has a “Mark all read” button per channel, but somehow I’m not seeing it in the UI despite the many ways I toggle the options.

Indigenous also has the ability to set a Read later channel, which seems useful. There is another setting for “Move items” that indicates one can move posts from one channel to another, but when choosing individual posts to move, the UI reads “Select channel to add the feed to”. I was leery at first because I didn’t want to move my entire feed to the new channel, but after  trying it there’s a pop up that said “Post moved to channel X”. Perhaps Kristof might change the word “feed” to “post” in that part of the interface? Sadly though, I have to report that looking at my Unread items channel doesn’t actually show the things that were to have been moved.

 

 

This post was originally published on Chris Aldrich

Extra Feeds Plugin for WordPress

David Shanske has built a simple new IndieWeb friendly plugin for WordPress.

For individual posts, the Extra Feeds plugin will add code into the <header> of one’s page to provide feed readers that have built-in discovery mechanisms the ability to find the additional feeds provided by WordPress for all the tags, categories, and other custom taxonomies that appear on any given page. 

Without the plugin, WordPress core will generally only provide the main feed for your site and that of your comments feed. This is fine for sites that only post a few times a day or even per week. If you’re owning more of the content you post online on your own website as part of the IndieWeb or Domain of One’s Own movements, you’ll likely want more control for the benefit of your readers.

In reality WordPress provides feeds for every tag, category, or custom taxonomy that appears on your site, it just doesn’t advertise them to feed readers or other machines unless you add them manually or via custom code or a plugin. Having this as an option can be helpful when you’re publishing dozens of posts a day and your potential readers may only want a subsection of your posting output.

In my case I have a handful of taxonomies that post hundreds to thousands of items per year, so it’s more likely someone may want a subsection of my content rather than my firehose. In fact, I just ran across a statistician yesterday who was following just my math and information theory/biology related posts. With over 7,000 individual taxonomy entries on my site you’ve got a lot of choice, so happy hunting and reading!

This plugin also includes feeds for Post Formats, Post Kinds (if you have that plugin installed), and the author feed for sites with one or more different authors.

This is useful in that now while you’re on any particular page and want to subscribe to something on that specific page, it will be much easier to find those feeds, which have always been there, but are just not easily uncovered by many feed reader work flows because they weren’t explicitly declared.

Some examples from a recent listen post on my site now let you more easily find and subscribe to:

  • my faux-cast:
    <link rel="alternate" type="application/rss+xml" title="Chris Aldrich &raquo; listen Kind Feed" href="https://boffosocko.com/kind/listen/feed/rss/" />
  • the feed of items tagged with Econ Extra Credit, which I’m using to track my progress in Marketplace’s virtual book club:
    <link rel="alternate" type="application/rss+xml" title="Chris Aldrich &raquo; Econ Extra Credit Tag Feed" href="https://boffosocko.com/tag/econ-extra-credit/feed/rss/" />
  • the feed for all posts by an author:
    <link rel="alternate" type="application/rss+xml" title="Chris Aldrich &raquo; Posts by Chris Aldrich Feed" href="https://boffosocko.com/author/chrisaldrich/feed/rss/" />

This post was originally published on Chris Aldrich

Annotation posts >> Highlight posts

Because they’re so similar, I’ve decided to discontinue the custom highlight posts my site had in lieu of the more prevalent annotation post kind. The layout and format of both as highlighted text quoted from another site was almost exactly the same with the primary difference being my additional commentary added to the highlighted text to call it an annotation. Conceptually I considered “highlight + commentary/reply = annotation”. The difference is marginal at best–pun intended.

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.

This post was originally published on Chris Aldrich

Cleaning up feeds, easier social following, and feed readers

I’ve been doing a bit of clean up in my feed reader(s)–cleaning out dead feeds, fixing broken ones, etc. I thought I’d take a quick peek at some of the feeds I’m pushing out as well. I remember doing some serious updates on the feeds my site advertises three years ago this week, but it’s been a while since I’ve revisited it. While every post kind/type, category, and tag on my site has a feed (often found by simply adding /feed/ to the end of those URLs), I’ve made a few custom feeds for aggregated content.

However, knowing that some feeds are broadly available from my site isn’t always either obvious or the same as being able to use them easily–one might think of it as a(n) (technical) accessibility problem. I thought I’d make a few tweaks to smooth out that user interface and hopefully provide a better user experience–especially since I’m publishing everything from my website first rather than in 30 different places online (which is a whole other UI problem for those wishing to follow me and my content). Since most pages on my site have a “Follow Me” button (courtesy of SubToMe), I just needed to have a list of generally useful feeds to provide it. While SubToMe has some instructions for suggesting lists of feeds, I’ve never gotten it to work the way I expected (or feed readers didn’t respect it, I’m not sure which?) But since most feed readers have feed discovery built in as a feature, I thought I’d leverage that aspect. Thus I threw into the <head> of my website a dozen or so links from some of the most typical feeds people may be most interested in from my site. Now you can click on the follow button, choose your favorite feed reader, and then your reader should provide you with a large list of feeds which you might want to subscribe. These now broadly include the full feed, a comments feed, feeds for all the individual kinds (bookmarks, likes, favorites, replies, listens, etc.) but potentially more useful: a “microblog feed” of all my status-related updates and a “linkblog feed” for all my link-related updates (generally favorites, likes, reads, and bookmarks).

Some of these sub-feeds may be useful in some feed readers which don’t yet have the ability for you to choose within the reader what you’d like to see. I suspect that in the future social readers will allow you to subscribe to my primary firehose or comments feeds, which are putting out about 85 and 125 posts a week right now, and you’ll be able to subscribe to those, but then within their interface be able to choose individual types by means of filters to more quickly see what I’ve been bookmarking, reading, listening to or watching. Then if you want to curl up with some longer reads, filter by articles; or if you just want some quick hits, filter by notes. And of course naturally you’ll be able to do this sort of filtering across your network too. I also suspect some of them will build in velocity filters and friend-proximity filters so that you’ll be able to see material from people who don’t post as often highlighted or to see people’s content based on your personal rankings or categories (math friends, knitting circle, family, reading group, IndieWeb community, book club, etc.). I’ve recently been enjoying Kicks Condor’s FraidyCat reader which touches on some of this work though it’s not what most people would consider a full-featured feed reader but might think of as a filter/reader dashboard sort of product.

Perhaps sometime in the future I’ll write a bit of code so that each individual page on my site that you visit will provide feeds in the header for all the particular categories, tags, and post kinds that appear on that page?That might make a clever, and simple little plugin, though honestly that’s the sort of code I would expect CMSes like WordPress to provide out of the box. Of course, perhaps broader adoption of microformats and clever readers will obviate the need for all these bits?

 

This post was originally published on Chris Aldrich