Weblog ping services

Given the sheer number of weblogs that exist, and more importantly the number of those that could be dead, knowing which weblogs have been updated and when is a critical piece of information. The solution to this problem is a notification service, whereby weblogs alert a system when they’ve been changed. Pioneered by weblogs.com, ping services are the linchpin of every major weblog aggregator.

Nowadays, every weblog author has a number of options to choose from when they setup their blog. The big three are:

There are a number of other ping services for specific communities (e.g. geographic, topical, etc.), but most people decide on the big three. In addition to these choices, the Pingomatic meta-ping service has emerged as a way to easily manage your pinging adventures. Since most of the smaller systems also troll Weblogs.com and Blo.gs, this seems like a suboptimal solution. Why ping 15 individual services when you can ping just one and get the same effect?

As for who receives your ping, Technorati, Bloglines, and Feedster are all closed systems, and pings sent to them are available only to their service. As the weblog economy grows, there will only be more and more competition for each ping, and I assume these companies will protect their data, and for good reason. Any additional updates they get above and beyond the free, open services provide an advantage over other companies. For me, the choice of an open ping system is obvious, but i fear that new webloggers will choose the only name they recognize and many smaller services will lose out at the expense of better-marketed systems.

In the realm of open ping systems, Blo.gs has taken a leap ahead with respect to the efficiency of ping delivery. Most ping services use HTTP as a delivery mechanism, requiring a user to poll a URL to get an XML list of recently updated sites. This is highly inefficent given the nature of the process, namely using a pull technology to push information. Probably due to demand, Blo.gs has moved to a push system whereby blog aggregators can recieve updates as they roll in.

While the future of Blo.gs is unknown, their source code is available, and it has remained a freely available system from the outset. As the author of a blog aggregation system, their efforts have made my life that much easier over the course of the past few years. I sincerely hope that this system, or another open system like it becomes the industry standard for providing update information. Otherwise many of the smaller weblog systems will suffer.


7 Comments

  1. Posted February 22, 2005 at 1:02 pm | Permalink

    Agreed, the blo.gs streaming interface is really nice.

    Have you seen this?

    http://search.cpan.org/~btrott/POE-Component-BlogCloud-0.01/

    Makes it easy to write a client that grabs updates from blo.gs, then does something with them.

  2. Posted February 23, 2005 at 9:36 am | Permalink

    Hmmm — how had I not seen this yet? Thanks for the heads-up… time to do some integration with a few apps I’m working on.

  3. Posted February 24, 2005 at 7:11 pm | Permalink

    a commercial service that deserves props for supporting the same streaming updates interface as blo.gs, and thus sharing the data they collect, is pubsub.com.

  4. Posted July 23, 2005 at 12:53 am | Permalink

    Pingoat.com interface can ping around fifty blog services :) check it out : http://pingoat.com

  5. Posted February 14, 2006 at 1:00 am | Permalink

    Saveallyear.com, save all year long with super deals, up to 89% every day!!!

  6. Posted March 12, 2006 at 6:02 am | Permalink

    I found a dutch Weblog Ping Service to ping multiple blogsearches. Technorati, Blo.gs, weblogs.com, … all included.

  7. Posted August 4, 2007 at 8:49 am | Permalink

    pingomatic and pingoat are used by me everyday:)

One Trackback

  1. By Zuckervati MissingLinks on June 14, 2005 at 11:54 am

    Weblog ping services

    Given the sheer number of weblogs that exist, and more importantly the number of those that could be dead, knowing which weblogs have been updated and when is a critical piece of information. The solution to this problem is a…

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*