Seeing the node reputation then being able to vote for it could skew the vote. However, if someone doesn't know whether a node is worthy of positive or negative votes, then there's no reason to vote for or against it.

So if this were to be done, I'd say someone should have to log in and pick a choice like "I'm not voting on this node, and don't want to in the future. Please show me the current reputation and take away my ability to vote on this node". This would mean someone could still post as an AM, then view it as a logged-in user. The obvious abuse of posting as AM and then voting on the node while logged in is possible already.

There's the limit of not being able to moderate in a thread and post to it over at Slashdot. This is used along with everyone being able to see the node's status. It seems to work well enough there, but I don't think that's what PerlMonks needs. This is a different kind of community and needs approirately different methods of voting/moderation.

Many types of forum software, Citadel and clones come to mind, allow logged-in users to post anonymously (often only in certain rooms where anonymity is more than usuallky important, such as sexual abuse survivor support rooms, bi/gay/lesbian rooms, embarrassing story rooms, etc.). The system and possibly the admins know who posted, but it's not attached to the post. The Citadel family of software in particular generally don't have voting on posts.

There are lots of models available, and more permutations I'm sure are out there. Even more than that are possible. But we must consider what's worthwhile and what's workable. This is not to mention what would majorly disrupt and what would not majorly disrupt the already successful system in place.

Update: fixed numerous tpyos.

---

---

• 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.