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.
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.
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.
I’m still tinkering away at pathways for following people (and websites) on the open web (in my case within WordPress). I’m doing it with an eye toward making some of the UI and infrastructure easier in light of the current fleet of Microsub servers and readers that will enable easier social reading without the centralized reliance on services like Facebook, Twitter, Instagram, Snapchat, Medium, LinkedIn, et al.
If you haven’t been following along, here are some relevant pieces for background:
Since I’ve been digging around a bit, I’ll note that Yannick Lefebvre’s Link Library plugin seems to have a similar sort of functionality to Links Manager and adds in the ability to add a variety of additional data fields including tags, which Ton Zijlstra mentions he would like (and I wouldn’t mind either). Unfortunately I’m not seeing any OPML functionality in the plugin, so it wins at doing display (with a huge variety of settings) for a stand-alone blogroll, but it may fail at the data portability for doing the additional OPML portion we’ve been looking at. Of course I’m happy to be corrected, but I don’t see anything in the documentation or a cursory glance at the code.
In the most ideal world, I’d love to be able to use the Post Kinds Plugin to create follow posts (see my examples). This plugin is already able to generally use bookmarklet functionality to pull in a variety of meta data using the Parse This code which is also built into Post Kinds.
It would be nice if these follow posts would also copy their data into the Links Manager (to keep things DRY), so that the blogroll and the OPML files are automatically updated all at once. (Barring Post Kinds transferring the data, it would be nice to have an improved bookmarklet for pulling data into the Links Manager piece directly.)
Naturally having the ability for these OPML files be readable/usable by Jack Jamieson’s forthcoming Yarns Microsub Server for WordPress (for use with social readers) would be phenomenal. (I believe there are already one or two OPML to h-feed converters for Microsub in the wild.) All of this would be a nice end -to-end solution for quickly and easily following people (or sites) with a variety of feeds and feed types (RSS, Atom, JSONfeed, h-feed).
An additional refinement of the blogroll display portion would be to have that page display as an h-feed of h-entries each including properly marked up h-cards with appropriate microformats and discoverable RSS feeds to make it easier for other sites to find and use that data. (This may be a more IndieWeb-based method of displaying such a page compared with the OPML spec.) I’ll also note that the Links Manager uses v1 of the OPML spec and it would potentially be nice to have an update on that as well for newer discovery tools/methods like Dave Winer’sShare Your OPML Subscription list, which I’m noting seems to be down/not functioning at the moment.
Dramatically extending a Domain of One’s Own with IndieWeb technology: How to improve your online research notebooks, commonplace books, and digital pedagogy
(This description will be edited and used on the website. Please include 1-2 paragraphs and a list of key takeaways for the audience.)
Having a Domain of One’s Own and using it as a “thought space” to own your online identity and work is just the tip of the iceberg. Can you imagine how useful it would be if you could use your Twitter account to reply to someone on Facebook (without needing a Facebook account) or vice versa? Open web technology from the IndieWeb movement that utilizes simple plugins, modules, or even built-in functionality now exists so that people can now use WordPress, Drupal, WithKnown, Grav and many other content management systems on any domain name to have rich site-to-site communications in a simple and intuitive way. Third party (and often unethical) corporate platforms are no longer needed to have rich interactions between scholars on the web.
It is now easily possible to have a teacher write a post on their own website and their students to easily reply/react to that post on their own websites (along with a useful reply context) and send that reply to the teacher’s website for possible display. Each participant can now own a copy of both sides of the conversation.
Teachers and students will learn how to (individually or together) collect, analyze, write, collaborate, and interact easily online while doing so in a space they own and control without giving away their data to third party platforms.
Researchers can now easily bookmark, highlight, or annotate portions of the web and keep this data (public/private) on their own website (aka digital commonplace book or notebook) for future reference or use.
We’ll show how courseware can be decentralized so that the instructor and the students each own their own pieces of the learning processes and can keep them for as long as they wish.
We will demonstrate how one can use their WordPress-based website with a few simple plugins to own all of the traditional social media types (bookmarks, items read, highlights, annotations, comments/replies, photos, status updates, audio, checkins, etc.) on their own site while still allowing interacting (if desired) with other websites as well as in social spaces like Twitter, Instagram, Swarm, etc.
We will demonstrate a new generation of free feed readers that allow composing in-line responses and reactions that post them directly to one’s own website as well as send notification to the site being read and interacted with.
You can now have the joy of a Domain of Your Own and still easily interact just as if your site were a (better-than) first class social media platform.
More Information About Your Session
(Please describe your session in greater detail for the organizers. You may be more casual in this description as it will not be posted on the website.)
In some sense, this session will be a crash course on using IndieWeb technologies and building-blocks with WordPress in the Education space. I’ll aim to remove a lot of technical jargon and keep coding examples to a bare minimum (if using any at all) so that those with the technical ceiling of downloading and installing a plugin can immediately benefit from the talk. I will also provide enough pointers and describe the broad outlines that developers will have a broad overview of the IndieWeb space to find and extend these plugins and functionality if they wish.
I’ll be covering the basics of new W3C recommendations like Webmention, Micropub, and WebSub along with forthcoming specs like Microsub in combination with IndieAuth (a version of OAuth2 for login). I’ll show how they can be applied to personal websites in research, teaching, collaboration, and other educational domains like creating Open Educational Resources. Many of these can be easily implemented in WordPress with just a handful of simple plugins that allow the web to become the social media platform we all wish it would be.
I’ll use examples from my own personal website and several others (which use Drupal, WithKnown, Grav, etc.) to show how these plugins can be used in educational settings and will walk through a case study of a course built using DoOO and IndieWeb philosophies and technologies (EDU 522: Digital Teaching and Learning at Southern Connecticut State University) on which I collaborated with Dr. Gregory McVerry.
It may still be a while before I can make the leap I’d love to make to using Microsub related technology to replace my daily feed reader habits. I know that several people are working diligently on a Microsub server for WordPress and there are already a handful of reader interfaces available. I’m particularly interested in the fact that I can use a reader interface integrated with Micropub so that my reactions in the reader (likes, bookmarks, replies, etc.) are posted back to my own personal website which will then send notifications (via Webmention) to the mentioned websites. Of course it’s going to take some time before I’m using it and even more time after that for the set up to become common and easy to use for others. So until then, I and others will need some tools to use right now.
Toward this end I thought I’d double down on my use of Inoreader in my daily web consumption workflows. I wanted to make it easier to use my feed reader to post all these types of posts to my website which will still handle the notifications. In some sense, instead of relying on a feed reader supporting Micropub, I’ll use other (older) methods for making the relevant posts. As I see it, there are two potential possibilities using Inoreader:
(1) using a service like IFTTT (free) or Zapier (paid) to take the post intents and send them to my WordPress site, or
(2) using the custom posting interface in Inoreader in conjunction with post editor URL schemes with the Post Kinds plugin to create the posts. Using WordPress’ built-in Post This bookmarklet schemes could also be used to make these posts, but Post Kinds plugin offers a lot more metadata and flexibility.
If This Then That (IFTTT)
Below is a brief outline of some of the IFTTT recipes I’ve used to take data from posts I interact with in Inoreader and post them to my own website.
IFTTT has an explicit like functionality with a one click like button. There is an IFTTT recipe which allows taking this datum and adding it directly as a WordPress post with lots of rich data. The “then that” portion of IFTTT using WordPress allows some reasonable functionality for porting over data.
IFTTT also has explicit favorite functionality using a one click starred article button. There is an IFTTT recipe which allows adding this directly as a WordPress post.
Since the “starred” article isn’t defined specifically in Inoreader as a “favorite”, one could alternately use it to create “read” or “bookmark” posts on their WordPress websites. I’m tempted to try this for read posts as I probably wouldn’t often use it to create favorite posts on my own website. Ultimately one at least wants an easy-to-remember 1 to 1 mapping of pieces of functionality in Inoreader to their own website, so whatever I decide I’ll likely stick to it.
While there is no specific functionality for creating bookmarks in Inoreader (though starred articles could be used this way as previously mentioned), there is a “saved webpage” functionality that could be used here in addition to an IFTTT recipe to port over the data to WordPress.
While Inoreader has a common feed reader read/unread functionality, it is often not used tacitly and this is a means of reducing friction within the application. Not really wanting to muddle the meaning of the “starred” article to do it, I’ve opted to adding an explicit “read” tag on posts I’ve read.
IFTTT does have a “New tagged article” recipe that will allow me to take articles in Inoreader with my “read” tag and post them to my website. It’s pretty simple and easy.
For dealing with replies, there is an odd quirk within Inoreader. Confoundingly the feed reader has two similar, yet still very different commenting functionalities. One is explicitly named “comment”, but sadly there isn’t a related IFTTT trigger nor an RSS feed to take advantage of the data one puts into the comment functionality. Fortunately there is a separate “broadcast” functionality. There is an IFTTT recipe for “new broadcasted article” that will allow one to take the reply/comment and post it to one’s WordPress website.
Like many of the above there is a specific IFTTT recipe that will allow one to add subscriptions directly to WordPress as posts, so that any new subscriptions (or follows) within the Inoreader interface can create follow posts! I doubt many people may use this recipe, but it’s awesome that it exists. Currently anything added to my blogrolls (aka Following Page) gets ported over to Inoreader via OPML subscription, so I’m curious if them being added that way will create these follow posts? And if so, is there a good date/time stamp for these? I still have to do some experimenting to see exactly how this is going to work.
RSS feed-based functionality
In addition to the IFTTT recipe functionality described above, one could also use IFTTT RSS functionality to pipe RSS feeds which Inoreader provides (especially via tags) into a WordPress website. I don’t personally use this sort of set up, but thought I’d at least mention it in passing so that anyone who might like to create other post types to their website could.
Custom posting in Inoreader with Post Kinds Plugin
If using a third-party service like IFTTT isn’t your cup of tea, Inoreader also allows custom sharing options. (There are also many pre-built ones for Facebook, Twitter, etc. and they’re also re-orderable as well.) I thus used WordPress’ post editor URL schemes to send the data I’d like to have from the original post to my own website. Inoreader actually has suggestions in their UI for how to effectuate this generically on WordPress. While this is nice, I’m a major user of the Post Kinds Plugin which allows me a lot more flexibility to post likes, bookmarks, favorites, reads, replies, etc. with the appropriate microformats and much richer metadata. Post Kinds has some additional URL structures which I’ve used in addition to the standard WordPress ones to take advantage of this. This has allowed me to create custom buttons for reads, bookmarks, replies, likes, and listens. With social sharing functionality in Inoreader enabled, each article in Inoreader has a sharing functionality in the bottom right corner that has a configuration option which brings up the following interface:
Once made, these custom button icons appear at the bottom of every post in Inoreader, so, for example, if I want to reply to a post I’ve just read, I can click on the reply button which will open a new browser window for a new post on my website. The Post Kinds plugin on my site automatically pulls in the URL of the original post, parses that page and–where available–pulls in the title, synopsis, post date/time, the author, author URL, author photo, and a featured photo as well as automatically setting the specific post kind and post format. A lot of this data helps to create a useful reply context on my website. I can then type in my reply to the post and add any other categories, tags, or data I’d like in my admin interface. Finally I publish the post which sends notifications to the original post I read (via Webmention).
Conclusion and future
With either of the above set ups, there are a few quick and easy clicks to create my posts and I’m done. Could it be simpler? Yes, but it likely won’t be much more until I’ve got a fully functional Microsub server and reader up and working.
Of course, I also love Inoreader and its huge variety of features and great usability. While I’m patiently awaiting having my own WordPress Microsub server, I certainly wouldn’t mind it if Inoreader decided to add some IndieWeb functionality itself. Then perhaps I wouldn’t need to make the switch in the near future.
What would this look like? It could include the ability to allow me to log into Inoreader using my own website using IndieAuth protocol. It could also add Micropub functionality to allow me to post all these things directly and explicitly to my website in an easier manner. And finally, if they really wanted to go even further, they could make themselves a Microsub server that enables me to use any one of several Microsub clients to read content and post to my own website. And of course the benefit to Inoreader is that if they support these open internet specifications, then their application not only works with WordPress sites with the few appropriate plugins, but Inoreader will also work with a huge variety of other content management systems that support these specs as well.
Whether or not Inoreader supports these protocols, there is a coming wave of new social feed readers that will begin to close many of these functional gaps that made RSS difficult. I know things will slowly, but eventually get better, simpler, and easier to use. Soon posting to one’s website and doing two way communication on the internet via truly social readers will be a reality, and one that’s likely to make it far easier to eschew the toxicity and problems of social sites like Facebook and Twitter.