Judging by the quick pings on my last entry, the DNS change for the new weblogs.com server has made it out to me. No more messages about failed pings and read timeouts, and no more trying to explain how a ping could fail when you can see that it worked, because you’re in the update list, right there. Nice.
Fast or not, the comments on my previous entry have got me thinking that I ought to build myself a personal ping proxy server, so that I can have Movable Type just ping it, and then it can take its time about pinging anything I know of that accepts weblogs.com-style pings. Or, for that matter, other styles: a ping proxy server could ping wanderlust.com in a way that they understand, rather than having to send them an XML-RPC message they don’t really comprehend, and then generating an error because they don’t return an XML-RPC response.
I’m trying really hard not to think about how Dave was seeing a heavy load during the changeover because someone was crawling all over the Radio discussion group. Whether he meant radio.userland.com/discuss/ or radiocomments.userland.com/discuss/, in either case if I were crawling it, it would be because of all those juicy email addresses, sitting out at the end of /profiles/$ URLs all over the place. I’ve always thought those were fat enough targets to be well worth writing a special purpose crawler. (Note for the irony impaired: I’m not actually a spammer, or a writer of email harvesters.)