Background
Recently, the state of the entire DevForum has declined drastically. Previously, closed-off areas of the forum were only accessible through post approval. However, over the past few months, categories that were once partially accessible have either been completely opened or absolutely locked down.
Having a small post approval team was effective when Roblox had a small DevForum. With the recent explosive growth, it is necessary to create a more scalable solution. Thus, creating a decentralized system of community moderation would limit low-quality content without restricting access to more commonly abused categories.
Solution
* implies that this value may be subject to change
In order for members to post a topic, 1 credit must be used. 1 credit can be earned by reviewing 5* topics (1/5* credit per topic). When a post is sent to approval, it will be reviewed by 5* different people. To start, everyone* will receive 1* credit, and the maximum amount of credits any one user can have at a time is 5* credits (which prevents people from hoarding credits to spam). Credits are private and serve only as a utility to control the flow of posts, not as a cosmetic forum stat.
For accountability, every user who reviews a topic and approves it is liable for any moderation action inflicted upon the original poster. This ensures that reviewers don’t just approve every topic to get posting credits. In addition, the queue would be strictly first-in-first-out to stop people from using alts or friends to falsely approve posts. To prevent changing a topic immediately after approval, editing will be restricted for 30-60* minutes depending on the category (i.e. #development-discussion would be less; #bug-reports would be more).
Depending on the outcome of the approval process the poster will either receive the anonymous feedback of the community members who reviewed the topic or a message stating the topic had been approved. However, no matter what the outcome, the posting credit is still consumed (i.e. you don’t get a refund if your topic fails). Also, as seen above, flagging an inappropriate unposted topic would be quick and easy, and doing so preemptively prevents the bad content from spreading to the wider Roblox community.
After a certain amount of topics correctly approved/successful posts, the member can be promoted to regular and not be subject to any posting limits. This framework provides a structure for members to police their own posts as well as advance to regular status and graduate from the system.
This system would be made possible by a custom plugin, similar to the bug report wizard or the old community post approval system, but with the addition of credits.
Arguments
This section will be updated as replies are added to the topic.
Pros
- Opens up formerly closed sections of the forum
- Provides a new system for promoting members to regulars
- Creates a sustainable cycle that discourages posting for the sake of posting
- Decreases workload for DevRel of moderating the current deluge of low-quality topics
- Increases the quality of posts by preventing bad content before it can be posted as opposed to trying to retroactively flag the bad content.
- Spreads the workload among thousands of users rather than a small group of volunteers.
Cons
- Requires significant work to set up
- Counter: DevRel has already shown they are willing to start large projects to improve forum quality. If they are in the research stages of such an undertaking, now is the time to suggest it before plans become more solidified.
- Depends on members being able to understand the rules
- Counter: Anyone who incorrectly approves or declines a post that successfully appeals will receive moderation action. This means that if a reviewer incorrectly approves/denies a topic, they will receive the appropriate moderation action (i.e. feedback → temp suspension → perm suspension).
- Counter: Posters who submit low-quality content will still receive feedback, but now from the community before the topic is posted rather than from the moderators after the topic is flagged.
- Counter: The number of reviewers can be increased for greater accuracy if necessary. However, at 5-10, a majority should still have some grasp of the rules. In addition, learning by reviewing is much less destructive than learning by doing.
- Creates a new credit system that could be confusing.
- Counter: The new system will be implemented in such a way that it will be obvious how to use posting credits. Here’s what it could look like:
- Counter: The tutorial could be updated to include information on posting. As players and now developers on Roblox, members should be familiar with virtual currency systems.
- Counter: The new system will be implemented in such a way that it will be obvious how to use posting credits. Here’s what it could look like:
- Friends could approve each other’s posts to bypass the system
- Counter: Whoever incorrectly approves a post that gets taken down will receive moderation action in addition to the OP.
- Counter: The chance of having 5* friends who would be able to refresh through the queue to find and approve your post is unlikely. With 1.2 topics being posted on average every minute, that creates a window of around 15 seconds where the topic has not been reviewed by anyone yet. As more legitimate users pull the topic from the queue from review, the lower the saturation of false reports.
- Counter: Measures could be added to prevent this sort of abuse, such as by limiting users to one topic pulled for review every 2-5 minutes. This also has the added benefit of decreasing the incentive to speed through reviews, because you would have to wait for the next one anyways.
- May expose normal users to offensive or inappropriate content.
- Counter: Malicious content already appears on the DevForum with the current system. Implementing this system would decrease its reach by limiting the audience to 5* reviewers. This may not completely eliminate harmful content but will represent an improvement.
Common questions:
What about regulars?
Regulars would not be subject to the post-approval system. Members could advance to regular through repeated successful posting in the system.
Why credits?
A credit system can operate on its own without having to burden a small team of volunteers, and has the benefit of being more sustainable.
Is there any particular reason behind the suggested numbers for reviewers/credits awarded?
Yes! By making the two values inverse (i.e. 5 → 1/5), it ensures that the input of 1 credit to pay for approval only outputs one collective credit to the reviewers.
Wouldn't this be some completely new system that should be suggested to Discourse?
First, the bug report wizard shows that DevRel can add new plugins to augment posting topics.
Second, this forum is very large and encompasses a very wide range of topics. Discourse is unlikely to add a native feature this large unless there is significant demand. At the moment, a plugin would likely arrive faster and be easier to tailor to the DevForum’s needs than a Discourse feature.
However, depending on the feedback on this topic, I may consider filing a separate Discourse feature request if the community supports the concept of a posting credit system, in order to get the process started.
What about replies?
Replying would not be affected by this system, only the creation of topics.
Which categories would be governed by the new systems?
This is up to DevRel to decide. However, all of the categories have been decreasing in quality lately.
Is this supposed to be a replacement for the flagging system?
No! This new system is meant to better control the incoming flow of topics and supplement the flagging system by creating preventative measures to decrease low-quality content.