
User rights resources


Atx playericon holiday 15.png

This is a guide for content moderators at Nukapedia. A content moderator is a user rights role that is granted upon successfully applying for and passing a community vote. The following will outline new tools and responsibilities for content moderators.

Content moderator 101

Atx playericon perks 13.png

Content moderators, or "comods," are important members of the staff, helping to ensure the integrity of the information presented to users. Beyond basic editing tools, content moderators put the finishing touches on articles to make them as tidy as can be. This role grants access to additional technical features that will aid in article maintenance and are a reflection of becoming a trusted member of the community.

Review

At each progressive level of user rights, each staff members is still responsible for carrying out their former roles as well, both to help and to be good examples for those with varying levels of rights. Below is a brief review of these responsibilities.

Tools and options

TIW Patroller example 4.png

The "rollback" option immediately reverts back to the previous version without the option to leave an edit summary, used primarily for acts of vandalism. Please read FDekker's guide to Reverting Responsibly for more information on the topic.

The "undo" option is preferred in all other cases, which will revert the edit, but allow the option to add an edit summary before "undo revision by" in the edit summary box. Each staff member must always explain reverts in a polite way, as this is an important teaching moment for those who may not be familiar with the policies.

Marking as patrolled

Lastly, selecting "mark as patrolled" is required no matter what decision a staff member comes to. This communicates with the rest of the group that it has already been reviewed. One can find the option to mark as patrolled at the top and bottom of the page. New pages can only be patrolled via the bottom of the page option. Sandbox, user and talk pages should still be reviewed and patrolled to ensure no vandalism has taken place.

New tools

Beyond those tools granted at the patroller level, content moderators can protect and delete articles and modify images. The new role requires more knowledge of the policies and guidelines that govern the actions of staff, and may require more user interaction, providing guidance to those who may not yet be aware of these policies.

Modifying images

TIW comod edit button example.png

In line with the image policy, images should be of good quality, have a descriptive name, and should not include parts of the UI (HUD, crosshair) unless the point of the given image is to illustrate the UI itself. Part of the content moderator role is reviewing the images that are uploaded. By reviewing the new files page, one can see each new image, if it has been added to a page and its name.

In addition, one can click on the image to double-check if it has been added to an appropriate category and to review if it is located on more than one page. This is important when renaming or deleting an image. Images should always be salvaged if possible. If a minor HUD is showing, consider saving the image to the desktop, doing a minor edit via whichever photo editing software or site is preferred to remove the crosshair, and reuploading. If an image is a strange aspect ratio, consider doing the same.

Reuploading can be accomplished via the "file history" tab, under the image or via the green "edit" button in the top right of the screen. It replaces the image anywhere it exists, so one doesn't have to do it manually on each article. Sending a talk page message to the individual who added it can help teach them how to remove the HUD for future pictures (on PC, console command tm).

Deleting an image

To delete an image, whether it has been replaced by a better one or does not meet the quality criteria, click on the green "edit" button in the top right of the screen. Now one will see the option to "delete." Unlike replacing, the image must be manually deleted from each page it appears. If the image is new, consider sending a talk page message to thank the contributor and teach them about what an optimal image looks like, so their future images will be in line with the policy and they will not be discouraged by their contribution's deletion.

TVA Global image example.png

Similarly to deleting an image, renaming one will require finding where the image is already located, to replace the old name with the new name. In addition, make sure that the image is not used by Fallout wikis in other languages. You can click the "show usage" button under global heading to see if this is the case. Before deletion, shared images will also result in a prompt alerting you to the shared use. In these cases, the other wikis need to be updated as well, whether it be by replacing or deleting the equivalent image. Do not use the redirect option for images.

Format

The format should be:

Game abbreviation + Content + Description (if needed).png

an example being

FO76 Traffic cone Silver Bridge.png

Renaming may be the most frequent modification made to images, simply because the users are not familiar with the format in which to name images. Such as the other cases, sending the user a talk page message to teach them the naming structure will ensure future images will be named correctly.

Modifying articles

Atx playericon perks 11.png

The process is the same for deleting images, with just a small difference in option screen and accounting for redirects. Accomplished the same way, via the green edit dropdown, selecting "delete" and making one's choices on the following page. You can enter your reason from the drop down, leave any comments needed and click delete. A deletion log can be seen here as well, showing any decisions or changes made in the past.

Merges

If an article has been merged to another, we do not delete it, we will instead leave a redirect to the new page. Instructions for redirects can be found here. In the case of deleting any article, one should always make sure that nothing currently links to that article. This is done by using the "what really links here" tool at the bottom of the page. Instructions for adding this gadget and using this tool can be found here.

If a redirect is "empty" or is no longer used, do not delete it. Leaving it will help to avoid redundancy, alerting any future user if they try to create a new article with this name.

Deleting outright

TIW comod delete article example.png

Sometimes a page will be made with vandalism or spam, this can be outright deleted. Sometimes a page will be created that appears as if a user is trying to make the equivalent of a user page. This is not vandalism but comods should copy and paste the information to the individual's user page and then can delete the mainspace article. Afterward, head to the user's talk page and leave them a note, welcoming them to Nukapedia and directing them to their own user page to customize it as they see fit, with a note on how to create a sandbox if so inclined.

Nominate template

Users may utilize the nominate for deletion template, which is written as {{delete|reason for deletion}}. This gives the message to others that they believe it is a candidate to be deleted, and for what reason. Content moderators can use their best judgment when reviewing these, ensuring that it is accurate, or taking steps to merge with another article first and leaving a redirect instead. Talk pages should always be utilized for discussing deletions beforehand, except in cases of vandalism. Those articles that have been nominated for deletion will appear in the nominated for deletion category.

Protecting pages

Atx playericon perks 14.png

Protecting pages is an important part of content moderation. It is covered under the administration policy.

Policy

Most pages should remain unprotected and allow editing by both anonymous and registered users. Protection is generally only applied to:
  • Critical parts of the site. This includes pages like the main page or widely used templates.
  • Articles that are frequent targets of vandalism.
  • Pages which are the "battleground" for an edit war. If a set of editors repeatedly reverts each other's changes, an administrator may protect the page to encourage them to resolve the dispute in a different manner (i.e. by discussion as appropriate).
  • User pages may be protected at the request of the respective user.

In general, page protection should only be applied as long as necessary. Articles especially should only be protected for a reasonably short timeframe (one week maximum).

Process

TIW comod protect page example.png

If one notices an edit war occurring, or vandalism of a page, protecting it is a good way to either fix and prevent damage or to allow users to pause, encouraging them to resolve the dispute via article talk page or user talk page. A patroller or user may ask for help if they are dealing with these issues.

Head to the article, and then select the green edit dropdown to "protect." It will point to a screen to review options. In cases of vandalism by an anonymous user, one can choose "block new and unregistered users" and then a duration of time. This is up to each individual rights holder, but should be as short as possible. The rights user can select from the drop down choices or choose their own duration, selecting "other time" and then writing it in the box (for example, 3 days).

The first box is for restricting editing the article and the second box is restricting moving/renaming the article. Make sure the intended box is utilized (one or both). Choose a reason from the dropdown at the bottom and any comments as needed, and click "confirm."

Edit warring

Atx playericon perks 10.png

A brief aside about edit warring, which is explained in the user conduct guidelines. It is defined as a breach of the three revert rule as follows:

An editor must not perform more than three reverts on a single page—whether involving the same or different material—within a 24-hour period. An edit or a series of consecutive edits that undoes other editors' actions—whether in whole or in part—counts as a revert.

For articles in which users are repeatedly overriding each other's contributions, protecting it can stop the bleed and allow time for conversation. Select "administrators and content moderators only" and choose a duration (up to one week, generally). One can then enter the reason as mentioned before. No matter what duration or reason, protections will automatically end when scheduled, so users do not have to manually unprotect it. A comod or admin can unprotect it before the duration is over, via the green edit dropdown, selecting "unprotect" and then changing it back to "allow all users."

Edit warring can be a touchy subject, and it is always good to leave a polite message on each user talk pages, explaining the policy on edit warring, that the page has been protected, and encouraging the users to talk it out on the article talk page or the other individual's user talk page. The faster staff members intervene with communication and action, the better the outcome.

In cases where edit warring is occurring between rights holders, or if for any reason something is happening that may need additional attention, please feel comfortable reaching out to one of the administrators or bureaucrats for assistance, we are all here to help.

Contacts

the gang's all here

That being said, if there are ever issues or assistance needed, the rest of the staff members are here to support you. Feel free to ping us on the Nukapedia Discord server or write us messages on our talk pages at any time. You will receive access to the #security-desk Discord channel, and if not, let one of us know so we can set it up. In addition to the general channel (#the-editorial-bullpen), this channel can be used to discuss issues or questions with other rights users only and can be used if something requires swift action, such as if someone needs help protecting an article from vandalism.

Remember to communicate and always assume good faith, or in other words, always assume that someone is trying to help, but may not know how best to do so. We were all new at one point or another. You can review the policies anytime, including the resources below. The time and effort each staff member dedicates to Nukapedia is appreciated and valued, and we thankful and excited to have you on the team. Welcome!

Resources

Resources
Community content is available under CC-BY-SA unless otherwise noted.
https://fallout.fandom.com/wiki/Fallout_Wiki:Content_moderator_guide
fallout.fandom.com
crawl=CC-MAIN-2021-39
224767
application/http; msgtype=response
sha1:XLPUKLW3Q5Y5VZN4PMPDPHMKBPJ7W5TV
<urn:uuid:d7c3f978-d2a5-4ef8-ad5f-883b69201c36>
2021-04-18T17:06:11Z
151.101.192.194
text/html
sha1:TO3LKW6YQGVFNAEYMRINXD2GOGVCWXGN
<urn:uuid:614b6109-4ad1-4160-84e0-0210d26464c0>
https://fallout.fandom.com/wiki/Fallout_Wiki:Content_moderator_guide
response
<urn:uuid:7fe5ef02-6765-48ce-9275-984df34e350f>
isPartOf: CC-MAIN-2021-17
publisher: Common Crawl
description: Wide crawl of the web for April 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-191.ec2.internal
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/