Like Sam, I ping weblogs.com because it’s the big daddy, and if something reads any changes.xml it’ll read that one, and I ping blo.gs because it’s fast and feature filled, and even though it will pick up weblogs.com pings once an hour, there are features (like IM notification) that you only get if you are pinging it directly, and I ping Movable Type because it puts me in good company, and now I ping blogrolling.com, too, just to see what Jason can do with the pings, but I shouldn’t have to do all that pinging, and they shouldn’t have to do all their cross-polling of changes.xml files.
If weblogs.com just registered for notifications from blo.gs’s cloud, then with a little trust it could just treat pings received from blo.gs as pre-verified, and cut down on all the traffic load that I presume is what’s slowing it down so much. Pinging programs would only need to ping until one went through – ping blo.gs, and if the ping succeeds you’re done, if it fails because blo.gs is down fall back to weblogs.com, if that doesn’t go through then try blogrolling.com. But it’s going to require a bit of cooperation, and quite a bit of trust. Why, if Blogger would cooperate on what constitutes a change (more than just clicking the Publish button), and weblogs.com and blo.gs would trust them to provide a clean update list without having to check for themselves, we could finally have update notification for more than just the privileged few Blogger Pro weblogs.