XMPP. The Future. Enterprise collaboration company Jive Software posted today about a theory it's advancing on the rise of XMPP (called Jabber in IM) for powering communication services hosted in the cloud.
The company also announced that it will include what it says will be the first XMPP-powered document sharing and collaboration tool in the forthcoming 2.0 release of its product Clearspace. If you think AJAX changed the web experience, imagine a web with decentralized, open standards-based IM at its center. That's an exciting thought. This post introduces the concepts at issue in accessible terms, discusses some of the possible impacts of such a trend on innovation and offers some counter-arguments to Jive's rosy picture of the future.
The changes that XMPP could enable for web innovation in general are quite interesting. Jive is based in Portland, Oregon, took funding from Sequoia Capital (Early Google and YouTube funders) and has an impressive customer list available on its site. Early Examples. & The Real Time Web. & Semantic Web. While the MD5 hack that puts e-commerce sites at risk by faking security certificates received most of the attention at the 25C3 conference in Berlin today, another interesting talk about using XMPP to ensure privacy and security on social networks by Jan Torben Heuer caught our eyes as well.
Heuer demoed a social bookmarking service named Diki, which implements some of his ideas, though in the long run, the developers are planning to take this prototype and develop a full-blown social network with a focus on privacy and encryption around this. Heuer argues that ensuring privacy on social networks is almost impossible, due to the centralized architecture of these networks, where all your information is controlled by one corporate entity, and where the user has to simply trust the service provider without having any control over what this provider does with the information. Diki. In Superfeedr. Superfeedr provides a realtime API to any application who wants to produce (publishers) or consume (subscribers) data feeds without wasting resources and maintaining an expensive and changing infrastructure.
This documentation shows how to integrate Superfeedr into a variety of diverse infrastructure, as well as highlights most of the features offered by Superfeedr. Table of Contents You can find links to the pages below in the top menu bar as well. Introduction: this pageSubscribers: your app consumes RSS feedsPublishers: your app publishes RSS feedsSchema: learn about the data sent by SuperfeedrMisc: extra features and information. Audience. Superfeedr.
Seesmic. In Google Wave. Google just opened the Google Wave developer sandbox for federation.
Developers can now begin prototyping tools against WaveSandbox.com. Google tested earlier versions of Wave with a small number of developers on the Wave sandbox and this server will now become the platform for testing interoperability between different Wave servers. Google also released a how-to document that explains how to set up a Java-based Wave server over the weekend.
More details about how to implement the Wave Federation Protocol can be found here. Running Wave on Your Own Server Developers who want to run their own Wave server can find all the necessary information for setting up a Wave Federation Prototype Server in these documents. Google Wave. As we announced in August 2010, we are not continuing active development of Google Wave as a stand-alone product.
PubSubHubbub. A simple, open, server-to-server webhook-based pubsub (publish/subscribe) protocol for any web accessible resources.
Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (resource URL) they're interested in is updated. What is it ? Real-time web protocol PubSubHubbub's co-creator Brett Slatkin, an engineer at Google, gave a talk at Facebook headquarters today about how the new information delivery system works and how Facebook can support it.
He's published his deck on his blog and we've embedded it below as our Real-Time Web Article of the Day. Vs RSSCloud. Editor’s note: With all of the debate lately between RSSCloud versus PubSubHubbub, we wanted to hear from a developer who could actually tell us which one might be better and why.
The following guest post is written by Josh Fraser, the co-founder of EventVue, who is an active contributor to PubSubHubbub in his free time. He has contributed several client libraries for PubSubHubbub including a WordPress plugin. Guess which side of the debate he falls on. In Superfeedr. Superfeedr provides a realtime API to any application who wants to produce (publishers) or consume (subscribers) data feeds without wasting resources and maintaining an expensive and changing infrastructure.
This documentation shows how to integrate Superfeedr into a variety of diverse infrastructure, as well as highlights most of the features offered by Superfeedr. Table of Contents You can find links to the pages below in the top menu bar as well. Introduction: this pageSubscribers: your app consumes RSS feedsPublishers: your app publishes RSS feedsSchema: learn about the data sent by SuperfeedrMisc: extra features and information. Audience. Superfeedr. In Typepad. Typepad. In Netvibes. The next version of popular web dashboard service Netvibes will push "near real-time" updates from feeds to the browser, a dramatic change in how the service works.
Those feeds will be served up along with the standard suite of functional widgets the company has always provided. As the number of real-time feeds available around the web has rapidly grown over recent months with the rise of real-time publishing technologies, the big question has been: when will a major feed reader consume these feeds? Google Reader may be too complex and too slow-moving to be first; that Netvibes is going to steal the show should be no surprise. In an unembargoed presentation sent to press this morning, Netvibes said that it would be adding support to its next version for both Pubsubhubbub and RSS Cloud protocols.
When those technologies are used to tell Netvibes that new items are available, the items will be pushed automatically to the browsers of subscribers - with no browser refresh required. Netvibes. In Google Reader. Google Reader is about to get much faster for developers. You'll be pleased to note that Reader has just adopted the PubSubHubbub protocol for shared items. This means that instead of repeatedly requesting that Reader's shared items reload from the server, the feed automatically updates via a distributed hub model. Rather than waiting on the back and forth pings of update notifications and polled Atom URLs, feed subscribers can receive both the notification and the message from a hub. Subscribers get the latest content on their favorite feeds in near real time (sans repeated links), while publishers let the hub handle the subscription load.
This distributed model allows publishers and subscribers to reduce the number of actions required to serve up feeds and is what Anil Dash eloquently describes as the Pushbutton Web. This latest Reader effort is a 20% Google project of Mihai Parparita, Brett Slatkin and Brad Fitzpatrick. Google Reader. RSS cloud. In WordPress. All blogs on the WordPress.com platform and any WordPress.org blogs that opt-in (using this plug-in) will now make instant updates available to any RSS readers subscribed to a new feature called RSSCloud. There is currently only one RSS aggregator that supports RSSCloud, Dave Winer's brand-new reader River2. That will probably change very soon. WordPress. In Netvibes. Netvibes.