A couple of considerations:

(1) A lot of the big aggregators require that you register your site with them in order to process your pings. This is related historically to item (2). While your ping is simply discarded if you haven't registered, I think it's not considered good etiquette to send pings to sites that you know will just discard them.

(2) I believe there is an updated form of the WeblogUpdatesPing call that includes the feed url. However, Roller currently sends an earlier version of the ping message that includes the blog url, but does not include the feed url, and therefore requires the recipient of the ping to know in advance the feed url corresponding to the blog url. We should update the code to send the new version. Have to refresh my knowledge of this a bit but it shoudn't be hard.

(3) So, If we make the change in item (2) above, we can enable pings by default to ping targets that don't require preregistration. For targets that require preregistration, we should leave the default disabled.


----- Original Message ----- From: "Allen Gilliland" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, May 04, 2006 2:52 PM
Subject: ping targets enabled by default?


guys,

one of the things that we are looking to do on blogs.sun.com is promote some more ways of getting our blogs to be better connected with the blogosphere as a whole. one of the obvious ways of doing that is through pinging of various sites that are interested in hearing about blog content as it gets published, like Technorati.

Roller already has all the right tools for doing pings, but unfortunately those pings are all turned off by default and there is no way for a large site like ours to apply ping config changes that affect all blogs in the system. right now it is basically up to the user to manually enable any pings they want to send and i am thinking it would be nice if we did 2 things ...

1. provide the ability to make ping targets enabled by default for new weblogs. this way the user has to manually disable a ping, rather than manually enable it.

2. provide a way for admins to enable/disable auto pings on a site wide level.

This way large sites like ours could add a new ping target and quickly enable that target for auto pings on all existing blogs as well as future blogs.

The work to do this should be fairly minimal, basically all happening in the global pings config page and a tweak to the action that creates a new weblog.

thoughts?  comments?

-- Allen



Reply via email to