Google Reader Redesign

[lefty]

ing man, I use this everyday. What's the alternatives now?

Feedly

Also, if you use mobile devices a lot, there are other options

[leemajors]

ing man, I use this everyday. What's the alternatives now?

Me too. Nothing else keeps everything synced across multiple devices. I can mark an article read on my iphone in reeder, and it's marked read on my desktop in google reader as well as Mr. Reader on my iPad. It's awfully nice of feedly to offer what they are going to, but their servers are already crushed and I have no interest in the graphic heavy feeds that it and other similar clients like flipboard use. I just to scan and see if its worth reading the whole article.

[leemajors]

Feedly

Also, if you use mobile devices a lot, there are other options

And almost all depend on the Reader API.

[lefty]

And almost all depend on the Reader API.

I just checked Drachen's 2nd link

They talk about it

[NASpurs]

Me too. Nothing else keeps everything synced across multiple devices. I can mark an article read on my iphone in reeder, and it's marked read on my desktop in google reader as well as Mr. Reader on my iPad. It's awfully nice of feedly to offer what they are going to, but their servers are already crushed and I have no interest in the graphic heavy feeds that it and other similar clients like flipboard use. I just to scan and see if its worth reading the whole article.

That's an excellent point about how GReader connected devices. Personally I did the same thing. I marked an article "read" on my tablet and it all synched to my PC and phone. No other service that I know of is connected like that with whatever device you throw at it. That sucks.

Some alternatives from Lifehacker: http://lifehacker.com/5990456/google...t-alternatives

And Feedly is going to launch a backend named "Normandy" that is "intended to be a clone of the Google API running on Google's own App Engine, set to swap in on July 1st when the service ends." http://www.engadget.com/2013/03/13/f...fter-google-r/

(Beaten by Drachen )

I guess we'll have to wait and see after July 1st to see what services pop up and what others lead the charge to take over the RSS niche.

[NASpurs]

I went to the feedly website and it gave me a 503 Service Unavailable error. People are hammering the out of that website.

[lefty]

I went to the feedly website and it gave me a 503 Service Unavailable error. People are hammering the out of that website.

Its working now

[lefty]

But loading is a bit slow

[IronMaxipad]

What the man. now how am i suppose to stream all my podcasts?

edit: Feedly seems to do a decent job.

[IronMaxipad]

http://blog.feedly.com/2013/03/14/ti...ing-to-feedly/

[Drachen]

Man everyone is pissed about this. I only follow like 10 people on twitter and my feed still blew up. I can't imagine that they don't just end up reversing course, or spinning this off. Maybe they open source it like wave.

[Drachen]

You know a really good way to show that you are shutting down an extremely popular service that has no business being shut down?

The day after you announce the shut down, there are literally 10s (or more) of companies (of varying sizes) announcing that they are going to be building a clone, or are going to enter into the market which you are vacating.

http://www.theverge.com/2013/3/14/41...-google-reader

[leemajors]

http://www.theverge.com/2013/3/24/41...acy-compliance

Google is taking a lot of heat for its decision to scrap the popular Reader RSS feed aggregator, leading many to question why it would pull the plug on such a popular service. It turns out that the answer might have a lot to do with the hidden costs of safeguarding privacy. According to a report from All Things D, an unnamed source says that the closure is at least partly because of Google’s reluctance to build out the staff and infrastructure needed to deal with legal and privacy issues related to the product.

"UNLESS IT'S GOING TO GET TO 100 MILLION USERS IT'S NOT WORTH DOING."

The source says that Google is trying to position the company so that it stops getting stuck in expensive privacy lawsuits, like the $7 million Wi-Fi data-slurping case in the US, by adding dedicated staff to deal with those issues to each of its teams. When the company announced it would be shuttering Reader, the service reportedly didn’t even have a project manager or full-time engineer assigned to it, and it’s said that Google didn’t want to spend the money to build the service out into a tentpole app. And while many longtime users of the service have questioned why Google doesn’t simply sell Reader off to a third party, its deep integration with other Google Apps means it’s apparently easier for the company to just shutter it. So how many users would have made it worthwhile for Google to keep Reader around? Former Reader product manager Nick Baum tells ATD, "my sense is, if it’s a consumer product at Google that’s not making money, unless it’s going to get to 100 million users it’s not worth doing."