17,366
edits
SmashWiki:Autoconfirmed users: Difference between revisions
no edit summary
(Undid edit by Black Vulpine: it doesn't change) Tag: Undo |
No edit summary |
||
| Line 9: | Line 9: | ||
*Editing semi-protected pages | *Editing semi-protected pages | ||
*Uploading files from a URL | *Uploading files from a URL | ||
*Uploading new versions of files | *Uploading new versions of existing files | ||
*Purging page caches without needing confirmation | *Purging page caches without needing confirmation | ||
==Autoconfirmed FAQ== | ==Autoconfirmed FAQ== | ||
| Line 19: | Line 17: | ||
;Q. What is the purpose of autoconfirmation? | ;Q. What is the purpose of autoconfirmation? | ||
:A. | :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 | :*The purpose of semi-protection is to disallow edits from anonymous and new users to combat vandalism or spam. | ||
:*Uploading images from a URL is generally unnecessary anyway, and makes it significantly easier to upload undesired images. | :*Uploading images from a URL is generally unnecessary anyway, and makes it significantly easier to upload undesired images. | ||
:*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. | :*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. | ||
:*Limiting cache purging is simply a MediaWiki default, likely done to prevent possible denial-of-service attacks by bots. | :*Limiting cache purging is simply a MediaWiki default, likely done to prevent possible denial-of-service attacks by bots. | ||
;Q. Why does the wiki require autoconfirmation to make new articles or overwrite existing images? | |||
:A. The wiki is fairly established in its content with an active userbase, so this helps to prevent spam, vandalism, and poor-quality pages. We want new users to familiarize themselves with our [[SW:POLICY|policies]] and the editing tools before diving-in to some of these more advanced tasks, and the autoconfirmed process is what allows us to set a minimum baseline. | |||
;Q. Can a user become autoconfirmed without making any edits? | ;Q. Can a user become autoconfirmed without making any edits? | ||
| Line 32: | Line 33: | ||
;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 | :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. | :A. Yes. You won't be able to create your RfA subpage or add it to the [[SW:RFA|requests page]] until you're autoconfirmed. | ||
==Established users== | ==Established users== | ||
{{shortcut|[[SW:ESTABLISHED]]<br | {{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: | '''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 everyone else 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 | |||
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}} | ||