pubsub hubbub Archives - Stay N Alive

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/

LazyFeed Becomes First Real-Time Web Aggregator for rssCloud

Lazyfeed LogoToday Lazyfeed announced they had officially launched rssCloud and Pub/sub Hubbub (PSHB) support into their real-time RSS aggregator, making them the first major aggregator for rssCloud outside of Dave Winer’s own River2 client, and the first client of its type for the Web (Dave Winer’s client is written for the desktop OS).  What does this mean? It means now you have a way to get the most relevant information you are looking for real-time, as it happens.

Lazyfeed is a new aggregation service that aims to provide real-time news updates on specific topics you want to know about.  You give it the keywords you’re interested in, and it comes back, as the news happens, with the news written about those keywords.  It goes further though and provides additional suggestions for other keywords you might be interested in as they happen, and you can add those to your list as well.  See Louis Gray’s demo here for a great view of how it works.

Now, with rssCloud and PSHB support for real-time news aggregation, they are now one of the most real-time aggregators on the web.  On their blog they mentioned some of the hurdles they had to jump to get through the implementation, and ironically, Feedburner seemed to have the biggest issues with set up (through PSHB) since the Atom protocol wasn’t built natively with any sort of real-time support. No problems were mentioned about rssCloud, showing promise for the protocol developed by Dave Winer. Lazyfeed seemed to think Feedburner wasn’t even real time, based on their experience, showing a delay of a few minutes on each feed published.

Problems aside, seeing aggregators like Lazyfeed implement these technologies is promising, showing we are on the cusp of the 2010 web and real-time news and updates being at our fingertips.  I’ve talked to several other companies also getting ready to embrace these technologies and I’m pretty sure by the end of 2010 it will be an entirely new web and opportunity for entrepreneurs and developers alike.

UPDATE: Brett Slakin, one of the originators of the PSHB protocol, has clarified some of the PSHB and Feedburner issues here: http://blog.lazyfeed.com/2009/09/lazyfeed-rsscloud-pubsubhubbub-real.html#comment-16898143

Dave Winer to Bring Realtime RSS to Millions via WordPress.com?

realtimeToday in a very inconspicuous post by Dave Winer, he demonstrated that his new real-time RSS protocol, rssCloud, could very soon be available to the millions of blogs, real-time on WordPress.com.  Dave Winer, who played perhaps the most significant role in defining the RSS standard and the subsequent RSS 2.0 standard through which most blogs are read today, is taking the long-known extension to the RSS protocol to the masses with some sort of relationship he has built with Automattic, the owners of WordPress.com.

rssCloud vs. PubSub Hubbub

rssCloud was defined in its early form in 2001 as a solution to provide a “next step” for RSS to get instantaneous updates from blogs or websites wishing to push information immediately to readers.  The readers weren’t quite ready for the standard at the time (see the Guitar Scene in Back to the Future), so it sat stale until this year when real-time updates again came to front and center for getting and retrieving massive amounts of information as they happen through sites like Twitter.  Dave Winer says he adapted it in order to provide a better, more open microblogging solution that works outside and independent of Twitter.

Here’s how Winer explains it works:

1. The Writer gets an idea.

2. He or she enters it into the authoring tool, saves, it goes to a file, a feed.

3. The authoring software sends an Update ping to the Cloud (which is just a bit of software running on EC2).

4. The Cloud checks to see if anyone is subscribing to the Writer, and finds that indeed the Aggregator is.

5. He updated! says the Cloud to the Aggregator.

6. The aggregator then reads the feed, finds the new stuff and informs the Reader.

After less than a second the Aggregator has the update and the user is reading the content, real-time.

Pubsub Hubbub works similar.  With this protocol, you have a “hub”, rather than the cloud, and the content provider pings the “hub” for every new post.  The reader can then request to be notified by the hub (or hubs) if there is any new data.  Google has taken the initiative on this particular protocol and is utilizing FeedBurner as their initial hub.  The protocol is also designed for mostly blogs, rather than microblogs, which seems to be the space which Winer is targeting with rssCloud.

What’s the difference?  Quite honestly I’m trying to figure that out myself.  It would seem that the major differences are that a) with rssCloud, feeds expire after 24 hours, so aggregators need to make at least one call a day to notify the Cloud that they want to be notified.  This has the advantage in that the Cloud doesn’t have to continue pinging even when aggregators aren’t there, but also increases the number of calls an aggregator must make.

The other difference is that Dave Winer is an individual developer while Google is a big company.  If you ask me that doesn’t matter much due to the fact that these are both open protocols and both seek to decentralize the control of our data.  Google’s response is disconcerting though where they seem to try and discredit Winer’s protocol.  The more of these protocols the better (also see the OpenMicroblogging protocol).  However, it is very appealing to see an individual developer, the inventor of RSS, so-to-say, take a protocol that has been around much longer and adapt it to work with modern standards.  I want to see Dave succeed, but I hope they all work together.  This is a space everyone benefits, despite the competition.  Keep in mind that Dave isn’t the only guy behind this protocol either – there is an entire governing board that manages this standard.
Competition for Twitter?

So with this potential development, what does this mean for WordPress?  First, millions of blogs will now instantly be real-time in the same way Twitter is real-time.  Second, where Dave Winer wants rssCloud to be targeted towards the micro blogging space this could very well mean WordPress could be looking at something in that area to compete with Twitter.   I predicted this at the beginning of this year, remember?

Here’s what I see happening: Automattic will utilize its BuddyPress and P2 platforms to create a decentralized microblogging platform that utilizes rssCloud to provide real-time updates.  Wordpress.com will be extended to enable “mini-blogs” which accompany your existing blog and provide real time status updates anyone can subscribe to.  Clients like Seesmic, TweetDeck, and PeopleBrowsr will utilize the rssCloud protocol as Aggregators and allow you to view all this data in one place in ways you could never do before.

Dave Winer’s demonstration today is HUGE news for the blogging world and decentralized micro-blogging.  I can’t wait to see what happens.

UPDATE: You can download the WordPress plugin for rssCloud here.  StayNAlive.com is now officially one of the first rssCloud-enabled blogs on the internet.