User talk:ViperNerd

THE GREAT FAILURE OF WIKIPEDIA (by Jason Scott)

I have now tried extended interaction with Wikipedia. I consider it a failure. In doing so, I will describe why, instead of just slinking off into the night on my projects. Maybe it will do some good. Maybe it will not. I’m sure, at the end of the day, there must be hundreds like me at this point. Burned, slapped, ejected from the mothership for not following the rules, no matter how intricate and foolish. Let me at least go with some smoke.

The concept of Wikipedia is a very engaging and exciting one, especially to someone like myself who spends an awful lot of time collecting information and then presenting it to people. Normally, the work I do is the work that’s done. That is, if I don’t give much attention to a specific section of my sites, that section will stay static, even if it’s in need of improvement. This is not very enjoyable. In collaboration, you will put your tools down for the night, and when you wake up the next morning, more work is done. This is very exciting, very enjoyable. It’s why people work in teams in the first place.

Within the social spectrum of information specialists, I am best classifyable as a moody loner. I don’t work well with others, at least, that is, people who I don’t like. Which is a lot of people. As a result, the vast majority of my sites are one-man operations, meaning that the firehose of my concentration goes from one site to another, giving it some sort of monsoon season of attention and update before firing in another direction. This means that some are truly ghost towns for months at a time. With the additional strike of my documentary, my time is almost completely eaten up, and so the other sites have been suffering.

The idea of Wikipedia, on its face, is really neat. A bunch of people can work on an entry in a huge, growing encyclopedia, its subject matter gaining far and wide, and deep, into the whole of human knowledge. Pretty cool stuff to hear about, as you browse the outside of it. You click on some of the more complete entries, and really, you just say to yourself “wow, such a great thing is man” and so on. Maybe you wave a little flag with a logo on it. Wikipedia’s watchword is entirely collaboration. With a few exceptions, anyone can modify anything in any way, and anyone can undo their modifications, with a full tracking of the history of edits and methods included to keep track of these changes. Exciting stuff.

I had run into people who spoke of Wikipedia in a near-fanatical aspect, of how all these hands were forming these great and beautiful entries, and that it was just a matter of running along and having a great time making the whole project better. Naturally, I regarded this with suspicion and hopeful interest. I’m always interested in people doing stuff tangental to the work I do, but I always wonder if it will turn out my work has been for naught, or if in fact I’m still doing something unique and the efforts being expended on the other project are unrelated.

On the other hand, it is an awful lot of work tracking down the history of America Online or John Paul Aleshe or any of the other subjects I am always researching, and a bunch more hands kicking in would be fantastic. So I bought in, for a little while. Signed myself up and started some work.

I should pause for a moment, before I continue further. If you work on Wikipedia, I’m just going to make you angry. What I am doing is trying to stop people from working on Wikipedia with the idea that they’re accomplishing good. I am quite convinced, from the outside, over here, that no amount of suggestions from a lone voice will have any effect. Mobs don’t listen. So please, traipse happily back to Wikipedia and get cracking; someone is not eschewing a NPOV, even as you read this. Go! Go!

Note, also, that in what I’m writing about, I’m not speaking about the concept of a “Wiki”, or indicating that a collaborative tool such as Wiki software is a failure. Confined with a number of limitations on who does what in the context of undoing work, it can certainly work. It’s just software, after all. it’s the implementation that’s the sticking point.

To understand Wikipedia, it helps to understand the Usenet FAQ and its unique place in history.

The Usenet FAQ was (and is) to me, one of the true great advantages and creations of the Internet age. Previously, it had always been the case that the same 5 or 10 questions plagued a subgroup, cultural icon, hobby or occupation. These questions, while quite valid, quite reasonable, would be asked so many times that it would eventually be the case that no-one was willing to step up for the thousandth time and explain them. This led, inevitably, to speculation, wrong information and misquoting that would come back to bite everyone later. For no good reason! But the Frequently Asked Questions list fixed that. It allowed all the common questions to be answered, and even for the common controversies to be addressed even if no firm conclusion had been reached. These things grew like crazy in the 1980s and there’s massive collections of them out there, still with good information (as long as its a general subject, and not a pop star or the like), and the work of many people coming together to build something good. Like Wikipedia is supposed to be.

I would attest that the reason for the success of the FAQ was a lot of collaborators but a short list of people maintaining it. A very large amount of maintainers leads to infighting, procedural foolishness, and ultimately a very slow advancement schedule. There’s an interesting book called The Mythical Man-Month that goes into this in some detail, but the basic idea is: the more people you slap into a project that’s behind, the more the project will fall behind. Unintuitive, but true. Even in the case of raw horsepower, this becomes the case; you would think that if the basic job (photocopy this paper) was simple enough, the job would go faster with more people, but it doesn’t. You end up with people photocopying stuff wrong, collating wrong, bending pages badly, skipping pages… and the errors increase as you smack more people on. And you fall behind.

Now, at the risk of sounding a tad elitist and exclusivist, a low barrier to entry leads to crap. Maybe not initially, but with any amount of quality attached to a project, once it gains some respectability and perhaps fame or infamy, it is then beset upon by crap. By making it really, really easy to change, fundamentally, the nature of a project, you run the risk of the project becoming a battleground. A really, really crappy battleground.

For exhibit A, one merely has to traipse over to the Internet Movie Database (IMDB), which is now a sub-company of Amazon. For better or worse, Amazon now defines that body of information’s future, and along the way they ended up adding a few nice features (like a very fast search engine, and links to buy the movie if you so choose). But they also added user comments.

Have you seen the user comments there? Choose a movie; I won’t bias you. Go find the threads under a $100 million picture, an Oscar-winner or an independent production. Go browse them and bring to me a thread that isn’t a garbage pile of one-line off-the-cuff nothings, a handful of withered one-sentence dandelions. Devoid of insight, meaningless to anyone truly trying to find insight into the film at hand. In many cases, these films represent years of work in someone’s life, but because tourist3398 can just log right in and ask a completely stupid question, or make an inane comment, they get equal time on that front page for a while. Ultimately, it’s insulting to the work done and it adds nothing.

The reviews that accompany each movie are slightly better, because it appears there is a moderation system in place. Reviews that are fundamentally wrong are in place, but they’re wrong in a matter of opinion, not often in a matter of being unreadable. You disagree with what’s being said, not the brickheaded way it’s being said.

The simple fact is, a low barrier to entry and an easy access to an audience tends to lead to problems. A web-based comic named Penny Arcade captured this succinctly, but I want to add that the issue is not that damage will occur immediately, but will occur over time. And eventually, given enough time, damage and low quality will win over high quality, because high quality requires effort and low quality does not.

So we come to Wikipedia.

I often get myself into trouble and lose my audience with my metaphors, but so be it. Think of Wikipedia as a massive garage where you can build any car you want to. Great tools are provided, a lot of shop manuals are there, and you get your own lift and away you go. Fantastic. But every one else, and I mean everyone else in the garage can work on your car with you. There’s no “lead mechanics”, no “shop floor managers”, no anything. In fact, the people who are allowed to work on your car can completely disregard what you were doing with it. They could have flown in from Boola-Boola Island 2 hours ago, not know the language, can’t read the manuals, and just go in and paint your car pink. And drive it. And leave it somewhere. Now, since tools are free and paint is free and you can easily go and retrieve your nice car and get it back to something resembling sanity, a lot of the people in the garage see there’s no problems. But in fact, the fifth, or the hundredth time you’re traipsing down the lane to find your messed-up, polka-dotted, covered-in-chrome-pussycats car, you’re kind of inclined to drive it into the lake and leave it upside down, wheels spinning.

This is what the inherent failure of wikipedia is. It’s that there’s a small set of content generators, a massive amount of wonks and twiddlers, and then a heaping amount of procedural whackjobs. And the mass of twiddlers and procedural whackjobs means that the content generators stop being so and have to become content defenders. Woe be that your take on things is off from the majority. Even if you can prove something, you’re now in the situation that anybody can change it. And while that’s all great in a happy-go-lucky flower shower sort of way, it’s when you realize that the people who are going to change it could have absolutely no experience with the subject whatsoever, then you see where we are.

If you’ve ever worked in a large company, one where not everyone’s name is known by everyone else, you’ve bumped into these people, who don’t know the thing the company makes very well, don’t keep on top of new ideas beyond buzzwords, yet wield the kind of power where they can stop and start innovation and positive growth because they simply feel like it. It’s pretty heartbreaking stuff and I hope a bunch of you never have to deal with it.

But thanks to Wikipedia, you can experience this on a daily basis! College students with too much free time deciding your subject matter is not worth reporting. Bizzare insight from strange lands telling you they didn’t think your paragraph was relevant. And ever the bizzare need for a Neutral Point of View. Neutral Point of View is a doctrine about how Wikipedia articles should be written. Like wikipedia itself, it is a great idea in theory. In application, of course, it turns into yet another hammer for wonks and whackjobs to beat each other and innocent bystanders.

Wikipedia is a relatively new creation, but it already quite beset with the same problems that inhabit any self-styled intellectual collaboration. People make little empires, have their agendas, push through ideas and themes they want, and disregard and delete things they do not. The main difference between this and other similar academic environments is the pure speed at which stuff can happen; you can literally have 30-40 little editing nibbles on a page within a single day. If people are feeling frisky, it can take place in a few hours. This means that you get all the politics and turf war of Ivory Tower Academia without the mitigating barrier of time to cool down or consider. That is, you get a nice big mess.

One of the stated concerns of nanotechnology (wherein a bunch of tiny things make a lot of small changes very quickly, which should sound forever) is the ‘grey goo’ problem. The concern with grey goo is poorly programmed nanobots will make a bunch of wrong incremental changes to the world and reduce everything to a grey, goo-like substance of all creation. It is not hard, browsing over historical edits to majorly contended Wikipedia articles, to see the slow erosion of facts and ideas according to people trying to implement their own idea of neutrality or meaning on top of it. Even if the person who originally wrote a section was well-informed, any huckleberry can wander along and scrawl crayon on it. This does not eventually lead to an improved final entry.

Let’s put it another way. In the motion picture industry, there’s a term called “on the screen”. It’s phrased in this way: “is this money going to end up on the screen?”. And what is meant by that is that if you pay a bunch of money to rent a spectacular shooting location, then it’s going to end up on the screen, that is, people will see the spectacular location and go “wow” and they’ll feel the movie is giving them their money’s worth. If you pay for the rights to use a location, and then there’s a hurricane and your location is wiped out and you didn’t get insurance, then you just spent a lot of money, and did no shooting. Your money is not on the screen. Other than on a bunch of reciepts, there will be no trace of the $2 million you spent on that location rental. So there’s wasted money, energy and time, and that can add up. This is what plagued movies like Cleopatra, Waterworld and Heaven’s Gate, which contained huge behind-the-scenes costs that did not result in footage, meaning the movies were now expensive blockbuster budgets with medium-level footage to show for it.

I would contend to you that the Great Failure of Wikipedia is how little truly ends up “on the screen”.

As I said, you are no longer in the role of content generator soon after your works are exposed to the wonks and twiddlers and procedural whackjobs. You are a content defender and that means that time you could be spending finding new and interesting facts or finding original sources or otherwise making the world a better place (or at least an entry or two) is being spent explaining for the hundredth time that no, this really happened and yes, I got clearance for that photograph, and yes, I believe this shows a neutral point of view, and so on. It’s like you get to play one note of your trumpet and then you spend 20 minutes defending it. To anybody who walked in. Just now.

I’m sorry, but content creators are relatively rare in this world. Content commentators less so. Content critics are a dime a hundred, and content vandals lurk in every doorway. Wikipedia lets the vandals run lose on the creators, while the commentators fill the void with chatter. It is, a failure.

Naturally, the question that arises is what solutions would I suggest to fix this situation. Well, I continue to run my own private collection of data and research and will continue to do so. You know, generating content. I made the mistake of gifting over a photograph to Wikipedia back when I thought it would be a success and not a failure, but I will not make that mistake in the future. I may offer the works I have collected and generated essentially for free to the public, but I will not give permission to Wikipedia to use them. This actually breaks the Wikipedia way, because they need explicit permission to function. It’s another fatal flaw; they will not mirror content. They are terrified of copyright violation. They are scared of what might happen if they were to copy over some text in a fair use situation and they were to be sued. So they do nothing. This is why so many links from Wikipedia are dead.

I’ve seen people point to Linux/Open Source as an example of a Wikipedia-like entity accomplishing things, but the fact is that this is a false comparision. The vast, vast, vast majority of open-source projects have a small amount of maintainers and an audience of users who, upon being able to see the code, suggest changes. If maintainers suck, they fork, but more often than not, the maintainers are told of their bugs, of feature requests, and so on, and implement them, sometimes slowly and sometimes not. Incremental improvements, not waking up one day and finding the I/O libraries gone or switched to a neutral point of view. Maybe this is a natural maturation of collaborative projects that Wikipedia hasn’t gone through yet. Time will tell on that level.

Already, there are many Wikis out there, sites using Wikipedia-like software (but interestingly, not often the exact software, choosing instead to implement their own version of the heirarchy and approach) and then collecting knowledge. Wikipedia calls them “Knowledge Bases”. I call them “Wikipedias”. I think over time, people will want to get away from the grey goo of Wikipedia’s mess and move towards specialized or properly-run Wikis, which contain, not a cabal, but at least a slight barrier to entry that will ensure that the person who is going to undo your hours of work with a few mouse clicks is at least, from some relatively objective standpoint, vaguely entitled to do so.

Meanwhile, I will aim my energy in my own direction, knowing that while my tools will be where I left them the previous morning, they’ll also still be recognizable as my tools.