WordPress Reverts To Original Ping Behavior

pingomaticlogoIn case you missed it, there was some bruhaha over a recent change in WordPress where pinging went from being instant to being sent once per hour. Karamell.net argued that this change halted the real time web and that it would negatively affect announcement services such as Google news. A counter patch was then made to reduce the wait limit to 30 minutes and also bundle pings together. Then after all the discussions were made, the final verdict was to restore the original behavior which means pinging takes place when the post is published as well as any time it’s been successfully updated. The changes will be in WordPress 2.8.3 if released or WordPress 2.9.

At one time, I removed the Ping-O-Matic code from my WordPress install because I believed in the rumor that if I published or updated content too much, I could be banned from these pinging services because of so many pings. While it looks like that might still be a possibility, I’ve since learned to schedule posts and try to keep editing down to a minimum.

2 responses to “WordPress Reverts To Original Ping Behavior”

  1. If you use Feedburner, as I wrote about recently, they do their own intelligent filtering based upon what has changed within a document.
    Exactly how that works is hard to determine, but combine that with their eventual full database of ping services, and you have a killer combination whereby services can potentially specify ping intervals.

  2. I use posts differently on some of my blogs, in a way that depends on frequent numerous edits. I open the post “live to the public” at the start of a real-time event. I add to the post continually, repeatedly, for the next 2-6 hours. It could be 20, 50, 100 edits. After the 6 hours the post is basically complete. If the readers visit the blog live during the event they will see the latest updates in the post, and can refresh for by-the-minute changes. If the readers visit the blog the next day (or anytime later), then the post is a complete permanent archive of the event. In my case the event is radio playlist of songs and announcements, but I could imagine others doing the same technique for reporting on a race, sports, or game. Anything where there is an opening-announcement which is later edited to include realtime statistics, and eventually finalized into a permanent record. For SEO purposes, it seems advantageous to maintain the flow of all that related content in the same post, same permalink.

    That’s why I always have turned off Ping-O-Matic on that kind of WordPress install. Don’t know if that is the correct decision. I feel it would be best for this site to Ping the first time I post it, and maybe Ping again on the next day when the post is finalized, but certainly not ping for each of 20+ edits in the span of 6 hours. Any advice of the best approach for my set up?


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: