-
Task
-
Resolution: Fixed
-
Normal
-
None
-
None
See https://community.metabrainz.org/t/ban-evasion-policy-addition-to-code-of-conduct/478148/2 and discussion at ORG-39. I suggest the passage in the MusicBrainz Code of Conduct about creating extra accounts for voting be amended to cover use of alternate/sockpuppet accounts for uses other than voting.
This change is imperative for MusicBrainz, but there is a high probability of the same issue coming up on other MetaBrainz projects, so I recommend similar language be adopted for them.
[ORG-40] Update wording of the MetaBrainz projects' Codes of Conduct
I’m currently considering either
Don’t abuse or game the systems. Use of sockpuppets, unauthorised bots, or other means of voting, editing, boosting ratings, or in other ways “gaming the system” is an abuse of the system and completely unacceptable.
or
Don’t abuse or game the systems. Use of sockpuppets, unauthorised bots, or other means of circumventing the intent or integrity of our projects is strictly forbidden.
I feel like the former is learning towards being too MusicBrainz specific, and the latter might be too vague… but I’m leaning towards the latter or something like that myself.
This doesn’t really cover what Yvan was touching on though, but I feel the essence of this is more the subject of gaming/circumventing the system (e.g., creating sockpuppets for boosting artist/release/recording ratings or voting edits through or running bots that boost listen counts in ListenBrainz) more than it is about preventing "technical abuse" such as (D)DoS’ing etc. Suggestions for how to include the latter in the former/the above welcome.
It could probably be generalized to “do not try to abuse system resources” especially when limited at purpose. Specific examples to be mentioned: creating multiple accounts (except if requested), tricking web service’s rate limit, flooding, …
Deployed.