Usuario:Penitencia

De Eireapedia
Revisión del 23:23 10 mar 2011 de Penitencia (discusión | contribuciones) (Prueba de edición bot con PHP desde archivo..)
Saltar a: navegación, buscar

Usuario:Penitencia

Plantilla:Procedural policy Plantilla:Nutshell RevisionDelete (also known as RevDel or RevDelete) is an administrative feature that allows individual entries in a page history or log to be removed from public view. It is used for "Selective deletion", largely replacing the prior method (delete and partial undelete) which should not be used except for history merges and occasional other cases where it is needed. Revision deletion should only be used in accordance with the criteria for redaction.

RevisionDelete can hide the text of a revision, the username that made the edit or action, or the edit summary or log summary. On the English Wikipedia, criteria exist to govern the use of RevisionDelete, which are outlined below. Use of RevisionDelete by oversighters in "Suppression" mode is covered separately by the Oversight/suppression policy.

Any administrator may handle RevisionDelete requests made by users, but Category:Wikipedia administrators willing to handle RevisionDelete requests lists administrators who have declared a particular willingness to handle such requests. Users who have concerns about any particular use of RevisionDelete may ask any administrator to review the matter, but again administrators listed in that category may be particularly well placed to do so. When contacting editors about sensitive material, prefer email to public talk messages, to avoid exposing information to more readers.

Overview of RevisionDelete

RevisionDelete allows selective redaction of posts and log entries by administrators, as well as peer review by any administrator of the correct use of the tool. Entries still appear in redacted form on the public wiki, and any user may request that an administrator review a RevisionDelete action, to determine whether its removal was reasonable.

As a deletion tool, RevisionDelete is capable of removing material from the wider community's view. Because of this, the tool should only be used within strict guidelines.

In time-sensitive situations where breach of WMF oversight policy (broadly covering privacy breach and legal defamation) is a concern, an administrator may redact first, then immediately bring the matter to the attention of oversighters. (See below)

Misuse

RevisionDelete was introduced for administrators in 2010. The community's endorsement of the tool included a very strong consensus that its potential to be abused should be strictly barred, prevented by the community, and written into the policy. Especially, RevisionDelete does not exist to remove "ordinary" offensive comments and incivility, or unwise choices of wording between users, nor to redact block log entries.

Material must be grossly offensive, with little likelihood of significant dissent about its removal. Otherwise it should not be removed. Administrators should consult as usual if uncertain that a revision would be appropriate to redact.

RevisionDelete compared to traditional selective deletion

Technical advantages over traditional selective deletion (using delete and partial undelete):

  • There is no need to delete the article first, to remove specific revisions
  • Revisions can have selected material removed rather than the entire edit (eg, edit summary or revision text is a problem but username is okay)
  • RevisionDelete may be used on pages with long history
  • RevisionDelete may be used in logs (eg, material from page move vandalism).

Other significant advantages:

  • It does not remove edits from public view. It also does not cause prior edits to appear as another user's edit, so attribution and history may be less affected.
  • It does not require full deletion and partial restore, so previously deleted revisions are not at risk of being accidentally restored, and the article does not appear as "deleted" during the process.
  • An article's history is not split between two separate pages (history and deleted history), so all edits are visible on the one public page.
  • Non-administrators can see which revisions/log actions were deleted, even if they cannot see the deleted material.
  • If the article has any protection (semi protection, edit protection, etc), this is not disrupted by RevisionDeletion.

Criteria for redaction

Plantilla:Shortcut

A certain low degree of inappropriate or disruptive posting is normal within a large community. In general, only material that meets the criteria below should be deleted. Users should consider whether simply reverting or ignoring would be sufficient in the circumstances. If deletion is needed, only redact what is necessary (i.e. leave non-harmful fields visible), and give a clear reason for the removal.

The community's decision was that RevisionDelete should not be used without prior clear consensus for "ordinary" incivility, attacks, or for claims of editorial misconduct. The wider community may need to fully review these at the time and in future, even if offensive.

  1. Plantilla:Anchors Blatant copyright violations that can be redacted without removing attribution to non-infringing contributors. If redacting a revision would remove any contributor's attribution, this criterion can not be used. Best practices for copyrighted text removal can be found at Wikipedia:Copyright problems and should take precedence over this criterion.
  2. Plantilla:Anchors Grossly insulting, degrading, or offensive material that has little/no encyclopedic or project value and/or violates our Biographies of living people policy. This includes slurs, smears, and grossly offensive material of little or no encyclopedic value, but not mere factual statements, and not "ordinary" incivility, personal attacks or conduct accusations. When attack pages or pages with grossly improper titles are deleted, the page names may also be removed from the delete and page move logs.
  3. Plantilla:Anchors Purely disruptive material that is of little or no relevance or merit to the project. This includes allegations, grossly inappropriate threats or attacks, browser-crashing or malicious HTML, shock pages, phishing pages, known virus proliferating pages, and links to web pages that disparage or threaten some person or entity and serve no other valid purpose, but not mere spam links.
  4. Plantilla:Anchors Oversightable information – see separate section below for criteria.
  5. Plantilla:Anchors Valid deletion under Deletion Policy, executed using RevisionDelete. With the exception of fixing cut-and-paste moves and history merges, if selective deletion is required, RevisionDelete is usually preferable (see above), and should be used instead of the old method of "delete and partial undelete". It is important that the underlying reason for deletion be made clear in the log summary.
  6. Plantilla:Anchors Non-contentious housekeeping including correction of clear and obvious unintended mistakes in previous redactions, changes to redaction based upon communal discussion and clear consensus, adding information to the delete logs, and converting traditional selective deleted edits to RevisionDelete. (The action must not be likely to be contentious or controversial, consult if needed)
Plantilla:Anchors AC. Deletion mandated by a decision of the Arbitration Committee. At times the Arbitration Committee may determine that a logged item was sufficiently improper that the record should be formally deleted in the public log. The deletion reason should clearly link to the decision. Deletions under this criterion are considered to be Arbitration Enforcement matters and should not be overturned improperly; they may however be appealed.

Log redaction

Log redaction (outside of the limited scope of RD#2 for the move and delete logs) is intended solely for grossly improper content, and is not permitted for ordinary matters; the community needs to be able to review users' block logs and other logs whether or not proper. Due to its potential, use of the RevisionDelete tool to redact block logs (whether the block log entry is justified or not) or to hide unfavorable actions, posts and/or criticisms, in a manner not covered by these criteria or without the required consensus or Arbcom agreement, will usually be treated as abuse of the tool.

Plantilla:AnchorHiding oversightable material prior to Oversight

Personal information includes almost any material that is (or looks like it might be) actual claims, facts, hints, or allusions to non-public, personal, or private information. (See WP:SIGHT and WP:OUTING)

It does not matter whether the privacy breaching material was posted by the user themselves or by a third party, whether in good or bad faith, recently or in the past, whether accurate, whether the target is identifiable to the administrator, nor whether it is a statement, pointed speculation, or implied.

RevisionDelete can be used to hide any privacy breaching and/or defamation posts while waiting for Oversight. Since Oversight is not immediate, an administrator may provisionally delete the information from public view to minimize harm, then promptly contact an oversighter.

Even if the material is ultimately found not to be suppressible, administrators are allowed to err on the side of caution, even in cases with an apparent conflict of interest, provided it is in good faith and they quickly seek oversighter review. If the oversighter decides suppression was not appropriate, the material will be restored or admin-deleted instead.

Administrators should be aware that delete logs are public and scrutinized. Deletion may lead to extra attention at times. Only administrators can see the material when it is RevisionDeleted (and before oversight), but even so it may sometimes be more discreet to contact oversighters directly, and not use RevDelete first. A lot depends on the material itself. If RevisionDelete is used, avoid obvious suggestive terms in the reason (eg don't use "RD4", "oversight", "private material", "hiding IP of logged out user" etc).

Notes on use

It does not matter if the target is identifiable, just that it appears to have a target:

It is not necessary that the target is identifiable. It is sufficient that it appears to refer to some real person, organization or group, or could be intended to suggest a specific target to the right reader. For example a smear could target a person known locally by a nickname or other allusion that no Wikipedia administrator has heard of, but that is instantly recognizable to people in that school, town or social community. It is therefore not necessary to be able to identify the target/s in order to treat it as if a target exists.

Username hiding (copyright attribution issues):

Wikipedia's licenses require that accessible edits are linked to the user who performed them, so it is generally a problem to hide the username from a revision while leaving their edited changes to the page in public view. Cases where it is acceptable are those where the revision contains no valid information copyrightable to the user who posted it (i.e. plagiarism, gibberish, vandalism, adding categories, no copyrightable change made to revision text, etc), where all changes will be reverted, or where the user accidentally posted "logged out" and the aim is protection of privacy at the request of the user.

High traffic pages:

If redaction may be required on a busy page it can sometimes be worth an edit to take care of problematic text. If redaction is eventually required, fewer revisions will be affected.

Large-scale use

RevisionDelete is mainly intended for simple use and fairly recent material. Text that exists in numerous revisions (e.g. on busy pages) or which has been the subject of many others' comments, may not be practical to redact. Redaction of such material should take into account how practical and effective redaction will be, how disruptive it would be (e.g. to others' valid posts), and whether redaction will itself draw attention to the issue. No hard line exists; judgment is required.

Administrators in this situation may wish to initially edit the page to revert or remove the grossly improper material, and then consult.

How to request Revision Deletion

In order to avoid the Streisand effect, there is no dedicated on-wiki forum for requesting RevDel. You can send a message to any administrator in Category:Wikipedia administrators willing to handle RevisionDelete requests either at their talk page or by email if privacy is a concern. If it could be subject to oversight, follow the procedures at Wikipedia:Requests for oversight or email oversight-en-wp@wikipedia.org.

Appeal and discussion of actions

Actions performed using this tool remain visible in the public logs. They are subject to review by other administrators (who can see redacted material), and to reversal upon clear, wider consensus. As with other administrative tools, good judgment and appropriate use are expected; improper use can lead to sanctions or desysopping.

Technical details

Archivo:RevDelete isn't subtle (2).png
The effects of two different visibility combinations on a page history. Redaction is shown to all users.
Archivo:RevDelete effect on pages (short).png
RevisionDelete (del/undel) link on page history and logs (administrators only). The same option is also added to diff pages and old revisions (example).

On the English Wikipedia, the revision deletion feature is available in administrator mode to administrators and in administrator and suppression mode to Oversighters (all of whom are currently also administrators).

Functionality

Every page revision and log entry has a small (del/undel) button displayed next to it for administrators and oversighters, as shown.

Some pages have checkboxes and a "Del/undel selected revisions" button instead, to allow multiple revisions to be redacted as a group.

When a revision or log entry is hidden from view in its entirety, it is displayed as shown to the right, with the elements hidden from view stricken and greyed out. The struck-out elements cannot be viewed by any usergroup which does not have the deleterevision right. A user who cannot access the relevant revisions and who tries to compare the revision with other revisions or access its &oldid= page will receive an error stating that the revision has been removed from the public archives. Similarly, looking up log entries or contributions by username will not show log entries where the username has been redacted.

The (del/undel) link can usually be clicked by an administrator to view the diff. It will appear in bold if suppression has been applied, in which case both the redacted material and its deletion settings cannot be accessed by administrators or users who lack access to the oversight tool.

Revision deletion actions are retained even when the revision or page is deleted in the traditional manner. If a page is later undeleted, data that was deleted with RevisionDelete will still remain deleted. Plantilla:Clear

Limitations and issues

  • The revision text of the most recent edit on a page cannot be redacted. The revision must be reverted or deleted first. Other fields (username and edit summary) can be redacted even on the most recent edit.
  • Revision links change when a revision is traditionally deleted or undeleted. If a revision's visibility is modified using RevisionDelete, and the revision is later deleted or undeleted, the links in the delete log and elsewhere may break. It will be necessary to look at the page history/deleted page history/page logs to work out what revision was being referred to. (This has been reported but is not simple to fix)

Changing visibility settings

Archivo:RevDelete Special-RevisionDelete (narrow).png
The RevisionDelete dialog. The suppression option is included for completeness, although this is only visible to users with oversight access.

To hide or unhide a revision or a log entry, click the small (del/undel) button next to the relevant revision, diff, or log entry that you wish to show or hide. Depending on your permissions, there may be either three or four options to choose from:

  • Delete revision text
  • Delete edit comment
  • Delete editor's username/IP
  • Suppress data from administrators as well as others (only available to users with the suppressrevision right, namely oversighters)

Tick the checkboxes next to each of the actions you wish to apply to the selection, and provide an informative summary in the "Log comment field". Once this information has been filled in, click the "Apply" button to submit the information. If this has been done correctly, a success message should be displayed on your screen.

To unhide a revision or log entry, or to amend the data that is hidden, click the (del/undel) button for the revision or log entry and simply untick the boxes, provide a reason or summary and click the "Apply" button. Success should be marked by the display of a success message.

Hiding of a username or IP should only be used where that username or IP has a reason in and of itself to be hidden, such as accidentally editing logged out or an attack username. Hiding a username will remove the contribution completely from the user's contributions list (except from administrators, who will see a warning indicating it is invisible to users), rather than a crossed out entry for deleted edits without hidden username. This will cause issues with users trying to review actions taken on the user, as well as potential copyright violation risks.

RevisionDelete's own log entries

Archivo:RevDelete own log entries.png
RevisionDelete's own log entries in the public deletion log.

Use of RevisionDelete produces an entry in the public deletion log, or the private suppression log if used by an oversighter and "Suppress data from administrators as well as others" is checked. Log entries created in the public deletion log look like those displayed to the right, for page revision and log entries visibilities respectively. The options (diff | change visibility) provide an easy link to view or redact the underlying page revision to which the log entry refers.

Selective undeletion

The older method of selective undeletion (i.e. delete the entire page then selectively restore revisions) as a method of deleting revisions should be considered deprecated in favor of this system. While selective undeletion does still have a few valid uses (such as complex history merges), due to its relative lack of transparency and poor efficiency, it should not be used to remove revisions from the page history.

Statistics

See also

Obtenido de «https://wiki.reinosdeleyenda.es/index.php?title=Usuario:Penitencia&oldid=10363»