As the sun sets on the reader empireAuthor: will | Filed under: cloud computing, google
I’ve been trying out the three main cloud-based rivals: Feedly, Digg Reader and AOL Reader.
Feedly is the number one, and has a working backend
AOL is good, working well but no back end (yet)
Digg should be buried for now
- This is the front end cloud-based reader I’m commenting on, not the app, not the back end.
- Love it. There are a few niggles, and I’m convinced that some of my feeds didn’t make it over but it synced with Google Reader and kept count/synch with it.
- Keep getting caught out on different keyboard shortcuts, but that’s practice.
- Last out of the gate, and surprisingly good. (Or this is an old project they updated)
- As it pulls out the feeds, but not the state from Reader, you end up seeing old posts again, about 50 items from some feeds.
- Polished. Apart from the newsprint look, its pretty close to Google Reader. I’d be happy to keep this as my alternative. I might actually have to start using the rest of the AOL feature set (which is probably why its doing it).
- Same keyboard settings (instinct kicked in when reading through)
- If you are not app-based, this may be the reader alternative for you.
- Downside, slow to update. 24 hours later its finding new / old feeds to expand things out. I think its servers are getting a little hammered.
- As it pulls out the feeds, but not the state from Reader, you end up seeing old posts again, but not quite as excessive as AOL
- The only way to get Digg reader to see that you’ve read a post is to select the section and “mark all as read”. Which ruins part of the reason for a reader. (Note I am using NoScript, but its not showing any blocked scripts)
- Its something that needs a “lot” of improvement, but given that it looks like Digg wants to use it to feed in to their voting systems, things are going to improve.
Something else might change over the weekend, so pay attention if you mourn the loss of Google Reader.