Trolls eat votes. People see a horrendous post and think it's important to downvote it, not knowing that it's already got plenty of downvotes. This is significant to those who are on a vote budget.
Doesn't the same hold for good posts? People find it important to upvote good posts (even more so than to downvote bad notes - just look at the number of upvotes vs downvotes). High level monks eat votes as well - they eat more than trolls. If you consider "vote budget" to be a real issue, you should argue for a limit on both sides: once a node gets more than X upvotes, or more than Y downvotes, voting on the node closes.
As an alternative, I would propose that posts by Anonymous Monk have a minimum reputation limit of -9. Once a post has reached that limit, the downvote option is disabled. That would act as an indicator and also eliminate the negative-rep badge incentive for Anonymous trolls.
The few trolls that would actually care about node reputation (doubtful - real trolls care about responses) and would be bothered by the reputation limit would take a few seconds to create an account. Just go to the sign-on page, enter an email address of 'troll@mailinator.org', collect your password, and you're off.
I also think you're solving the wrong problem. Trolls are not the problem. Troll droppings are: the replies. And considering there are always people eager to reply, the damage will be done before enough downvotes have been collected. For a flag to warn people about the existance of a troll, you need the flag in place before people can reply. So you might want to disable making replies before a node is at least X hours old, for some X. Which I don't think is what people really want.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
