19 April 2005

How to ping services with revisions to buried content

Normally, when you make an updated to a buried blog, the services like Technorati, PingOMatic, and other members of the FeedMesh have no indication that there's a change.

Apparently, the services only look at the top item on the blog. Maybe a service like Technorati does dig deep, but I've made updates and haven't seen the changes report.

Google is different. It digs through everything. It doesn't hit everything either.

The issue for publishers is how to get this buried content pinged; and how to get updates and changes to the old content reported to PingOMatic.

There's a solution to this.

First, convert to draft-status all the blog-spots published after the blog-spot-of-interest. This means that the blog you want to send a notification about is at the top of the "published" stack, and the "first" thing on your blog homepage.

Second, ping PingOMatic with you content. PingOMatic will just hit this spot as if it were new. And the updates will get accepted.

Third, convert all the items you converted to draft back to published-status.

That's the hard way, and really doesn't do much good if you want to update something that's behind 40-blogs. Who wants to convert that many blogs twice?

An easier way

In the ideal world, we would be able to ping any page and let PingOMatic know about the new content on a specific page, not just the most recent blogspot at the top of the blog.

It would be nice... if there was an auto-convert tool that changed content from published to draft status.

In the meantime, until PingOMatic or the other services have a way to automatically accept pings in re specific webpages, the services might want to think about this:

What if there was an auto-matic way to convert all blog-spots to draft status.

If I have an update to a deeply buried page, then when I republish that page, a couple of things could happen:

Blogger could convert all subsequent pages to draft-status, making that most-recently-updated-blog-spot the title-spot on the blog.

Then blogger could have an auto-notify of PingOMatic and the FeedMesh.

Once all the services had been pinged, then blogger would re-convert all the spots back from draft back to their original status. Remember, not all "draft-blog-spots" were originally published, so blogger would have to know which of the blog-spots not to convert to a published status.

It would be nice if this was automatically done, with a single "publish" request at any level of the blog-spot-stream.
Normally, when you make an updated to a buried blog, the services like Technorati, PingOMatic, and other members of the FeedMesh have no indication that there's a change.

Apparently, the services only look at the top item on the blog. Maybe a service like Technorati does dig deep, but I've made updates and haven't seen the changes report.

Google is different. It digs through everything. It doesn't hit everything either.

The issue for publishers is how to get this buried content pinged; and how to get updates and changes to the old content reported to PingOMatic.

There's a solution to this.

First, convert to draft-status all the blog-spots published after the blog-spot-of-interest. This means that the blog you want to send a notification about is at the top of the "published" stack, and the "first" thing on your blog homepage.

Second, ping PingOMatic with you content. PingOMatic will just hit this spot as if it were new. And the updates will get accepted.

Third, convert all the items you converted to draft back to published-status.

That's the hard way, and really doesn't do much good if you want to update something that's behind 40-blogs. Who wants to convert that many blogs twice?

An easier way

In the ideal world, we would be able to ping any page and let PingOMatic know about the new content on a specific page, not just the most recent blogspot at the top of the blog.

It would be nice... if there was an auto-convert tool that changed content from published to draft status.

In the meantime, until PingOMatic or the other services have a way to automatically accept pings in re specific webpages, the services might want to think about this:

What if there was an auto-matic way to convert all blog-spots to draft status.

If I have an update to a deeply buried page, then when I republish that page, a couple of things could happen:

Blogger could convert all subsequent pages to draft-status, making that most-recently-updated-blog-spot the title-spot on the blog.

Then blogger could have an auto-notify of PingOMatic and the FeedMesh.

Once all the services had been pinged, then blogger would re-convert all the spots back from draft back to their original status. Remember, not all "draft-blog-spots" were originally published, so blogger would have to know which of the blog-spots not to convert to a published status.

It would be nice if this was automatically done, with a single "publish" request at any level of the blog-spot-stream.
" />