Technology Archives - Page 21 of 40 - Stay N Alive

I’ve Been a Little Rough on Google Lately

For having posted just less than 1,000 posts, this blog has gotten a lot of attention in just the last one or two years.  It used to be when I posted something I would get few comments (I still wish I had more), little traffic, and I knew it was only going to perhaps a few hundred eyes at most in an RSS Reader somewhere.  But it took off.  I’m not saying this to gloat, and I accept that I’m nowhere near a TechCrunch or a Mashable in terms of readers or traffic, but I’ve quickly learned that some times when I say things here it seems to have a lot of influence. Some times my articles end up on Techmeme.  Some times people like TechCrunch and Mashable mention what I say.  Some times Google employees talk about them.  Not only that, but it goes out to near 25,000 people on Twitter, thousands on FriendFeed, not to mention the thousands of subscribers that read this in their RSS Reader.  I tend to forget that when I talk here, it has the potential for a lot of people to read what I say. It’s not the old days of when I would just strive to get someone to read my stuff.  For that, I apologize – I’ve been a little negative on Google lately without realizing the implications, and I want to make ammends.

The truth is, I like Google for a lot of stuff.  My main e-mail client is Gmail.com.  In fact I also use it as my FriendFeed, Facebook, and Twitter client.  Despite my frustrations, I still use Google Reader as my main RSS Reader, not because it’s Google, but because it’s still by far the best Reader out there.  There have been various Chrome releases that have been by far the fastest and best browser out there.  Google Calendar is my favorite scheduling application – it’s the best of any tool I’ve come across.  I’ve replaced the phone icons on my iPhone with Google’s http://voice.google.com Google Voice client.

Truth be told, I still love Google.  They’re an amazing company.  They’re a company full of amazing talent and smart people.  Perhaps I hold them to a higher standard, and hence my criticism.

I think it’s obvious that I also have a bit of a Facebook bias.  I’ve written many apps both for myself and others on the Facebook platform, wrote two books about it, and I’m very close with many of their team over there.  Most of my business is to help other businesses integrate Facebook technology into their products – with over 400 million users and still growing, a very accessible API, and a lot of rules that go with that API, my help is often needed, and I’m happy to provide.  I’m just as passionate, if not more about Facebook as I am Google, but I think some of that gets to me at times.

I am also passionate about open standards.  I admit Facebook is not open across the board as others like to define it, but neither is Google.  Ideally, I guess I’d like to see a web that is completely free of the big guys like Facebook and Google – sure, they’ll still have a presence, but the user will be in control, not these companies or even developers.  There is no one perfect solution right now.  This is why I talk about Kynetx a lot.  I don’t think any of the open standards available right now completely tackle this, so I get passionate, perhaps too passionate about it at times.

So, to Google, DeWitt, and any of the team there I may have offended, I apologize.  I’d like to make ammends.   Sure, we may disagree at times, but as my Mom always taught me, “If you don’t have anything nice to say, don’t say anything at all”.  I’m going to be much more careful with what I say online from now on, especially when I disagree.  I’d like the things you take from here to be positive.  I want to influence, but in a good way.  To start the mending process, I’m re-creating my Google profile and re-opening my Buzz account, which you can find here.

Let’s open the air here – what else can I improve about this blog and what I share online?  Am I making the right choice in backing down in my criticism?

Image courtesy http://www.youpimped.com/comment_graphics/i_am_sorry

BoomStartup Brings TechStars-like Seed-Capital and Mentoring Program to Utah

I’ve talked often about Utah’s tech scene.  While it doesn’t always get the publicity it deserves, there is an incredible booming tech scene happening here in the Salt Lake City area right now.  Just last Wednesday I attended a Launchup event, where about 100+ entrepreneurs, investors, and bloggers all conjoined in this monthly meeting to hear 3 other startups have their claim to fame.  Kynetx, Simler, and iActionable were all given advice and free help from those 100+ peers hoping for them to succeed.  With a very tight-knit environment, coworking spaces like BetaLoft and CoWork Utah, along with close proximity to the mountains, 15 minutes from great skiing, rock climbing, hiking and other outdoor activities, along with some of the hardest working people I’ve ever been around, it deserves more attention.  Along with all this, BoomStartup, a new Mentoring and Seed-Capital program that hopes to mimic TechStars (out of Boulder, CO) announced it is taking applications for its Orem, Utah (just outside Salt Lake City) location.

BoomStartup brings such mentors as Josh James, former CEO and John Pestana, his co-founder of Omniture, Inc., which just sold to Adobe. Joining them is former Novell Luminary, Ralph Yarro, former Cisco Executive Martin Frey, and former former HP Executive Warren Osborn.  Also participating are Nobu Mutaguchi, one of Utah’s most prolific angel investors and Warren Osborn, an active venture and private equity investor.

John Richards, an early founder of InfoSpace, Inc., and later investor in Omniture and EnticeLabs, founded BoomStartup to “provide current and aspiring tech entrepreneurs an ideal opportunity to get their businesses up and running by presenting each company with seed capital, mentoring and networking from successful entrepreneurs and technologists.”  BoomStartup provides each selected company in the program “with seed capital (up to $15,000), mentoring from successful entrepreneurs and technologists, free office space and resources, and education that takes them through the various steps of getting a tech startup off the ground. Key to the program is the involvement of “investor-mentors” who give of their financial resources and their time as mentors.”

Applicants must meet specific criteria including a founding team of 2 or more, focus on the web, mobile, software, or non-hardware tech, must be scalable, must be able to apply full-time commitment from May to August during the program, work from their Orem, Utah based offices, and have a CTO/master coder with at least 20 percent equity in the company.  They are hosting a series of “Meet the Investor/Mentor” days, the first happening today at 4pm at their offices in the former WordPerfect buildings at Canyon Park Technology Center, Building J (1401 N. Research Way, Orem, Utah).  At the event, applicants can talk and ask questions about the program from the Investors-Mentors.

Living in Utah I’m very excited about this program.  With the wealth of experience here, former Novell Execs, WordPress Execs, and many of the early Web 1.0 startups that formed the history of the software world as it is today, there’s no doubt there will be enough experience to foster some very interesting companies from this program.  I’ve also offered my help if they want it to mentor in the realm of social media, getting blogger attention, etc. so perhaps you’ll see me around as well.

If you’re looking for a cool place to live during the summer, along with some great mentors, and what I know will be a very successful startup mentoring program, I encourage you to apply.  Applicants can apply at http://www.boomstartup.com – and while you’re out here, look me up and show me what you’re working on!

Brazen Careerist Launches Site for Job Seekers That Gen-Y-ers Can Actually Enjoy

screen-shot-2010-03-11-at-3-40-00-am-1732574Generation Y, those that grew up with the web and many of which probably know of no life without it, is prime target for those looking for fresh blood in the Job Marketplace.  It is this generation that is just entering the marketplace, and which Employer after Employer is fighting to gain access to.  These are the founders of Facebook, the latest entries to the Google workforce, and the future of Microsoft.  These are those that will shape the ideas of our future.  Just recently, Brazen Careerist, a site targeted towards Job Seekers, became one of the first to jump at this market by building an entire Social Network targeted towards the Generation Y Job Seeker.

Brazen Careerist hits all the points that Gen Yers love.  Being a much more open audience than their older peers, the site focuses on this fact, bringing attention to a Facebook or Twitter-like stream.  The first question it asks you is, “What are you thinking?”, a question the Gen-Y audience is likely to be more than willing to share with employers.  The entire site integrates well with Facebook Connect, Twitter, LinkedIn, and other networks, enabling users to share across multiple networks, import from their favorite sites, and discuss the ideas their friends are sharing.

In my early 20s, working for startups such as Freeservers.com, and OneGreatFamily.com, I was known as the idea man.  At the time I didn’t have that much experience, but, being the entrepreneur that I am, I always had an idea that I was sharing.  I think you can still see this today on this blog, Twitter, and Facebook.

Brazen Careerist helps to highlight the less-experienced workers’ way of thinking by enabling thoughts, and ideas to be shared and discussed.  For an idea person such as myself, this service is a God-send in empowering the truly innovative minds of our society.  At the same time it is a great tool for employers to discover those bright minds, as, one of the first questions most employers ask in the interview process is “Tell me about yourself”.

Let’s face it.  LinkedIn is for old people.  It has hardly innovated over the years.  While still a great network for the Gen-Xers and more experienced workforce to network, it is just too hard for a new employee entering into the workforce to get the most out of such a site, especially in a group of people so willing to share information about themselves.  The new Brazen Careerist takes the LinkedIn Resume, but adds to it the ability for each potential employee to truly express themselves in a way history just hasn’t manifested yet.  In a much more open workforce it seems suitable a new entrant into the networking marketplace came forward.

If you’re one of these Gen-Yers looking to gain an edge with your peers and potential employers, Brazen Careerist is the perfect tool to accomplish that.  I encourage you to check it out and let me know what you think in the comments.  You can also “fan” me there at http://www.brazencareerist.com/profile/jesse-stay.

Did Google Reinvent the Wheel by Adopting the Protocols They Chose?

In a response to my article here, DeWitt Clinton of Google defined what he deemed the definition of “open” to be.  According to DeWitt, “the first is licensing of the protocols themselves, with respect to who can legally implement them and/or who can legally fork them.”  I argue if this were the case, then why didn’t Google clone and standardize what Facebook is doing, where many, many more developers are already integrating and writing code for?  Facebook itself is part of the Open Web Foundation, and applies the same principles as Google to allowing others to clone the APIs they provide to developers.

DeWitt’s second definition of “open” revolves around, according to DeWitt, “the license by which the data itself is made available. (The Terms and Conditions, so to speak.) The formal definitions are less well established here (thus far!), but it ultimately has to do with who owns the data and what proprietary rights over it are asserted.”  Even Facebook makes clear in its terms that you own your data, and they’re even working to build protocols to enable website owners to host and access this data on their own sites.  Why did Google have to write their own Social Graph API or access lesser-used protocols (such as FOAF or OpenID) when they could, in reality, be standardizing what millions (or more?) of other developers are already utilizing with Facebook Connect and the Facebook APIs to access friend data?  Google could easily duplicate the APIs Facebook has authored (even using the open source libraries Facebook provides for it), and have a full-fledged, “open” social network built from these APIs many developers are already building upon.  I would argue there are/were many more developers writing for Facebook than were developing under the open protocols and standards Google chose to adapt.  I’d like to see some stats if that is not the case.  Granted, even Facebook is giving way to Google to adopt some of these other “open” standards so developers have choice in this matter, even if they were one of the few adopting the other standards.

I still think Google is adopting these standards because it benefits Google, not the user or developer.  If Google wanted to benefit the majority of the audience of developers they would have cloned the already “open” Facebook APIs rather than adopt the much lesser-adopted other protocols they have chosen to go by.  This is a matter of competition, being the “hero”, and a brilliant marketing strategy.  Is Google evil for doing this?  Of course not.  Do I hate Google for this?  Only for the reason that I have to now adapt all the apps I write in Facebook to new “open” APIs Google is choosing to adopt.

IMO, if Google wanted to truly benefit the developer they would have chosen to clone the existing “open” APIs developers were already writing for.  This is a marketing play, plain and simple.  It may have started with geeks not wanting to get into the Facebook worlds, but management agreed because in the end, it benefits Google, not their competitors.  If you don’t think so, you should ask Dave Winer why Google is not implementing RSS or rssCloud instead of Atom and PSHB (I’m completely baffled by that one, too).

Image courtesy http://northerndoctor.com/2009/04/17/re-inventing-the-wheel/

The Web is No Longer Open

“So it can benefit everyone.”

That’s what a Google employee said today as he tried to explain Google’s recent push to have websites use the ‘rel=”me”‘ meta HTML tags to identify pages a user owns on the web.  It’s not a bad strategy – index the entire web, know every single website out there, and when they change, and now the web is your network.  The thing is, since the “open” web hasn’t had a natural way of identifying websites owned by users, Google, the current controller of this network, needed a way to do it.  Why not make people identify their websites to Google’s SocialGraph network, and call it “open” so it benefits everyone?  I’m sorry, but the “open” web that we all grew up in is dead now that 2 or 3 entities have indexed it all.  This is now their network.

Let’s contrast that to Facebook, the “Walled Garden”, criticized for being closed due to tight privacy controls and not willing to open up to the outside web.  Of course, all that is a myth – Facebook too has provided ways for website owners to identify themselves to Facebook on the “open” web, making Facebook itself the controller of that social graph data, thereby giving Facebook a new role in who “owns” the “open” web.  Facebook has even made known in its developer roadmap its intention to build an “OpenGraph API”, making every website owner’s site a Facebook Fan Page in the Facebook network.  Don’t kid yourself that Facebook wants a role in this as well.  They’re a major threat to Google, too because of this.

Then there’s Twitter, just starting to realize how to play in this game, now starting to collect user data for search in their own network.  Don’t count them out just yet, as they too will soon be trying to find ways to get you to identify your website on their network.

So we’ll soon have 3 ways of identifying our websites on the “open” web.  I can identify my site through Facebook, as you see by the Facebook Connect login buttons scattered around.  I can identify myself in the Google SocialGraph APIs, which, if you view the source of this site you’ll see a ‘rel=”me”‘ meta tag identifying my site so Google can search it.  Who knows what Twitter will provide to bring my site into its network.  Each network is providing its easiest ways of identifying your site within their own Social Graph, and calling it “open” so other developers can bring their stuff into their networks easily, without rewriting code.

I think it’s time we stop tricking ourselves into thinking the web is open at all.  Google is in control of the web – they have it all indexed.  Now that we are seeing that he who owns the Social Graph has a new way of controlling and indexing the web, which we are seeing by Facebook’s massive growth (400+ million users!), I think Google feels threatened.  They’ll play every “open” term in the book to gain that control back.  Of course the new meta tags are beneficial – is it really beneficial to “everybody” though?  I argue the one entity it benefits most is Google.  Yeah, it benefits developers if we can get everyone to agree on what “open” is, but that will never happen.  I think it’s time we accept that now that the web is controlled and indexed by only a few large corporations, it is far from “open”.  “Open” is nothing more than a marketing term, and I think we can thank Google for that.  No, that’s not a bad thing – it’s just reality.

Do these technologies really “benefit everyone” when no other search startup has a remote chance of competing with owning the “open web” network?

Further note:

How do we solve this?  I truly believe the only solution to giving the user control of the web again is via client-side, truly user-controlled technologies like what Kynetx offers.  Action Cards, Information Cards, Selectors, and browser-side technologies that bring context back in the user’s hands are the only way we’re going to make the web “open” again.  The future will be the battle for the client – I hope the user wins that battle.

Image courtesy Leo Reynolds

UPDATE: DeWitt Clinton of Google, who wrote the quote above this post is in response to, issued his own response here.  The comments there are interesting, albeit a lot of current and former Google employees trying to defend their case.  I still hold that no matter what Google does now, due to the size of their index, any promotion of the “open web” is still to their benefit.  I don’t think Google should be denying that.

UPDATE 2: My response to DeWitt’s response is here – why didn’t Google just clone Facebook’s APIs if their intention was to benefit the developer and end-user?

Is Google Stealing Authors’ Copyright With Buzz?

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.

Facebook to Developers: "You Decide"

By the time I hit publish on this 5 other bigger blogs will have probably already covered this, but this deserves some praise.  One reason I love the Facebook Platform is because they really seem to care about API developers.  They do things the “right” way.  For instance, they have a beta site where they always release new bug fixes and features before they go live on the site.  They always release new API features in “sandbox mode” before going live with them.  No other platform releases new features and updates in this manner!  Just today they upped their game even more, giving developers full control over this process by letting developers decide when new API features go live.

The service gives developers a new “Migrations” option in their application settings, enabling them to choose when things go live.  The first one of these they launched has to do with a bug they’ve fixed which formats empty JSON strings correctly.  To enable the feature you just go to your “Migrations” section for your app, and select “on”, and now all empty JSON strings will be formatted in the correct manner.  The power of all of this is that you get to decide when these features go live, but you can start trying them immediately!

Of course, all features will eventually go live, but what this shows is that Facebook is willing to keep developers aware of changes before they go live.  Facebook won’t be launching features into the wild out of the blue like many of their competitors do quite regularly.  Previously, changes would go live, and while they would often show on the beta site, developers had little notice and little time to test them before putting them into production.  These changes would break many apps the minute they went into production.

IMO, this small feature changes the game for many other app platforms.  NO OTHER major app platform does anything like this.  Kudos to the Facebook platform team for continuing to change the game in regards to API development.  Since the Facebook platform launched, they have always been ahead in changes like this.  I can only hope other API platforms can follow suite in giving developers more control like this.  No one likes their applications to break because of simple API changes.

Speculation: Expect Something BIG in the Area of Real-Time at F8

I don’t do speculative posts like this too often, except around Facebook’s F8 developer events for the most part.  The last one I predicted was that Facebook would announce a Mobile Platform at F8 – the announcement did occur along with Facebook Connect.  The first F8 was the announcement of the Facebook API, which revolutionized Social Development and has left players like Google scrambling to play catch up since.  Now, 2 years since the last F8, the next F8 has been announced, and we are all wondering what the next big announcement will be.  If it is to be in line with the last 2, and, considering they waited 2 years to have another one, they have to be announcing something game-changing.  I predict it directly involves some of the FriendFeed team and it’s directly related to real-time.

First of all, let me preface this with the fact that I am not receiving this data from any inside contacts at Facebook, nor have I been told anything the rest of the world doesn’t already know.  This is pure speculation – I hope it’s taken as such.  I am also certainly not a psychic.  I think if you look at some of the hints though, you can see the potential for something big, perhaps FriendFeed 3.0-like (remember, FriendFeed 2.0 was the advent of their real-time stream you see now) about to happen at Facebook.  Here are my reasons for thinking such:

What is Paul Buchheit Working on?

Paul Buchheit, one of the founders of FriendFeed, creator of Gmail, and now working at Facebook after FriendFeed was acquired, hasn’t yet made it evident exactly what he’s working on.  We know Bret Taylor, also a founder, is now Director of Product for Facebook, and working heavily with the Facebook APIs and the new Roadmap Facebook has laid out for developers.  We know Kevin Fox, pretty much the man behind all the design of FriendFeed, has been working on the new Games and Apps dashboard that Facebook just launched (that you can see on the left-hand side of Facebook).

But what is Paul Buchheit working on?  He recently commented stating he is definitely not working on Facebook’s new e-mail product that they have been rumored to be working on to replace their current inbox structure.  I’m not sure anyone has specifically stated exactly whether he’s working on the Facebook developer platform now or not.  He seems to be doing something big, and he’s certainly been studying Google Buzz recently if you look over his FriendFeed stream lately.

Float Like a Butterfly, Sting Like a Bee

Then there’s that “Butterfly” post.  Paul Buchheit specifically stated when Robert Scoble, Steve Gillmor, and others were all pressuring Facebook to make a statement on what they were going to do with FriendFeed that “the team is working on a couple of longer-term projects that will help bring FriendFeedy goodness to the larger world.”  He then continued, “Transformation is not the end. Consider this the chrysalis stage — if all goes well, a beautiful butterfly will emerge”.

The mystery in all this is that Facebook has not yet released anything even remotely similar to what Paul described yet.  Paul’s a really smart guy.  He’s not just going to work on something mediocre for Facebook – whatever it is, it has to be game changing.  I really believe that whatever it is will blow our minds away when it happens.  The FriendFeed team doesn’t just innovate.  They revolutionize.  I don’t believe they would still be at Facebook if they didn’t have that opportunity.

Facebook’s Needs

Then there’s the lack of any real-time APIs or architecture at Facebook.  I have to click on the page to have it refresh.  Frankly, I think that fits their current audience of 400 million+ “average Joes” well.  It doesn’t tap into the news-seeking, data-mining, and publishing audiences very well though.  That’s what Twitter does well.  It’s what FriendFeed and Buzz also do well.  All of these come with real-time APIs and real-time searches (or “track”).

Facebook needs a real-time interface for developers still.  It needs search.  It needs search to be real-time.  It needs a public view into all of that, supported by the powerful privacy controls Facebook already has in place.  Facebook has already built out the building blocks to launch this with their recent emphasis on encouraging users to open up their posts more and at the same time enabling them to have granularity in who sees those posts.  The next natural step is to finally open up those public posts to developers, and provide a real-time interface to it all.  With a 400 million user audience, that would be game-changing in the realm of real-time data.  We ain’t seen nothin’ yet!

The Lack of any Really Big Known Announcements at F8

Lastly, we know everything else Facebook could announce at F8.  Facebook has already started rolling out credits to developers, so a payment system wouldn’t be much of a “game changer” per se.  I’m sure they’ll talk a lot about it at the conference though.  Facebook has already started rolling out its Ads API to developers.  They’ve already announced the desire to open up websites as virtual 3rd-party “Pages” on the web.  They’ve let us know just about everything in their roadmap, except the fate of FriendFeed.

Doesn’t this seem strange to you that Facebook and the FriendFeed team have been so mute on this in general for almost a year now?  What’s going on behind the scenes?  Even when asking the FriendFeed team about plans to integrate better into Facebook they have remained mute.  How cool would it be if, while everyone is ranting and raving about Google Buzz and calling FriendFeed dead, the FriendFeed team along with the incredible talent that Facebook adds to the mix have all been working on FriendFeed 3.0 behind the scenes?  What if Facebook caught wind Google was working on Buzz and bought FriendFeed in response to that rumor?  Will the “Butterfly” emerge at F8?  The chrysalis stage takes patience – I’m not giving up on FriendFeed yet.

Google Changes the Way You Read My Feeds – You Still Have no Control

Louis Gray just reported a new way Google is trying to control the problem of mine and Louis’s and Robert Scoble and Mashable, and more of the more active feeds and streams on Google Buzz taking over the streams of our followers.  The problem that was occuring is that for those with a lot of followers, their posts would continue to dominate the streams of those following them because every time someone commented or liked the post, it would go right back to the top of your feed.  While I understand the problem, and agree there needs to be a fix, I argue Google is trying to fix this the wrong way.

The way Google decided to fix it is now they decide, based on some sort of algorithm, how often my feeds get thrown up to the top of your stream.  This ensures no active user will ever fully dominate your stream.  However, what if we want to consume this data?  The problem is Google is the one making that choice for you, not giving you the power to make that choice yourself, and I think that’s a very wrong approach.

Rather than Google making that choice for us, they need to focus on lists, the way FriendFeed and Facebook do it, and the way over 400 million people are familiar with.  This is the natural flow – if someone is too noisy, you take them out of one list and put them in another.  Let us choose which list is the default.  Give us an easy way to assign people we follow into different lists.  This isn’t that difficult a solution for someone Google’s size, and gives the users absolute, full control, rather than taking it away from them to make the decision on how active their feeds are.  This needs to be their 100% focus right now to keep my attention.

The way Google is approaching this is wrong.  I really hope they change their focus to lists, open up the flood wall, but give us filters, privacy controls, and put the control back in the users’ hands.  Don’t take our power away from us Google.

Image courtesy http://arbroath.blogspot.com/2008/03/let-me-out.html

Did Google Reader Just Turn on the Firehose?

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/