Help:Pseudo Personal Space Protocol
From SpiralKnights
This page is a subpage of the Style Guide.
Introduction
This protocol describes how users should behave when editing "pseudo personal space" that is not associated with their account.
Certain changes have to be made to maintain the wiki project. Edits are considered justified if they are in accordance with this protocol.
The following are considered to be pseudo personal space:
- Any pages and subpages in the Userspace (does not include User talk)
- Pages with (Guild) in the title. See Category:Guilds.
- All other pages, entities, and/or namespaces are not considered by this protocol.
Considerations
Before editing, be sure another user is not actively working on a page to avoid edit conflicts. A safe bet is to see if a user has not edited the page for at least 24 hours.
It is best to avoid disrupting the "look" of the user's page. Instead of replacing the issue with empty space (removal), update the page with the most current linking, file, etc. so the page appears to be unchanged. Sometimes conflict and/or effort is too great, so removal of the issue is an appropriate solution.
Before saving changes, remember to provide a concise description in the summary box. Always refer to the appropriate section(s) in this protocol - this will likely suffice as the edit summary.
Reasons to Edit
Procedure(s):
- Replace all content with {{delete}}-spam. An admin will eventually ban the associated user.
Explanation:
- This behavior takes advantage of hyperlinking to increase hits in search engines by using the wiki's hosting space. This is essentially advertising the spammer does not have to pay for and is considered harmful to the wiki project.
Examples on this Wiki:
- Special:Log/block search for spamming links to external sites
- Special:Log/delete search for Vandalism: content was (not all deletion logs with this summary pertain to spam)
Citation:
Several of these reasons are similar to other reasons listed in this protocol. They differ because they are specifically concerned with the mainspace, as well as requiring slightly different procedures and considerations.
Procedure(s):
- Remove usage of the file(s). This can be done by completely removing file usage, or replacement with acceptable names.
- Add {{delete}} to the bad file(s).
Explanation:
- Users can edit pseudo personal space in order to remove usage of a file if the file interferes with the wiki project. A file interferes with the wiki project if it is a low quality duplicate of a file functioning in the mainspace, has a name that is inconsistent with an ideal naming system in the mainspace, or has a name that is far too similar to other files in use. A file is also harmful to the wiki project if it brings the project into disrepute or reveals content that has not been released. Bad files have to be deleted in order to prevent confusing propagation around the wiki for various technical reasons. Bad files are eventually deleted by admins, but this can only be formally done if the file is not in use, hence the need for editing.
- This does not pertain to correctly named files. If these are low quality or out of date, simply upload a new version - but only if the file is used in the mainspace. Files that seem to be for exclusive use in pseudo personal space should not be tagged for deletion unless they bring the project into disrepute or break ToS.
Examples on this Wiki:
- Admin: do not upload duplicates of files that already exist
- Admin: "correct the name in whatever pages the 'bad' name linked to"
Citation:
- Wikipedia: When to tag files for deletion (emphasis on low quality)
- Wikipedia: Images that would bring the project into disrepute
- Wikipedia: Duplicate files are bad
- (because this is a gaming wiki, we have to make certain exceptions, in case visuals are updated to be specific - this happened with costume icons. Each entity gets its own associated images, even if these images are the exact same as others. This is the case with several stats, ability, and accessory icon images. This protocol does not consider these mainspace issues).
Procedure(s):
- Remove usage of the entity if conflict is too great.
- Replace templates with User-Specific Template with specialized switches if necessary so desired format is retained.
- Adjust coding of template with a switch, then edit the user page so category=no.
- Fix navigation content which registers as Double Redirects or broken redirects by linking to the final destination.
Explanation:
- Inappropriate: In order to maintain high quality navigation of a wiki so that users may find content easily by searching, using "go," or using categories, pseudo personal space should not register for said navigation. This sometimes occurs due to templates.
- Distracting: Edits should be made in order to retain the functionality of special pages such as Special:WantedFiles. We cannot isolate the function of these "Special:" pages to a specific namespace. There are several solutions in place (see Things to do), but the best solution is to remove the call from the page by either editing a relevant template with a switch or deleting the call. Unless requested, it is inappropriate for a user to upload an image for specific use by another user in pseudo personal space.
- Out-of-Date: Sometimes, we make a better template system, or fuse templates together, or require the use of an older template with a name that's currently in use to be consistent with other templates. This most often occurs with Linking Templates. Editors may change pseudo-personal space in order to prevent the template changes from making pages that use the "out-of-date template(s)" fall apart - the example below is the best solution for this, besides removal.
Examples on this Wiki:
Citation:
Procedure(s):
- Remove the issue.
- Add {{delete}} if necessary. This might be needed for files or inappropriate page titles, etc.
- Notify an admin immediately through the support portal.
Explanation:
- This usually consists of swearing, offensive content, links to offensive content, and uploading unreleased content obtained from the files or an external program such as spiral spy.
Examples on this Wiki:
- notifying an admin via talk page (it would likely be faster to use the support portal)
- Special:Log/block search for vandalism
Citation:
Procedure(s):
- Move content to the user's page. Access the user's page by viewing history and clicking the contributor's name. You might have to create the page with this content.
- Add {{delete}} tag to redirects of user pages to other user pages.
- Add {{delete}} tag to redirects of user names in inappropriate namespaces to user pages.
Explanation:
- User pages and subpages simply do not belong outside of the userspace in any way.
Examples on this Wiki:
- A warning that shows above the edit window under certain circumstances:
User account "NAME" is not registered. User pages need to be created under the account name, NOT the knight name. Pages for non-existent account names will be DELETED.
Citation:
Procedure(s):
- Move content to NAME (Guild) with the "move" command (don't simply copy/paste content into the target page)
- Add [[Cateogry:Guilds]] to bottom of page if it doesn't already appear (many templates automatically add categories).
- If the guild is retired, or "dead," add [[Cateogry:Guilds|retired]] to bottom of page. Only do so if format suggests the guild is dead - the creators and/or current editors of the page have blanked it, or stated as much somewhere on the page. It must be obvious via edits on the page, not an observational opinion of activity in-game.
Explanation:
- Guild pages need to be organized and fundamentally formatted in this manner so they can easily be found. They are otherwise free format.
Examples on this Wiki:
Citation:
Procedure(s):
- Move content to appropriate page(s), or paste content under the content of existing page(s) so work is not lost.
- Add {{delete}} to pages associated with duplicate account(s).
- Discuss the issue on the user's talk page (the talk page that seems to be their main. Determine this by timestamp of contributions. Often a user will simply be editing a page named after their knight due to steam account problems - this is more of a section 2.4 issue and the user should be encouraged to contact support).
- Notify an admin if the user seems suspicious of sock puppetry.
Explanation:
- On this wiki, we maintain one account per person. Multiple accounts make communication via talk pages difficult and might have a role in ban evasion.
Examples on this Wiki:
- Special:Log/block and search for Abusing multiple accounts.
Citation:
Procedure(s):
- Investigate the issue.
- If needed, restore the page to an untouched version via page history.
Explanation:
- It is unacceptable to harm the wiki in any way. User pages are part of the wiki, so it is unacceptable to harm them.
- The malevolent edit must be obvious. There might be an inside joke between guild members editing their guild page which seems similar to vandalism, for example. As long as "joke edits" do not violate the ToS or interfere with the Wiki Project, the page should be left alone. If you are uncertain and suspicious, bring the issue up on the page's talk page.
Examples on this Wiki:
Citation:
Procedure(s):
- Proof of permission consists of a message from the user who desires help on their talk page.
- It would be helpful to outline desires in addition to giving permission.
- Editors spending their time helping the page should make an effort to politely teach the user, providing clear edit summaries, links to template documentation, and so on.
- The user should close the issue (and therefore close permission) by stating so on their talk page when the desired outcome(s) are achieved.
Explanation:
- Permission must be given via the user's talk page due to significant issues with alternate account abuse and identification authentication. Users are able to change their names in-game with a Name Change Pass and use different names on the forums. Forum requests, screensots of in-game messages, and any other sources are not sufficient proof of permission.
- Editors should take notice of requests made from elsewhere, and notify the user of the necessary permission step. Remember, the wiki is edited by volunteers, and time is valuable - so make sure you really need help before making a request. Editors should not be expected to design and maintain pages for other users.
- If the user is unable to edit their page to give permission, this is a separate issue that should be taken up with support.
Examples on this Wiki:
Citation:
- This is specific to Spiral Knights and developed by the Spiral Knights community. Please read comments associated with comment #5 in this editor development thread.
About
This protocol specifically pertains to pseudo personal space. It should not be used as a reference for edits made to pages which are not considered by this protocol. See other topics covered by the Style Guide instead.
It is a social taboo to edit pseudo personal space that is not associated with your account.[1] It is assumed that each edit made by a user to their pseudo personal space is of their volition and intentional. Pages considered to be pseudo personal space in the Spiral Knights Wiki are free format within the Spiral Knights Terms of Service as long as they do not interfere with the wiki project.[2] But certain changes - reasons to edit, described above - simply have to be made.
Out of respect for the individual, the Spiral Knights editor community has created this protocol. Its purpose is to provide a reference for justifying edits, as well as to educate editors about acceptable behavior in the userspace. If you disagree with edits made to your page(s), but they are justified by this protocol, do not "make a fuss" or fight editors regarding the changes. We are often enforcing standards set by game staff, as they mostly leave the wiki to volunteers after describing what we can and can't do. Staff has also stated that developing this protocol is up to the community.[3]
Users are using this wiki's service, and do not own any pages on a wiki.[4] Furthermore, ...a user cannot avoid administrator attention or appropriate project notices and communications by merely demanding their talk page is not posted to. [5]
See Also
- Node 112452 - Spiral Knights Editor Community development thread for this protocol
- Wikipedia's Policy for user pages
- MediaWiki's Policy for user pages
