PuSH It Real Good: Deliver Content in Real-Time

As we discussed in an earlier post, everything is instantaneous these days. That’s why we’re excited to announce that dlvr.it is now fully PuSH (pubsubhubbub) enabled. You publish and we deliver…now!

If your feed is PuSH enabled, dlvr.it will receive new items as you publish. We’ll immediately post those items to twitter, facebook and all your destinations.

In short, this means dlvr.it gets your content in front of your audience – Fast!

So what’s all the fuss about PuSH and real-time publishing? Prior to the arrival of PuSH, it could take an hour or more from the moment you published an article until it was in front of your readers in Google Reader, Twitter, or Facebook. This delay was largely due to feed retrieval lag time at each step in the distribution chain. With PuSH, the content distribution timeline – from publication to consumption – is condensed to a few moments. This means immediate distribution of your content to your readers.

Distribution lag time creates real, tangible pain for many publishers, especially publishers in highly competitive markets. Based on our data, the vast majority of clicks on a new stories occur within a couple of hours of publication. This means that the lifespan of news is very short. And publishers who don’t get their news out quickly are at risk of becoming irrelevant — other publishers get their stories out first and quickly grab the limited attention of readers. The accelerating competition for attention and the increasingly condensed lifespan of news make it essential to break news as fast as possible.

So by leveraging PuSH-enabled dlvr.it in your distribution process, you’re giving your content the speed it needs to get to your audience fast, bolstering your relevance, reach and readership.

Oooh, baby, baby
Baby, baby

Update: dlvr.it automatically activates real-time updates for your PuSH enabled feeds. You don’t need to make any adjustments to your dlvr.it settings to take advantage of real-time updates — we’ll automatically recognize PuSH-enabled feeds and subscribe to your hub. To determine if your feed is PuSH enabled look for the “hub” tag in your feed source — it will look something like this:

<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" 
href="http://pubsubhubbub.appspot.com/" />

Keep in mind that if you are using a feed management service like Feedburner, there may be a delay between the time you publish and the time Feedburner picks up your content. This will lead to a delay in dlvr.it receiving your updates. More on Feedburner feeds and PuSH

About Charles Smith

I am one of the founders of dlvr.it and love working at the intersection of business, technology and design. I am an avid Oregon Duck football fan and, along with my two young sons, have built the third largest (unofficial) private Lego collection in the state of Oregon. I also enjoy discovering and mixing vintage cocktails.

  • Pingback: dlvr.it blog

  • Pingback: PuSH It Real Good: Deliver Content in Real-Time | dlvr.it blog Contact

  • http://www.reverbstudios.ie/blog Leon

    So, is this enabled in my Dlvr.it account now by default and do I have to do anything on my wordpress blog RSS?

  • dlvrit

    Yes, this is now enabled in your dlvr.it account by default. If your wordpress blog rss feed is PuSH enabled, dlvr.it will receive new posts as you publish them.

    Charles

  • http://www.reverbstudios.ie/blog Leon

    So would a wordpress RSS feed normally be PuSH enabled!? I have the latest 2.9.2..

  • dlvrit

    If you're using the WordPress-hosted service, then PuSH is enabled automatically. If you are hosting your own blog, there is a WordPress plugin called PuSHPress which enabled PubSubHubbub functionality.

  • http://www.reverbstudios.ie/blog Leon

    Hosting my own. Excellent thanks.

  • http://elabee.be/ el7cosmos – Abi أب

    That's great, and thanks for plugin information

  • http://our-party.org.uk/blog/ Scott Herbert

    I'm not sure how PuSH works, but why not poll the feed every minute (as my app does) and not have to worry if the user has enabled it on their site?

  • dlvrit

    Polling the site too frequently is hard on the publisher, and it consumes a lot of time and resources on both ends of the request. It would be nearly impossible to scale that frequency of request across thousands, or millions, of feeds.

    Most services only pull feeds every 30 minutes (or more) – PuSH ensures that they receive the new content in near-real time without ever having to manually retrieve the content at all. It can even be faster than pulling the feed every minute, and it doesn't have the same problem with resource consumption.

    Pulling feeds once per minute is actually a good way to have your service banned from sites for abusive behavior – just something to keep in mind.

  • http://our-party.org.uk/blog/ Scott Herbert

    Good point re scaleing, but only if you have a centralised web app, TwitterBrite is a desktop client (and windows service) which doesn't need to scale in the same way a web app does.

    If your just pulling your own RSS feed from your own hosting then who's going to ban you? if your pulling others content, then your going to be running into copyright issues anyway.