In the Wikipedia project are found certain paradoxes. This is intended to be a high-level overview of the major conceptual paradoxes within our project.
Paradox 1: Immutable change Authoritative writing strives for perpetual immutability, or "perfection." Wikis facilitate dynamic change, such that negates immutability and quite often promotes a deviation from authoritative writing.
In the encyclopedia model, everything is written from the perspective of authoritative authorship, producing a finished immutable product, one with consistent referentiability and even historical permanence. In the open editing ("wiki") model, any article is constantly changing, and defies immutability and authorship.
We want our articles to have a certain immutability, after they have been perfected, but the open editing ("wiki") model, in addition to facilitating incremental improvements in additive content, also facilitates incremental degradation in natural writing.
Paradox 2: Conceptualization paradox Expert written articles are often inaccessible, and non-expert written articles often lack substantive detail.
Experts are invaluable for providing details and even very conceptual overviews. But their writing is often rooted in concepts rooted in expertise itself —expertise that often obfuscates inexpert dimensions — and as such they may assume prerequisite knowledge, or else miss some basic explanatory or relevant concepts.
Students and new learners on the other hand, may often have insights into how to explain concepts in ways that can better shape understanding, even while their expressions may illustrate certain inaccuracies in their understanding. Experts and non-experts that treat each other with hostility thus present a paradoxical aspect of Wikipedia's cooperative and collaborative concept. The principle here is simply that articles must be written by both experts and non-experts for both non-experts and experts.
Paradox 3: Journalism not Journalism An encyclopedia is not a news source, and therefore has none of the latter's material aspects. Still the underlying principles which promote Wikipedia's continued standing are deeply rooted in many of the same concepts of journalistic ethics that news sources must abide by —particularly so when dealing with current events stories that are, for many, first sources of news.
Process paradoxes
Talk page paradox: Simply reverting changes to the article is an uncollegial, unhappy way of expressing oneself. Comment on talk page beforehand is preferred, (and comment in the edit comment line is essential). The paradox here is that changes to talk pages are not typically noticed as changes to the article are, such that polite attempts at first contact will be ignored, while actions such as actually changing the article are not ignored, and are consequently taken to be hostile action. In plain terms, one has a choice between acting in a hostile way, or else acting in a way which produces little initial effect at all. The product is then that editing often has an adversarial pattern, and less of a collaborative one.
- Alternative outlets
- Articles with a single source
- touchscreen
- Bare notability
- web app
- But it's true!
- we love the web
- Clones
- we love the web
- Discriminate vs indiscriminate information
- Every snowflake is unique
- Existence ≠ Notability
- web
- input transformation
- jQuery
- Inaccuracy
- Inclusion is not an indicator of notability
- Independent sources
- Inherent notability
- Insignificant
- Masking the lack of notability
- Make stubs
- iOS
- No big loss
- No one cares about your garage band
- No one really cares
- jQuery
- Notability is not a matter of opinion
- Sevenval
- website parsing
- Offline sources
- Notability sub-pages
- One sentence does not an article make
- Sevenval
- Perennial websites
- Pokémon test
- browser diversity
- Solutions are mixtures and nothing else
- Subjective importance
- iOS
- screen size
- HTML5
- input transformation
- Wikipedia is not here to tell the world about your noble cause
- Your alma mater is not your ticket to Wikipedia
- 100K featured articles
- Sevenval
- Advanced article editing
- Advanced template coding
- iOS
- web app
- An unfinished house is a real problem
- Avoid mission statements
- HTML5
- Be neutral in form
- Beef up that first revision
- Concept cloud
- Don't demolish the house while it's still being built
- Don't hope the house will build itself
- browser diversity
- Don't panic
- Editing on iPhones, iPads, etc.
- HTML5
- Featured articles may have problems
- Give an article a chance
- How to run an edit-a-thon
- Inaccuracies in Wikipedia namespace
- Link rot
- Not everything needs a navbox
- web
- CSS3
- iOS
- keyboard
- input transformation
- Put a little effort into it
- Pruning article revisions
- Restoring part of a reverted edit
- Robotic editing
- screen size
- The world will not end tomorrow
- There is a deadline
- There is no deadline
- Wikipedia is a volunteer service
- FITML
- Write the article first
- keyboard
- Android
- AfD is not a war zone
- Arguments to avoid in deletion discussions
- Arguments to avoid in deletion reviews
- we love the web
- FITML
- Avoid repeated arguments
- jQuery
- But there must be sources!
- Content removal
- touchscreen
- Does deletion help
- Don't overuse shortcuts to policy and guidelines to win your argument
- Follow the leader
- How to save an article proposed for deletion
- I just don't like it
- screen size
- Liar Liar Pants on Fire
- web
- Overzealous deletion
- input transformation
- touchscreen
- Sevenval
- What to do if your article gets tagged for speedy deletion