It’s just data

PubSubHubBub Publisher

Previously, I had been pushing pings to blo.gs, blogrolling, technorati, and weblogs.  I removed all of these, and added pubsubhubbub.appspot.com.  This involved two steps.

Adding the following to my feed:

<link rel="hub" href="http://pubsubhubbub.appspot.com/"/>

And, adding the following to my publishing flow (based on pubsubhubbub_publish.py):

#!/usr/bin/python
import urllib, urllib2
         
hub = 'http://pubsubhubbub.appspot.com/'
feed = 'http://intertwingly.net/blog/index.atom'
        
try:
  data = urllib.urlencode((('hub.mode','publish'), ('hub.url',feed)))
  response = urllib2.urlopen(hub, data)
except urllib2.HTTPError, e:
  if not hasattr(e, 'code') or e.code != 204: raise

Awesome!

Posted by Brett Slatkin at

What kind of setup did you have to do for blo.gs, blogrolling, technorati, and weblogs to pickup up the pings? Or do they, like Google Reader automatically opt for push?

Posted by Damien at

Damien: the have their own APIs, and I used to ping each.  As of today, I simply stopped pinging them.

Posted by Sam Ruby at

replacing blog pings...

Excerpt from Delicious/jemisa at

Sam, do you feel that you receive an equal or greater benefit from this new type of ping?

Posted by Scott Johnson at

Scott: I don’t have any hard data, beyond the following entry in my log:

64.233.172.20 - - [04/Mar/2010:14:58:51 -0500] "GET /blog/index.atom HTTP/1.1" 200 21534 "-" "AppEngine-Google; (+http://code.google.com/appengine; appid: pubsubhubbub)"

I also know that sending pings to multiple places slowed down my publishing (technorati alone often took tens of seconds and even would occasionally time out).  Hopefully, there is enough critical mass around PuSH now, so that those that crave real-time updates will fetch the data from there.

On a somewhat related note, I just added code to ping the hub when there is a change in my overall comments feed.  I have not yet decided what I want to do on my comments feed per post.

Posted by Sam Ruby at

The delay problem is why WordPress switched to sending them out asynchronously one slow (or currently offline) hub could take a normally speedy publish process and dramatically slow it down.

Posted by Joseph Scott at

WordPress certainly has a different scale problem than I do (that’s putting it mildly).  I only get a handful of comments per day, so I opted to do my pinging on the Apache thread.  That being said, I do daemonize the process first so that the response is sent to the commenter either before — or concurrent with — the sending of the ping.

Posted by Sam Ruby at

Add your comment