timeistight

I had that problem too under WP 2.0. It went away when I upgraded to the latest version.

I think there’s some confusion here between services to ping when you update your weblog and services to query to find out who else has updated theirs. I’m happy to continue to ping pingomatic when I update mine, but I’d like to find a working alternative service to query until the pingomatic api gets fixed.

I’d be in a pretty bad state if I’d been holding my breath since January. However, this used to work pretty weel; I can’t see why it can’t be made to work again.

What service to use, though? It used to weblogs.com, but it got to the point where it was down as often as it was up.

I agree with niziol: If pingomatic won’t be fixed, then the update-links function should be dropped.

Still not working.

Pingoat’s new to me. Any idea how to query it with a list of links?

The pingomatic API hasn’t worked since the middle of January. Requests for information have fallen on deaf ears.

I guess that’s one solution.

$fs = fsockopen('api.pingomatic.com', 80, $errno, $errstr, 5)

The above code (from wp-admin/update-links.php) has consistently failed with a timeout error since at least January 11, 2006.

Matt Mullenweg has mentioned revamping the api: https://photomatt.net/2006/01/12/ping-o-scratch/. I hope that solves this problem.

Matt Mullenweg says that he has fixed the Pingomatic bug I refer to in “2)” above.

Actually, it only “just worked” when weblogs.com “just Worked”, which has been a rare occurrence lately.

There are, however, a couple of issues with the Pingomatic API:

1) The number of sites that ping it is still small compared to some of the older blog trackers.

2) It only recognizes sites in the “https://domainname.tld” format. If a link in your list is in the “https://www.domainname.tld” format, the API will not recognize it.

There’s a plugin around that uses https://blo.gs instead of Pingomatic. You may have more success with it.

I don’t think it belongs in Mosquito because it’s not a WordPress bug. I think it’s an “undocumented feature” of the Pingomatic API.

I did email Matt Mullenweg about it but he’s off to Europe now, according to his weblog.

“somehostname.domain.com” is fine; it’s just “www.domain.com” that it doesn’t seem to recognise. I guess a site where “www.domain.com” isn’t the same as “domain.com” is just SOL, as far as Pingomatic is concerned.

I should emphasize that I have no inside knowledge of the workings of Pingomatic – this is just the way things worked for my particular link collection.

I think I finally figured out why I’ve only been getting updated times for half-a-dozen of the ninety-plus links in my link roll: If the links in your database are of the format “https://www.timeistight.com,” the Pingomatic API won’t recognize them, even if the site pings Pingomatic religously; the Pingomatic API responds only to links without the “www,” e.g., “https://timeistight.com”. Be sure to check links in the database itself, as the Link Manger list trims the “www” automatically.

Fixing this does nothing for those sites that don’t ping Pingomatic, of course, but it’s still a big improvement over they way things were.