Is this new change worth the time and effort that will be required in order to implement it? If it's something that is already there, just one click away, chances are the answer is 'no'.

It was to me when I wrote it. The fact that the gods and some of pmdev didnt personally see the use of it was an obstacle. As was that apparently my implementation was too full featured for the reviewers and as such i have been recommended to dumb-it-down for pretty much no good reason ive heard or seen.

Is this change likely to be appreciated by a majority of the monks, or is it something so small and insignificant that only a few will want the change implemented.

I have two issues with this point. First off _unless_ the code affects system stability this argument is moot. An added feature appreciated by a minority that is produced by that minority that doesnt affect the majority is no business of the majority. Second I would say that far far far more people will appreciate features of this site that you or I wont. I personally don't like the personal nodelet that much but I wouldn't argue it be removed. In fact Ive posted signifigant patches to it to make your browsing experience more enjoyable. The fact that those patches as well haven't been applied is a matter you should address to the gods.

Is the change likely to take up a significant amount of additional server resources that is just not worth the outcome of the change?

Until the code is put into play and profiled any answer to this question is pure conjecture and smacks of premature optimisation (maybe that feature will be too slow, cool lets optimize and leave it out!)

Is the feature something that should actually be implemented directly into the website interface, or would it be more ideal to create an external client

IMO its better implemented in PM. That way a single implementation is available to all, regardless as to how clued into the site they are.

Regarding your points about feature requests and etc. My attitude is that if you want a feature and are willing to do the work to implement it and test it then petition to join pmdev or send a msg to any of the other pmdevils. If we think you are up to the task well let you join pmdev and put together a solution. Unless the feature compromised the sites integrity then the feature should stay. Fook, weve _still_ got the stupid tick tock nodelet. (PS: the 'we' in this para represents the gods and pmdevils. A recommendation by a pmdevil to the gods about a person joining pmdev is usually respected, but naturally the gods are the final deciders.)

The real trick is convincing a god that they should apply code that they personally dont want. And by that I dont mean they dont want it included, I mean that if they have no personal desire for the feature then it can be difficult to get them to apply the patch even when it works and is tested. But thats life.