The problem

Almost three years ago we introduced Abilities to Codidact as an improved system for granting activity-based permissions, such as allowing users who have made consistently great edit suggestions to edit posts without requiring approval. I'll defer to the linked posts on how Abilities function in detail.

I do still believe that coupling permissions with specific experience in the area of the permission is a good idea and should be kept as the basic premise of the permission system.

However, there are a three major issues I see with how our abilities system works currently:

1. The Ability thresholds are calculated using the Wilson score formula we use for posts. This means, that the minimum number of (positive) actions needed and the minimum percentage of positive actions are directly coupled.

   In some cases this coupling can be inappropriate for the intended purposes. For example, a community might want a user to have suggested many edits to demonstrate experience but want to require only an average approved percentage of like 75%. In our current system this would not be possible.

   In some cases communities might want the opposite. They would want a high percentage of 95% edits approved, but because they have low activity they only want a small sample of 5 edits (which would of course mean that once one edit is rejected your amount of edits that need to be approved would rise drastically). This would also not be possible with the current system.

2. Currently abilities are directly coupled with permissions. This means, that the system will check whether or not you have a certain ability and will infer your permission from this. This becomes a problem once a permission should be inferred from multiple abilities, because then the every time a permission is checked the code would have to keep in mind how exactly abilities bind to permissions, and if multiple permissions are coupled into one ability, because they are then affixed together as an all-or-nothing thing. However one might want to separate permissions from another for moderation purposes. A user might need to be banned from reviewing edits while their power to edit posts should not be restricted.

3. The current system is based on specific existing abilities hard-coded in the application. However communities might want to change the ability progression to better match their individual needs.

A solution?

Therefore I am proposing some tweaks to how abilities are implemented:

1. There are two factors: "privileges" and "abilities" (or "trust levels").

2. Privileges are technical allowances, such as "may edit other people's posts without review", "may review suggested edits" or "may vote to close". A user can have or not have a privilege at any time.

3. Abilities are steps on the progression ladder. Technically an ability consists of one or multiple privileges and a "win condition". If you earn an ability, you will be granted the privileges it contains.

4. Privileges can be individually suspended by moderators (as abilities can be suspended for time/infinity right now). Abilities cannot be suspended because the only thing that goes beyond suspendable privileges are "bragging rights".

5. Abilities are reached when its win condition is reached. A win condition may consist of multiple requirements, each of which must be completed. Requirements could be, for example,

   • minimum user age
   • obtaining a specific ability
   • minimum post count
   • minimum positively received post count
   • minimum percentage of posts positively received
   • minimum (suggested) edits
   • minimum approved/applied edits
   • minimum percentage of suggested edits approved
   • minimum flag count
   • minimum helpful flag count
   • minimum percentage of helpful flags
   • minimum close/delete votes
   • minimum effective close/delete votes
   • manual appointment (i.e. this ability can only be awarded manually)

As before, moderators would have all such privileges.

Something similar to the current ability progression should be set as standard, so that we have an ability trees not unlike this:

• everyone (general path)
  • established user (general path)
    • editing posts (edit path)
      • editing tags (edit path)
    • closing posts (mod path)
      • deleting posts (mod path)
  • moderators

However communities would be free to change this progression as they like.

I think that these tweaks would allow better bootstrapping of communities and would allow it to better react to community size with configuring the ability system.

Discussion

What do you think? Do you have any other ideas on how to improve abilities?

posted over 1 year ago

CC BY-SA 4.0

luap42‭ staff

17 68 568 98