PingTimeout 60?
Apparently it’s not just MT 2.6 users who are having trouble getting a ping through to (or, more accurately, a ping response back from) weblogs.com: Simon Fell says his Radio event log is showing that it’s regularly taking over 30 seconds to complete. PingTimeout 60, anyone?
And, as anyone could have predicted, the ping for this entry timed out after 30 seconds. I wouldn’t think it’s a matter of server load, since there were only four blogs that updated during the same minute, so something must be going wrong.
Ah! Timeouts! I never thought to check that. I thought that maybe weblogs.com didn’t like me or something, so I just switched over to pinging blo.gs, since everyone I know who is interested in me pinging somewhere with updates does it with a blo.gs blogroll, afaik.
Well, pinging weblogs.com is useful for automated tools that don’t realize that blo.gs’s list is a superset of weblogs.com’s, though: I’m pretty sure that allconsuming.net runs off weblogs.com, and probably lots of others do, too.
I’d be inclined to just ping weblogs.com with a super-short timeout, and ignore the result. If at some point you notice that you aren’t showing up in their list, you can always go back and see whether the response is actually saying something useful.
And now, it seems to be quite a bit better: early today I was trying to get to the specs on http://newhome.weblogs.com and getting browser timeouts, but now it’s snappy quick. Here’s hoping the pings are, too.
Dr. Phil’s JavaScript
I’m appointing Phil Ringnalda an honorary doctorate for noting my previous problem with weblogs.com timing out. Also, if you’re reading NSLog(); in Mozilla or Navigator, errr, Chimera, err, Camino, then you’ll appreciate the javascript/css I stole from…
More blogrolling pings
OK, I’m in. I now ping blo.gs, and blogrolling.com and weblogs.com. It is nice to see that there are now regional services. What would be really nice is if these services could federate. If this were done, then I could ping one local or topical or