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

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
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.


In reply to (kudra: consideration limitations) Re3: Front Page with Negative Rep.. by kudra
in thread Front Page with Negative Rep.. by Moonie

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    [Eily]: you could tie a variable into not having the same value each time, if you like to make people who try to debug your code facepalm
    [Corion]: perl -wle 'package o; use overload q("") => sub {warn "str"; ""}, bool => sub{warn "bool"; 1}; package main; my $o={}; bless $o => o; print "Yay" if ($o && !length($o))'
    [Corion]: But people writing such code should document the objects they construct and why it makes sense for an object to be invisible as string while being true in a boolean context
    [hippo]: That's equal parts clever and horrendous.
    [Eily]: the overload version wouldn't return true with "$x" && !length $x though, I guess
    [hippo]: The more I look at this code, the more $x is a plain old scalar and the more this condition will never be true. I'm calling it a bug at this point.
    [hippo]: Thanks for your input which has soothed my sanity (a little)
    [Corion]: Eily: Sure - if you force both things into stringy things, then you break that magic. But that would also mean that you changed the expression, as now $x = 0.00 will be true instead of false as it were before
    [Corion]: Ah no, at least in my feeble experiments that doesn't change the meaning
    [Corion]: We sell sanity in small packages ;)

    How do I use this? | Other CB clients
    Other Users?
    Others drinking their drinks and smoking their pipes about the Monastery: (9)
    As of 2017-07-27 13:40 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      I came, I saw, I ...
























      Results (413 votes). Check out past polls.