Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

(kudra: consideration limitations) Re3: Front Page with Negative Rep..

by kudra (Vicar)
on May 17, 2002 at 08:50 UTC ( [id://167234]=note: print w/replies, xml ) Need Help??


in reply to Re: Re: Front Page with Negative Rep..
in thread Front Page with Negative Rep..

I agree with chromatic that 'itchy trigger fingers' can be a bit of a problem here. Recently I've seen quite a few nodes considered which end up being kept--and rightfully so, because they don't meet the criteria by which nodes should be deleted. Every single one of these nodes has to be manually removed from nodes to consider.

To quote from What is consideration?: "Request that a node be deleted. Please do this for blatant trolls (egregiously offensive) and true duplicates...For useless, stupid, off-topic, and annoying nodes: if it is a root node, then don't approve it for any section; if it is a reply, just ignore it."

I think it is becoming neccessary to limit the power to consider nodes. I'm against 'raising the bar' to a higher level because I think that just keeps newer people from participating. In my opinion it would be better to allow a group (power users, perhaps) to be able to prevent a person from using consideration for a period of time in much the same way someone can be kept from the chatterbox temporarily.

It has been suggested that this be linked to response to the consideration, but I don't really care for duplicate purpose voting. What if someone made a mistake and accidently considered a node when intending to message, or considered the wrong duplicate? It also starts to seem a bit circular with meta consideration for the consideration, will we soon need meta meta consideration? For that reason, I'd rather see a selected group responsible for this (and note that I'm *not* a member of power users, whom I recommend for the task).

As for the specific node in question that was reaped, I'm of the opinion that it should be reinstated. There were several interesting answers to the question, and it looks as if enough people here would have voted keep if they'd been around at the time it was considered.

On the subject of not allowing the front-paging of negative nodes, I don't see any need for it. The Gates should contain a spectrum of nodes, and if there is disagreement over the front-paging of a node, the mechanism is already in place to remove it from the front page. However, I admit to not reading the Gates at all, so I'm not sure if front-paging nodes is a widespread problem.

Replies are listed 'Best First'.
Re: (kudra: consideration limitations) Re3: Front Page with Negative Rep..
by giulienk (Curate) on May 17, 2002 at 17:49 UTC
    Quoting the quote from What is consideration?: "For useless, stupid, off-topic, and annoying nodes: if it is a root node, then don't approve it for any section; if it is a reply, just ignore it."

    The real problem is that these rules aren't followed by the majority of monks, even saint ones (i therefore see little use in raising the level barrier to consideration). I saw approved such stupid/homework nodes in SOPW that's easy to be tempted to consider some.
    Even the suggestion of not replying to off-topic nodes isn't followed as it should (maybe thirst for XP is too strong?).

    Said that, i got no easy solution, cause there is none: indeed these kind of problems raise up once every 3 days lately.
    Maybe the Monastery need a bit of revolution...


    $|=$_="1g2i1u1l2i4e2n0k",map{print"\7",chop;select$,,$,,$,,$_/7}m{..}g

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://167234]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (5)
As of 2024-03-28 13:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found