Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re: RFC: Hide Very Bad Answers From Visitors

by hippo (Bishop)
on Jul 24, 2018 at 21:29 UTC ( [id://1219198]=note: print w/replies, xml ) Need Help??


in reply to RFC: Hide Very Bad Answers From Visitors

I think this is a positive step and I am in favour.

One suggestion for (very minor) improvement would be to have the threshold be -$NORM instead of the fixed, arbitrary -7. Other than that it's a total winner. Good work!

Replies are listed 'Best First'.
Re^2: RFC: Hide Very Bad Answers From Visitors
by jdporter (Paladin) on Jul 24, 2018 at 21:44 UTC

    Yeah, I was thinking vaguely of something along those lines as well. But I don't think using -$NORM is quite what we want, because that would mean that as the average node "quality" goes up, we become even more tolerant of even worse nodes. Instead, how about maybe something like -20 + $NORM. That would result in a threshold of -10.3 today. To put this in context: such a threshold would result in having no nodes posted today hidden, but all of this week's worst nodes of the week hidden (and then some).

    I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.

      Obviously, a node with a positive reputation should not fall under this rule.

        Right; that would be clamping at zero. I think I'd clamp at something negative. My personal feeling is to have a clamp at -7. I don't know why.

        I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.

      If you're going to use a formula like that, I would lobby for clamping to negative: $NORM<20 ? -20 + $NORM : -1;. Otherwise, if our $NORM quality spikes suddenly to 25*, some poor schmuck who "only" got +4 for a mostly-unnoticed post for some "Re^9" gets his reply hidden.

      *: okay, probably not likely with modern Best Nodes scores... but the idea is that I believe positive-voted nodes shouldn't be evaluated as "very bad", and so protection should be built in against that admittedly-unlikely event.

        Definitely agree with the clamping suggestion (for any system with a dynamic threshold), although I'd lower the "high" end clamp a bit, probably to -3, so that middling-to-decent responses don't get hidden simply because one or two people are having a bad day (or just want to be assholes) and give it drive-by downvotes before it receives any upvotes.
      that would mean that as the average node "quality" goes up, we become even more tolerant of even worse nodes.

      That only holds true if the actual mean quality increases. If $NORM goes up (or down) purely as a function of how many votes are cast in total (which it will), then using -$NORM seems perfectly rational.

      Instead, how about maybe something like -20 + $NORM.

      That also suffers form the same problem as just using -7: it puts an arbitrary fixed point into things which becomes problematic if $NORM changes greatly from where it is today.

        I see your point; but I note that -$NORM also has this problem, because it has an arbitrary fixed point of zero.

        I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.
Re^2: RFC: Hide Very Bad Answers From Visitors
by Anonymous Monk on Jul 25, 2018 at 07:04 UTC

    Perhaps we should consider the distribution of the votes and hide posts with rating in 10th percentile and below. The number 0.1 is subject to discussion, of course.

    Pro: no need for complicated formulae based on $NORM. Contra: it still may not mean what we think it means.

      Any node with replies will have replies in the bottom 10%. I don't think it makes sense to hide these if these have not gathered a significant amount of downvotes.

        What if quantiles are computed over last year over whole section / whole website and not just the current thread? That should give us a representative threshold of a "really bad node rating", I think.

Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others about the Monastery: (3)
As of 2024-04-23 23:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found