Instead they killed their popular Reader and made Orkut and Google Plus.
I never got why people moved to Twitter, it wasn't, and isn't, as good at consuming or sharing content as Reader was. It's just one more step towards the more centralized web we have today, and hopefully we will move back to a more decentralized experience soon.
[0] http://googlereader.blogspot.se/2009/03/google-reader-is-you... [1] http://googlereader.blogspot.se/2011/10/new-in-reader-fresh-...
I think the problem with RSS was - and still is? - is the data it provides. A social network can harvest MUCH more data (due to the endless number of connections between "the nodes.") RSS is too old school.
Put another way, imagine being hired by Google - while FB and Twitter are taking off - and being told you're going to work on a new & improved RSS reader. That would have triggered a mass exit.
I wasn’t a heavy RSS user, but had a few bookmarks in Firefox – and the same thing is doable today.
I would say Google Reader's discontinuation actually increased the popularity of RSS. The protocol was big news for a few weeks, and it sparked a lot of new services which made news themselves.
I don't know whether feeds usage was growing but it was not comparable to social media. At that time papers were increasingly adding paywalls and didn't show any signs of embracing feeds any further.
It seems odd to me to take a federated protocol, centralise it in a proprietary system and then shrug and forget RSS when that goes away.
I was on Akgregator for years, then Bamboo in Firefox, now on QuiteRSS now that Quantum has killed Bamboo. All using the same imported OPML file of feeds.
Which self hosted RSS aggregator contains an easy to deploy, backup, and maintain ecosystem (easier than Dokuwiki), an Android and iPhone app, that all work synchronized together...
It's overly complicated to set up and maintain the infrastructure needed for most people. Time costs a lot.
For example, in the article list view, there's a single basically-identical swipe left/right gesture to...
* mark single article as read
* mark single article as unread
* mark all articles on page as read
* mark all articles on page as unread
The difference between marking a single article and marking all articles seems to be based on how far you've swiped, but if (for example) you don't release your swipe and keep moving your finger further after it's marked all as read, it suddenly does the opposite and marks all articles as unread. The direction of the swipe (left or right) doesn't seem to control whether you're marking read/unread -- it's (in my experience) been completely arbitrary what it decides to do, regardless of swipe direction. It's ridiculous how painful it is, and it's basically been this way for as long as I can remember.The app has really poor bulk management of articles, so I just turn to other apps. Currently I'm using News+, which has superior bulk management capabilities... but it hasn't been updated in forever (and is buggy in other ways).
Google Reader was a social network around RSS
(I also think there was in platform commenting too?)
I never used Google Reader nor Twitter but RSS has seen plenty of use here, from following commits to projects to simply following news sources. I currently use the News reader [1] for Nextcloud, sometimes in combination with one of the Android apps compatible with the former. Works fine, no Google nor Twitter needed, no spurious censorship, no centralised data mining.
It went away when Google killed Reader. Reader had more or less killed off the independent RSS reader market. When it got shuttered, alternatives weren't well developed and people shifted more or less entirely onto Twitter. The Twitter shift had been happening already but the shutdown kind of forced the issue.