Slashdot Asks: How Will You Replace Google Reader?
Despite a hue and cry from disappointed users, Google has not made any moves to reverse its decision to close down Google Reader on the first of July, just a few weeks away. Despite the name — and the functions it started out with in 2001 — Reader has become more than a simple interface to RSS feeds; Wikipedia gives a concise explanation of how it evolved from just a few features to a full-blown platform of its own, incorporating social-sharing features of the kind that have become expected in many online apps. Those features have morphed over the years along with Google's larger social strategies, along the way upsetting some readers who'd grown used to certain features. If you're a Google Reader user, will you be replacing it with another aggregator?
I'm going to miss igoogle :(
Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.
www.commafeed.com
The NSA already reads all the feeds I subscribe to so I don't have to!
Feedly is OK, but not as good as reader. In particular I miss being able to use it to combine multiple feeds into a bundle - which then has its own RSS feed that can be displayed on web pages. Also an embeddable view for igHome would be good
How Will You Replace Google Reader?
(Disclaimer: I'm going to use the term 'bandwidth' universally instead of the more correct 'latency' or 'throughput' so normal people can hopefully understand this post) The biggest problem I have with every alternative I have tried is that they are built with the most annoying design flaws. They are so painful to me that I am certain these flaws will be look back upon as the geocities of our modern day web development.
When I fire up an alternative, the responsiveness that was in Google Reader just isn't there. And it always seems like the alternatives require you to hit "refresh" on their interface and then what happens? It apparently makes a call out to every single RSS feed to get updates. On the surface this may seem like standard HTTP way of thinking about things. But it makes for a shit user experience. I have thousands of RSS feeds. Thousands. And if I hit refresh in this paradigm, my browser makes 1,000+ HTTP GET requests. It's not a lot of data but if even one of those requests is slow, it's usually blocking on ceding control back to me.
So let's iterate improvements on here that will get us back to Google Reader style responsiveness, shall we? Well, one of the simplest improvements I can see is to do these requests asynchronously with nonblocking web workers. You can attach each of them to the div or construct that each feed is displayed in and only have them work when that feed is visible (for instance if I am collapsing/expanding folders of feeds). You can grey out the feed until the request comes back but if another request returns first, it is parsed and inserted and activated to my vision. That way if cnn.com comes back faster than NASA's Photograph of the Day, I can read while waiting for my images.
But the core problem is that I'm on my home computer on a residential cable modem and, let's face it, Cox sucks. So what I think Google was doing was sacrificing their bandwidth to actually "reverse" the request from client to server. And, in doing so, they could package up all your updates and ship them out in one request (probably compressed). So, this is how I would approach that. Instead of doing a heart beat HTTP GET to check for RSS updates, I'd build a WebSocket and instead of requesting information, the client (browser) would be listening for information. The event/listener paradigm here would save both the user and the RSS host a lot of bandwidth but it would cost the host of the feed reader service some of that bandwidth (although much less). So basically the client JavaScript would load the page just like normal but instead of continually sending HTTP GET requests, a WebSocket would merely inform the server which feeds are active and listen for updates coming in from the server.
On the downside, this greatly complicates the server side. You need to have one be-all end-all "cache" or storage of all incoming feeds that any user is subscribed to. And for each of these feeds, you need to have a list of the users subscribed to it. And now your server will need to maintain the HTTP GET requests to cnn.com and NASA in order to get updates. When it gets an update, there's two ways you could handle it (user queues are complicated so I won't suggest that) but the most basic way is to send it right out to everyone on that subscription list who has an active WebSocket session established with their account. If a new WebSocket session is established, they simply get the last N stories from their subscriptions (Google included pagination backwards binned by time). To alleviate even more bandwidth from you, you could store it on the client side with HTML5 Web Storage and then the first thing the Web Socket does is find the last date on the last stored element and send that across to t
My work here is dung.
An application on my desktop, or "app" on a tablet or smartphone, is all the aggregation I need in order to read the RSS feeds to which I'm subscribed. The only functionality that Google Reader ever provided that I needed was syncing unread/read information across those applications. Of course, under the covers the applications were letting Google do all the heavy lifting, even the RSS feed checking. Going forward, though, all I need is an RSS reader application that's multiplatform with read/unread syncing.
Michael J.
Root, God, what is difference?
In the very worst case, you can stand up your own server, as we have access to the source: https://github.com/samuelclay/NewsBlur
I've been using http://yoleoreader.com/ for the last few days and it works well for me. It even pulled the existing feeds directly from Google since I signed on with Google Account.
I'm really seriously considering going with http://theoldreader.com/ as they're the only ones who are even attempting to make a mobile website. However, their mobile site's layout is quite cumbersome to use and desperately needs fixing.
Everyone else seems overly obsessed with being "app first, screw the rest," where said apps don't run on my phone platform of choice. But if any 3rd party apps I actually can run will support other sites in time, I may give them a shot too.
I'll go for a self-hosted tinytinyRSS: http://tt-rss.org/
Never cared much for all the social features, I like keeping up with websites and being absolutely sure I haven't missed anything.
I'm not sure why I sign into google anymore. No need for reader. Youtube favs I suppose.
I have been very happy with NewsBlur as my Reader replacement. I am now 100% switched over. I use it to read nearly 1500 feeds and performance is great. They have clients for iOS and Android and FeedMe is a decent third party Windows Phone client. For the amount of time I spend each week in feeds, I am happy to pay $20 per year for a premium NewsBlur account.
Newsblur is clean, fast and easy to use.
I've been trying inoreader and have found it to be easy to use and fairly feature-rich.
Some highlights
- Easy import of all your Google reader feeds
- Lacking an android app, but one is planned and there is a mobile version of the site
- Fast
- Free
The switchover was simple - log in with my goolge account and authorize it. The layout is clean, and the app form on my phone is prompt and beautiful. Thanks google for making me switch... Feedly kicks google readers butt. Feedly may not be the beat alternative, but it was the only one I tried after reading a few reviews of the options. I didn't feel the need to look any further.
More Caffeine. NOW
I've completely switched over to NetVibes, but I'm not happy about it. The Netvibes web page is slow to load and has buggy UI on every browser I've tried, especially on mobile platforms. But it does what I want it to do, which is give me my RSS feeds synched on several different devices, and it allows me to permanently save some articles.
TheOldReader probably has better UI -- because it's simpler -- but I don't believe it has the 'save' functionality that I need. Feedly is just god awful for what I need. Bloglines is NetVibes -- literally, it's a front-end for the same service. I don't know of any others that have what I want, but if I find one I'm ready to switch again in a heartbeat.
Genocide Man -- Life is funny. Death is funnier. Mass murder can be hilarious.
This isn't sufficient.
Some of my feeds update several times a day, and yes, it would be OK to just check back regularly.
Other feeds update irregularly, sometimes with weeks or months between updates. I still want to see those updates, and I want to see them reasonably promptly. It's dumb not to automate the checking of those sites, and RSS is the rational way to achieve it.
Really bummed that Google Reader is closing. But if Google is no longer interested in my news reading habits then it's their loss. And I'll no longer be logged-in to Google all day. So it's really their loss. But a huge gain for my privacy.
At work using Windows RSS Owl is looking like my best choice. Akregator for Linux. Not yet sure what I'll use on Mac.
The Old Reader. It's web-based and you can use Google or Facebook login, or a completely separate one if you like. Since the Google Reader shut-down was announced they've made a lot of changes including adding keyboard shortcuts mostly the same as Google Reader.
YMMV of course, but I find it a suitable replacement personally.
I have an instance of OwnCloud setup at home. I use it mostly for syncing contact and calendar data. I'm even subscribed to my girlfriends calendar and vice versa. The WebDav part I only really use as a quick way to get files from one device to another, and by device I mean smartphone, tablets as well as proper computers.
When Google announced the closure of Reader, OwnCloud started work on a news reader app too. I've been running it since the beta and I'm very happy.
Several months before Google's announcement, I was fed up with some details regarding Google Reader (namely, going always through *their* servers according to *their* conditions). Given I am a systems adminstrator and have the ability (and little extra bandwidth) to self-host that service for myself, I installed a rssLounge instance.
I now learn rssLounge has been renamed to selfoss. I have yet to check this new version — but leaving minor glitches aside, rssLounge has me quite happy.
I switched to TinytinyRSS, and since its hosted on my friends server (will probably set up my own once my ESXi host gets more RAM) i dont have to worry about it suddenly dying on my. Migration was easy too since i could just export my list and import it in TTRSS.
When I received the first warning about Reader going away I started looking for alternatives. For me, having it be web-based was most important since I wanted to used it at home and work. The "at work" thing is a problem since I can't just install anything I want on my work PC.
It seems like the RSS reader market is flooded with apps so it was difficult to find web-based services. I had grown used to the Reader look and feel so I settled on NetVibes as being the closest fit.
My main criticism is NetVibes is not as fast as Reader but otherwise the format and whatnot is perfectly usable.
I replaced it ages ago, with a simple python script croned every 15 minutes. It picks up new entries to my feeds, and emails them to me. Sieve filters those emails into a different mailbox, so I've a special mailbox which is basically entries for my rss feeds.
I don't know why I've never made a web interface for that, it might become pretty popular. :P
No, it wasn't open source, sorry!
Someone could create a clone. I'm curious as to why that hasn't happened. Probably no interested developers.
You must have a lot of spare time. I just want to zip through the news looking for anything that interests me. That is when an RSS reader really helps. I don't have time to load up 10 websites 5 times a day, re-reading the same headlines many times over. Going back to that would be like going back to writing with quill and parchment instead of using a keyboard and screen.
I used Google Reader more than any other Google service. Which is why when they announced discontinuation, I decided to roll my own replica.
I follow over 60 sites. If I could manually check each one in 5 seconds, it would take me 5 minutes - not counting the actual reading. With a "freaking 24/7/365 watchbot", that's down to, essentially, zero.
Now, of course, it would be even quicker to go cold turkey and drop all those blogs. I don't want to do that; why should I?
I tried both Feedly and NewsBlur, and both did a lot of things I did not want or need. They were pretty, but when it came down it it I was losing control of my important feeds.
I had to upgrade my ancient Linux server (it was overdue) before I could install it (although I think they might have relaxed some of the requirements now)
I am very happy with it now. It is lean and light, clean and works flawlessly for me.
The android app is written by the developer and rivals that of Google Reader. (clean and simple) Although it is paid... but I don't mind paying for it for all I got.
I can recommend it to everyone who feels a bit of reticence and want and alternative.
Yes, I agree wholeheartedly. Why should we be subjected to articles about stuff you know nothing about?
Indeed, the articles should only relate to areas of your expertise, like realtime midget scat porn, and arithmetic for 'tards.
Looking forward to your daily updates.
cheers,
The Old Reader is almost as good as Google Reader for my use. I just want a simple web browser based list of my article subscriptions.
I tried Feedly, and other "replacements" but they were just too annoying with their stupid swiping and web browser plugins.
In a few days of spare time, I added an RSS Aggregator to my blogging engine. Only tracks a single list of feeds per blog, and only works in Lisplog, which is currently not easy for non-wizards to get bootstrapped, but it serves my purposes.
https://billstclair.com/blog/aggregator/
https://lisplog.org/aggregator/
I never understood this desire to put everything as a web service.
Why is RSS not just an Email mailer that can send news to my Email address?
IMAP is perfect for it, and POP3 is also capable. Plus you have encryption (IMAPS), user management, and you don't need Yet Another App.
There is for example rss2email that can receive RSS feeds and send them as Email. Here is come better documentation: https://wiki.archlinux.org/index.php/Rss2email
http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
unless you like to read a wide variety of things i have in my desktop email/rss reader over 70 feed many of those are from aggregators/webspiders that scower the web looking for more content on a specific subject giving me a feed, rss for people who enjoy reading or need to stay up to date on things is great.
oh and its pretty good for torrents too.
---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
Simply stunning.
Google: "Here, let me do this free awesome thing for you. I'll be taking notes of course, but you know that."
Gweihir: "How LONG are you going to do it for me?!?"
Google: "Uh, probably a few years at least. And you can use someone else's service if you want when we stop, we'll make it really easy to do so. Like, one button push."
Gweihir: "So, not forever?"
Google: "Well, no, but it's not like we're charging you for..."
Gweihir: "EVIL!!! OMG, YOU'RE JUST LOOKING FOR A PROFIT!!! FUCK YOU!!!"
Yeah, you definitely dodged a bullet there.
There is a steep learning curve, but having mail and news in one place is nice. This video gives a preview of how it works.
Still rough in some respects, but entirely usable right now, and there's even an Android app. Hell, the dev behind the current quasi-official Android app (there's also a more-official one planned, and of course there's an open---albeit not yet stable---API) has even made it work on Android 2.1 devices, so my rooted Nook Touch works. Reading RSS on an e-ink screen? As the kids wouldn't say anymore, hells to the yes.
Okay, so I'm using EC2 for the server at the moment, thus relying on a third party again. But since it's ownCloud, I can back up and reimport my entire setup on any webserver I control anywhere, so if Amazon self-destructs or such I'm not left searching for another full solution stack. Never again. Plus, well, I'm a KDE user, and integration in Akregator is coming down the line in theory. So I'll be able to have discrete desktop and mobile apps for a web service that I can put up wherever I have hosting. That's not a solution for everyone per se (although if any of my friends want to use it I'll obviously give them accounts) but it's a pretty perfect replacement for my own needs.
I remember sigs. Oh, a simpler time!
I've tried most of them and, to be honest, they are all pretty rubbish. I don't want any fancy new bells and whistles - but what Google Reader had today (minus the sharing bit) would be just fine.
Unfortunately none of the alternatives I looked at could manage that. From non-working sites, to ghastly user interface design, to one which requires a browser plug-in just to work (seriously wtf?).
On that basis, I'm really hoping that Digg Reader (whenever it arrives) doesn't suck. If it does, then I don't think there are any viable alternatives.
Avantslash - View Slashdot cleanly on your mobile phone.
Not perfect, but it's pretty close and I store everything on my own server.
Feedly has created a clone, at least for the backend, which is all I care about. Their front end is pretty awful, but I'm hoping some good front ends come along or some of the old ones that used GR as a backend switch over.
Ignorance killed the cat. Curiosity was framed.
MetaARPA members of SDF have access to tt-rss, and SDF is worth supporting: http://sdf.org/?join#meta