google reader Archives - Stay N Alive

Category: google reader

The Death of Google Reader: Did Email Kill the RSS Star?

Posted on by jessestay
29055-google-reader-dead-300-3211908

Alas, the day has come. We knew it was coming and we were all just digging in our heels waiting for the day. I admit I’m not as mad as before, as the dust has settled off since they killed sharing and replaced it with a very limited Google+ sharing feature (on top of the “send to” feature that was there before). At the same time we see other “social networks” of Google’s (Youtube) hitting over a billion active users. Compared to that, Google Reader was minuscule.

With all that though, there’s no doubt to those of us, the most devoted and perhaps heaviest users of Google Reader (I saw some stats that I promised not to share that suggested before Google Reader killed sharing I had some of the highest numbers of shares on the site), will miss the service. Like, a lot. So much that you see all of us bloggers that depended on its superior interface (which works best in Ninja Mode, btw) screaming from the house tops like little children. Many are even screaming that the death of Google Reader is the death of RSS and the beginning (or end?) of the death of “open”. Truthfully, there is nothing else out there like it and most of us don’t know what we’re going to do.

With all that I can’t help but wonder if the paradigm has just shifted. Users have spoken. While RSS is great for B2B applications of sharing information and likely won’t go away, from a consumer perspective I think email has won this battle. If your site, which previously had a “subscribe via RSS” button on it doesn’t also have a “subscribe by email” button, it probably should. It is evident to me that while many are searching for a new RSS reader that the answer for many trying to guarantee delivery of content will actually be email. In many ways Google Reader is forcing many of us to simplify.

The advantage RSS gave us is that for every site that implemented it it gave more than just a way for Google Reader users to subscribe and get updates one-by-one with their “j” and “k” buttons on their keyboards. It gave every user on the web a way to consumer information any way they wanted. And for that, I’m sad. Google Reader was the last straw, supported by a great brand that made it official.

As much as I hate it, I’m afraid we’re headed towards the death of open ways to consume information. Every website is being forced to create their own APIs for accessing information, and there is now no good reason to use a common standard as simple as RSS to allow consumers to consume information on your site.

There will be a day when we all look back and remember “the roaring 90s/00s” where anyone could consume any data they wanted on the web. The problem is businesses found easier ways to make money and RSS never found a way to fight back.

I hope I’m wrong. I hope RSS makes a come-back. If not, I hope some other standard comes available that makes the web a more open and connected place again. I hope big businesses like Google and Facebook and Microsoft will fight for that and provide solutions to make these things more widely available. Thus far they have let me down though.

With the death of Google Reader, a little piece of me dies. But with it, another open standard, email, replaces its stead. My hope is that even while RSS is not as important as it used to be, we continue to see businesses and organizations and websites and mobile apps provide means to allow consumers to consume information, at a minimum, through the open standard of email.

Until then, I’m going down with the ship. I’m not giving up, and we’ll find a solution that fixes this big mess we’re in right now.

With the New Design, Twitter Kills RSS, Literally

Posted on by jessestay

The blogosphere is abuzz lately about the latest trend: “RSS is Dead,” everyone says.  Other blogs say “RSS isn’t dead.” (of which side I tend to agree with).  The debate lies with the fact that more and more people are starting to use Twitter, Twitter lists, Facebook, and other social means to just get the news from the streams they follow on these sites rather than typical RSS Readers like Google Reader.  For instance, even on my own Google Reader shares, you can get them right on my @jesseslinks Twitter stream if you don’t ever want to touch Google Reader (yet I’m still using Google Reader to provide those to you).  Whatever side you agree with, I just discovered one thing we’ll all be able to agree with: at least on its own site in the new design, Twitter has quite literally killed RSS.  Into thin air it’s gone in the new UI.

I talked previously about Twitter increasingly becoming less and less open and more and more a walled garden.  Facebook itself just added RSS to its feeds for Facebook Pages and opened its database so you can reformat their content, so long as users approve, in any way you like.  It appears, as no surprise, Twitter is moving in the opposite direction.  In the new design I can’t find an RSS feed anywhere.  Previously there was a link to the lower-right allowing you to add an RSS feed.  They also had a link to the RSS in the source of the HTML so your browser would automatically recognize the feed, and just entering the URL for the user profile into Google Reader, they could automatically detect the feed for you.

Currently the only way to find an RSS feed is to log out and visit the profile of the user when you’re not logged into Twitter.  This might also be why Google Reader still recognizes feeds when you enter user profile URLs in the “Add Subscription” box.  Firefox doesn’t recognize the feed when I’m logged in – it does when I’m not.  It does make you wonder how long the RSS feed will be in the unauthenticated version.

It’s hard to tell if this is intentional or not, but we do know Twitter wants to be a source for news.  Perhaps they think this is in their best interest – the harder they make it for you to read your news elsewhere, the more likely you are to come to Twitter.com to read your news from your friends.  One thing is for sure however – the new Twitter design is certainly less open than it was before.  Twitter, especially with the new design, is now a walled garden.

I’ve contacted Twitter about this and will update here with any response.

UPDATE: For some reason Twitter’s PR never responded.  However, even better, Isaac Hepworth, a developer from Twitter, responded on Buzz, inferring some of it was a mistake, while some of it was intentional to make things simpler:

“Hey Ade, thanks for the cc and sorry for the delay jumping in. I’ve been talking to people internally to work out what happened here so that I could untangle it properly.

Here’s the scoop: the RSS itself is still there (as Jesse’s roundabout method for finding it shows). Two things were removed in #NewTwitter:
1. The hyperlink to the RSS on the profile page; and
2. The link to the RSS in the profile page metadata (ie. the element in the ).

(2) was wholly accidental, and we’ll fix that. In the meantime, Jesse’s way of finding the RSS is as good as any, and you can still subscribe to user timelines in products like Google Reader by just adding a subscription to the profile URL, eg. http://twitter.com/isaach.

(1) on the other hand was deliberate, in line with the “keep Twitter simple” principle which we used to approach the product as a whole. Identifying RSS for a page and exposing it to users per their preferences is a job which most browsers now do well on their own based on s.

Hope that helps!”

Loud Noises Be Gone! Mute Posts by Source in Google Buzz

Posted on by jessestay

I’ve long said that in good social networks, it’s not how you give, but how you receive that makes the social network powerful.  This is why I like Facebook – I can hide the types of applications I don’t ever want to see, or I can just hide individuals.  I liked FriendFeed even better because they took it a step even further by allowing me to not just hide by source or application or just the user, but they allowed me to hide specific applications for only specific users.  So, for instance, if I wanted to hide all the Twitter posts from Robert Scoble I could click a button, “hide entries like these”, configure it correctly, and now I would never see a Twitter post from Robert Scoble again, even though I might still see Twitter posts from others.  Google just entered the scale of FriendFeed with the same level of granularity in what you want to receive.

In a post on Buzz, Rick Klau, the person over Google Profiles, formerly over Blogger, and originally one of the founders of Feedburner, posted, “Some of us would rather keep up with our friend’s Google Reader shared items in Google Reader or our co-worker’s Twitter posts in Twitter. So, by popular request, you can now mute Google Buzz posts by source for each person you follow.”  So, in typical Google fashion, Google is using the “mute” functionality from Gmail and other areas to allow you to hide specific applications from specific individuals you don’t want to see.

According to Klau, to turn on the functionality:

“You can do this from two places:
1) Click the arrow in the corner of any post
2) Click a person’s name from the Buzz tab

If you ever want to unmute a source, just click the person’s name from the Buzz tab again and “unmute.”

So if you’re on Buzz or you want to try Buzz, you can safely turn on your Twitter feed or whatever feed you chose, and now it’s up to those receiving your feed on how noisy they want to be.  Now MG Siegler doesn’t have to complain about how noisy my Twitter stream is any more. 😉

UPDATE: The post by Rick Klau was actually a re-share of a post by the Google Buzz Team here: http://www.google.com/buzz/googlebuzz/eaCpwkgqPiu/Mute-posts-by-source-Some-of-us-would-rather-keep

Google Reader is Behind the Times – Here is What They Can Do to Fix That

Posted on by jessestay

nashua-big-fix-duct-tape-patch-6459481As anyone who knows me can attest, I’m a huge Google Reader user and fan.  Despite users like Robert Scoble and others declaring RSS Readers dead, I still find utility from being able to finely adapt my reading experience by selecting what I want to subscribe to on the web.  As a blogger, it’s one of my greatest weapons – in fact, sites don’t even have to have an RSS feed for me to track their changes.  For instance, let’s say I want to track job announcements at a certain website to know when new features are coming based on the new jobs they’re hiring for. All I have to do is enter the jobs page into Google Reader and it will automatically tell me when it notices new changes on that Page. No coding necessary.

However, while I disagree that RSS is dead, I am worried that News Readers like Google Reader have neglected to stay up with modern news gathering trends.  Perhaps they think remaining simple will win, but frankly, using just RSS and friends suggestions from RSS to find the news just doesn’t cut it any more.  This is why you see Readers like FlipBoard and FLUD and Pulse making a big inroads on devices like the iPad.  They’re ignoring Google Reader and going straight to social networks like Twitter and Facebook, where the news is likely to come from your close friends and family.  I’m concerned Google Reader is taking so long to adapt towards this trend – here are some tips that I think would make it a much better, and more modern service:

Embrace the Dark Side

With the exception of Youtube, Google seems to have a real issue with this.  They seem afraid to embrace their competitors, the sites that currently have the edge, and the sites that their users are most likely using.  Let’s face it – currently the majority of web users are getting their news from their friends on sites like Facebook and Twitter.  They’re not going from site to site, plugging in an RSS feed to Google Reader, and reading it that way.  I’ve tried to show both my wife and my 10 year old daughter how to do this and they just don’t get it.  Even more experienced users who used to be power users of Google Reader like Robert Scoble are moving in this direction.

There’s a minefield of explosive links out there in public on Twitter and Facebook.  Slap a social graph on top of that and you now have extremely relevant links you could be harvesting, indexing, and extracting content for your users to read in full inside Google Reader.  Google has an opportunity here to pull these users over to their interface and make it even easier for them to read the content their friends on Facebook, Twitter, and other sites are sharing.  While RSS is certainly not dead, the Social Graph most definitely reigns supreme – embrace it.  Use Facebook Graph API.  Use Twitter’s API.  Otherwise Google is going to get left in the dust by competitors that do.  Users want this.

The Desktop is Not the Future

While Google Reader has built an amazing desktop and web experience, it’s time they move forward.  We have gone beyond the typical, dynamic desktop browser being the interface to the web and have moved towards an app era that leverages the web to build custom experiences tailored for static screen sizes on various platforms.  There’s the iPhone.  There’s the iPad.  There are various flavors of Android and Windows for Mobile Phones.  Every other web developer building a company right now is building for these platforms.  Google seems to be stuck in the web browser, something I argue is a mistake.

True, Google has a custom web experience for the iPad and iPhone, but quite frankly – that experience stinks.  Look at the Reeder app for iPad and iPhone to contrast.  It has a “move to the next unread item” button, for instance, that lets you easily surf through your unread news and skim it as you please.  It has a simple interface for sharing, leaving notes, and even allows you to share to other social networks if you choose.  They’ve built an amazing interface that focuses on mobile and tablets that wraps around the stale Google Reader web interface.

Now look at the non-RSS centric experiences like FlipBoard.  Swipe your fingers and it flips pages similar to a magazine or book.  The experience is magically formatted in a natural way that makes reading the news easy!  Mobile devices were built for reading the news.  They are the magazines and newspapers of the future.  Google Reader should be the ones in control on this front or they’re going to get out-taken by their competitors.

Share! Share! Share!

Google Reader does a little of this.  You can share to Twitter and Facebook and other sources, but quite honestly, the experience is lacking.  This should be at the forefront of their experience – easy to see and obvious to the reader that this is what they want them to do.  Right now to share to Facebook, for instance, I have to click on the “send to” link (or press shift-t), and for any site I want to share to Google makes me leave the site and go to each individual site to share.  This experience should be much more integrated into the UI, controlled by keyboard gestures, without having to leave the site.  Facebook Graph API and Social Plugins should be used.  Twitter’s API or @anywhere should be used.  The links should be in more prominent positions, easy for the reader to see.  The “Send To” should be consolidated with the “share” link and terminology should all be centered around “sharing”.

The entire experience should be much more social.

Streamline the UI

Google Reader used to be top of the line when it came to great user experiences.  They enabled keyboard shortcuts and a very simple UI that was easy to manage.  Since then, they have added all sorts of bloat to the interface, slowing it down and making it harder to manage.  To hide someone or add them to another group, for instance, it takes at least a minute for me to do anything surrounding that.  Refreshing the page takes too long.

Google needs to start fresh and build the UI from the ground up, with these new focuses in mind, and focus on speed, simplicity, and cleanliness.  The entire UI needs to be re-done and targeted towards the new features I’ve suggested here.  It needs to be faster.  No site should take longer than 4 seconds to load.  It needs to have entirely different versions for mobile devices, and most of all it needs to be easier to use.

Be Sure Not to Neglect Your Strengths

In all this I am not suggesting Google Reader become FlipBoard.  Google Reader needs to stick to its strengths – it needs to continue a strong focus on RSS, while bringing in all the other elements I mentioned.  It needs to remain top in its game of strong UIs and easy to organize content reading.  It needs to keep the focus on leaving notes and sharing with other Google Reader users.

I’m afraid Google has stopped innovating in this space.  We’re seeing so with evidence of other strong readers emerging in the areas I have mentioned.  Google has such strong potential to own this space if they chose.  I really hope they take this advice constructively and try to adapt these things.  If not, users, including myself, are going to be forced to bigger and better ways of consuming our news in a way that is more modern and convenient to the user.

In the meantime, you can follow all my Google Reader shares on my link blog at http://www.google.com/reader/shared/jessestay.

Getting Me to Share Your Posts

Posted on by jessestay

One of the things I like to do on my Twitter account is to share interesting articles around the web that I think would be interesting to my readers.  Such articles can be techy, geeky, mainstream, pop-culture, or anything I deem interesting.  Based on your retweets, I think you like it.  I had someone ask me the other day why I wasn’t sharing more of their posts.  It’s actually quite easy – I’d like to share how, and I’m pretty sure you can use this same technique on any other blogger that uses Google Reader.

I have a policy on Google Buzz – it’s the same policy I have on Twitter.  I follow everyone on Buzz who follows me.  The thing is that I think it’s even more powerful on Buzz because, just like Twitter, it gives me an opportunity to discover interesting people I may not have known about before.  For the spam, I have SocialToo for that.  However, with Buzz, for everyone I follow, I also see their Google Reader shares.  That means for every one of you that follows me on Buzz, if your content is interesting, I am very likely to discover your content that you share (that can even be your own blog posts!), and if I like it, that content goes straight to Twitter and Buzz.

So the secret is just to follow me on Buzz!  Yes, I hide many people in my Google Reader, so it’s important you share unique, and interesting posts.  Also, if I know you I’m also more likely to not hide your shares, so get involved in the conversation.  Comment on my shares, retweet my posts, reply to me, comment on my blog.  I read every single comment and try to respond where it makes sense.  As we have more discussions I get to know you better and I’m less likely to hide your content.

I hope that helps.  I don’t think the individual who asked me to share his content more is following me in Buzz.  I’m pretty sure I wouldn’t hide his content because I know him and I like his content.  The secret is to follow on Buzz, join the conversation, and I’ll very likely share your interesting shares on Twitter.  I think the same goes with anyone that uses Google Reader.  There’s a great opportunity here – I hope you use it.

You can follow me on Buzz over on my Google Profile.  Can’t wait to start seeing your shares!

Photo courtesy Creative Commons on Flickr.

Is Google Stealing Authors’ Copyright With Buzz?

Posted on by jessestay

2 years ago I shared about a blogger and follower/friend of mine, Ali Akbar, who purchased the domain, googleappsengine.com (he still owns it) in order to create an AppEngine-related blog (since Google apparently forgot to purchase the domain).  Ali received a threatening Cease-and-Desist from Google shortly after asking him to immediately discontinue use of the domain and “Take immediate steps to transfer the Domain Name to Google”.  It would appear that Google needs to take a dose of its own medicine though.  To my surprise, I’ve realized recently that my articles from StayNAlive.com and other blogs are being shared, in their full text, on Buzz and having my ads stripped from them, without my permission.

For those unaware, there’s a “subscribe” button when you visit this blog that allows anyone to obtain the RSS of this blog and plug it into a Reader.  For those of you reading this in a Reader, thank you, and you’re already aware of this.  One thing I have done with those feeds if you haven’t noticed is at the bottom of each post in the RSS, I’ve added Google Adsense to my feeds so I can at least cover my costs of running this blog and make at least a few cents a day trying to re-coup costs of hosting and time spent writing posts.  If you visit http://staynalive.local/feed in a browser like Chrome, you can look at the raw feed and see the ads at the bottom of each post.  Or, if you’re reading this post in a traditional feed reader, look down at the bottom of this post and you’ll see the ad.

However, there’s a feature on Buzz that enables anyone reading my shared posts to expand the summarized content and view the entire post, right in Buzz.  For one, I didn’t give Buzz permission to do this on shared posts, and second, Buzz is stripping out my ads, depriving me of that potential revenue rather than either displaying those ads, or redirecting the user back to my site where I can monetize that in some other form.  This is blatant copyright infringement if you ask me!  Now, if you expand my posts, since it’s integrated into Gmail, look over to the right – see those ads?  Yup, I’m not getting a penny of that.

Google is now monetizing my content, and neglecting to ask for my permission in doing so, while removing what I had put in place to monetize my content.  Starting today, I’m removing my blog from my Google Profile, as well as my Google Reader shares so that I don’t help further the copyright infringement on other blogs I share.  The problem that still exists is that anyone who shares my content from Google Reader will also have my content available on Buzz in full format, and my ads stripped.  There’s no way to stop it, and Google is encouraging this wrong practice.

To be clear, I’m fine with them either displaying the ads that I put there (and allowing me to monetize off the other ads that are on the page), or just summarizing the article and encouraging users to click through to my site.  I’m not okay with Google scraping my content, stripping my ads, altering my content, and pushing it out for them to get 100% of the revenues off of something I spent time and money making.

Google, how is this not evil?  Maybe I should use Google’s own Cease and Desist letter to get them to stop this practice.  Or would that itself be copyright infringement?

Image courtesy Warner Bros. Entertainment – “The Ant Bully”

UPDATE: The Google Buzz Team did contact me on Buzz (Ironically, considering the content of this post), and they say they’re going to have the ad scraping issue fixed by next week.

Did Google Reader Just Turn on the Firehose?

Posted on by jessestay

Google’s big push recently has been on enabling open, real-time technologies to publish, read, and interact with its new service Buzz.  Reader, its RSS subscription and website reading service, is one of the biggest tools to integrate with the service.  So much that my Reader contacts are now my Buzz contacts.  Until now, Google Reader, while when it would share your posts, it would send updates to subscribing services via Pubsub Hubbub (PSHB), it did not support the reading end of it for supported blogs that publish via PSHB.

Just after my last post on Google ironically, I noticed immediately after publishing people were sharing my post, something very unusual for the service, which usually takes up to an hour for my posts to show up on the site.  Going into Reader, I noticed it had immediately recognized my post.  I quickly queried a friend of mine at Google, who stated, “They can neither confirm nor deny my suspicion” (that it was launched), but I was “observant”.  Sounds like they just launched Pubsub Hubbub support.

WordPress-enabled Blogs that want to be seen immediately after publishing in Google Reader just need to install Josh Fraser’s Pubsub Hubbub plugin for WordPress.  After hitting publish, your post should appear immediately afterwards in PSHB-supported clients, which, if I am correct, now includes Google Reader’s massive user base.

If this is true, you should see this post immediately after I hit publish in Google Reader.  Assuming I’m right (which it seems so), Robert Scoble’s concern of it taking too long to get news (#5) just went out the door today – he can now get this just as fast, if not faster than any service such as Twitter, FriendFeed, or Buzz, and this way, he gets to read the full content of the article.  When I hit publish on this post you will see it immediately.  You are subscribed to my feeds, right?

UPDATE: Just after hitting publish it appeared immediately in Google Reader on this post as well.  I’m 99.9% sure now that PSHB was launched on Google Reader today.

Image courtesy http://www.scotduke.com/getting-a-drink-out-of-a-fire-hose/

Google Has Large Company Syndrome

Posted on by jessestay

google-5647674I’ve worked for various companies over my career.  Some of those very small (including my current startup), and some very large, international and public corporations.  I currently work with similar clients of various sizes and types.  Each and every one of them shared characteristics that come with the turf in managing a large or a small company.  In a small company, you’re dealing with issues like how to grow, how do you start to deal with a growing employee base, and how do you handle all the workload in front of you on such a limited budget.  Yet you have much more flexibility to get things done and build for the whole of the company.  With large corporations you’re dealing with politics, and budgets, and individual departments all fighting for control.  It’s common amongst every single organization I have come in contact with, and I believe that is starting to include Google, which we’re seeing evident in many of their new Social products.

Let me preface with the fact that I love the concept of Buzz.  As an avid FriendFeed user and Social Media addict, Buzz hits many points that are just sweet in my eyes.  I love that they’re embracing open technologies to build it, and working hard to empower individuals and even (soon) developers to have control over their own experiences on the platform.  With the size of Google, this will bring much more attention to these types of technologies, so what they are doing is a good thing.  I don’t think they needed to reinvent the wheel to do it though, and I think the reason they did it may be in part due to the size and politics of the company.

Enter Google Reader.  I’ve complained many times that I don’t think Reader needed to focus on Social.  I don’t think it needed to re-build your Social Graph all over again.  Now, with Buzz in the mix they are trying to cross-integrate the two, and I think it’s really the wrong approach.

What I think is happening is departments at Google aren’t working close enough together to make things work properly.  For instance, Orkut already has the strength of building social connections.  Its strength is in building Social Graphs and empowering users to share with their close friends and family.  They already have the tools to do it, and, in some countries this has proved to be quite successful.  I think the Orkut team knows that.

In the case of Reader, what I think is happening is in the product development cycle they realized they needed social features.  The Orkut team wasn’t available, or one of the two teams didn’t have the budget to cross-integrate, or perhaps politics got in the way, so Reader reinvented the wheel to do Social in the Reader environment.  They could have rather done something similar to Facebook Connect, and enabled users to connect to their Orkut Social Graph and brought in shares via that means.  Then Orkut continues to own the Social Graph, social interactions continue to happen through Orkut, and people can continue to build connections with Orkut as the main hub for Social interactivity.  My guess is that the Orkut team was too booked to create such a tool just for the Reader team.  Someone up the line said no to it, so the Reader team built their own tools to accomplish the task.

I think we’re seeing the same with Buzz, and many more tools like Friend Connect and OpenSocial and others at Google.  Sergey most likely assigned a team at Google with the task of building a FriendFeed or Twitter-like product that enabled people to communicate better.  Orkut does not yet have such functionality, and it made sense to do it as a separate product.  They decided to integrate it into Gmail, where your contacts are.  Rather than utilize the strengths of Orkut for organizing these contacts, it was probably easier due to the size of Google to utilize Gmail’s contact manager to do so, which Google Reader just so happens to also use.  The cross-integration with Reader just happened naturally, but thanks to the lack of expertise in Social Graph management, it was done poorly, now making it extremely hard for Google Reader users to manage their stream.

In large companies it’s very hard to cross-integrate.  I think had Google from the get-go started to find ways to build a Facebook Connect-like interface for Orkut, they could have very well created more activity in Orkut itself, while cross-integrating all their other products into the Social Graphs built on Orkut.  Now Google is stuck with an unorganized mush of multiple social graphs, multiple streams, and messaging and content going all over the place within those streams with little regard to privacy.

It may be too late, but if I were Google, I would look at taking a step back, focusing on Orkut, and building out from there before continuing further on any Social Graph-based products.  These social products Google is building should all be relying on Orkut for that social data and then they would have a true Social Network to build from.  They shouldn’t be reinventing the Social Graph every time they build a new service.  This is why Facebook has had such success in the social space – they’ve focused on the one product as the source for all their Social releases.  Google really needs to do the same, and they can still do it with open standards, but this time starting from the Orkut environment and building out.

Is Google Reader Still an RSS Reader?

Posted on by jessestay

2426084610-reader-logo-en-6607753I’ve been following the Buzz about Buzz today (click on the link – get it?), and, wanting to try it (since I’m not of the privileged few bloggers given access at launch), I started browsing on my iPhone where I heard it was available.  Immediately I was presented with a list of people following me that I was not following back, so I went in and clicked follow on about 300 or so people that it said I was not following yet.  Big Mistake.

Later in the day I went to check Google Reader, which until today was my RSS Reader of choice, and lo and behold I had over 400 items from just the last hour sitting in my unread items box.  It turns out when you follow someone on Buzz, it also follows them on Reader, and who knows what else on the various Google properties.  Now, the only way to bring my volume of repeat RSS shares from friends down on Google Reader is to go into each and every one, mark hide, and manually move each into their own separate folders.  All this on an already slow Google Reader interface.  I’m not looking forward to that.

I have been critical ever since the Reader team introduced social features into Google Reader.  Now, rather than being a place where I can just go to ensure I’m getting the latest news from the blogs I want to subscribe to, as a traditional RSS Reader should be, I’m now stuck in a world with hundreds to thousands of shared items from friends, many of those repeat items, getting fed to me over and over again, even when I don’t want them!  Add to that all the likes, comments, ability to post “status updates”, and more, it occurred to me today that Google Reader is no longer an RSS Reader – it is now a Social Network!

I wish Google Reader would just stick to what it’s good at – being an RSS Reader.  I now need a place I can go just to get the news I want and don’t want to miss.  Some say those days are gone, but it’s still a need for me.  Today with the introduction of Buzz, Google Reader became useless to me.  If I want to skim the news I can go to Buzz and get all the features of a social network.  I don’t need Google Reader to do that for me.  But when I just want to read the news I want, Google Reader has lost its use for me.  Maybe some of this is the reason Google Reader’s former team lead just switched to the Youtube team?

I’m first to admit RSS is far from dead, though I think it’s time to find another RSS Reader.  Should I just switch to Mail.app?  Where can one go to get the news these days?