Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

Re^2: Feature: Auto hide. Change: show node vote counts to all, not just logged in users.

by haukex (Monsignor)
on Jul 18, 2017 at 10:56 UTC ( #1195320=note: print w/replies, xml ) Need Help??


in reply to Re: Feature: Auto hide. Change: show node vote counts to all, not just logged in users.
in thread Feature: Auto hide. Change: show node vote counts to all, not just logged in users.

I now agree on the font size issue. I just wanted to pick up on one other thing:

Nodes are sometimes downvoted ... for bad cause

IMO the issue of why nodes get downvoted would be best for another discussion in another thread. In my view the central issue at hand is that we've got nodes with a significant negative reputation, i.e. the community has already spoken, but we don't have a way to inform newcomers and casual visitors of that fact. (And of course adding a CSS class for such nodes would also allow registered users to hide or format such nodes to their liking.)

Update: Fixed typo.

  • Comment on Re^2: Feature: Auto hide. Change: show node vote counts to all, not just logged in users.

Replies are listed 'Best First'.
Re^3: Feature: Auto hide. Change: show node vote counts to all, not just logged in users.
by 1nickt (Prior) on Jul 18, 2017 at 11:43 UTC

    I do not intend that the reasons for down-voting should be debated here. However, in my view it *is* pertinent to consider the fact that nodes can be down-voted both in accordance with and not in accordance with the guidelines that are published. Unfortunately, those are not always followed and some posts accrue a slew of downvotes based on something else, such as, as mentioned earlier, antipathy towards the poster.

    Therefore I am opposed to any automated system that would determine, in the absence of consideration by a human Monk, whether a post should or should not be displayed to viewers and/or search engines, based solely on down-votes cast.

    update: added clarification


    The way forward always starts with a minimal test.

      "any automated system that would determine whether a post should or should not be displayed to viewers and/or search engines, based solely on down-votes cast."

      For completness, what you are proposing would seem to be a change in the existing consideration process, for example, current and new use cases:

      • Reap: SPAM.
      • Reap: troll.
      • Reap: abuse.
      • Edit: add code tags please.
      • Edit: reparent to [id://xxxxxx].
      • Hide content: A collection of poorly formatted buzzwords/Does not address OPs question/Is not an answer.

        No, because that implies the additional step of someone having considered the node (reply above up∂ated).


        The way forward always starts with a minimal test.

        Reap: troll. Reap: abuse.

        Those aren't "rules"

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1195320]
help
Chatterbox?
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (7)
As of 2017-10-18 09:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My fridge is mostly full of:

















    Results (243 votes). Check out past polls.

    Notices?