More Ping Problems?

Here’s another pinging problem. Redundant Pings:

A couple days back, FeedBurner contacted me saying that they’re interested in adding Pingoat to their ping list. Indeed I was really excited about this. But out of perplexion, I asked them how their pinging works, i.e, how does it prevent ping redundancy (what i mentioned above). But still, I haven’t received any answer.

So unless FeedBurner is doing something to stop ping redundancy, pinging services like Pingoat from within their system, along with the individual pings they send is a major flaw. Still unsure why they aren’t taking any action on this matter.

TailRank can prevent this. If we’re pinged more than once every 5 minutes (per weblog) it’s just dropped. I’m thinking of reducing that window though. I often post to my blog in less than 5 minute intervals.

One idea is top include a max hop count within the ping. This way a ping is only passed around in the pingosphere N times (whatever maxHopCount is). Each ping service would increment the ping count.


  1. I agree this is a subtle but important issue. FeedBurner’s priority is to make sure publishers are getting the benefits of the ping network with the minimum amount of research and understanding required AND that FeedBurner be a good citizen and not abuse that network. So we are carefully folding in services. We haven’t added any service until we have been comfortable with our approach AND communicated with service to make sure that they were comfortable with our approach too.

    chris frye
    vp engineering
    FeedBurner

  2. I think the problem of duplicate pings may get worse before it gets better. Given enough growth and interest in pings though the problem will get sorted out.

    As for reducing the timeout to less then 5 minutes, my gut feeling is that isn’t a good idea. Does it really matter if you send one ping out or two if you’ve written two posts in less than 5 minutes?




Leave a Comment