I brought this up, as well, but the suggestion is to tell the blogspot people to ping ping-o-matic
I brought this up, as well, but the suggestion is to tell the blogspot people to ping ping-o-matic
I don't wish to demand that everybody be forced to check blogs.com or whatever it used to be, but I'd like the option. It's easier to change my behaviour than everybody elses. I don't wish to be in a WordPress ghetto of non-updating blogrolls!
Well, I just started using the cron job with 1.5 (before with 1.2 I was running the plugin). It's obviously doing something -- but as gregorsmith said above, it's only showing WordPress blogs updating. Other blogs that I know are updating aren't showing up as updated anymore and this is frustrating. Is this because Pingomatic doesn't know about them? Is there anything we can do?
(Edited to add: Ack, I posted this having read the first page of replies, not realizing there is a second page. I see others have said much the same thing. So I'll just add my voice to the chorus. Apparently most of the blogs I read aren't pinging Pingomatic.)
I've got it working somewhat, but the times are still incorrect. Is there a way to modify the time that's displayed?
Working? Working how? Checking something other pingomatic? Pray tell.
Sorry, I don't know anything about the times.
the times are still incorrect
Yeah, I don't know anything about it either. At the very least, my blogroll shows that it was recently updated. It'd be nice if there was a way to configure that, of course. I'm not plugin developer, though - I wish. =/
The times haven't updated because wordpress isn't getting any new times from ping-o-matic, so the time displayed is the last time it updated to.
I sent a note to ping-o-matic yesterday, asking what the appropriate workaround was going to be, since so few people are pinging ping-o-matic:
Beyond sending pings, do you have any plans to actively look up other pinging services, so catch updates you missed? Or maybe some other workaround that doesn't involve me evangelizing on your behalf?
Matt Mullenweg wrote back:
Well I would of course recommend evangelizing, but we do plan to expand
checking to include blogs that ping weblogs.com, we just didn't want
that to hold up the release of WP 1.5.
So basically, they're planning on setting up ping-0-matic to check weblogs.com, but it hasn't been set up now.
In the mean time, I'm thinking about seeing if I can get the old links-update file to work. Probably bad, but I need something to work :)
Not to be offensive here (though I'm sure it will be taken that way) but it seems a bit silly that the update links would be tied in with ping-o-matic, simply because Matt and Dougal are running that as well, when there was no problem with the pinging of weblogs.com to update links, apart from the occasional time it would be down...
Surely they would have realised the people would notice that their sidebar wasnt showing updated links...
And if that's Matt's "official" reply then it just reeks of self-promotion, as if it's not enough for us all to be preaching about wordpress, we have to pretty much convince people to ping ping-o-matic as well...
I don't suppose he mentioned a likely timetable for this, did he? I mean, two weeks I can live with; six months, OTOH, would be supremely frustrating.
No offense on my part, anyway.
Of course it's shameless self-promotion. You expect them to not promote their services? Nevertheless, ther WAS a problem with welblogs.com. And it's spelled MOLASSES. Weblogs had terrible response times, and little responsiveness from the people maintaining it. The problem is that they released 1.5 before getting ping-0-matic up to par AND not telling anybody about it.
But then, somebody could theoretically use the old links-update file, or create a plugin that adapts it to 1.5. (obviously, I haven't tried yet)
In defense of Matt and Dougal:
Weblogs _is_ unreliable. And depending on the way in which you call update_links.php, that may or may not be a problem. If you have set up a cron job, then no worries, but if you have the old links updater plugin installed, and your blog is waiting for weblogs.com before it loads, then timing out, etc. can become a big problem.
Blo.gs is another option, that seems much more reliable. However, they have stopped using the changes.xml type service, in favor of a streaming service. This makes it much more difficult for a program like WordPress to get updates from such a service. It would be better if such a service was first parsed by a server such as Ping-O-Matic, then accessed by WordPress users as needed.
That said, I agree that Matt, Dougal, et al. should provide a clear timeline as to when Ping-O-Matic will implement this.
I am currently working on a plugin that will parse an RSS feed of favorites and use it to update links on your blogroll. It is designed to work with blo.gs favorites, and it will use the LastRSS library, including cache functions. This will allow it to be run using a hook every time the page loads without overloading the blo.gs server. I am not a programmer by any means, but if/when I am able to get this fully functional, I will make it known on this forum.
My cheap solution was a flop. I don't have time just yet to try thefreefood's plugin, but it doesn't sound like it's going to be a very useful solution for my needs.
How do I run a "cron job"?
Is there a timeline for pingomatic getting a wider set of update stats?
It would be great if WP 1.5 will tell us when most bloggers who don't ping pingomatic but ping other major ping sites have updated.
I just keep rechecking this thread every couple of days, hoping for news... my blogroll is so pathetic now, with only three of the blogs showing as "updated" since Feb 20. :D
I contacted ping-o-matic a few days ago asking about any plans to get ping-o-matic retrieving information from other major webping services and have not yet heard back. But, I'm sure Matt et al are keeping very busy supporting WP 1.5. Hopefully they'll get back to us soon.
Weblogs.com is not an option, the file was getting to be almost an entire megabyte and processing it was causing major load on servers, as well as the weblogs.com service which is not terribly robust.
Checking ping-o-matic every 15 minutes WILL NOT help, in fact it will get you banned. The new API doesn't have the "catch-up" problem, if you check once a hour or once a week you still get the latest update times.
The new system does not need to write to the filesystem or have any files CHMODed. It also uses maybe 1-2k of bandwidth rather than megabytes. It hardly requires any processing on the client side.
Bumping this thread isn't helping the problem and is obnoxious, any more "bump" replies will be deleted on sight and if repeated the user will be permanently deleted from the forums.
Matt, thank you for that info (my cron job was at 30 minutes, but I am NOT the one who set it up so don't ban me! It's changed to every hour as of now), but the question I think most people really care about is -- will Ping-o-matic start giving us update times for more blogs? Right now I'm only seeing three blogs update out of my whole blogroll, and it is really frustrating. Of course, more people could be pinging Ping-o-matic, but I personally can't force the people on my blogroll to do this. Weblogs.com sucks in many many ways, but it still seems to be the one that everyone sends pings to.
I understand very well that you all are really busy with the 1.5 release now, so I think the main thing we all need is just some information -- will this problem be fixed and what is the time estimate? I know you don't have an exact time -- I just mean a rough estimate like "within the next few weeks/months, etc." Or even "we don't think it's important, so don't expect things to change." (I wouldn't LIKE that answer, but at least I'd know how things stand and would be able to start looking for some other solution to the issue.)
Really, the main thing that is frustrating is the not knowing, that's all. :) So thank you for the info you do provide.
A. The developers are so busy with their normal lives and developing WordPress that they rarely visit here.
B. There is a bug track system by which you can submit bugs directly to the developers and can track the progress of that bug.
C. This bug has not been submitted to the bug tracker.
D. Basically speaking: Instead of sending mail to a developer's house, you are sending it to his summer vacation cabana, and you're hoping that he stops by more often than once a year to pick it up. Demanding an immediate response doesn't work well when there's no one around to hear your demands.
So, please submit the bug appropriately: http://mosquito.wordpress.org/
Well, since you've gotten all alphabetical on us... ;)
A. Matt just *did* visit here; I was surprised that he didn't address the question that had been brought up so many times in the thread, so I asked about it.
B. The impression I got from the other replies is that this is not a WordPress bug, hence I (and the others posting here, probably) wouldn't have thought to post it as a bug. I mean, the software is doing exactly what it is supposed to do... contacting Ping-o-matic. It's just that Ping-O-Matic isn't supplying as much info as weblogs.com did. Now, maybe it's a Ping-o-matic bug, though...! Do you think it's an appropriate thing to clutter the WP bugs database with? I mean, if everyone thinks so, I'd be glad to report it -- it just doesn't seem like a WP bug to me.
C. See above.
D. No one was demanding an immediate response. At least, I wasn't. And I made a point of acknowledging his busyness, thanking him for his help, etc. But I don't think it's unreasonable, when a dev comes in and addresses a support issue here, to ask further follow-up questions. Do you? I mean, I appreciate greatly what they have done, since I'm not a programmer and couldn't do it myself. But they are not gods that walk the earth, above any questioning whatsoever. ;) It's part of the job, basically. What is unreasonable is expecting that people should not ask questions.
True. I'm just suggesting that he may not be back for a while. And, if you'd like to be in the know about the progress of this issue, there are better ways to go about doing it.
I did receive a response from my email to Ping-o-Matic. It's a known problem. I guess that means they are working on it or will work on it at some point.
From my research I would say it is not a WP bug. It's either a Ping-o-Matic problem, or an interfacing problem between the two. Sadly PoM doesn't seem to have an excellent support forum like this, so this is where the complaints end up.
Just popped in to see Matt saying any bumps would cause that member to possibly be deleted from the forums. So, I won't bump this thread any longer.
However, I'll just link to my post explaining how to track the updated times for the sites that are pinging Ping-O-Matic.
*runs and changes cron job to 1-hour intervals*
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 "http://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., "http://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.
But what if the site being linked to does actually require a www? I know many times that is not the case, but I have occasionally run across sites that don't function without the www hostname. (And what about sites that are "somehostname.domain.com" -- for example, Blogspot sites? The hostname is absolutely required for those.)
"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.
That is very weird. I wonder if it's a bug. It sounds sort of as if it might be. Did you report 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.
Well, good -- it does sound like something that probably isn't quite working as it should be. :)
This topic has been closed to new replies.