Friday, July 10, 2009

What's all the hubbub about PubSubHubbub?

One of the questions we get from publishers most often is "How do I make sure updates to my feed are delivered to feed readers as fast as possible?" We know this is important to our publishers' businesses and we are constantly making improvements to our back-end systems to minimize the time from when you publish a post to when it appears to subscribers in feed readers.

Recently there have been a lot of developments around the so-called "real-time" web. The promise of the real-time web is distributing new information as quickly as possible. This encourages users to engage in more active participation online and makes the web more dynamic than ever before. However, so far the real-time web has not been easily accessible by feed publishers using their existing infrastructure.

Today we're happy to announce initial support in FeedBurner for the PubSubHubbub protocol. 'Hubbub is an open specification in draft for web-scale publish and subscribe. The protocol can be used to transform any existing Atom and RSS feed on the web into a real-time stream. Best of all, it's open, free, and decentralized like the rest of what makes the web so great: No single organization controls the protocol or how it's used.

As of right now, burned feeds with the PingShot service enabled are automatically enhanced with the PubSubHubbub protocol. We'll add the required discovery elements to these feeds and notify a Google-run Hub, running on App Engine, of publish events. We also convert any pings we receive into 'Hubbub events. That means for many of our publishers out there, your existing feeds are available as real-time streams right now. Like, immediately. This very moment.

If you are a publisher and are not already using our PingShot service, turning it on is easy. From feedburner.google.com, visit the Publicize tab for your feed, select PingShot, and click the [Activate] button at the bottom of the page. From your AdSense account, go to Manage Ads, then click View Feed Stats link, and do the same thing. That's it.



If you manage a service that would like to receive updates to the millions of FeedBurner feeds that use this service as soon as possible, or just want to know more about the PubSubHubub protocol, we encourage you to check out our project on Google Code. There are open-source clients for Python, Perl, PHP, Ruby, and WordPress. We have an open-source reference implementation of a Hub built on Google App Engine. And there are other Hub implementations built and run by other companies. Please let us know what you think in the PubSubHubub Google Group!

Thursday, July 2, 2009

Happiness is more subject in your subject line.

If a certain lack of variety has weighed on the format of your day-to-day, feed-to-email deliveries, things are looking up at last. Recent advances in dollar-sign technology have brought some strange and fascinating new capabilities to the Email Branding section of FeedBurner's Email Subscriptions feature. Read on, ostensibly for the many useful pictures and descriptions, but really for the danger and excitement only a new checkbox can bring.

First, sign in to your Google Account on FeedBurner and then click your feed's title, then Publicize > Email Subscriptions > Email Branding.



Always want to feature the title of the latest post in your subject line? Just put ${latestItemTitle} in the Email Subject/Title textbox:



Do you often have more than one post per day? You can help your readers uncover exactly how many new missives you've got planned for them in each update. Check the "Change Subject…" box and reveal a secondary subject line to use when 2 or more feed posts are delivered in a single email.

Remember, good subject lines command attention in crowded inboxes.



Behold! The mythical "almost empty" inbox. But in this case, the most recent post's subject line, thanks to ${latestItemTitle}, is right in this FeedBurner-delivered email, shining through.



Have fun with this new feature, but please note that ${pithyRetort}, ${iambicPentameter}, and ${heartfeltApology} are not yet supported.