SWDTeam Forums

Welcome to the SWDTeam forums. Enjoy your stay!, Thank you for being part of our community!

[SWD Forums Suggestion] Improved Site Moderation, Thread Posting Permissions, Staff Management

In light of recent events of some users spamming the forums, this raises the importance of better moderation here on the SWD Forums. The below are suggestions that could be made to improve the SWD Forums.

 

 

User Posting Restrictions (Originally by Arcphoenix, expanded on by 50ap5ud5)

 

Description: Site Moderators and above will be able to restrict a user’s ability to create threads if they are repeatedly spamming.

 

Features: Site Moderators and higher site ranks will be able to:

 

Show content

  • Disable users from creating threads temporarily
  • Permanently disable users from creating threads
  • Disable users from commenting on existing threads
  • Disable users from editing their original threads

Justification:

In the scenario that a user is repeatedly breaking the forum rules and continuing despite many warnings, Site Moderators and above can prevent them from using the forums while still allowing them to access other parts of the site. This can allow for more flexible punishments without waiting for a Site Administrator to ban the user outright.

 

 

Deleted Threads will show in Thread history on User profiles

 

Background: In light of the spammer, brw88181, the user’s threads does not show up on their profile after deletion by Site Moderators. This can be a problem as this prevents staff from accessing the user’s misbehaviour history when discussing this with said user.

 

Before Deletion:

Show content

 

After deletion:

Show content

Description: All threads by a user will show in their profile. However only Site Moderators and above can read and edit these threads. The owner of the thread and other users will not be able to access the thread and instead be met with the existing error page.

 

Risks and Justification:

 

Show content

Justification:

Allows administrators to access user’s history much more easily, even when the thread has been deleted. This prevents tampering of evidence by the offender or other users.

 

Risks: This can cost SWD storage space if the user has a large number of deleted threads. The deleted threads will show in the User’s profile for 2 weeks, after which the thread will be truly deleted.

 

Site Staff can delete comments by users

 

Description: Site staff can delete a comment’s contents quickly when users continuously spam/post inappropriate comments on threads.

Site Admins can view these changes in the Admin Control Panel Audit Log, and restore the comment if deemed necessary

Justification:

Allows site staff to manage messages much more efficiently.

 


 

 

Admin Control Panel Addition: Moderator Audit Log

Description: Inspired by the Discord Audit Log, Site Admins (AKA SWDTeam members) can view all actions made by DMU staff and Site staff.

Specifications:

Show content

Perhaps a panel of some sort that can only be opened by Site Admins

This logger can list actions such as:

  • Pinning of Threads
  • Locking of Threads
  • Deletion of Threads
  • Deletion of Forum comments
  • Deletion of comments outside the forums. E.g. The ones on product pages
  • Change in a thread’s permissions (can be hidden to prevent spam haha)

 

REFERENCE:

Forum comments:

Show content

 

Non-Forum Comments: 

Show content

 

Justification: Allows Executive members to keep an eye on their staff and their actions.

This allows them to manage and review their staff’s actions so they may identify areas in which their staff needs to improve upon.

 

Site Moderator Addition: Forum Thread Audit Log

 

Description: Similar to the above, this logger allows Site Moderators to keep track and modify a thread or comment’s permission and history.

Specifications:

Show content

When clicking “Edit Thread” or “Edit Comment” on a user’s thread/comment, a Site Moderator is able to:

  • View the thread’s whitelist and blacklist permissions
  • Modify thread’s whitelist and blacklist permissions
  • View a thread’s history
  • View a comment’s history
  • Restore a certain version of a Thread/comment history

 

Mockup of Version History log:

Show content

 

Risks:

Show content

To reduce storage space, only the history of the thread/comment in the last 3 weeks can be seen. (So minor changes such as spelling corrections etc. won’t waste space) The rest of the thread’s history can still be accessed by Site Admins for another week. After the 4 weeks, the rest of the thread’s history will be deleted to conserver space.

NOTE: This risk analysis is still incomplete, feel free to make suggestions.

 

 


 

 

New Feature: Thread Permissions

User-Specific Whitelisting

 

Description: Allows thread owners to whitelist certain others to post or edit their thread

Specifications:

Show content

  • Thread owners can create a whitelist on a thread to only allow certain users to post a comment or edit in their thread.
  • Thread owners can allow certain users to edit their threads. All changes on the thread can be viewed in a changelog by the thread owner and Site staff.
  • This permission can be used by all users.
  • Site Staff can access these permissions by editing the thread, and make changes to the thread’s permissions

 

Justification: This can allow for threads which benefit from only the owner and trusted users from posting.

E.g. Tutorial threads, reference threads.

Sometimes random comments from users can clog up the thread and detract from the thread’s importance and purpose.

 

For instance, in my ban appeal reference thread:

Show content

 

Several users post irrelevant and unneeded comments on a thread.

Show content

 

As you can see this can frustrate thread creators. Instead, suggestions and feedback on informative threads can be made on the thread owner’s profile.

 

This also means Site Moderators don’t need to lock important threads. Since locked threads often imply that the thread is no longer of use, this permission can allow thread owner to draw attention to it and keep the thread organised and clean.

 

 

 

User-specific Blacklisting

 

Description:

Thread owners can create a blacklist on a thread to prevent certain users from post a comment in their thread

 

Justification: Can block certain users from posting comments on their thread.

E.g. If a user is harassing the thread owner, they can be blocked from commenting on the thread.

 

 


 

Forum-Specific Permissions

 

 

Description: Certain sections of the SWD Forums can have designated permissions on all threads that created.

 

Justification:

For instance, Ban Appeals and Reporting can have threads that use the User-Specific Whitelist permission to allow only the banned user, Site Staff and DMU Staff ranks to comment on the thread.

  • This can prevent other users from interjecting or causing confusion in these types of threads.
  • Instead, if a user wants to post in this type of thread (E.g. Another witness has evidence for staff in a ban appeal), their comment must go through approval by a Site Moderator before the comment is published.

 

Specifications:

Show content

A few suggested default permissions for certain sections:

 

Tutorials:

  • Whitelist enabled: Only Thread owner and Site Staff can post
  • Thread owner can allow other users to edit/post on the thread
  • Queries about the tutorial thread can be sent to owner’s SWD profile

 

Projects/Creations:

  • Open: All users may post here
  • Whitelist optional: Dictated by Thread owner. E.g. Group project thread can be accessed by those involved.

 

Ban Appeals/Reporting:

  • Whitelist enabled: Only Thread Owner, Site Staff, DMU Staff can post
  • Other comments must go through approval by Site Staff or DMU Staff

 

All others sections:

  • Open: All users may post here
  • Permissions optional: Site Staff can add whitelists or blacklists to certain threads

 

 

Please feel free to make suggestions and offer feedback!

 

 

 

 

These are great ideas, 50ap!! I support them, hope they get added!

You must be logged in to post.