More transparency around the admins and the hierarchy above it would be a good start, as would some kind of countervailing pressure to the ballooning of meta rules (bylaws). For instance:
- Oppose the "Super Mario" effect: if admins do something ordinary users would get banned for, they get banned too, they don't just lose their admin title.
- Implement restrictions on Arb Com to make it worthy of its "supreme court" moniker. Provide prior notice, allow representation, access to evidence ahead of the case, and require the Arb Com to disclose the logic of any automated scripts they use for mass judging (e.g. counting proportion of edits being reverts, or that counts every change to a reference as "reference vandalism"). Grant defendants the ability to force the Committee's judgment to be disclosed to the public, with PII redacted if necessary.
- Require that precedent be recorded for unclear meta rules: what counts as a violation of e.g. canvassing? When do reversions become evidence or proof of "ownership"?
- Create an independent appeals body for Arb Com decisions. Like the Arb Com itself, the logic or source code for any scripts they use to aid their decisions, should be public. Ideally, choose the independent appeals body by different means than the Arb Com itself is chosen, e.g. by random selection of users with a certain activity level, independent of the ordinary admin track.
- Grant all users the right to be forgotten (courtesy vanishing), not just users in good standing, so that users bullied off the platform can remove their proverbial stockade.
- Create a mechanism that forces rules to be refactored or reduced in scope. Just spitballing, one possible way might be to limit the growth of any given WP: page per unit time, require negative growth for some of them, or in some way reward editors who reduce their extent.
There may be fundamental unsolvable problems, but that doesn't mean the current system can't be improved.
Not when someone with connections and better knowledge of the WP bylaws weaponizes the Arb Com against you.
Here are some of the things you can get banned for:
- Having a too large fraction of your edits be reverts.
- Updating raw references to <ref cite> references (without changing the contents of the reference).
- Saying something on a forum that could be construed as telling people to edit a particular article in a particular way.
The Arb Com doesn't have to open up a public discussion about the matter. They can simply pronounce judgment in private and ban you. There's no prior notice, no representation, and no independent appeal. For a "supreme court", that's quite a low bar.
- Oppose the "Super Mario" effect: if admins do something ordinary users would get banned for, they get banned too, they don't just lose their admin title.
- Implement restrictions on Arb Com to make it worthy of its "supreme court" moniker. Provide prior notice, allow representation, access to evidence ahead of the case, and require the Arb Com to disclose the logic of any automated scripts they use for mass judging (e.g. counting proportion of edits being reverts, or that counts every change to a reference as "reference vandalism"). Grant defendants the ability to force the Committee's judgment to be disclosed to the public, with PII redacted if necessary.
- Require that precedent be recorded for unclear meta rules: what counts as a violation of e.g. canvassing? When do reversions become evidence or proof of "ownership"?
- Create an independent appeals body for Arb Com decisions. Like the Arb Com itself, the logic or source code for any scripts they use to aid their decisions, should be public. Ideally, choose the independent appeals body by different means than the Arb Com itself is chosen, e.g. by random selection of users with a certain activity level, independent of the ordinary admin track.
- Grant all users the right to be forgotten (courtesy vanishing), not just users in good standing, so that users bullied off the platform can remove their proverbial stockade.
- Create a mechanism that forces rules to be refactored or reduced in scope. Just spitballing, one possible way might be to limit the growth of any given WP: page per unit time, require negative growth for some of them, or in some way reward editors who reduce their extent.
There may be fundamental unsolvable problems, but that doesn't mean the current system can't be improved.