Wikipedia:Wikipedia Signpost/Single/2006-07-10

The Signpost
Single-page Edition
WP:POST/1
10 July 2006

 

2006-07-10

Reuters tracks evolution of Ken Lay's death on Wikipedia

The sudden death of former Enron CEO Kenneth Lay last week brought renewed media attention to how editors respond to current events on Wikipedia articles. Reuters came out with a widely reprinted story focusing on some of the early changes to Lay's article, with the headline "Ken Lay's death prompts confusion on Wikipedia".

How the editing unfolded

News reports of Lay's death began appearing around 14:00 UTC on 5 July. The first Wikipedia edit reporting Lay's death (at 14:01 UTC) was actually in error, as it gave the date of his death as 3 July. This was fixed in the following edit, and the first reported cause of death, at 14:03 UTC, correctly indicated "an apparent heart attack." This was changed to suicide two minutes later, and Reuters only began its chronology after this point. Their timeline included both causes being mentioned simultaneously, then backpedaling to saying the cause was "yet to be determined", an edit attributing the supposed suicide to Lay's "guilt of ruining so many lives", and finally restoration of a heart attack as the cause.

All of this transpired by 14:12 UTC, when the article was semi-protected, which cut down on the problems with this particular issue in the article. Interestingly, before semi-protection all of the edits indicating a cause of death, whether correct or erroneous, came from unregistered users. Reuters did note the later insertion and removal of some "speculation as to the cause of the heart attack" connecting it with stress from Lay's recent criminal trial and conviction.

Criticism and analysis of the story

As Mathias Schindler noted, in the rush to put the story out on its wire service, Reuters itself managed to misreport the source of its own information about the cause of Lay's death. The initial version of the story said the information came from a Lay family spokeswoman. Subsequently a corrected version appeared, indicating that the spokeswoman only confirmed the death, not the cause; the report of a heart attack had come from a pastor at the family's church. By the time Reuters published, more than six hours had transpired since the initial reports of Lay's death. Reuters previously contributed to publicity over a mistranslated quote from Jimmy Wales at last year's Wikimania conference purporting that Wikipedia would start permanently freezing articles once they reached a sufficiently high level of quality (see archived story).

Aside from this error, some criticism was directed at the sensationalism of the headline. Andrew Lih dismissed the notion that "confusion" was the problem or that Wikipedia was "reeling", as a subsequent headline on CNN.com put it, "rather irresponsibly" according to Lih. The accuracy of the story itself garnered less objection, but the reporting in the body of the article didn't explicitly reach the conclusion contained in the headline, much like last month's New York Times story on semi-protection (see archived story). The Times subsequently issued a correction and changed its headline after Wales complained.

In an analysis on his blog, Lih concluded that the evolution of the Lay article was actually fairly routine for the circumstances. From his background as a journalism professor, he compared it to the typical "sausage factory tour" of a newsroom where the parts of a story are put together as a deadline approaches. Lih concluded that the Reuters story was an example of "parachute journalism" where the reporter wrote from a perspective on the outside of a community, but without taking the time to understand it.

The Washington Post also carried a follow-up on the story Sunday in its Web Watch column by Frank Ahrens. Ahrens declared himself "a fan of Wikipedia" but said the incident "exposed the critical weakness of Wikipedia that prevents it from becoming the go-to source for Internet knowledge that it ought to be." He pointed to the expectations of reliability people have for an encyclopedia and the problems when this is misused to serve an agenda. On the CBS Public Eye blog, Vaughn Ververs thought this criticism was "a touch over-the-top for such a short-lived incident". But Lih agreed that it is problematic to approach Wikipedia "with the same expectations as a uniformly and systematically edited publication". He suggested trying to manage expectations while also systematically improving quality through such efforts as WikiProjects.



Reader comments

2006-07-10

Creating stable versions using existing software proposed

A new proposal to implement stable versions of articles was put up for community discussion last week. While most plans for identifying stable, quality-reviewed versions have been awaiting anticipated support for such a feature in the MediaWiki software, this proposal, dubbed "Stable versions now", would be capable of use without any additional features.

The plan, suggested by Gmaxwell, involves moving articles to a development subpage once an acceptable revision has been found to serve as the stable version. The wikitext of that revision would then be copied into article's original location and protected. The two versions should be labeled with {{stableversion}} and {{development}} templates, respectively. The article can be "destabilised" at any point by deleting the protected article and moving the development version back to that location.

Any article "of a reasonable quality level" is theoretically qualified for this proposal, without needing other designated such as featured article or good article status. The article "must contain no obvious factual, grammatical, or typographical errors and must contain at least some level of referencing." To avoid actual content forking, the protected stable article generally should not be edited for any reason, only replaced with a new revision from the development version once that is chosen.

Gmaxwell also recommended that only actively edited articles be stabilised. He explained that he hoped people would regularly "resync" the article to a new stable version. However, he said the proposal was not intended for use on controversial articles, since consensus on a particular version would be impossible to get. The effort to solve the problem of controversial articles, which Gmaxwell called a minority of articles, is what he said has made previous technical designs too complex to implement.

The proposal received an enthusiastic response from some editors, and Wikimedia Foundation interim Executive Director Brad Patrick commented, "I love it." Others raised questions about the need for administrator involvement, since the stable article would be protected and destabilisation requires the ability to delete. SPUI called it, "Yet another piece of the growing divide between admins and non-admins." Gmaxwell responded that protection was necessary to prevent a fork of the article. Lar said he thought it was a good idea and recommended trying it as an experiment on a few articles before going further.



Reader comments

2006-07-10

Wikimania updates

Related articles
Wikimania 2006

Wikimania recap
28 August 2006

Wikimania recap
14 August 2006

Wikimania recap
7 August 2006

Wikimania last-minute information
31 July 2006

Events: Contests, parties, and the local area
24 July 2006

Wikimania updates
17 July 2006

Wikimania updates
10 July 2006

Meetups And Newsworthy International Assemblages
3 July 2006

More featured speakers at Wikimania
26 June 2006

Hacking Days
19 June 2006

Featured Speakers at Wikimania
12 June 2006

Other international meetups
5 June 2006

About Wikimania
29 May 2006

About Wikimania
22 May 2006

About Wikimania
15 May 2006

About Wikimania
8 May 2006

About Wikimania
1 May 2006

About Wikimania
24 April 2006

Three years of meetups : 2003-2006
17 April 2006

Introduction to a series: Looking forward to Wikimania 2006
10 April 2006


More articles



Reader comments

2006-07-10

News and notes

Blocking changes

Tim Starling announced proposed changes to the blocking mechanism in a wikitech-l post on Monday. The change would allow for the fixing of bug 550, a request to only block anonymous IP edits from blocked IP addresses with an additional option to allow or deny creating accounts from the blocked IP. Brion Vibber said that the change might go live in as little as 24 hours.

Briefly



Reader comments

2006-07-10

In the News

Ken Lay death makes a splash

Following the quickly developing news story on the death of Ken Lay, some typical short-lived instances of biased speculation introduced to Lay's Wikipedia article caught the eye of Reuters, "Lay's death prompts confusion on Wikipedia". (See related story)

Rocketboom split draws attention

The video-blogging team of Rocketboom, which covered Jimmy Wales' appearance at the TIME 100 gala, has gone their separate ways. News of the breakup between producer Andrew Baron and host Amanda Congdon circulated on the Internet and eventually reached major media while the Wikipedia articles were being updated accordingly. Andy Carvin, a Rocketboom correspondent, analyzed how Wikipedia policies influenced what it reported about the reasons for the split and how this compared to other sites. Carvin noted that earlier it had been suggested that Congdon's article be merged with Rocketboom, observing "that's pretty much a moot point now." Interestingly, Congdon's own website directs you to her Wikipedia article to learn more about her.

Quirky editing of senator

The Salt Lake Tribune seemed to be amused in its report about a vandal adding nonsense to the article about Utah's Senator Orrin Hatch. The paper commented that "many techies aren't fans" as a result of Hatch's previous comments about music downloading.

Wikia turns political

Jimmy Wales and Angela Beesley's for-profit wiki hosting company, Wikia, Inc., launched a Campaigns Wikia site last week that received considerable publicity. In light of the efforts of political operatives so far on Wikipedia, one might expect the initiative to be a potential minefield, but Wales said it could be "a central meeting ground for people on all sides of the political spectrum who think that it is time for politics to become more participatory, and more intelligent." David Postman of the Seattle Times said he expected political campaigns to increasingly adopt wikis in some fashion, in the same way that they have begun to use blogs. On his own blog, Postman pointed out some similar local initiatives, the moreperfect.org site started by two activists and separate partisan wikis for Democrats and Republicans from Seattle company Wetpaint. Another candidate, Pete Ashdown, has a wiki for a campaign site.



Reader comments

2006-07-10

Features and admins

Administrators

Three users were granted admin status last week: Avraham (nom), Mangojuice (nom) and Tyrenius (nom).

Featured content

Ten articles were featured last week: Sikhism (nom), Poetry (nom), Knights of Columbus (nom), Cornell University (nom), Sesame Street (nom), Muhammad Iqbal (nom), Damon Hill (nom), Jabba the Hutt (nom), Manila Metro Rail Transit System (nom) and Aradia, or the Gospel of the Witches (nom).

Two articles were de-featured last week: Hero of Belarus and H. P. Lovecraft.

The latest portal to reach featured status is Portal:Portugal.

Five lists reached featured list status last week: List of circulating currencies, 2004 NFL Draft, List of Prime Ministers of Luxembourg, List of Australian ODI cricketers and List of European Union member states by political system.

The following featured articles were displayed last week on the main page as Today's featured article: Pope Pius XII, History of New Jersey, Three Laws of Robotics, Cystic fibrosis, Cædmon, Nauru and Mauthausen-Gusen concentration camp.

These were the pictures of the day last week: Hypervelocity, Caslon, Warship, Great Wall of China, Woolworth Building, Lockheed SR-71 and Toda people.

Six pictures reached featured picture status last week:



Reader comments

2006-07-10

Bugs, Repairs, and Internal Operational News

Last week in MediaWiki software

New functionality

  • Blocks of only anonymous contributions will be enabled in the next 24 hours. (Tim Starling)

Note: Last week's report, which was not ready at press time, is now available.



Reader comments

2006-07-10

The Report On Lengthy Litigation

The Arbitration Committee closed one case and opened four others this week.

Closed cases

  • Highways: A case involving naming conventions on highway-related articles, closed on Wednesday. As a result of the case, User:SPUI, JohnnyBGood, Rschen7754, and PHenry were all placed on probation, allowing administrators to ban them from highway-related articles in case of disruption. Participants were also prohibited from moving pages between preferred names until a policy on the names is adopted, and SPUI and JohnnyBGood were warned to remain civil at all times.

New cases

Four cases were opened this week; all are in the evidence phase.

  • Alienus: A case involving Alienus. Users Tony Sidaway, Nandesuka, and Jossi have presented evidence in the case, noting that Alienus has been blocked 15 times, has assumed bad faith, and has been warned many times about making personal attacks, edit warring, and incivility. Alienus had not presented any evidence as of press time.
  • Trey Stone Appeal: No evidence has yet been presented in the case, which is an appeal of an August 2005 case which banned Trey Stone from articles relating to politics for one year (to end August 11, 2006).

Evidence phase

  • Eternal Equinox: A case involving Eternal Equinox. Several users complained that Eternal Equinox has been trying to claim ownership of articles with edit wars and abuse directed at those who try to edit them. Eternal Equinox claims to have left Wikipedia, but the other parties argued that this was not credible because of a number of similar statements made previously.
  • Hunger: A case involving a dispute about articles related to The Hunger Project. One of the parties, Jcoonrod, identifies himself as John Coonrod, an executive with that organization. The dispute has been in mediation about how and whether to include unflattering material about the organization in the article.

Voting phase

  • 8bitJake: A case involving 8bitJake. badlydrawnjeff, the initiator of the arbitration request, has asserted that 8bitJake's editing on political articles was biased, and that 8bitJake was incivil to other editors on the articles. Remedies brought by Fred Bauder, and not yet voted on by other members, would place 8bitJake and related editors on probation and ban them from articles relating to the politics of the State of Washington.
  • Dionyseus: A case involving Dionyseus and Danny Pi, and their actions on Veselin Topalov, an article on a Bulgarian chess player accused of cheating. Remedies brought by Fred Bauder, and not yet voted on by other members, would ban Danielpi for a week for "discourtesy and personal attacks".
  • Iloveminun: A case brought against Minun. Evidence presented asserted that Minun and various sockpuppets violated fair use and image deletion policies by uploading copyrighted images and removing tags. Remedies supported by Fred Bauder and James Forrester would limit Minun to one account, banning Minun for a year for various actions (with all bans running consecutively), and placed on probation, personal attack parole, and revert parole.
  • Irishpunktom: A case involving Irishpunktom, Karl Meier, and Dbiv. Measures to ban Irishpunktom and Dbiv from editing Peter Tatchell for one year, place Irishpunktom and Karl Meier on probation for one year, and place Irishpunktom on one revert per article per week parole have the support of four arbitrators. Debate is still ongoing on an appropriate remedy for the actions of Dbiv.
  • Saladin1970: A case involving an appeal of Saladin1970's indefinite block originally placed by Jayjg, and later by SlimVirgin. Saladin1970 would be banned for at least 2 years, perhaps indefinitely, and placed on probation, general probation, and personal attack parole.

Motion to close

There are currently no motions to close on the table.



Reader comments

If articles have been updated, you may need to refresh the single-page edition.