The upshot was that Google Reader was both the standard bearer and pall bearer for RSS at the same time.
Colin Devroe made a good point.
He is subscribed to my main feed and wondered why he didn’t see my Watch follow-up post about the woman on the train.
The answer was that it was a microblog post and, therefore, in the /feed/microblog feed instead.
As you’ll know, if you’ve been reading this for a while, I have taken a different approach and have a directory of people that have interacted with this site via webmentions – both blogs and micro.blog accounts.
When my ‘Likes and Replies’ plugin is done I’m considering building an integrated feed reader that will allow me to read and respond to items all within the same place.
As I wrote before, a self hosted reader tied to your own blog is a logical step; if we want to encourage responses to be owned by their authors at their own properties then it should be as simple as possible to create them.
While listening to the audio from a presentation by Tantek Çelik in 2014 (video on YouTube) I was struck by his contrasting the experiences offered by social networks and blogs/RSS readers.
I added a filter to functions.php to truncate posts in the RSS feed of type ‘status’ that were longer than 280 characters, then insert a permalink at the end, so that they would play nicer with Micro.blog.
I previously detailed a method of automatically replacing blank post titles so that I didn’t have multiple items (posted from the Micro.blog app) listed as ‘(no title)’ in the WordPress back end.
Dave Winer’s post “I want my old blog back” throws up some interesting questions.
He discusses how his blog used to look before succumbing to the lure of Twitter which became the de facto home of short status-like posts for many of us.
I used to be an early adopter, I was among the first to put my name down for anything.
I joined Twitter early before hardly anyone even knew what it was, or what it could be. I signed up for every clone that came after and virtually every other service that appeared.
Way back in 2008 Dave Winer wrote “Microblogging should be decentralized” arguing that reliance on a single, for profit platform such as Twitter was a bad idea.
Admittedly, this was against the backdrop of the fail whale but the idea of a federated service seemed sound – the catch would be that Twitter would have to enable it and build the required tools (or allow developers to build them and we all know how that went!)
Is Facebook being forced to reinvent itself adding, new features to reinvigorate its user base and placate the disaffected youth?
I have made no secret in the past that I am an admirer of Facebook CEO Mark Zuckerberg and his vision for creating a socially connected world.
After the initial anger at the news of Google Reader’s closing came the realisation that this could actually herald a new era for RSS based news consumption.
Feedly have advised they are developing “Project Normandy” a clone of the Reader API and will switch to it automatically and other services such as Digg have announced plans to build their own alternative.
RSS is dead, long live RSS!
The announcement yesterday that Google would be, finally, sunsetting the Google Reader service was met with disappointment, anger and confusion but with a small counterpoint of “it will force innovation”.
I started writing this post over a week ago and in that time the argument has sprung up in many different places with advocates on both sides.
Just before I went on holiday a discussion emerged around what the RSS feed service fav.or.it is or isn’t starting with Louis Gray’s post "Fav.or.it Beta Effort is Not My Favorite. Not Even Close". In this post he argues that fav.or.it is not living up to its initial potential citing a confusing interface, OPML import problems and "limitations" on the service in that you could only import 25 of your RSS feeds in to the system. Louis was also unhappy that any feeds imported were shared will all users of the service.