Live data from Hacker News

RIP Google Reader

ripgooglereader.com

31–40 of 424 posts

Re: RIP Google Reader

#31

A very sad day when this was killed. It was my favorite social/intellectual experience at the time. Really never recovered from it.

The Web hasn't recovered from it, either. In retrospect, they obviously did it to pave way for AMP. Now that AMP is gone, maybe there's a small chance they could bring it back.

AMP doesn't cause any issues for RSS readers. People are still using Inoreader, Feedly, etc just fine today.

> Now that AMP is gone

Why do you say that?

Re: RIP Google Reader

#33
geez, when was this made, recently/now? It's like come on, "dead longer than it was alive"..... there were so many contributing factors to the environment and shifts of the day when it happened -- this endlessly bringing it up shows like so much unawareness of surroundings/history

and also, what other options took its place / fill the void / RSS is not dead! etc

Re: RIP Google Reader

#34

I didn't use Google Reader much, what did it do for you that made it memorable? Or perhaps, what are other Readers failing to deliver?

I had a great time with my friends on it. I've never had that much good discussions with my friends about anything since.

Re: RIP Google Reader

#35
It was in the summer of 2008, three years after Google launched Reader and had at least 5 million users, when I decided to write my own RSS reader. There were just so many features I wanted that I knew Google would never build and for some strange reason I thought I could make money with my own opinionated take on a news reader.

Then at 4pm on March 13th, 2013, I got an email from Nilay at The Verge asking if I'd heard the news. That was a difficult month as I scaled (and wrote about scaling[0]), since by then Google Reader had 10 million active users. After Reader was sunset, about 5 million found their homes on the news readers that remained.

It's strange to think that naively competing with one of the big platforms paid off, but there's plenty of companies that did well in the wake of a giant choosing to ignore the ecosystem near their feet.

[0]: https://blog.newsblur.com/post/45632737156/three-months-to-s...

Re: RIP Google Reader

#36
I find https://feedbin.com/ almost identical (Feedly feels a bit too different for my liking, but is clearly the most popular) but it also feels like times have moved on and I don't find myself using it in the same way. The blogosphere isn't quite what it was back in the late 00s.

Re: RIP Google Reader

#37
post #29

I recently started to consume content via RSS again. It turns out, most of the blogs I care about have a working RSS feed. I'm using newsblur (no affiliation) and it's working quite well, I no longer need to poll the websites, or wait for posts to appear here or on Twitter. The nicest side effect is that checking newsblur before HN/Twitter limited my mindless scrolling, although this comment proves it didn't eliminat…

Newsblur also lets you subscribe to YT channels, which is much nicer experience than YT's own way of handling subscriptions

Re: RIP Google Reader

#39
post #8

I didn't use Google Reader much, what did it do for you that made it memorable? Or perhaps, what are other Readers failing to deliver?

For me, it wasn't so much Google Reader itself, it was a free feed sync source. So I could subscribe to a feed in Google Reader, then use a 3rd party app (like Reeder or any number of others) to view the feeds I was subscribed to, and it would provide all the tracking and syncing so to speak. It fills the gap of services like Feedbin, Feedly, and others. Except it was "free" and now I have to pay $50/yr for Feedbin.…

> So I could subscribe to a feed in Google Reader, then use a 3rd party app (like Reeder or any number of others) to view the feeds I was subscribed to, and it would provide all the tracking and syncing so to speak.

Can you explain what this means? What's involved here? How does it differ from dumping all your RSS feeds into an ordinary RSS reader?

Re: RIP Google Reader

#40

All these years later, I still use the Google Reader frontend (with newsblur as the backend). It turns out that Reader's UI assets were stand alone enough that you could just implement the backend API and it all would work. I saw this originally in a project for viewing your Reader Takeout data[1], and just built on that idea to make my own personal Google Reader experience. [1]: https://github.com/mihaip/readerisdea…

Actually, that project still has the nostalgia Reader interface online: http://readerisdead.com/reader/view/#overview-page
Post reply on HN