|Perl: the Markov chain saw|
I think it's an interesting idea, but like many proposals, risks over-engineering a solution away from the simplicity that makes Perlmonks work, all for the sake a what I believe are relatively few instances of PM "not working".
Personally, I see very few questions that aren't answered. The ones that aren't are usually poorly written or lack sufficient information for someone to help -- and there's usually at least one reply that points that out. If I see a good but poorly answered or unanswered question, I'll Front-Page it (if it hasn't been already) and give it a little more attention. (There have been similar proposals to yours about "re-Front-Paging" things that fell off and for simliar reasons.)
My default view is "Recently Active" so I can see what does and doesn't have significant activity. If you haven't tried it, I recommend reading PM that way for a week -- at first, don't mark the threads as read and you'll get an ongoing view of the pockets of activity and which posts are drawing less interest. It may help draw you to areas where your contribution will be valued.
(P.S. Statsmonks -- just for curiousity's sake, any way of counting how many OP's have zero replies? Or a distribution of # of replies?)
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
In reply to Re: How do you find nodes that need your answer most?