Why this Site?

  • Our Mission:
  • We exist to shine the light of scrutiny into the dark crevices of Wikipedia and its related projects; to examine the corruption there, along with its structural flaws; and to inoculate the unsuspecting public against the torrent of misinformation, defamation, and general nonsense that issues forth from one of the world’s most frequently visited websites, the “encyclopedia that anyone can edit.”
  • How you can participate:
  •  Visit the Wikipediocracy Forum, a candid exchange of views between Wikipedia editors, administrators, critics, proponents, and the general public.
  • 'Like' our Wikipediocracy page on Facebook.
  •  Follow Wikipediocracy on Twitter!

The Bahasa version of Wikipedia is apparently a hotbed of propaganda (more so than other places) asiasentinel.com/pol…

Google Search

Press Releases

  • Please click here for recent Wikipediocracy press releases.

The Battle for Wikipedia: How Your Donations May Be Destroying the Crowd-sourced Encyclopedia

By The Masked Maggot

Just as the Wikimedia Foundation (WMF) was wrapping up its annual show of “wiki-love” and idealism at London’s Wikimania 2014, the latest round of tensions between the foundation and the volunteer community reared its ugly head. The trigger this time was the forced introduction of the Media Viewer to the German Wikipedia, after the community of editors that work on that version voted to disable it. While a slight change to the presentation of images might seem like a minor issue, it points to a deeper and widening rift between the offices in San Francisco and the global community which they serve.

The WMF’s gradual grab, or How the Wikimedia Foundation is harming Wikipedia

.

While there are all sorts of issues worth complaining about, Wikipedia really is an amazing thing. For 13 years, a vast collection of unpaid and unsung volunteers have written, organized, and advocated for an online encyclopedia-like website that pretty much everyone uses, naively or reluctantly. It’s been a long run where volunteer “editors” have not only created the content, but have also been enfranchised to have a say in how the site is run. Wikipedia’s “consensus” model, for all its problems, has been the real driving force behind getting the product to market, and the “Stone Soup” way that everyone brought something to the table (from content to structure to presentation) worked a bit better in practice than it should have in theory.

Those happy days seem to be coming to an end, and while the seeds for that end were planted at the beginning, the fruit is only becoming apparent now. The Wikimedia Foundation, which accepts all the donations and was (so the Wikipedians thought) dedicated to supporting the volunteers who write Wikipedia’s articles, has over the past year or two managed to alienate its volunteers. The irony is that many of the things causing tensions between the WMF and the volunteers are actually things aimed at improving the interface and attracting more editors.

Making editing easier, in theory

During the first several years of Wikipedia and the WMF, the “coding language” behind the articles was mostly created by volunteers, both at the level of the software, and through creative use of the wiki markup language to create “templates”. This made editing rather complicated over time, as more and more templates became standard and in some ways required.

This wasn’t such a bad thing in the heady days of the mid to late ’00s, because there was a large community of “gnomes” who would follow content contributors along and add the appropriate templates. For example, if someone created an article about a species of fungi or lizards, someone would helpfully follow along and add a “taxobox” and categories to provide a uniform look to all the fungi and lizard pages, while others would contribute more information about the taxon. In many cases someone would even add references to the taxon in movies or comic books, which while not exactly what you’d expect to find in an encyclopedia, did lend Wikipedia its particular charm.

The problem with the stone soup method was that the Wiki Markup Language (WML) was very spare, and mostly only updated when a volunteer coder added a feature they thought would be particularly useful. So, for example, that “taxobox” became a very large and detailed “template” that needed to be added to each page and properly filled in, and even the templates used to add references to articles became complicated and wordy, making it harder and harder to actually read the text while viewing the edit window. This became a higher and higher hurdle for new contributors to get past, and also may have contributed to the jumbled prose since it became difficult to read while writing.

By the end of 2011, many were beginning to complain about the steep learning curve needed to add content. Jimmy Wales even declared his userpage a template-free zone. The calls for an easier editing interface got louder and louder, and the WMF began using its newly acquired millions to create one, eventually introducing the Visual Editor (VE).

A Visual Editor

While VE was introduced to great fanfare, it was an epic flop with the volunteer community. The software was buggy, causing all sorts of problems to pages it was used on. The editor was also unable to add or edit the many templates found on almost every Wikipedia article. Worst of all, it was imposed against the will of the volunteer community.

The flaws of the Visual Editor weren’t just a problem for the people who tried to use it, because the bugs actually caused “damage” to the pages it was used on by “breaking” templates and links, and even inserting random Unicode characters such as chess pawns: ♙♙♙. The gnomes and patrollers suddenly needed to waste even more time looking at every edit that had been tagged a visual editor edit, closely looking over each change to see if any brackets were missing or random characters added.

Despite a nearly-unanimous cry from the volunteers to turn the thing off (or at least make it “opt-in only”), the WMF refused to budge. The “community liaisons” from the tech department became frankly abusive, insisting that a little pain was just part of the “Agile” way of doing things. Finally, a savvy Wikipedia admin changed the javascript file for the site to override the developers, and only then did the developers finally back down and make it an opt-in tool. It seemed, for a time, that the WMF had learned to serve the community, rather than to try to force it to follow their lead. However, they have since developed another new feature to prevent the community from overriding them in the future: “superprotection”.

The Media Viewer, Round Two

As reported here on Wikipediocracy a few weeks ago, the Media Viewer’s introduction on the English Wikipedia was not at all popular with the volunteers, or at least the small subset of volunteers who spoke up about it on the Request for Comments (RfC). The foundation’s representatives, and Deputy Director Erik Möller in particular, dismissed the discussion because not enough people had participated in it. The RfC wasn’t very well advertised, and the community had perhaps been demoralized by the fight over VE, as well as signs from the WMF that “Flow” (a potentially disastrous “improvement” for discussion pages) was going to be imposed in similar fashion following their self-imposed deadlines. Meanwhile on the German Wikipedia, a much larger RfC was underway, and the result there was far more definitive: the German volunteers did not want this feature, preferring the simpler presentation of simply viewing the file pages.

As was attempted on the English Wikipedia, a German administrator edited the javascript file for the site in order to disable the feature. Just like on the English site, a WMF representative reverted the change. The change was then restored (beginning an “edit war”), then removed again, but this time the new “superprotection” extension was added to prevent the administrators from editing the interface page. The volunteers were not at all happy about this, but remember that these are the same volunteers who had been creating and honing the interface all along, so comically enough, they saw a way around the protection by deleting the page (the extension didn’t prevent that), then creating a new page with their preferred version. The developers in San Francisco scrambled to fix the extension to prevent deletion as well, and so finally their preferred version stands.

At this point, the volunteers became truly infuriated. The Wikimedia Foundation’s technical department head Erik Möller (a German) was blocked by a volunteer admin. The mailing lists erupted into displays of anger, frustration, and demoralization. Some users even expressed the feeling that the WMF was intentionally alienating the volunteers in favor of its paid staff, and perhaps its Wikipedian in Residence program. One wrote on the “meta” RfC:

They are not worried about chasing the active users away. They don’t want us. They want new users, different users, facebook users, hyperactive people, that make pictures anywhere and edit with their mobile, that add to the article what goes through their mind at the moment, not what is written in reputable books and found out after a long and tiring reasearch. They want masses, a movement, millions of bot-articles. And they hope that the new masses will finally chase the old users away, those who are questioning their godlike decisions and their godlike self-declared superpowers. You see this in every answer: “You, who have argued and voted, are only the old editors, but we care about the silent readers and the fictive new editors. So of course we stand above your arguments and elections.” Our opinions are not in the strategy focus anymore and can be ignored without consequences. In the view of the WMF, the readers are not reading the articles because we editors have written them in a way that is well appreciated, such that it raises multi million dollars of donations a year. The readers visit them because of the great software that WMF develops. They would read anything, if it was just presented by their great software.

Intentional or not, the WMF seems on course to severely weaken its most important asset: the volunteer contributors who have created the product they ostensibly exist to promote.

The crisis on the German Wikipedia remains unsettled at the date of publishing (as it is on the English Wikipedia as well).

The Scramble, and the Fallout

The official and semi-official line from the WMF has been bizarre to say the least. In response to a comment about the imposition of VE and other “improvements” on co-founder Jimmy Wales’s page, Jimmy had this to say about the “spiritual side” of the issue:

this is an extremely unfair and false representation of the situation that does nothing to bring light and love and healing and progress and does much to create the kind of tensions that make progress difficult. You’ve got the motivations exactly wrong. We badly need software improvements.

Less interested in the spiritual but rather reframing the issue in an e-commerce light, incoming Executive Director Lila Tretikov wrote:

Our site, technology and content have far reaching impact and scale. Today, we do not fully appreciate ourselves as a top-5 website from an operational standpoint. This was surprising to me and I would like to bring clarity to what this means in practice for the benefit of the staff as well as the community. I would like to outline a number of operational principles to help us navigate towards this goal. These are not something we are inventing: these are widely used high-scale product practices; we will need to modify and adopt for our use. I look forward to discussing them with you all here.

And Erik Möller hints at how they see the volunteers as lesser partners of the WMF, rather than the community they exist to serve:

Lila and I will post more thoughts on the larger issues within the coming days. We deeply regret the disruptive impact this discussion is having on Wikimedia’s mission and our work together. At the same time, working through these questions has long been overdue, and my hope is that we can come out of this with greater clarity regarding how we partner on issues that are often likely to be contentious, which includes user experience changes.

It’s hard to see how these three somewhat contradictory sentiments can help calm things down. The question is: will the volunteers stick around when they’re not given a franchise? Again, the history here is that Wikipedia was built by contributors who gave their time, energy, and expertise to help create their product. The WMF was formed (at least in part) to serve that community and support their efforts. The community had always until recently had a strong say in the policies, content, and appearance of the website. It should surprise no-one that they’re unhappy with the path the WMF is taking now. German Wikipedia administrator Henning Schlottmann, a “Wikipedian” since 2005, succinctly laid out the problem here in a widely endorsed comment, as translated by Andreas Kolbe (emphases added):

Frank [Schulenburg], too, is not looking at the real issues that the MV has ignited. The Foundation has a miserable cost / benefit ratio and for years now has spent millions on software development without producing anything that actually works. This is in large part due to the fact that decisions are made without consultation with the community. On the other hand, it has to do with the fact that people like Erik, Steven and Philippe were recruited from the community, but obviously have no experience in really getting a product “out the door” and completing a project successfully. It was a good idea to employ Rachel, so she can take care of the communication about software development. But unfortunately Erik has severely damaged her chances after less than two months.

My theory: The WMF isn’t up to the job. Nobody who works there really understands and has a handle on software projects. This is evidenced by a horrific track record over many years. That the MV is rolled out even though it doesn’t recognize many licence templates is a symptom. The underlying cause is that the MV is based on a framework that has not been validated. We see the same thing in what is really a very minor issue, the thumbnail display. The layout team wants to abolish the frame and replace it with more white space. That they have not thought of images that need a frame to really show the image (Japanese flag) is one thing. But the guys have deleted the “Zoom” icon in the thumb frame without replacement. Why? Because they have not thought about what function it might have. With image maps that icon is the only way to get to the image information and the licence info! None of them knew that. And none of them asked or tried to find out for themselves what the function of that icon was. It’s the same with the MV. It reads the licence templates according to a microformat. So far so good. But this micro format is not universally distributed. Therefore, it should either have been rolled out only when everything was converted to that micro format and the millions of files had been migrated, or the MV should have used a more flexible model for reading information. But no, the thing has now been in development for XX months and has already cost Y million dollars, so it had to be rolled out now.

But it’s not only software development. What’s it like with user recruitment? How many millions have been invested in this over the past five years? Probably a two-digit number. And how many new authors were gained by it? Correct: practically zero. Why? Like Micha above I don’t see the problem with the editor. Anyone who has the intrinsic motivation to contribute to the greatest free education project in human history will not be deterred by the editor. There are many other barriers that are more important (first and foremost the ability to prepare information appropriately, but I mention this only as an aside). So here, too, the Foundation mucks about, but has achieved exactly no demonstrable results. 

Why is it all like that? Because the Foundation (and in a similar way but to a lesser extent also WMDE) has grown much too fast. The unlimited money supply from the fundraising campaigns shows the tremendous enthusiasm of our readers, but it has seduced people into hiring staff without first agreeing on goals and methods. This excessive staff and bureaucracy then very quickly became estranged from its base, the community, and is now fighting for self-preservation. As far as content is concerned, they have nothing to show, so they have to use force. Best, –h-stt? 16:17, 16 August 2014 (CEST)

One thing should be clear: if the WMF loses its volunteers, or even starts to lose them at a faster rate than they already have been, their product will suffer greatly. If the sentiments being expressed by the German community are a sign of things to come, the talented volunteers might begin to take their talents elsewhere.

 

Image credits: Wikimedia, Flickr/gtall1 ~ licensed under Creative Commons Attribution 2.0 Generic

12 comments to The Battle for Wikipedia: How Your Donations May Be Destroying the Crowd-sourced Encyclopedia

  • Tulio Padilha

    Time to start discussing a Statement of Principles to guide a new comunity. Just like Wikitravel comunity forked and migrated to Wikivoyage, it’s time for Wikipedia’s comunities (language by language) start making their forks to where the guiding principles are enforced AND ALSO where these principles don’t favor the construction of corrupted information, starting by completelly banning biographies of living persons and for those tho died less than 5 years before.
    Many things show me that a fork in the MediaWiki development would be good too. The development of Openoffice was also a source of conflicts between Sun and the comunity, and many good news came after it was forked with the creation of the Open Office Foundation and its LibreOffice.

  • metasonix

    “They are not worried about chasing the active users away. They don’t want us. They want new users, different users, facebook users, hyperactive people, that make pictures anywhere and edit with their mobile, that add to the article what goes through their mind at the moment, not what is written in reputable books and found out after a long and tiring reasearch. ”

    That’s basically what deletionist patrollers say to justify their abuses. Most of them couldn’t give a rat’s ass about the content. Wikipedia is their videogame and they’re having fun, killing “demons”.

    • stmullin

      “That’s basically what deletionist patrollers say to justify their abuses. Most of them couldn’t give a rat’s ass about the content. Wikipedia is their videogame and they’re having fun, killing “demons”.” . . .

      by perverting copyright laws, ignoring 5th pillar, and having template tantrums . . . do not feed the trolls . . .

  • Kumioko

    I totally agree with Metasonix, the WMF simply does not care about the editors of the Wikiprojects and that has been displayed time and time again. They have no respect for the editors and the editors in turn have non respect for the WMF. Whats worse, the editing environment within Wikipedia and other projects has become progressively more abusive largely because the WMF spends too much time making changes that no one wants in order to attract a demographic of individuals that do not want to edit and not enough time focusing on the actual problems.

  • NH

    There is a saying that “Make anything fool-proof and only a fool will use it”.

    By having a certain skill level required to add articles it also ensures that the articles entered are of at least a decent basic quality level. It won’t stop all junk-posters or trolls, but it might at least slow down the drunk postings.

  • HRIP7

    Statement from Jan-Bart de Vreede (Wikimedia Foundation board) here (permalink), with discussion.

  • HRIP7

    German community survey about Superprotection here. This survey has, I believe, the second highest participation of any such survey in Wikipedia history, with close to 650 user votes against the Wikimedia Foundation to date. The only time I can recall where more (around 750) votes endorsing a proposal were made in a Wikipedia Request for Comments was prior to the SOPA protest (and in that case numbers were augmented by many non-Wikipedians who were allowed to vote). In the German survey, however, the vast majority are core users, of which the German Wikipedia has less than 1,000. Those are the users that engage in regular quality control tasks, approve contributions from new users (unlike the English Wikipedia, the German Wikipedia has a system that ensures that contributions from new and unregistered users are not shown to the public without prior review by a more experienced Wikipedian), delete copyright violations etc. So 650 is a very significant number. A number of users have gone on strike.

    In addition, a petition to remove Superprotect has been launched by a US-based user from the English Wikipedia (also on change.org).

  • […] 过去几周,维基基金会又在英文维基百科引入了新的图像浏览器Media Viewer,用户和编辑对其印象很差。Media Viewer也被引入了德语维基百科,德语维基百科的管理员修改了 javascript文件关闭了这项功能,但被维基媒体基金会的代表恢复,于是维基基金会和社区之间发生了一场“编辑战”——你移除我恢复。维基媒体基金会为此引入了“超级保护”扩展,阻止管理员修改界面。但管理员们找到了方法绕过保护——删除页面创建新的页面版本,超级保护扩展没有阻止删除。维基基金会的开发者立即修复了漏洞禁止删除。此时志愿者被真的激怒了,一些用户认为基金会偏爱它的付费雇员而疏远社区志愿者。 […]

  • […] The Battle for Wikipedia: How Your Donations May Be Destroying the Crowd-sourced Encyclopedia […]

  • […] with a similar admin revolt in the German Wikipedia, the WMF created a new access right, Superprotect, to put the relevant configuration file out of volunteer administrators’ reach. The result was […]

  • […] grantmaking operation”. Its priorities currently are to expand its software engineering staff and modernize its software, especially in the mobile sector, in order to prevent readers from flocking to rival […]

  • […] not address the issue of toxic, unpopular employees in the WMF engineering staff, starting with Deputy Director Erik Möller and cascading all the way down to their community liaisons. He is instead building on this staff. […]

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>