3,679
edits
Project:Content policy: Difference between revisions
Jump to navigation
Jump to search
overhaul P:V
(trim fluff in P:NPOV) |
(overhaul P:V) |
||
| Line 43: | Line 43: | ||
== Verifiability == | == Verifiability == | ||
{{Shortcut|P:V}} | {{Shortcut|P:V}}Facts must have a source that sufficiently prove it's accuracy. The singular exception would be content which to any reasonable person would be equivalently as obvious as the sky being blue. For example, it is unnecessary to provide sourcing to support a community's name - that tends to be predominantly displayed on the relevant community's communications platforms, websites, and the works. | ||
=== Synthesis === | |||
{{Shortcut|P:SYNTH}}It is often necessary to synthesize information, or take information from multiple sources and draw a conclusion from it in the project's voice, in order to describe a community. This is most common when writing about a community's rank structure, since it is rarely spelled out. Sourcing will probably not exist that outright proves synthesis, which is acceptable; but sourcing must still be provided for the facts being used within the synthesis. | |||
Synthesis must ''never'' be performed when writing about a community's history or when writing about particular events that happened within it. Such content must remain structly neutral, only present what sourcing states, and only present the facts in the voice of whatever the source is. | |||
=== Media and verifiability === | |||
{{Shortcut|P:MAS}}It is acceptable and often necessary for media (e.g screenshots, video, PDFs) to be used as sourcing. The age of online community's having forums has generally passed and been replaced with Discord servers and their equivalent. However, media is ripe for abuse with editing tools. | |||
Any media uploaded with the intent of being used as a source may not be cited until it is independently reviewed for authenticity by an [[Project:Administrators|administrator]]. For example, if a screenshot of a Discord announcement is made, the administrator must be able to go to the Discord server themselves and find the announcement. They will then compare it against the screenshot to ensure it has not been altered. Media used as a source may not possess alteration in any form aside from organic cropping or clipping, though an administrator may rule that any piece of media fail authentication due to insufficient context. | |||
The administrator may perform authentication in whatever reasonable fashion they desire. Once a piece of media is authenticated, the media will be given an appropriate template and category, and then it may be used as a source. If authentication fails, it must be immediately deleted. | |||
==== Challenging authenticity ==== | |||
{{Shortcut|P:MASC}}Any autoconfirmed editor may, at any time, challenge the authenticity of a source. Once challenged, an administrator that was not the previous authenticator will perform the authentication again to ensure the accuracy of the source. If an administrator is the challenger, they may immediately perform the authentication themselves. | |||
If authentication is successful, it will be reported on the relevant talk page for the source, and it may not be challenged again for 6 months. If the administrator determines beyond a reasonable doubt that the source was altered in ''any way'', it must be deleted immediately. If authentication is wholly impossible (e.g website that is the source of a screenshot has deprecated without archival), the administrator shall be empowered to make a ruling on the matter within their best judgement. | |||
Administrators are encouraged to lean toward deletion if there are suspicious circumstances involving it's upload. | |||
==== Copyright and trademark considerations ==== | |||
Media uploaded as a source is still bound by our [[Project:Use of copyrighted materials|policy on the usage of copyrighted material]]. | |||
== Content disputes and consensus == | == Content disputes and consensus == | ||