2 ms·
Well, it's not unique to wikipedia, it's just more visible to everyone (you do have all the history there, with any luck, there's a comment in the talk page: 60
by e12e 12y ago
Well, it's not unique to wikipedia, it's just more visible to everyone (you do have all the history there, with any luck, there's a comment in the talk page: 600 days ago "This fact was apparently made up out of thin air, then cited as..."). If editors do a bad job (some always will) -- errors will happen and be harder to fix.
It's text, it won't magically curate itself.
There might be a lot of room for improvement in how wp is curated, similar to how we have various workflows to deal with code (eg: move to a model in which every change has a "bug" filed in a bugtracker, and edits are only accepted with a proper "fixes:xxx" tag -- rather than just "free form" commit messages).
[edit: I just realized (it's probably not a novel idea) that the best way to look at wikipedia is not as a set of articles/"facts" and their history, but as a process of collecting "true statements"/"true articles". This process could be viewed along the lines of:
1. Ask a question (why are bees black and yellow?)
2. Look for an article that answers the question
3. If no article exist, try to write one (this perhaps should be moved to an "issue tracker"/"stack overflow" type thing -- 3.1 "file a bug against wikipedia"
4. If an article exist, read it
5. If the article appear to contain errors, investigate (for possible factual errors, look at talk page, history -- for spelling errors "file bug" 3.1)
6. If there are open bugs (such as errors you've just found) submit a patch
7. If there are pending patches vote yes/no/commment
Something along those lines could constitute what wikipedia is -- not merely the articles and a wiki-interface. Then it becomes something more than "just" a wiki or "just" an encyclopedia.]