This high-risk/high-traffic page is protected.

SmashWiki:Autoconfirmed users: Difference between revisions

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
(Creating new pages has never been an ‘always’ restriction for autoconfirmation. It only becomes a restriction when we are in yellow or red status.)
 
(35 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{policy}}
{{ArticleIcons|protected=highrisk}}{{Policy}}
{{shortcut|[[SW:AUTO]]}}
{{shortcut|[[SW:AUTO]]}}
'''Autoconfirmed users''' are defined as [[SmashWiki:Users|users]] who have had an account on the SmashWiki for at least seven (7) days and have made at least ten (10) edits. New users gain certain rights upon becoming autoconfirmed.
'''Autoconfirmed users''' are defined as [[SmashWiki:Users|users]] who have had an account on SmashWiki for at least seven (7) days since their first edit and have made at least ten (10) edits total. New users gain certain rights upon becoming autoconfirmed.


The rights that are gained upon being autoconfirmed are:
The rights that are gained upon being autoconfirmed are:
*Moving pages and files
*Editing semi-protected pages
*Uploading files from a URL
*Uploading new versions of files
*Purging page caches without needing confirmation


In addition, if the wiki is in a heavily active state (such as surrounding the release of a new game or a new DLC character), the creation of new pages and uploading any images may also be restricted to autoconfirmed users. The wiki '''is currently''' in this state.
*Being able to create non-discussion pages
*Being able to [[SW:MOVE|move personal userspace pages, smasher/team pages, and files]]
*Being able to [[SW:PROT|edit semi-protected pages]]
*Being able to [[SW:IMAGE|upload files]]


==Autoconfirmed FAQ==
==Autoconfirmed FAQ==
Line 17: Line 15:


;Q. What is the purpose of autoconfirmation?
;Q. What is the purpose of autoconfirmation?
:A. While SmashWiki believes that accountless users and new users have the right to contribute as any other user, there are certain abilities that we choose to restrict for the purposes of security against vandalism and spam. Specifically:
:A. We restrict these abilities for the purposes of security against vandalism and spam. Specifically:
:*Moving pages and files can be burdensome to undo even for admins.
:*Moving pages and files can be burdensome to undo even for admins.
:*The purpose of semi-protection is to disallow edits from accountless and new users to combat vandalism or spam.
:*Deleting pages and files require admin intervention, the process of which is more time-consuming than reverting bad edits.
:*Uploading images from a URL is generally unnecessary anyway, and makes it significantly easier to upload undesired images.
:*The purpose of semi-protection is to disallow edits from anonymous and new users to combat vandalism or spam, or otherwise limit nonconstructive edits to pages covering contentious subjects and pages that require expertise to edit.
:*While the most important images are often protected, uploading new versions of images can be abused by new-account vandals to quickly insert unwanted images into multiple pages.
:*Unwanted images have a greater potential for harm than text-based vandalism, and so it's in the wiki's best interest to lock image uploading behind a barrier that most bad faith actors will not surmount.
:*Limiting cache purging is simply a MediaWiki default, likely done to prevent possible denial-of-service attacks by bots.
:*While the most important images are often protected, uploading new versions of existing files can be abused by new-account vandals to quickly insert unwanted images onto a multitude of pages.
 
;Q. Why does the wiki require autoconfirmation to create new articles?
:A. The wiki is fairly established in its content with an active userbase, so this helps to prevent vandalism, spam, and policy-breaking pages. We want new users to familiarize themselves with our [[SW:POLICY|policies]] and editing tools before diving-in to the advanced task of article creation, and the autoconfirmed process is what allows us to set some kind of baseline.


;Q. Can a user become autoconfirmed without making any edits?
;Q. Can a user become autoconfirmed without making any edits?
Line 30: Line 31:


;Q. Do users have to be autoconfirmed to be given [[SW:RBACK|rollback]]?
;Q. Do users have to be autoconfirmed to be given [[SW:RBACK|rollback]]?
:A. No. If one makes enough valid reverts within one's first week to create and pass an [[SW:RFR|RfR]], there is no reason to withhold the position.
:A. No. If one makes enough valid reverts within their first week to create and pass an [[SW:RFR|RfR]], there is no reason to withhold the position.


;Q. Do users have to be autoconfirmed to be promoted to [[SW:ADMIN|administrator]]?
;Q. Do users have to be autoconfirmed to be promoted to [[SW:ADMIN|administrator]]?
:A. Not technically, but it is virtually certain that a user who has yet to be autoconfirmed cannot have the experience and community support to feasibly run a successful [[request for adminship]].
:A. Yes. You won't be able to create your RfA subpage or add it to the [[SW:RFA|requests page]] unless you're autoconfirmed.


;Q. Why does the wiki require autoconfirmation to make new pages or upload images?
==Established users==
:A. Usually, we allow accountless users and new users to do these things. However, there are times when traffic is high enough that two things happen: we have enough autoconfirmed users active to handle new pages and images, and the risk of vandalism by abusing these abilities increases. Once activity dies down, these abilities will be "unlocked" once more.
{{shortcut|[[SW:ESTABLISHED]]<br>[[SW:EST]]}}
'''Established users''' are a step up from autoconfirmed users, requiring an account age of ninety (90) days since their first edit and a total of a hundred (100) edits. Established users have two additional permissions: moving pages without restriction and editing pages under established-protection. This allows more granular control over how pages are protected:


==Established users==
{{shortcut|[[SW:ESTABLISHED]]<br/>[[SW:EST]]}}
'''Established users''' are a step up from autoconfirmed users, requiring an account age of ninety (90) days and a total of a hundred (100) edits. Established users have a singular additional permission: editing pages under established-protection. This allows more granular control over how pages are protected:
*Pages that can be edited by anyone
*Pages that can be edited by anyone
*Pages that new users and IPs cannot edit, but everyone else can (used as a simple anti-spam or anti-vandalism measure)
*Pages that new users and IPs cannot edit, but autoconfirmed users can (used as a simple anti-spam or anti-vandalism measure)
*Pages that only users with a fair amount of experience can edit (used on pages that are nice for non-staff to edit but too complex/important for newer editors, or pages where autoconfirmed-protection against vandalism has proven ineffective)
*Pages that only users with a fair amount of experience can edit (used on pages that are nice for non-staff to edit but too complex/important for newer editors, or pages where autoconfirmed-protection against vandalism has proven ineffective)
*Pages that only staff may edit (used for pages too important to leave open)
*Pages that only staff may edit (used for pages too important to leave open)
As with autoconfirmed, users cannot skip ahead to obtaining the permission, and it is not a requirement to be given rollback or administrator status.
 
As with autoconfirmed, users cannot skip ahead to obtaining the permission. It is not a requirement to be given rollback or administrator status.


{{Helpnav}}
{{Helpnav}}

Latest revision as of 01:48, April 18, 2023

Policy.png This page documents an official SmashWiki policy, a widely accepted standard that all users should follow. When editing this page, please ensure that your revision reflects consensus. If in doubt, consider discussing changes on the talk page.
Shortcut:
SW:AUTO

Autoconfirmed users are defined as users who have had an account on SmashWiki for at least seven (7) days since their first edit and have made at least ten (10) edits total. New users gain certain rights upon becoming autoconfirmed.

The rights that are gained upon being autoconfirmed are:

Autoconfirmed FAQ

Q. What rights do new users have?
A. New users have all the same rights as autoconfirmed users except for those listed above.
Q. What is the purpose of autoconfirmation?
A. We restrict these abilities for the purposes of security against vandalism and spam. Specifically:
  • Moving pages and files can be burdensome to undo even for admins.
  • Deleting pages and files require admin intervention, the process of which is more time-consuming than reverting bad edits.
  • The purpose of semi-protection is to disallow edits from anonymous and new users to combat vandalism or spam, or otherwise limit nonconstructive edits to pages covering contentious subjects and pages that require expertise to edit.
  • Unwanted images have a greater potential for harm than text-based vandalism, and so it's in the wiki's best interest to lock image uploading behind a barrier that most bad faith actors will not surmount.
  • While the most important images are often protected, uploading new versions of existing files can be abused by new-account vandals to quickly insert unwanted images onto a multitude of pages.
Q. Why does the wiki require autoconfirmation to create new articles?
A. The wiki is fairly established in its content with an active userbase, so this helps to prevent vandalism, spam, and policy-breaking pages. We want new users to familiarize themselves with our policies and editing tools before diving-in to the advanced task of article creation, and the autoconfirmed process is what allows us to set some kind of baseline.
Q. Can a user become autoconfirmed without making any edits?
Q. Can a user become autoconfirmed in less than seven days?
Q. Can users bypass autoconfirm?
A. No. All users must pass both parts of the autoconfirm criteria with no exceptions.
Q. Do users have to be autoconfirmed to be given rollback?
A. No. If one makes enough valid reverts within their first week to create and pass an RfR, there is no reason to withhold the position.
Q. Do users have to be autoconfirmed to be promoted to administrator?
A. Yes. You won't be able to create your RfA subpage or add it to the requests page unless you're autoconfirmed.

Established users

Established users are a step up from autoconfirmed users, requiring an account age of ninety (90) days since their first edit and a total of a hundred (100) edits. Established users have two additional permissions: moving pages without restriction and editing pages under established-protection. This allows more granular control over how pages are protected:

  • Pages that can be edited by anyone
  • Pages that new users and IPs cannot edit, but autoconfirmed users can (used as a simple anti-spam or anti-vandalism measure)
  • Pages that only users with a fair amount of experience can edit (used on pages that are nice for non-staff to edit but too complex/important for newer editors, or pages where autoconfirmed-protection against vandalism has proven ineffective)
  • Pages that only staff may edit (used for pages too important to leave open)

As with autoconfirmed, users cannot skip ahead to obtaining the permission. It is not a requirement to be given rollback or administrator status.