Allowing multiple accounts to edit PvXwiki from a shared IP address raises the natural question of biased voting and sock-puppetry. If the accounts are in fact created by a number of distinct users they are likely either related to each other or friends with each other which leads to biased voting, the practical equivalent of sock-puppetry. However, there is also nothing to prevent a single user from creating multiple accounts and claiming that those accounts are controlled by his friends or family members. On the other hand, there is nothing wrong per se with two family members creating distinct accounts and editing. Thus, rather than seek to limit the number of account per IP address, this policy seeks to address the question of what should be done in cases where a number of accounts sha
| Attributes | Values |
|---|
| rdfs:label
| |
| rdfs:comment
| - Allowing multiple accounts to edit PvXwiki from a shared IP address raises the natural question of biased voting and sock-puppetry. If the accounts are in fact created by a number of distinct users they are likely either related to each other or friends with each other which leads to biased voting, the practical equivalent of sock-puppetry. However, there is also nothing to prevent a single user from creating multiple accounts and claiming that those accounts are controlled by his friends or family members. On the other hand, there is nothing wrong per se with two family members creating distinct accounts and editing. Thus, rather than seek to limit the number of account per IP address, this policy seeks to address the question of what should be done in cases where a number of accounts sha
|
| dbkwik:pvx/property/wikiPageUsesTemplate
| |
| abstract
| - Allowing multiple accounts to edit PvXwiki from a shared IP address raises the natural question of biased voting and sock-puppetry. If the accounts are in fact created by a number of distinct users they are likely either related to each other or friends with each other which leads to biased voting, the practical equivalent of sock-puppetry. However, there is also nothing to prevent a single user from creating multiple accounts and claiming that those accounts are controlled by his friends or family members. On the other hand, there is nothing wrong per se with two family members creating distinct accounts and editing. Thus, rather than seek to limit the number of account per IP address, this policy seeks to address the question of what should be done in cases where a number of accounts share a single IP address. The idea is to allow multiple users to share an IP (and to allow them to do so without raising questions of sock-puppetry) while still limiting the possibility of actual sock-puppetry. The actual solution is relatively simple. While a number of accounts may edit PvX from a shared IP address, they may not vote on builds which another user who shares their IP has created.
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)