Hopefully, by now you’ve recognized Inoreader as your go-to place for regular content consumption. But we know there are many more ways to come across great new content – and we want to help you with that, too. Now you can save pages from all over the web with our new feature, Saved web pages …
When you’re casually browsing the internet, there is nothing better than stumbling across a new source of excellent content – but nowadays you’re rushing so much that you might not put in the extra effort and fire up your Inoreader to add a feed to your subscriptions. Inoreader Companion, our dedicated browser extension, will save …
Because of the decentralized nature of the IndieWeb, it’s most likely that more centralized services in the vein of Indie Map or perhaps a Microsub client might build in this sort of recommendation engine functionality. But this doesn’t mean that all is lost! Until more sophisticated tools exist, bootstrapping on smaller individually published sorts of recommendations like follow posts or things like my Following Page (fka blogroll) with OPML support are more likely to be of interest and immediately fill the gap. Several feed readers like Feedly and Inoreader also have recommendation engines built in as well.
Of course going the direction of old school blogs and following those who comment on your own site has historically been a quick way to build a network. I’m also reminded of Colin Walker’s directory which creates a blogroll of sorts by making a list of websites that have webmentioned his own. Webrings are also an interesting possibility for topic-related community building.
Since Tumblr is unlikely to shut down immediately, those effected could easily add their personal websites to their bios to help transition their followerships to feed readers or other methods for following and reading.
Of course the important thing in the near term is to spend a moment downloading and backing up one’s content just in case.
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.
You can see that we are focused lately on the social stuff. Why? Because it was always there in front of you, but there were many obstacles that made it not very usable or friendly. Comment has improved, but one thing with them remained. Many people don’t know that comments in InoReader are actually public …
Reading is fun, but it can be even more rewarding with friends. We have built Inoreader with productivity in mind, but we never wanted to leave out the social element – so there are plenty of ways to share that interesting piece of content you just read with friends on social media or in Inoreader …
You can also read this post in Chinese. Our servers are dealing with millions of feeds like the ones you read every day. We have to have this smart mechanism which balances them and fetches every feed at different interval. This interval is calculated from many factors and is aimed to provide you with the …
You probably spend some time to carefully group subscriptions in folders, star and save interesting articles, tag pieces of interest. If you take pride in your content curation work in Inoreader, you’d probably like to share the results with others – and this is really easy in Inoreader, thanks to custom RSS feeds and HTML …
Upgrade Inoreader for 1 year and get 6 months free.
Considering doing this just to help support the product even though there’s a different direction I’d like to move in shortly.
Feedly and custom sharing
Apparently there were a bunch of us thinking and writing about feed readers and the open web a year ago last June. Several week’s prior to Richard’s article, I’d written a piece for Richard’s now defunct AltPlatform entitled Feed reader revolution (now archived on my site), which laid out some pieces similar to Paul’s take here, though it tied in some more of what was then the state of the art in IndieWeb tech.
Around that time I began tinkering with other feed readers including Inoreader, which I’ve been using for it’s ability to auto-update my RSS feeds using OPML subscriptions from the OPML files I maintain on my own website. Currently I’m more interested in what the Microsub specification is starting to surface in the feed reader space.
I’m not sure if he’s played around with it since, but, like Paul, I was using some of the Press This bookmarklet functionality in conjunction with David Shanske’s Post Kinds plugin for WordPress to make posting snippets of things to my website easier.
Feedly has a Pro (aka paid) functionality to allow one to share content using custom URLs.
While one can use the Share to WordPress URL functionality, I’d recommend the Custom Sharing feature. Using the Post Kinds plugin, one can use the following example URL to quickly share things from their Feedly account to their personal website:
One should change the URL to reflect their own site, and one can also change the word “bookmark” to the appropriate desired kind including “like”, “favorite”, “read”, or any of the others they may have enabled within the Post Kinds plugin.
I personally don’t use this method as it only allows one custom sharing URL (and thus allows only one post kind), and instead (again) prefer Inoreader which allows one to configure custom sharing similarly to Feedly, but doesn’t limit the number of kinds and the feature is available in their free tier as well.
In addition to some of what I’ve written about the Post Kinds plugin before, I’ve also detailed how to dovetail it with sharing from my Android phone quickly in the past.
Highlights and Annotations
Also like Paul, I was greatly interested in quickly creating highlights and annotations on web content and posting them to my own website. Here I’m using a modified version of the Post Kinds plugin to accomplish this having created highlight posts and annotation posts for my site. Next I’m utilizing the ability to prepend
http://via.hypothes.is to URLs on my mobile phone to call up the ability to use my Hypothesis account to easily and quickly create highlights and annotations. I then use some details from the outline linked below to capture that data via RSS using IFTTT.com.
Naturally, the process could be streamlined a lot from a UI perspective, but I think it provides some fairly nice results without a huge amount of work.
I will mention that I’ve seen bugs in trying to annotate easily on Chrome’s mobile application, but haven’t had any issues in using Firefox’s mobile browser.
The state-of-the-art in feed readers was frozen in place sometime around 2010, if not before. By that time most of the format wars between RSS and Atom had long since died down and were all generally supported. The only new features to be added were simple functionalities like sharing out links from readers to social services like Facebook and Twitter. For fancier readers they also added the ability to share out to services like Evernote, OneNote, Pocket, Instapaper and other social silos or silo related services.
So the real question facing companies with stand alone traditional feed reader products–like Feedly, Digg Reader, The Old Reader, Inoreader, Reeder, NewsBlur, Netvibes, Tiny Tiny RSS, WordPress reader–and the cadre of others is:
- What features could/should we add?
- How can we improve?
- How can we gain new users?
- How can we increase our market share?
In short the primary question is:
What should a modern RSS feed reader be capable of doing?