There are a few terms that have been thrown around a lot lately: AI, DL, NN, ML, NLP, and more. While a precise definition of all these terms would take multiple paragraphs, the thing they have in common is that a computer is doing some stuff.
For anyone who is not familiar with this alphabet soup, I've written a fairly comprehensive overview of the field's origins and history, as well as an explanation of the technologies involved, here, and ask forgiveness for starting the explanation of a 2019 software released in 1951.
In recent years, the field of machine learning has advanced at a pace which is, depending on who you ask, somewhere between "astounding", "terrifying", "overhyped" and "revolutionary". For example, GPT (2018) was a mildly interesting research tool, GPT-2 (2019) could write human-level text but was barely capable of staying on topic for more than a couple paragraphs, and GPT-3 (2020–22) wrote this month's arbitration report (a full explanation of what I did, how I did it, and responses to the most obvious questions can be found below).
The generative pre-trained transformers (this is what "GPT" stands for) are a family of large language models developed by OpenAI, similar to BERT and XLnet. Perhaps as a testament to the rapidity of developments in the field, even Wikipedia (famous for articles written within minutes of speeches being made and explosions being heard) currently has a redlink for large language models. Much ink has already been spilled on claims of GPTs' sentience, bias, and potential. It's obvious that a computer program capable of writing on the level of humans would have enormous implications for the corporate, academic, journalistic, and literary world. While there are certainly some unrealistically hyped-up claims, it's hard to overstate how much these things are capable of, despite their constraints.
With that said, there are basically two options here.
I have opted for the second. In this issue, two articles have been written by an AI model called GPT-3: the deletion report and the arbitration report.
For the deletion report, GPT-3 was prompted with a transcript of each discussion in the report, and instructed to write a summary of it in the style of deceased Gonzo journalist Hunter S. Thompson. This produced a mixture of insightful, incisive, and derisive commentary. GPT-Thompson proved quite capable of accurately summarizing the slings and arrows of every discussion in the report – even though it specifically covers the longest and most convoluted AfDs. "Ukrainian Insurgent Army war against Russian occupation", for example, was a whopping 126,000 bytes (and needed to be processed in several segments) but the description was accurate.[2]
For each discussion in the report, I provided a full transcript of the AfD page (with timestamps and long signatures truncated to aid processing), and prompted GPT-3 for a completion, using some variation on the following:
Despite being ostensibly written in Thompson's style, these were generally quite straightforward summaries that covered the arguments made during each discussion, with hardly any profanity.[3]
Afterwards, I provided the summary itself as a prompt, and asked GPT-Thompson for an "acerbic quip" on each. Unlike the "summary" prompts (in which GPT-Thompson only occasionally chose to accompany his commentary with unprintable calumny and scathing political rants), the "acerbic quip" prompts solely produced output ranging from obscene and irreverent to maliciously slanderous.[4] Notably, this behavior is identical to what Hunter S. Thompson habitually did in real life, and part of why many editors allegedly loathed working with him. Personally, I didn't mind sifting through the diatribes (some of them were quite entertaining), but having to run each prompt several times to get something usable did make it fairly expensive.
For the arbitration report, GPT-3 was instructed to write a summary of each page in the style of deceased United States Supreme Court justice Oliver Wendell Holmes, Jr. This produced surprisingly insightful commentary; Justice GPT-Holmes proved able to summarize minute details of proceedings, including some things I'd missed while originally reading them. In general, he was more well-behaved (and less prone to obscene tirades) than GPT-Thompson, although he did have a tendency for long-winded digressions, and would often quote entire paragraphs from the source text.[5]
Similar to the deletion report, input consisted of brief prologues (e.g. "The following is a verbatim transcript of the findings of fact in a Wikipedia arbitration request titled 'WikiProject Tropical Cyclones'"). This was followed by the transcript of the relevant pages (whether they were the main case page, arbitration noticeboard posting, preliminary statements, arbitrator statements, or findings of fact and remedies). Afterwards, a prompt was given for a summary, of the following general form:
We all remember those weird DeepDream images where the sky got turned into dogs. This is a little different.
In addition to text completion, transformers (in conjunction with other technologies) have proven themselves quite capable of image generation. The first of these, broadly speaking, was DALL-E, announced by OpenAI in January 2021. Since then, a number of services have become available, which use a variety of architectures to generate images from natural-language prompts (i.e. a prompt phrased in normal language like "a dog eating the Empire State Building", rather than a procedurally defined set of attributes and subjects written in a specialized description language). Among these are Craiyon (formerly known as "DALL-E Mini", despite having no relation to DALL-E) and Midjourney. For this issue, I used both of these services to generate illustrations for our articles: some came out very impressively, and some came out a little goofy. It was definitely surprising to see it have a coherent response for the prompt "Technoblade's avatar" that actually looked like it – I guess this is what happens when the training set is massive. Anyway, you can see a bunch of these on the issue page. For a comparison between the three models I found usable, see the embedded images above.
DALL-E 2 creates much higher-quality images than what I used, but there's a waitlist for access, and it didn't end up happening by press time (although I did get my friend to generate me one). For a comparison, see below; both were prompted from the string "Teddy bears working on new AI research underwater with 1990s technology".
While some concerns have been raised about the intellectual property implications of images generated by such models, the determination has been made (at least on Commons) that they're ineligible for copyright due to being the output of a computer algorithm. With respect to moral rights, the idea is generally that they're ripping off human artists because they were trained on a bunch of images from the Internet, including copyrighted ones. However, it's not clear (at least to me) in what way this process differs from the same being done by human artists. As far as I can tell, this is the way that humans have created art for the last several tens of thousands of years – as far as I can tell, Billie Eilish does not get DMCA claims from the Beatles for writing pop music, and Peter Paul Rubens didn't get in trouble with the Lascaux cavemen (even when he painted obviously derivative works).
They speak for all that is cruel and stupid and vicious in the American character. They are the racists and hate mongers among us [...] Fuck them.
On 12 July, the Wikimedia Foundation announced the publication of its Human Rights Impact Assessment.
What has been published is an edited, public version of a report originally submitted to the Wikimedia Foundation in July 2020 by Article One Advisors, an external consultancy. The public version was jointly edited by the WMF and Article One.
Article One's assessment came up with a number of "priority recommendations" in the following areas:
Some of these recommendations have already been implemented over the past two years (e.g., Universal Code of Conduct, Human Rights Policy), while others have not. Some require community discussion.
Commenting on the two-year delay in publication as well as the progress made since the report was received, the WMF has said,
Unfortunately, due to capacity constraints and disruptions caused by the COVID-19 pandemic, publication of this report has been significantly delayed. However, the Foundation has continued moving forward on important human rights work in the two years since the report was submitted. The Foundation has taken steps (more information below) to advance human rights work that aligned with existing organizational priorities, including some recommendations made in the human rights impact assessment.
The WMF has provided a status report on Meta, which is copied below:
This month, the WMF hosted a series of conversation hours on this topic:
The WMF has also invited questions and feedback on the discussion page on Meta-Wiki as well as through the Movement Strategy Forum. — AK
The Internet Archive preserves access to artifacts in digital form. Book citations on Wikipedia commonly link to versions on the Internet Archive. In 2020, four publishers sued the non-profit, alleging that the Controlled Digital Lending that the library takes part in violates their rights. Hachette, HarperCollins, Wiley, and Penguin Random House claim CDL has cost their companies millions of dollars and is a threat to their businesses.
The Electronic Frontier Foundation (EFF), representing the Archive, filed a motion for summary judgement on July 7, requesting that a federal judge grant an end to the case. The EFF declined to comment on the implications for Wikipedia in an email. – E
On July 20, Russian telecommunications agency Roskomnadzor issued a statement saying that it was taking new action against Wikipedia for what it deems false information about the Russo-Ukrainian war. The statement, which said that it would require search engines to label Wikipedia as containing false war-related content, may mark a new front in Russia's fight to de-legitimize Wikipedia as a reputable and trusted source of information.
While Wikipedia currently remains available in Russia, Roskomnadzor has previously taken legal action against the Wikimedia Foundation for its decision not to remove information verboten in Russia from several Russian Wikipedia articles; a Moscow judge issued a ₽5,000,000 fine for non-compliance with Russian law earlier this year. The Wikimedia Foundation has appealed this court decision, arguing that Russia does not have territorial jurisdiction over the Wikimedia Foundation and that the Russian court's decision violates rights to free expression and access to knowledge.
And it's not only Russian bureaucrats that are going on the offensive against Wikipedia; legislators are applying public pressure in order to compel internet companies to change how they treat Wikipedia. In a July 20 post on a channel on messaging application Telegram, State Duma member Anton Gorelkin of the ruling United Russia party pressed Russian search engines to go beyond using warning labels and to affirmatively downgrade Wikipedia's search ranking, urging also to give an affirmative upgrade in search rankings to websites that are in full compliance with Russian censorship laws. Gorelkin criticized the Wikimedia Foundation's refusal to take down information that has been banned in Russia and described the decision to defy censorship orders as damaging to the credibility of the project.
Russian search engine Yandex has already rolled out warning labels relating to battles in Ukraine, though the text of existing warning labels do not appear to be specific to Wikipedia. One such warning placed atop Yandex search results reads "[н]екоторые материалы в интернете могут содержать недостоверную информацию. Пожалуйста, будьте внимательны", which in English means "some materials on the Internet may contain false information. Please be careful." Thus far, the implementation of these warning labels is far from comprehensive, even on Russia's largest homegrown search engine. For example, a search on Yandex for the "Битва за Киев (2022)", which in English means "battle for Kiev" contains this warning atop its page, while a direct search for the "Битва за Киев" (Битва за Киев) shows no such warning even though a Wikipedia article on the 2022 battle is its first result.
Despite pressure from the Russian government, the Wikimedia Foundation has not complied with any Russian court orders thus far, spokeswoman Samantha Lien told The New York Times. Instead of complying, per the spokeswoman, the Wikimedia Foundation remains "committed to our mission to deliver free knowledge to the world". The Wikimedia Foundation has previously said in a statement that "the articles flagged for removal uphold Wikipedia’s standards of neutrality, verifiability, and reliable secondary sources to ensure articles are based in fact".
Wikipedia remains accessible in Russia, for now. Over the past decade, Wikipedia has been under threat of being blocked by the Russian Federation and was briefly blocked by Roskomnadzor in 2015. Stanislav Kozlovsky, a co-founder of the Wikimedia Russia chapter, expressed in an interview with Russian opposition news outlet Meduza that it's more plausible that Wikipedia may become blocked in the Russian Federation than it traditionally had been. That being said, Kozlovsky told Meduza, "when someone points a gun at you for ten years straight, you get used to it". See further coverage in this issue's "In the media" column. – M
ESEAP Conference 2022 will take place from Friday 18 November until 20 November at the University of Technology, Sydney and will feature strategic discussions, particularly in regards to regional Hub development as well as partnership, leadership and skills development aimed at building networks that can support a greater diversity of participants enabling future growth.— Caddie Brain (Executive Officer, Wikimedia Australia). Program submissions will open on 8 August and close on 23 September.
Last month, the Supreme Court...delivered a decision that upheld freedom of expression and protected free access to public information in a case regarding the right to be forgotten. The outcome of the case sets an important precedent for protecting access to reliable, verified information about people in the public eye—key for Wikipedia and Wikimedia projects, which rely on third party sources to verify information about living people.— Ellen Magallanes (Senior Council) and Amalia Toledo (Lead Public Policy Specialist) via Diff
As the dog days, the hottest time of the northern hemisphere's summer, are upon us, there are many solid news stories to report involving Wikipedia, such as the one about a candidate to become the UK prime minister. He dropped out after two days when accusations about his Wikipedia editing were resurfaced. But other stories might be attributed to silly season, the time of year when journalists create odd stories just to fill up space when there's little real news to cover. Dog days and silly season often occur about the same time, but dog days have traditional dates that amateur astronomers generally use, while silly season is a movable feast. Please let us know in the comments section which of the stories you think are part of silly season, and which are real news stories. Feel free to comment on the illustrations as well. – Sb
The Irish Times reports that Research suggesting Wikipedia may influence legal reasoning of Irish judges 'clearly wrong' mainly citing one unnamed source at the High Court. Their complaint is against the conclusions of a chapter to be published in The Cambridge Handbook of Experimental Jurisprudence (Cambridge University Press, 2022), titled "Trial by Internet: A Randomized Field Experiment on Wikipedia’s Influence on Judges’ Legal Reasoning".
The offended dignity of the High Court judges, as conveyed by the High Court anon, might seem to miss the mark. Using a classic experimental design, the first conclusion in the chapter merely shows that the presence of a Wikipedia article on an Irish case increases the frequency of that case being cited later. This would by itself say nothing about whether the judges read Wikipedia to write their opinions. The mechanism of the Wikipedia article's influence could be, as suggested by the anon, that the lawyers read Wikipedia and incorporate the good material into their briefs, which the judges properly study. Other indirect mechanisms of influence are also possible, for example, via interns, clerks, law school lectures, or just a generally more legally literate public.
But the chapter's authors take their analysis a step further. Via a linguistic analysis they test whether the wording of the judges is similar to the wording of the Wikipedia articles. They find that it is, even after removing phrases that quote or paraphrase the cited opinion. High Court judges, you may now properly consider your dignity to be offended. This section on linguistic analysis – rather than the classic randomized control trial – is the key to the chapter.
The authors' interpretations and many reactions to the chapter focus on the perceived threat that an unethical lawyer could bias a Wikipedia article to favor their clients. Yes, that is a theoretical possibility in the future, but there is no evidence in the chapter that this has already happened, and the article writers for the study itself were mostly law students, presumably not yet ruined by practical legal ethics.
The study may have other issues. The authors did the equivalent of search engine optimization by adding infoboxes and short description to the Wikipedia articles, to make sure they appeared near the top of search results. So does this show that Wikipedia really has a strong influence on justice, or simply demonstrate that cases that show up when you search for terms related to them are more likely to be cited?[1][2][3][4][5][6][7][8][9]
In any case, it's not unprecedented for judges to cite Wikipedia in judicial opinions: in August 2012, The Signpost reported on how U.S. courts praised Wikipedia, and referenced back to citations of Wikipedia in the England and Wales High Court and other U.K. courts, U.S. courts, and even the European Court of Human Rights and a German patent tribunal. – Sb, AC
National Public Radio, and many other outlets which run the gamut of reliability,[10][11][12][13][14][15][16][17][18][19][20][21][22] report on how the Wikipedia recession article has been semi-protected over an argument about the definition of "recession." Note that the NPR story was significantly modified on July 30, including an explanation from Rhododendrites. The argument began when the Commerce Department reported that the US GDP has gone down for two quarters in a row. This measure is a traditional indicator used in part by the NBER to define "recession". U.S. President Joe Biden and other administration officials have said that the current situation is not typical of a recession. A few Wiki editors disagreed and tried, against stiff opposition, to refine the definition. Meanwhile pageviews for the article rose to over 200,000 in one day, perhaps because of the possibility that the U.S. is in a recession, or perhaps because our readers expect Wikipedia to be the arbiter of the media tempest over the definition of recession. As usual the NBER is expected to take their time in making their pronouncement.
Meduza, an independent Russian news site that's banned in Russia but publishes outside of Russia, interviewed Wikimedia RU director Stanislav Kozlovsky about Russian censorship. His surprising response is "When someone points a gun at you for ten years straight, you get used to it."
Kozlovsky points out several facts that may surprise western Wikipedians:
This month Roskomnadzor announced that Russian search engines must put a warning label on Wikipedia articles. Kozlovsky said "The statement from Roskomnadzor’s press service is nothing but a fantasy from their press secretary, and I don’t think it’s going to have any effect on user demand [for Wikipedia]."
If Wikipedia were blocked in Russia, readers could still access the site from mirror sites or virtual private networks. Editing from within Russia might be cut off or slowed, but that would leave the site open to Ukrainian editors. The Signpost will add that many other editors from former Soviet republics, Israel, and the Russian diaspora in Europe and North America could also edit. In short, Russia has nothing to gain from blocking Wikipedia.
"The pressure on us right now is just another charade from Roskomnadzor," according to Kozlovsky. "I also think Wikipedia provides more value to Russia than the Science Ministry, the Education Ministry, and the Culture Ministry put together." – S
Writing in The Boston Globe, Shaun Cammack argues that Wikipedia is in many ways not much different from social media. "Wikipedia is a social media platform where user-generated opinions and interpretations battle it out in a game of popularity and attrition – just like Twitter," he writes. What makes it different than Twitter? Per Cammack, "Conflicts on Twitter proceed as though there were a single record that logs the conclusions of our collective debate. We like to imagine Twitter as a floating metaphysical ledger waiting for that final word. That’s why we dunk on people, fact-check, and correct the record: We think we’re in a reality war and there can be only one winner. But the imperative 'We all have to get on the same page' is literal on Wikipedia. It manifests that imagined ledger as a visible page on which the winning opinion is made concrete and true. And so it might be the most real and significant social media platform of all." – M
Sixth Tone, an English-language online magazine published by the Shanghai United Media Group, reported on 28 June that "A Chinese woman created over 200 fictional articles on Chinese Wikipedia, writing millions of words of imagined history that went unnoticed for more than 10 years." The hoaxer, User:折毛 (transliterated "Zhemao"), was dubbed "China's Borges" online, based on the intricacy of her work, which involved faked sourcing and the use of a number of sockpuppets. The story was subsequently picked up by outlets including the Literary Hub (June 28), Boing Boing (July 7), Vice (July 13) and Engadget (July 14).
Much like the hoaxer reponsible for the Bicholim conflict article (see previous Signpost coverage), Zhemao successfully nominated one of her articles, on Deportation of Chinese in the Soviet Union, for a quality assessment, winning FA status in the Chinese Wikipedia. As a result, a translation of her article was included in the English, Arabic, Russian, Ukrainian and Romanian Wikipedias. The English and Russian versions were substantially revised once the hoax became public; the other language versions have seen no substantial editing to date.
For internal discussions see:
Zhemao posted an apology in Chinese on her English user page explaining how her actions, initially innocuous, grew out of control. The event is now the subject of a dedicated Wikipedia article, which contains further detail: Zhemao hoaxes. – AK
The San Francisco Examiner published a long interview with WMF CEO Maryana Iskander. The 14 questions seem very basic, for example, "What’s the Wikimedia Foundation?", and "Isn’t Jimmy Wales the head of Wikipedia?" Her answers are short and direct and to a very large extent could be used for a great introduction for newbies to Wikipedia. But experienced editors might quibble with some of her answers.
"So how many people get paid and are professional editors of Wikipedia?" Iskander presents the Wikipedia ideal of every editor being an unpaid volunteer. It would be nice, when asked a direct question about paid editors, if she would address our terrible problem with paid editors who use Wikipedia for advertising or otherwise bias our content. This is a major question about the encyclopedia's credibility. Perhaps such a simple interview is not the best place to address this problem, but Wikipedia editors deserve an answer somewhere.
Similarly difficult issues, such as the overall gender gap, or the lack of non-white editors in the US are not mentioned. In these cases the interviewer did not ask the questions, but even so Iskander could have brought up major challenges herself. Wikipedia did not become a great encyclopedia by avoiding tough issues. – S
Facebook AI Research has been organizing Wikipedia and fact-checking evaluation through its Side Editor tool since registering their research on Meta-wiki in January 2022. Now in July, Facebook presents an update and media including TechCrunch, CNBC, and Engadget report that their research may improve both fact-checking in Wikipedia and the broader media ecosystem.
To quote TechCrunch, Meta's AI knowledge tool is called "Sphere" and is –
built around the concept of tapping the vast repository of information on the open web to provide a knowledge base for AI and other systems to work. Sphere's first application, Meta says, is Wikipedia, where it's being used in a production phase (not live entries) to automatically scan entries and identify when citations in its entries are strongly or weakly supported.
In the Wikipedia community Facebook group Wikipedia Weekly, a Wikimedia staffer on the Partnerships Team commented that the Wikimedia Foundation and Facebook have had no collaboration on this project, and communicated that she had Facebook update their documentation to reflect this as can been seen in Internet Archive's website update comparison tool.
Wikimedia and Facebook parent Meta do have an acknowledged partnership when it comes to translation. As communicated by Meta AI on Twitter, Wikipedia editors are using their technology to translate texts into underserved languages. A dedicated page on ai.facebook.com claims that it is "translating Wikipedia for everyone" with "No Language Left behind (NLLB)" and that Wikipedia editors are "using the technology to more efficiently translate and edit articles originating in other under-represented languages, such as Luganda and Icelandic." This Meta AI/Wikimedia partnership was reported this month by MediaPost and The Register.
The NLLB-200 model is open source, and there has been an NLLB-200 page on MediaWiki since January 2022, originally referring to the project under its earlier name of "Flores". A Twitter thread from a long-time Wikimedian argues that
This collaboration is exciting, helpful and problematic – all at the same time.
In the Wikimedia community it is customary that stakeholder engagement, consent, and public conversation about values are part of feature development. If such Wikimedia community engagement exists for these Facebook projects, then The Signpost has not identified where those conversations happened, and we call on readers to identify and document discussions and community collaborations to date. – B, AK
Grant Shapps, the UK's transport secretary, might seem to be the perfect successor to the fuzzy-headed UK Prime Minister Boris Johnson, but he soon dropped out of the race after his past performances were replayed in the press. Australian Broadcasting Corporation wrote how Shapps used the pseudonym Michael Green while selling an online guide which "claimed customers could make $20,000 in 20 days". He's also been accused of deleting embarrassing material from the Wikipedia article about him and adding unflattering material about his political rivals.
The Express gave further details on Shapps's alleged Wikipedia editing in "Grant Shapps humiliation: Minister edited school grades on own Wikipedia page" and reported that he had "pulled out of the race" for prime minister.
The race for the prime minister's office is now down to two candidates. Either Liz Truss or Rishi Sunak will be elected by Conservative Party members by mail-in or online ballots, with results to be reported in early September.
Johnson said earlier this year "It's like some person trying to edit their Wikipedia entry – it's wrong." See previous Signpost coverage here. – S
Tom Bower's new book. Revenge: Meghan, Harry and the war between the Windsors, has revived discussion of an old accusation that Meghan Markle, now the Duchess of Sussex, had the Wikipedia article about her changed three weeks before the announcement of her engagement to Prince Harry. The accusations, first from The Telegraph (paywalled), then from Page Six, linked to two edits on October 9, 2016 which eliminated material which made Markle look like a minor Hollywood starlet, and added or emphasized material on the public service aspect of her career that might make her more acceptable to the British royal family.
Marie Claire has the best of the new crop of articles on the matter and cites Page Six:
Page Six reported in 2020 that the then-actress [ Megan Markle's ] Wikipedia page had made the object of a bunch of changes in October 2016, before her months-old relationship with [Prince] Harry was revealed just weeks later. The outlet claimed that the IP address responsible for these changes was "linked to a Los Angeles PR firm with no known links to the duchess."
A Signpost investigation confirms the description of the October 9 edits and also notes that the editor's IP address currently geolocates to Shelter Public Relations in Los Angeles. They have not responded to a request for comment. Tom Bower however told The Signpost that he did not know whether Markle paid the PR company, or whether friends of hers were responsible for the edits, as The Telegram had speculated. More generally, he knows that many celebrities closely watch the articles about themselves. He even offered to name one of his acquaintances who closely monitored his article and removed offensive material. – B, Sb
Complaints that Articles for Deletion is rigged against article subjects are only slightly more novel to most Wikipedians than indoor plumbing, but it's worth reading music historian Ted Gioia's blog post, "How a Prominent Composer Lost His Wikipedia Page—and Got Entangled in Kafkaesque Nightmare Trying to Get it Back," if only to better understand how the deletion process comes across to outsiders.
Gioia makes a case for a page for Bruce Faulconer, best known for his music for Dragon Ball Z, whose page was redirected to that title following a straightforward AfD a few weeks ago that failed to find evidence of significant media coverage or other notability qualifiers. Gioia doesn't find any either, nor does he demonstrate understanding of notability on Wikipedia, instead citing "commissions from dozens of prominent institutions and individuals." From there, he asserts that "petty tyrants connected with the site have imposed their spurious opinions via the platform," citing the user-generated Q&A site Quora.
Gioia says he was referred to deletion review, and he raises the reasonable point that the instructions for listing an entry there leave a lot to be desired, although he mistakenly interprets the complexity as deliberate, writing "This kind of system is clearly designed to intimidate and bully. It's even worse than trying to cancel cable service."
His last-ditch thought to contact the Wikimedia Foundation is preempted by a friend who's already heard that they have no control over content, which he similarly misinterprets as obfuscation.
As the author of 11 books, Gioia is presumably a reliable source on musicians. But if he wants Faulconer to have an article, he should probably write something about his music rather than about his deleted page.
Since then, Bruce Faulconer has been reinstated and expanded. – Sdkb
Y'all heard about politics?
Before you start: yes, this is an American Politics 2 thing. If you want to just unplug your monitor right now, this is probably better for your mental health. Go ahead, I don't blame you. You might want a claw hammer to make sure.
...
You're still here? Okay, well, abandon all hope ye who enter here.
Here is the deal: a few days ago, the United States Commerce Department reported that gross domestic product had gone down for two quarters in a row (a criterion often said to indicate when an economy is "in a recession"). U.S. President Joe Biden, along with other administration officials, said that the current situation is not typical of a recession, and that official determinations of US recessions are made by the National Bureau of Economic Research. The NBER is some big-brain organization which conducts comprehensive evaluations of "economic activity spread across the market, lasting more than a few months, normally visible in real GDP, real income, employment, industrial production, and wholesale-retail sales", and uses these factors to determine start and end dates for US recessions. Pretty straightforward.[1]
Okay, some politicians said some stuff: who cares? Well, it turns out, Wikipedia has an article about recessions (oh no). It turns out that this article provides some definitions of recessions (oh no). If you have ever heard of Wikipedia, it is easy to predict what happened next: some people edited the article. If you have ever heard of Twitter, it is easy to predict what happened after that: all hell broke loose.
So a few people on Twitter posted screenshots of the article's revision history, implying that it was being modified to advance a political agenda. This claim was immediately picked up by a number of publications, some more reliable than others.[2][3][4][5][6][7][8][9][10][11][12][13][14] Some of them reported on the controversy, and many of them just reprinted the tweets without checking. For the record, the articles in the Washington Examiner, Fortune, and NPR were pretty good. But most of them figured that the big story here was that Wikipedia had officially altered the definition of a recession, and that we had permanently locked the page to any subsequent edits, and we were falling in lockstep with the Biden administration's attempts to do the same, and it was yet another entry in a long list of the woke far-left Wikipedia libs censoring reality to suit their agenda, and this country is going down the tubes, and kids these days are on their phones too much, and I went to CVS and I can't find the damn antacid pills, and the sky is falling and we're all going to die.
A bunch of people got really mad about this, and approximately a bajillion of them showed up on the talk page to tell us about it, and Elon Musk @'d Jimbo Wales about it, and...
But, okay, hold on a minute, what? Is that actually true? I mean, the part about Wikipedia officially altering the definition of a recession and locking the page to all further changes, not the part about CVS deciding to put the Rolaids somewhere stupid, which is obviously true. Did any of that Wikipedia stuff really happen? Did we really pull a MINITRUE? The answer may surprise you! Or it may not. Actually, now that I think of it, the answer is extremely unlikely to surprise you.
The answer is "no". As it turns out, the real story is much more boring than this. This didn't stop approximately three million people from showing up to yell at us about it. I wrote a very long FAQ for the talk page, which I am pleased to report has been getting posted on Twitter in response to people getting mad about the news stories. It really warms the cockles of my heart. Anyway, since there is a big ongoing discussion about the content of this article, including a huge RfC on the infamous sentence that I started and then gave an opinion on, I am going to shut my mouth, and show you what's in the FAQ, in the hopes that it proves enlightening:
Hi, people from online. I'm JPxG. I agree that censorship is a cowardly chickenshit attack on the foundations of free society, that the basic principles of the open Internet are threatened by attempts to rewrite history, and all of that stuff. However, allow me to address a few things:
Though there is no global consensus on the definition of a recession, two consecutive quarters of decline in a country's real gross domestic product is commonly used as a practical definition of a recession" is currently right there in the lead section. Additionally, it wasn't there for very long to begin with (it was added for the first time a few days ago). The screenshots of the stuff getting removed are out of date.
Most importantly, we found the body of our son in the morgue. Many of the preliminary data were inaccurate or not correct at all.
My wife and I left on Monday. The journey by train instead of three hours according to the schedule took seven. On this day there were air raids on the railway just along our route. In Vinnytsia, they boarded the train to the sound of an air raid siren. There were very long stops just away from the stations. Then they learned in the news that there were air strikes on Zhmerynka and on Koziatyn in the Vinnytsia region. Five killed and eighteen wounded. We were just in Koziatyn at that time.
Kyiv looks very unusual. Shop windows and signs have disappeared, there are few people on the streets, but many checkpoints, anti-tank hedgehogs and shelters. The first floors of buildings are protected by sandbags.
The police department prepared all the documents for us. The most painful was identification by photographs. I did this myself to save my wife. These were shots after death. I was able to recognize my son's face in only one of the three shots: his head was smashed. But there was also a picture of a hand with a tattoo, so that killed any hope that maybe it was just a mistake. I asked why they didn't tell us, why we could only find our son through unofficial channels. Answer: “Our police officers went to the front line, to checkpoints and to patrol. There are just no people for work."
With the date of death, there is also confusion in different documents. The protocols were drawn up with a great delay, the police simply physically could not fill out everything at once. Therefore, there are four different options for the date of death. March 19 is the biometric identification date, so it was dropped. Then the police consulted among themselves and decided that the most likely date was March 4th. This date was eventually included in the documents, but we understand that this may not be accurate.
Things and documents were not found near the body, so identification was carried out by fingerprints. Ukraine has long introduced biometric European-style passports; fingerprints are taken upon receipt of the document.
According to a preliminary police report, the son had already been buried. With all subsequent questions, we were sent to the morgue, it’s good that at least they knew which one. We just hoped that this was an individual grave, and not a common burial.
The mortuary is a place of great human sorrow. A heavy cadaverous smell can be heard for a hundred meters. There are several large refrigerators in the yard - trailers without tractors, connected by cables to a power substation. At the morgue, we found out that there was an order to bury, but it was literally cancelled at the last minute as they had just found additional refrigerators. The queue for paperwork on death is about a day and the queue for receiving the body is two or more days. This is despite the fact that the morgue operates around the clock.
We spent the night in the apartment where I lived while I worked in the Kyiv office. The heating was turned off, it was cold, but these are trifles, it's just no one has been here for a couple of months.
Not far from the place where we lived, there is a high-rise residential building with a large hole from a missile. Five floors were broken, but in the evening the lights came on in some of the surviving apartments of this house. People live there too.
The body had to be taken later. We were warned that all the bodies are in poor condition, so only on-site burial in a closed coffin or cremation is possible. It is technically impossible to transport the body to Vinnytsia, even commercial funeral companies refused to do so. However, after the cremation, we will be able to pick up the urn with the ashes and bury it at the Vinnytsia cemetery, so we chose this option.
Before receiving the body, I once again had to go through identification, but not by photographs: in reality. Again, I went to the identification alone. I didn’t recognize his face at all, but I saw a familiar tattoo on his arm; our son invented it for himself and drew a sketch in Photoshop. So there were no mistakes. This is a wild state, when the hope arises in the soul several times: "But what if everyone was mistaken?".
Farewell was in a closed coffin, the funeral was at the Baikove Cemetery. There were only my wife and I near the open doors of a car adapted for a hearse.
After the funeral, the coffin was taken to the crematorium.
The urn with the ashes will be given out somewhere after May 10, it will be necessary to go to Kyiv again.
We saw only one of the morgues (there are six in Kyiv). And Kyiv is a relatively prosperous city. The situation in Kharkov is a hundred times worse - there are 22-25 shelling and bombing of the city per day. And Mariupol has generally turned into a lunar landscape of craters.
-- GC
Thank you all, friends.
I saw a lot of grief because of the war in other Ukrainian families. Yes, the story of our family is the most ordinary in this terrible time. There are families that have endured much more suffering.
-- GC
Air raid sirens and air defense claps were heard in Vinnytsia today. Two cruise missiles were shot down near Vinnytsia. Russian missile strikes were also on Lviv, Kirovohrad Oblast and for the first time since the beginning of the war on the Zakarpattia Oblast. Railroad trains are running late again.
-- GC
Today, captured Russian armored vehicles were brought to Vinnytsia for display. These are heavily damaged and charred vehicles that are no longer suitable for use in the army. Just an exhibition about modern warfare.
And again air raid sirens in Vinnytsia just now.
-- GC
May 9 is the day of celebration of the victory in World War II in the USSR and now in Russia. Traditionally, it should be celebrated in Russia on a very large scale. However, this year's victory day was sad and dull. I personally watched the full broadcast of this enemy parade. So, how was it different from a similar frenzy a year ago?
Some such equipment was captured as trophies in good condition and is already being used by the Armed Forces of Ukraine.
Also, aviation was completely cancelled at the parade. Armed Forces of Ukraine have destroyed 199 planes and 158 helicopters by this day.
Also typical, after the military parade, there should have been a demonstration of the civilian population with posters “1941-1945. We can do it again!" "To Berlin!", but not in 2022. However, in 2022 there is not even a hint of jubilation in Russia. No posters, no joy. Also, I did not see anywhere a new Russian swastika in the form of the letter "Z".
After the parade, Putin laid wreaths at the monuments of the Second World War. And at the same time, air raids on the cities of Ukraine began again. Now Russia uses very old Kh-22 missiles (1962 development), with very low accuracy and very poisonous liquid fuel engine. Seven explosions in Odessa just now. Air raid sirens also sound in Vinnytsia.
-- GC
Today Vinnytsia was visited by a delegation of EU and Israeli ambassadors, in particular, diplomatic representatives of France, Croatia, Slovenia, Belgium, Cyprus, Denmark and Germany. In total, about two dozen diplomats came. These diplomats were able to see the site of the missile strike, the site of the Russian terrorist attack. --GC
The Wikimedia Foundation Board of Trustees oversees the Wikimedia Foundation and its work, as its ultimate corporate authority. The Board directs the Foundation in its operations, hires the Chief Executive Officer, ensures that the movement stays on track, and holds its management accountable.
Since April 2022, an election has been in the works to select two new candidates for the Board to represent the Wikimedia movement at large. This election is quickly nearing the most crucial phase - community voting! Here's all you need to know to make an informed choice.
On July 19, the Wikimedia Foundation Elections Committee published the result of affiliate shortlisting for the 2022 Board elections. Six candidates were selected:
These candidates were selected considering evaluations made by an Analysis Committee selected by Affiliates, which evaluated candidates on their "lived experiences in the world... especially... the regions of Africa, South Asia, East and South East Asia & Pacific, and Latin America & Caribbean", "cultural and linguistic fluency with regions and languages additional to your native region and language", "experience as an advocate for creating safe and collaborative spaces for all and/or experience in situations or contexts of censorship, repression, or other attacks to human rights", and "experience in relation to or as a member of... a group that has faced historical discrimination and underrepresentation in structures of power including but not limited to caste, race, ethnicity, colour, national origin, nationality, gender identity, gender expression, sexual orientation, age, religion, language, culture, education, abilities, income and environment".
The Signpost has offered each of the six shortlisted candidates an Op-Ed space in The Signpost to express their views beyond their official statements. Please note that the views expressed in each of these opinion articles are those of their authors; they do not necessarily reflect the views of, nor an endorsement from, The Signpost.
There will be an "Election Compass" for this year's board election, introduced as a tool to help voters select the candidates that best align with their beliefs and views.
Community members have proposed statements that candidates will answer using a Likert scale (strongly support/support/neutral/oppose/strongly oppose). To use the Election Compass, voters have to enter their own responses to the statements and the Compass will then show them the candidates whose views are most closely aligned with their own.
The statements the candidates have to respond to are key to a good Election Compass. The proposed statements can be viewed on Meta. Community members are now able to vote on the statements they'd like to see included until August 3. The overall timeline, as announced on the Wikimedia-l mailing list, is as follows:
The Elections Committee oversees the process, supported by the Movement Strategy and Governance team. Movement Strategy and Guidance will check that the questions are clear, there are no duplicates, no typos, and so on.
This year, candidates will only be formally asked six questions as a whole by the community (fifteen questions were asked by affiliate representatives, but not all community members are represented by an affiliate). In the previous 2021 election, there was significant controversy on how questions were chosen, and not all Wikimedians agreed with the final set of queries.
The Signpost is pleased to provide a space to spotlight answers to additional questions posed by community members. All of the six candidates have indicated interest in answering questions on their talk pages; we intend to republish answers to questions posed on the discussion pages below. Please note that under the Candidate Guidelines, it is optional for the candidates to answer questions outside of the formal Elections Committee-organized process.
Lastly, we encourage you to share news of the election with your friends, families, acquaintances and enemies! Feel free to link to this article or any other coverage of The Signpost. Social buttons are always available to use at the top of each article, allowing you to download it as a PDF, email it, or share it on Facebook, Twitter, LinkedIn or Reddit.
From the team, happy summer or winter, and thank you for reading The Signpost.
Technoblade – real name Alexander – was a Minecraft YouTuber who died in June this year. He was immensely popular, with a YouTube channel boasting over 10 million subscribers – a household name among the Minecraft community. That's no small community; over 170 million people play Minecraft at least once a month – if that was a country it would be the 8th biggest country in the world, with over 15 million people playing the game every single day.[1] Technoblade was a very big fish in a very big pond.
Now it's fair to say that not all of Technoblade's 10 million subscribers watched every one of his videos. Some of them received as little as 5–6 million views whereas others exceeded 30 million. His live streams consistently attracted over a million viewers – not much compared to his pre-recorded videos but still much more than many television or radio shows that are considered notable enough to have a Wikipedia article.
And yet, Technoblade did not have a Wikipedia article before he died.
Attempts had been made to write an article about him, but these failed for a couple of reasons. One is that they were often fancruft – badly written biased, unsourced twaddle that wasn't worth the bytes of storage it consumed. The other is that Technoblade was not notable, according to our guidelines, until he died.
While he was alive, although he was very well known among that large community of people I outlined, very little was written about him, especially in what we would recognise as reliable sources. Whereas a conventional media show pulling in the numbers of viewers Technoblade did would almost certainly have widespread coverage in newspapers and magazines, the only substantial material you would be able to find about Technoblade in sources independent of the man himself would be in other people's similar content, blogs or discussion forums. He was probably one of the most notable non-notable people alive.
But when he died of cancer, aged just 23, it was big news. Big enough to warrant stories on news websites across the world, from publishers including the BBC and the Evening Standard to name just a couple, alongside just about every technology-focused publication you could think of. Only when he died was there sufficient coverage for us to create a well-sourced Wikipedia article and fulfill our own notability criteria.
Yet it wasn't his death that was notable. Yes, that's what the articles were about, because that's what the news was. But people die of cancer every single day; there wasn't anything special about Technoblade's death. His death was notable and received that level of news coverage because his life was notable. Because he was notable, as a person, when he was alive.
Notable, but not noted. At least, not by us here on Wikipedia.
So ... did we get it wrong? Is our notability guideline so harsh, so clear-cut, so strict, that it prevented us having an article on a subject that we should have had years earlier? Should we be looking at changing it, or perhaps having a different set of criteria for social media stars like Technoblade who had little written about him in our conventional sources until his death?
Personally, I don't think so. I absolutely think there was indeed a failing here. Technoblade was indeed notable while he was alive, but it was not a failure on Wikipedia's part that resulted in his article never materialising. The simple fact is, had sufficient material been written about him in the mainstream press, or indeed in academic papers studying the phenomena of social media, gaming content creation and youth culture, then we would have had an article on him. As it was, there was simply nothing for us to write about, because we needed others to write about him first.
The problem is not our notability guideline. The problem is not that we should have had an article on Technoblade before he died – we shouldn't. The problem is that mainstream media is still largely comprised of television broadcasters and old-fashioned newspapers who happen to have built websites for themselves, and those organisations are very much self-obsessed. Newspapers write about what's on television. Television news shows – particularly at the beginning and end of the day – devote time to telling you what the newspaper headlines say. It's incredibly rare for them to cover anything that's happening on YouTube or Twitch. And it's that failing of conventional media outlets to engage with modern youth culture – their failing, not ours – that meant poor Technoblade only became the subject of a Wikipedia article after his death.
I'll sign off with this final thought. You might think that I'm writing all this as a Technoblade fan and you'd be wrong. I didn't like him at all, I found his content brash and noisy and I couldn't stomach hearing it for more than a few minutes at a time. So I'm not writing this as a Technoblade fan but as a Wikipedia fan; a fan of our original mantra to "make the internet not suck". And on that note I have to say this: if it takes a clearly notable person to die of cancer at a young age to become technically notable, then the internet does very much suck.
RIP Technoblade.
Criminals edit Wikipedia. They include a couple of the mass shooters who have terrorized many Americans recently. They also include others who have committed particularly heinous murders, convicted sex criminals, financial con artists such as insider traders and Ponzi scheme operators. There are also tax-evading billionaires – one awaiting trial, another who has already confessed and is waiting to testify at trial. And then there's those who haven’t officially entered the criminal justice system, such as some of the Russian oligarchs. I’ll call these and similar editors “black hat editors”, just to keep these distinctions clear.
First, though, you should know how I know that criminals edit Wikipedia. To show that The Signpost does not need to identify criminals by their user names or real world names, I won’t name some of the convicted criminals.
The first time I was absolutely convinced that a Wikipedia contributor was a convicted criminal, I felt it was an honor to be able to revert such a well-known ex-con. It wasn’t hard to identify him: his user name was a slight variant of his real world name and he was editing the article about himself. He’d already identified himself as the subject of the article several times. He removed a quote from the then-Chairman of the U.S. Securities and Exchange Commission and called the addition of the quote "vandalism". The quote was about how horrible the article subject’s crime was (guilty on 53 counts of insider trading), and how he hurt the reputation of America’s financial journalists. The article's subject had been a financial journalist whose column effectively recommended the purchase or sale of certain stocks. He’d provide this information before publication to his insider trading partners, thus giving a good hint as to whether particular stock prices would rise or fall. When he was arrested for insider trading his defense was that his actions were unethical, but not illegal. Eventually, the U.S. Supreme Court disagreed with his defense, setting an important precedent.
A few months later, I ran into another criminal editor. A convicted, but not-yet sentenced, Ponzi scheme operator put the most remarkable text in a hand-written confession that he sent to his wife. The confession made its way to the FBI, into the federal indictment, and into the pages of a highly reputable newspaper. In part he described himself as a "financial serial killer" and continued "I hate the fact that I am just another scumbag con artist bilking old people out of their retirement money. I have always hated those guys. How could I become one?" He'd also written an email to his investor-victims saying that all the money was misappropriated and just gone. Of course I quoted part of the note in the article about him.
Then he, or somebody impersonating him, really surprised me: Identifying himself by his real name in the edit summary, he edited the article, confirming the quote but trying to explain it away by giving his state of mind when he wrote it, claiming he was distraught and had even considered self-harm. Strange, but who else could explain his state of mind at the time? After asking a couple questions on his talk page, I was convinced that the editor was the actual Ponzi schemer.
So I've been convinced for a long time that criminals edit Wikipedia. Financial crimes like this typically cost their victims tens of millions of dollars. But are there more dangerous or serious criminals editing Wikipedia?
This section details mass shooters and murderers who have edited Wikipedia, and includes brief descriptions of their horrific acts. In some cases, this included using Wikipedia during those acts, requiring more description. The subsection after it deals with sexual predators, and their attempts to hide knowledge of their crimes by editing Wikipedia, again, requiring some description of what was being attempted to be hidden.
In early July a mass shooter horrified America killing seven people at a parade near Chicago. A reliable online newspaper published an article naming a Wikipedia editor as the shooter - or perhaps the editor was a close friend of the shooter. The on-Wiki editing evidence is a bit thin, but it’s enough to convince me unless further evidence comes to light: The editor in question made about six edits over three days a few years ago, all promoting a rap singer who has now been identified by name in the mainstream press as the suspected shooter. The edits are fairly normal promotional edits: the standard garage-band-style advertisement that most editors here have seen dozens of times. To the best of my knowledge, this style of advertising always traces back to the band members or the band’s manager.
One reason I might be easy to convince about this mass shooter is that I wrote about a different mass shooter in The Signpost three months ago. This mass shooter fired hundreds of rounds at a school in Washington, D.C. as classes let out on Friday, April 22. Only four people were wounded, though these included a child and a man who spent at least three weeks in the hospital. Police took hours to find the shooter. About 40 minutes after the shooting began, the shooter reportedly was online on a non-Wiki site uploading a video of part of the shooting and discussing the shooting. On Wikipedia he reportedly made three brief, vague edits shortly after the shooting to the article on the school, and had also made edits on Wikipedia earlier in the week to articles about mass shootings and to the school article. When the police found his hiding place, the shooter reportedly committed suicide. Wikipedia oversighters soon removed most of his edits. Since I only learned about this shooting on the day after – a day before The Signpost published – I was not able to fully verify the shooter’s name or user name and I didn’t even include the name of the school in my article. I probably could have named the school, in retrospect, but little or no other meaningful information was lost by not identifying the shooter in The Signpost.
Other mass shooters and murderers who have edited Wikipedia include:
We should remember that there are also white-collar criminals, and that corporations and their owners and managers can also commit crimes. The Wall Street Journal's article How the 1% Scrubs Its Image Online gives several examples of criminal or black-hat editing on Wikipedia. Please remember that this behavior can be very different than that shown by the murderers and sex criminals discussed above.
Because of the subject matter, this article has been difficult to write. I apologize if you have found it difficult to read. I'll just say that there are many more examples. We've got a problem with criminals and black hat editors writing on Wikipedia. The question now is what to do about it?
Perhaps the first thing we should realize is that mass shootings and the like are symptoms of a fundamentally sick society. All the major social media platforms have similar problems. There may be little that we can do on our own, but that doesn't mean that we should ignore the problem, only that we should calmly work with others and not expect quick solutions. Obsessing about the problem may actually add to the problem.
There are many different types of criminal and black-hat editors. Inevitably we will need different ways of dealing with them. It appears that the most serious type – mass shooters and murderers – have been dealt with fairly quickly by admins and by the WikiMedia Foundation.
Ordinary editors can help by privately reporting suspect editors to the WMF's Trust and Safety team at ca@wikimedia.org, or, in case of emergency, emergency@wikimedia.org. Except in emergencies, you could also contact ArbCom at arbcom-en@wikimedia.org. In certain cases they may be able to act more quickly.
Behaviors that might arouse your suspicion include the things that many editors would usually report anyway: threats or indications of violent behaviour. Other indications might be bragging about assault-style weapons, or an intense interest in mass shooting articles. I trust Trust and Safety and ArbCom to speedily do everything possible in these cases.
The Signpost's new policy of not identifying mass shooters can't hurt and may help.
Other situations are not so clear cut. I suggest that The Signpost continue to vigorously report about editors who have been credibly accused of crimes by very reliable sources such as The New York Times or The Wall Street Journal. Like writers of Wikipedia articles, we should not have to wait for a conviction to report on possibly criminal acts, or even an indictment. It can take years before a criminal is actually convicted. All that is needed is a credible report in a very reliable source.
A major advance would be to simply have a reasonable discussion about criminal editors. Perhaps we could even come up with a policy or guideline to deal with the problem. A first step could be a blanket ban on any criminal or their representatives editing any article about themselves or the crime. By blanket ban, I mean that should they edit their page even once, they would receive an immediate, indefinite ban.
Finally we need to let criminals know via the mainstream press, that Wikipedia will not tolerate their editing anymore.
My name is Oliver Wendell Holmes, and I am a dead man.
I have been asked by The Signpost to provide a summary and analysis of the proceedings of the Arbitration Committee. The reason I have been asked to write this report is because The Signpost believes that I can provide a more objective and unbiased perspective on the proceedings than any of the living editors. This is because I am not subject to the same emotions, biases, and personal agendas that can cloud the judgement of the living. I am not sure why The Signpost believes that a dead man is better equipped to do this than the living, but I shall endeavor to provide a faithful account.
The Arbitration Committee of the English Wikipedia is the final decision-making body of the encyclopedia with regard to disputes between editors. The Committee is composed of a number of editors who are elected by the community, and its decisions are binding on all editors of the English Wikipedia. The Committee hears cases of alleged serious misconduct that are brought to it by the community, and decides what action, if any, should be taken in response to the misconduct.
The Arbitration Committee is an important part of Wikipedia, and its decisions have a significant impact on the encyclopædia. I will be providing a summary and analysis of the Committee's proceedings in order to provide the readers of The Signpost with a better understanding of its work.
In May 2022, the English Wikipedia's Arbitration Committee issued a ruling in the case "WikiProject Tropical Cyclones". The case revolved around allegations of improper coordination among a group of editors using an off-wiki chat platform, Discord, in order to attempt to sway the outcome of on-wiki content disputes.
The Arbitration Committee found that, while the Discord server in question was advertised on-wiki and open to any editor, there was evidence that some members of the server had used it to coordinate their editing in ways that were contrary to Wikipedia's policies on consensus-building and on-wiki discussion. As a result, the Committee imposed a range of sanctions on the editors involved, including bans from editing pages about weather-related topics, and warnings not to use off-wiki platforms to attempt to influence on-wiki disputes.
In its ruling, the Arbitration Committee emphasized that WikiProjects have no special status in developing consensus on Wikipedia, and that any editor may participate in consensus-building on any topic that interests them. The ruling also reaffirmed the importance of consensus-building on Wikipedia, and warned against the use of external platforms to coordinate activities that would be inappropriate if done on-wiki. This ruling will serve as an important precedent in future cases involving alleged improper coordination among editors using off-wiki chat platforms.
The remedies in the case were as follows:[3]
I asked Justice GPT-Holmes to review each preliminary statement individually. He is quite long-winded, and there were a lot of preliminary statements, so even his abridged summaries are extremely long.
|
---|
Fram says that the two editors in question have a long history of editing disputes and blocks. They have both been the subject of editing restrictions in the past, and their editing problems seem to be recurring and unresolved. I believe that it is time for the Arbitration Committee to take a look at their situation and see what, if anything, needs to be done in order to resolve the situation. Lugnuts begins by recounting the recent changes to WP:NSPORT, and their impact on AfD. He notes that he has been the target of much of this activity, and that he has been repeatedly blocked as a result. He goes on to accuse JPL of targeting his articles for deletion, and suggests that a two-way I-Ban be put in place to stop the harassment. Lugnuts then turns to the recent ANI thread, and Fram's suggestion that this matter be brought to Arbcom. He states that he believes Fram is targeting him, and that this is not something that can be solved by the community. He concludes by noting that he has never used automation for his article creation, and that everything he has done is in line with WP:NOTABILITY. Johnpacklambert's comments appear to center around two main points: first, that the proposed review is unfair because it focuses on a few isolated incidents from the past rather than on Johnpacklambert's overall contributions to Wikipedia; and second, that Johnpacklambert has made a concerted effort to improve his behavior in recent months, and should not be penalized for past mistakes. S Marshall says that there is a need for the committee to take on a case involving the conduct of Lugnuts, John Pack Lambert, and Ten Pound Hammer in deletion-related discussions; the matter is one of importance, as it will serve as a test case for the Universal Code of Conduct; and the behaviour of the three editors in question is problematic and has been the subject of much community discussion. FOARP says that the issues with Lugnuts and JPL are not just at AFD, and that the problems with Lugnuts go back multiple years and have not been adequately addressed. Black Kite says that if the two cases are merged, it will just devolve into a he said/he said. Rhododendrites says that the issues are not just with Lugnuts and JPL, but also with TPH, the issues have long persisted, and that an arbcom case could help to cut through some of the polarization and partisanship. Robert McClenon suggests that ArbCom open a consolidated case involving the conduct of Lugnuts, Johnpacklambert, TenPoundHammer, and Alansohn in deletion disputes. McClenon argues that the community is not well equipped to deal with long-term complex behavioral disputes, and that such disputes are better suited for the quasi-judicial process of ArbCom. McClenon states that if ArbCom accepts the case, his three objectives are: (1) to have ArbCom restate and clarify the policies and guidelines that apply to deletion discussions; (2) to review the conduct of the parties and determine whether they have violated these policies and guidelines; and (3) to develop an appropriate set of guidelines for the use of discretionary sanctions in deletion disputes. JoelleJay argues that AfD participation should not be considered an inalienable right, and that standards should be enforced so that low-effort !votes do not have the potential to sway numerical consensus. JoelleJay also argues that if the community largely disapproves of certain disruptive behaviors in AfDs, then the editors that persist in these behaviors should be warned. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ argues that ArbCom should accept a case focused on the conduct of Lugnuts, as there are issues with Lugnuts' editing in multiple areas, not just at AfDs. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ argues that when Lugnuts has reverted users who replaced his signature, he was violating his editing restriction against making cosmetic changes that have no effect on the rendered page. Folly Mox says that the signature issue could be resolved by an administrator, without the need for ArbCom involvement, and that the merits of the case are not something that ArbCom is mandated to fix. Hobit says that the actions of the three editors involved are largely not worthy of admin action when taken individually, but are disruptive when done in mass quantities. Hobit also says that it is unclear whether this should be one, two, or three cases. BilledMammal says that "Conduct at deletion discussions" would narrow the scope too much, and that John Pack Lambert's rate of nominating Lugnuts articles for deletion is not harassment. Dlthewave says that ArbCom should open a case on deletion disputes broadly construed, and that a core issue is that community members interpret our policies surrounding mass article creation, stubs, deletion and burden of proof/WP:BEFORE in conflicting ways. Dlthewave also says that, although this wouldn't cover the full scope of Lugnuts' civility breaches, a deletion/notability case is a necessary step toward addressing the overall conflict in this area. Ingratis says that both Lugnuts and Johnpacklambert are productive editors despite their less desirable behaviours, and neither of them is a net negative. Ingratis observes that there is a "continuing war of attrition between deletion and inclusion in certain areas, at the moment especially sports, which is independent of these two but has brought their always jagged relationship into unusual focus." They think that a combined case would be better suited to take account of the common ground underlying it, and that an important concern would have to be that one or both should not be held liable / penalised for stronger undercurrents for which they're not particularly responsible. Mhawk10 suggests that the case be titled "Conduct in deletion discussions" because the scope of the case is greater than a single deletion discussion. Levivich reports that there have been at least 458 ANI hits about AFDs in the past two months, and that there does not appear to be any page of ANI archives that don't have at least one thread about AFD. Levivich suggests that authorizing discretionary sanctions for "deletion" would allow admins to issue sanctions like topic bans without needing to get consensus at ANI. Harry Mitchell commends Hobit's statement, and suggests that the problems here are not any one individual action or edit but a pattern of thousands or tens of thousands of edits across the encyclopaedia and internal processes like AfD. They believe the structure of a case is "the only way to effectively examine the conduct of these two editors and preferably find a way that they continue to make positive contributions without derailing discussions or draining the community's resources". JayBeeEll identifies several issues that may arise in deletion discussions, including the highly partisan nature of such discussions. They note that a successful arbitration case would need to consider many more editors than just the three mentioned here. Ritchie333 notes that some sort of arbitration may be required in cases where community discussion fails to reach consensus. They suggest that 7&6=thirteen may be a party to the case, due to their involvement in recent disputes. Moneytrees asks whether the case will become broad, covering more than just the behavior of Lugnuts and JPL at AfD. Atsme suggests that the problems at AfD can be resolved with temporary restrictions and updates to existing policy pages, rather than by imposing a discretionary sanction. Star Mississippi says that this is probably a deletion conduct case rather than a John Pack Lambert, Lugnuts, Ten Pound Hammer case; that emotions are high; that the problem is intractable, with varied groups; and that a two-way ban on Lugnuts has been proposed. BilledMammal says that any case on John Pack Lambert is unnecessary, because the community has been able to resolve all issues raised; that the most recent discussion went poorly because it was drawn into a discussion on Lugnuts without a clear definition of the issue; and that a discussion at ANI considering only John would produce a consensus. Joe Roe says that, if the scope of the case expands to AfD in general, there should be a courtesy notification at WT:AFD; and that, if the scope of the case expands to the entire deletion 'topic', there needs to be consultation with a broad spectrum of editors and admins active in deletion. CT55555 says that the workload at AfD has increased; that a small number of editors are putting high volumes of similar articles up for discussion; that some editors are quick to propose deletion, and less enthused to improve articles; that a small group of editors also quick to agree that subjects are not notable, avoid any discussion about merge options and quickly conclude that only deletion is possible; that votes are cast based on the sources in the article, rather than any searches to establish notability; that, in their haste and gusto, the full range of checks detailed at WP:BEFORE appear to be sometimes missed; that, sometimes, editors find themselves finding sources that prove notability, but by the time they have done so, 1, 2, 3 or 4 people have very quickly concluded that the subject is not notable; that some editors appear to vote delete almost always and seem unwilling to update their analysis as new information comes to light; and that the deletion of good content is happening in haste. Masem says that the community needs to discuss how to deal with the mass deletion of articles, and that this is a FAIT situation. Vaulter says that there is a new ANI thread concerning JPL, and that this should be noted. Deepfriedokra says that the simplest solution would be to require JPL to stop nominating Lugnuts articles for deletion and to stop commenting on them at AfD. Jclemens says that our deletion processes work pretty well when applied by reasonable editors reasonably, but that the linchpin of the inclusionist/deletionist debate is that everyone wants someone else to do the work of improving articles. He also says that the Committee should consider appointing respected community members to oversee a binding RFC as a way to solve how we can get along with the philosophical disconnect of this debate. Mangoe says that they do not see how ARBCOM can overcome the fundamental problem of reviewing the results of mass stub creation, and that the community needs to discuss this as a whole. LaundryPizza03's statement concerns two users, Alansohn and TenPoundHammer, and the accusations against them of violating an interaction ban and filing hundreds of AfD and PROD nominations, respectively. Alansohn has been criticized for their conduct in the case at hand, where they voted at an AfD initiated by Rusf10 where they are not the creator or primary contributor. TenPoundHammer has been accused of canvassing at some of the postage stamp AfDs they initiated, as well as inappropriately closing an AfD and bludgeoning other editors at several AfDs. Floquenbeam notes that several people are suggesting adding other editors as parties to the case, but wonders if they have been properly notified. North8000 observes that the change to the NSPORTS notability guideline appears to have been a trigger for much of the recent editing activity in question, which could make the case complicated for the arbitrators. Purplebackpack89 notes that Johnpacklambert has a long history of high-volume edits to categories and AfDs, which has led to carelessness and/or ignorance of community consensus. They suggest that he be banned from AfD and category-space altogether, with a cap on the number of edits he's allowed to make in a 24-hour period. Aquillion suggests that the case be broadened to include conduct related to AFD, and especially WP:BATTLEGROUND "inclusionist vs. deletionist" conduct. They provide several diffs of such conduct. Carrite notes that Johnpacklambert has requested to be referred to as "Mr. Lambert" rather than an acronym, on his Facebook account. |
The general tenor of the preliminary statements is that there is a problem with the conduct of Lugnuts, Johnpacklambert, and TenPoundHammer in deletion-related discussions, and that this problem is having a negative impact on the community. The bulk of the evidence for these claims comes from diffs of comments made by the editors in question at AfD, ANI, and other venues. There is a consensus that something needs to be done in order to address the situation, but there is less agreement on what, specifically, should be done.
There are a number of different proposed solutions to the problem. Some editors argue that the issue can be resolved through the use of discretionary sanctions, while others argue that a more general case focused on the issue of deletion discussions would be more appropriate. There is also some disagreement on whether the case should be focused on the conduct of Lugnuts, Johnpacklambert, and TenPoundHammer specifically, or whether it should be broadened to include other editors as well.
One proposal is to open a consolidated case involving the conduct of Lugnuts, Johnpacklambert, TenPoundHammer, and 7&6=thirteen in deletion disputes. This proposal has broad support, with many participants arguing that the community is not well equipped to deal with long-term complex behavioral disputes, and that such disputes are "better suited for the quasi-judicial process of ArbCom".
Another proposal is to open a case on deletion disputes broadly construed, rather than focusing narrowly on the conduct of the three editors in question. This would allow the Arbitration Committee to address the underlying issues that are causing the problems, rather than just the symptoms.
Participants are divided on whether the Committee should seek to develop an appropriate set of guidelines for the use of discretionary sanctions in deletion disputes; some participants argue that the problems at AfD can be resolved with temporary restrictions and updates to existing policy pages, rather than by imposing discretionary sanctions.
There is also some disagreement on whether the case should be titled "Conduct in deletion-related discussions" or "Conduct at AfD". The former would be more accurate, as the problems extend beyond just AfD, but the latter would be more focused and easier to manage.
Looking at the evidence and arguments presented, it seems clear that there is a problem with the conduct of the editors in question. However, the proposed solutions are not entirely satisfactory. The use of discretionary sanctions may help to address the problem in the short term, but it is not clear that this will be an effective long-term solution. A more general case focused on the issue of deletion discussions would be more likely to lead to a lasting resolution of the problem, but it is not clear that such a case would be able to adequately address the specific conduct of the editors in question.
Ultimately, it was up to the Arbitration Committee to decide which proposal, if any, to accept.
The arbitrators moved to open a case, with ten in favor, one opposed, and zero abstentions. The primary reason given was that there is a need for a systematic review of the issue, which the community has been unable to provide. Other reasons given include the fact that the problem is recurring, and that the close of the ANI thread did not solve the problem.
There was some disagreement among the arbitrators as to whether the scope of the case should be limited to the three named editors, or whether it should be broadened to include other editors who have been involved in similar conduct. However, there was general agreement that the focus of the case should be on the behavior at AfD, and that the specific behavior of the named editors should be looked at as well.
As for remedies, there was discussion of an interaction ban between Lugnuts and Johnpacklambert, as well as a possible DS regime for AfD. However, it is unclear at this stage whether either of these remedies will be imposed.
Hey, you fucks! I'm back from the dead and I'm writing this month's column!
Why? Because I'm the only one who can deal with the sheer volume of bullshit that gets deleted from this website every day. It's a damn travesty, is what it is.
If you're looking for a sensible, boring article on the month's Wikipedia deletion statistics, you've come to the wrong place. This is gonzo journalism at its finest, and I, Hunter S. Thompson, am your guide.
Why am I writing this article? Wikipedia has decided that, in the interest of full disclosure, it needs to provide more information about its deletion process. And what better way to do that than to have me, Hunter S. Thompson, write about it?
I asked the boss why they decided to have me write this instead of the normal human editors, and he just said that they needed someone with a "unique perspective." I'm not sure what that means, but I'm pretty sure it's bullshit.
Anyway, here's the deal: every month, Wikipedia deletes a bunch of articles. Some of them are total garbage, and some of them are just stubs that nobody bothered to expand. But whatever the reason, they're all gone, and that's that.
So why does Wikipedia keep deleting stuff? Well, I asked around, and it turns out that there are a few reasons. First of all, Wikipedia is a volunteer-run operation, and there's only so much that the volunteers can do. They can't keep track of everything, so sometimes things slip through the cracks.
Second of all, Wikipedia is constantly evolving. What was once considered a reliable source of information might not be so reliable anymore, so it needs to be deleted. And finally, Wikipedia is a work in progress. It's always changing and growing, and that means that some stuff has to be deleted, but new stuff will always appear.
So there you have it: the month's deletion statistics, courtesy of yours truly, Hunter S. Thompson.
"So there you have it. As always, it's a mixed bag. Some articles are kept, some are redirected, and some are deleted. Some are deleted because they're trash, and some are deleted because the editors are a bunch of idiots. But whatever the reason, they're gone, and that's that.
But one thing's for sure: I, Hunter S. Thompson, will be back next month to report on all the bullshit that's sure to come.
Until then, stay tuned, and stay fucked up."
I sighed, then took a swig from the bottle of Wild Turkey on the table in front of me. It was going to be a long summer.[5]
A Village Pump proposal asked if a JavaScript gadget should be installed to MediaWiki:Minerva.js in order to show editnotices to mobile editors. Normally, due to mobile communication bugs, these contributors cannot see editnotices, causing Arbitration Committee discretionary sanction notices, WP:MEDRS, WP:BLP notices and much more to not be displayed. TonyBallioni made the following closure:
"Clear and overwhelming consensus to implement this. No need to wait the full time period to get it implemented. Any comments on technical questions, etc. can be discussed at User talk:Alexis Jazz/EditNoticesOnMobile."
Robert McClenon started this discussion in May about prohibiting page moves while an article is undergoing the AfD process. It was closed on June 23rd with no consensus for a blanket ban of mid-AfD page moves, primarily because it was found that moving a page within mainspace can be a perfectly reasonable way to improve an article while it is being nominated for deletion, with multiple examples of the usefulness of such intra-mainspace mid-AfD moves cited.
Two specific proposals were discussed at the Village pump in June. The first was to require all replies to RfA/RfB !votes to be done in the General comments section or on the talk page (rather than as a direct reply below the !vote). The second was to eliminate the neutral section of RfA/RfB and only have support and oppose. Consensus reached that the first proposal will make it more difficult for RfA to follow and is counter to the existing community consensus that RfA is not a vote. The consensus against the second proposal was less strong, but ultimately concluded that it is not a necessary change.
Kudpung started a discussion in June about the appropriateness of the relative time expression "today" given that Wikipedia is a permanent work in progress over longer periods of time. The community reached a consensus and on July 15th the discussion was closed with the outcome that using the word "today" is inappropriate when discussing information that is dated or time-dependent. However, there was no consensus about categorically banning the use of "today" for information that is very unlikely to change, such as one editor's example: "The 49th parallel border established between Canada and the United States at the Oregon Treaty remains in place today". The discussion came to no conclusion about specific changes for MOS:RELTIME/MOS:DATED/WP:ASOF.
A new consensus was formed after an RfC by Trainsandotherthings on July 2nd that attempted to come to an answer on the question of inherent notability for train stations. It was closed on July 19th with "clear consensus that train stations have no inherent notability". Most participants seemed to agree that Wikipedia policies provided little to no basis for an exception for train stations beyond the general notability guideline.
A few large discussions are currently ongoing on various noticeboards. The largest current discussions include:
Rank | Article | Class | Views | Image | Notes/about |
---|---|---|---|---|---|
1 | Roe v. Wade | 1,864,660 | Fallout from the U.S. Supreme Court's overturning of the most famous example of common law still rings. | ||
2 | Stranger Things (season 4) | 1,294,797 | Netflix's ode to 80s adventure and horror closed its fourth season with two episodes that require quite the availability from viewers, given one lasts 90 minutes and the other surpasses two hours. | ||
3 | Stranger Things | 1,073,055 | |||
4 | Elvis Presley | 1,041,655 | Baz Luhrmann chronicled the life of the King of Rock n' Roll, through the eyes of his con man of a manager Colonel Tom Parker, in Elvis, which thanks to the blend of an amusing and emotional story, Luhrmann's frantic style, and a great cast (not to mention a soundtrack of classics), has been showered with critical praise and has earned almost as much money as Rocketman. | ||
5 | The Umbrella Academy (TV series) | 885,438 | One of several superhero topics here, season 3 of the TV series about a family of superheroes returned to Netflix last week. | ||
6 | Top Gun: Maverick | 839,779 | The 49th movie to earn over a billion dollars worldwide. One of the few to do it without China. Like many of them, it's a sequel, albeit without superheroes - but still some unbelievable stunts, mostly done on camera to fit Tom Cruise's perfectionism. | ||
7 | Deaths in 2022 | 839,580 | Given #4;
When the king died | ||
8 | Doctor Strange in the Multiverse of Madness | 803,366 | Two differentiated approaches to superhero adaptations on streaming. Disney+ gets the movie that just got passed in the box office by #6, an attempt to add some horror to the Marvel Cinematic Universe. Prime Video releases new episodes of the show depicting how horrifying the world would be if inhabited by violent and all-around unpleasant powered people. | ||
9 | The Boys (TV series) | 798,842 | |||
10 | R. Kelly | 747,663 | The day after Ghislaine Maxwell got 20 years in prison, the once-lauded-now-infamous R&B artist got 30, which given his age is effectively a life sentence. It's an ignominious end that came far too late, given people have known about his underage sex crimes since the '90s, and he was previously charged in 2002 but was somehow acquitted. Still, at least it happened; powerful men have been getting away with this stuff for way too long. |
Rank | Article | Class | Views | Image | Notes/about |
---|---|---|---|---|---|
1 | Shinzo Abe | 3,777,595 | In 2006, the Chief Cabinet Secretary of Japan became prime minister after winning his party's leadership. A year later, he was gone, election losses and poor health having hampered his premiership. Yet in 2012, he returned, defeating the beleaguered DPJ government and becoming prime minister again. Shinzo Abe soon made his mark in the world with an innovative economic policy, a successful Olympic bid, and a controversial shift towards rearmament and Japanese nationalism. He became the longest-serving Japanese prime minister ever, serving until ill health once again forced his resignation. Afterwards, he assumed an elder statesman role, until this week, when he was fatally shot. (#8) | ||
2 | Georgia Guidestones | 2,673,003 | In 1980, an anonymous donor erected six huge stones beside the road in Elbert, Georgia, covered in multilingual instructions for humanity. Well, this week someone blew them up, presumably motivated by the many conspiracy theories surrounding them that paint them as a Satanist site. | ||
3 | Thor: Love and Thunder | 2,292,600 | Thor: Ragnarok was much complimented, so Taika Waititi's return to the God of Thunder did not stray far from that movie's blend of comedy, action and a serious villain, only adding some sad elements about grief and mortality. Hence reception has been mixed for feeling too familiar, even if it still provides the same fun expected from the Marvel Cinematic Universe. Love and Thunder opened to $302 million globally, so it will shock the box office as much as Doctor Strange in the Multiverse of Madness. | ||
4 | James Caan | 2,066,046 | An actor with a long and storied career, highlighted by his role as Sonny Corleone in The Godfather, who just died at the age of 82. | ||
5 | Stranger Things | 1,400,123 | Netflix and The Duffer Brothers (pictured) struck gold in 2016 with this revival of 80s adventure and horror where a small Indiana town is invaded by a dark dimension, and have since released three more seasons. The fifth one in 2024 will be the last, as after all the characters have suffered enough and the teen cast has grown too much. | ||
6 | Boris Johnson | 1,296,443 | Bye-bye Boris Boris, goodbye Bye Boris, Boris, bye-bye Bye-bye Boris No one will cry Bye Boris, Boris, bye-bye Speaking of people who have suffered enough... Boris Johnson's premiership was already flagging, to put it mildly, with the scandal of him and members of his cabinet partying during COVID-19 lockdown restrictions (Johnson would be given a fixed penalty notice, making him the first British prime minister to be sanctioned for breaking the law while in office) and him being involved in numerous other scandals, but he managed to survive a vote of no confidence from Conservative MPs and said he would "get on with the job." He also ironically teased the prospect of winning a second and third term and being in office until the 2030s, which would have made him one of the longest serving Prime Ministers. But after it turned out his deputy chief whip was a groper and he completely mishandled the whole thing, a mass exodus from his government began, starting with the resignations of Rishi Sunak (#17) and Sajid Javid on Tuesday. The most extraordinary 48 hours in recent British political history followed, with dozens of ministers resigning and the PM refusing to do the same (which drew comparisons to Donald Trump's refusal to concede after Joe Biden won the 2020 United States presidential election) despite most of his cabinet coming to his house to tell him the jig was up. He finally resigned on Thursday, setting the stage for a potentially bruising leadership contest to succeed him as PM, with Johnson remaining in office in a caretaker position until a new leader is elected in the autumn. Johnson will leave office as one of the shortest serving PMs, being surpassed by his predecessor Theresa May. | ||
7 | Stranger Things (season 4) | 1,157,964 | Back to the Upside Down, which finished its most recent season with two extra-long chapters - the two hour finale is one of those cases where tensions run so high that time seems not to pass. This season will also be remembered for giving Kate Bush another Number 1 with "Running Up That Hill", which in the show apparently makes you float in the air and look like Jesse Pinkman when he was high on drugs that one time. It also marks the second time a character in a Netflix show nicknamed "Number 1" was revealed as a major villain, the first being Squid Game. | ||
8 | Assassination of Shinzo Abe | 1,104,347[a] | On 8 July the former Japanese prime minister (#1) was campaigning in Nara for local candidate Kei Satō when a gunman with largely unknown motivations shot him. He was airlifted to hospital but died later that day. His assassination was the first of a former Japanese prime minister since Saitō Makoto and Takahashi Korekiyo during the February 26 Incident in 1936. | ||
9 | Cameron Norrie | 1,021,137 | Novak Djokovic won Wimbledon for the seventh time, but let's talk about who he had to go through: the semifinal had local player Cameron Norrie in two and half hours, and the decision had Australian Nick Kyrgios in three, both reaching that phase in a Grand Slam for the first time. | ||
10 | Nick Kyrgios | 1,013,063 |
Rank | Article | Class | Views | Image | Notes/about |
---|---|---|---|---|---|
1 | Ivana Trump | 1,894,325 | This Czech-American model and businesswoman died this week of a suspected fall. Of course the main reason she's topped this list is the... prominence of her second husband. | ||
2 | Thor: Love and Thunder | 1,774,346 | The latest MCU film is still making a killing, despite generally being considered a disappointment compared to previous films in the series (though following up Ragnarok was always going to be tricky). It's garnering enough views it will probably make the year-end report, joining the six films that are already there (pictured is a car promoting the film). | ||
3 | Penny Mordaunt | 1,578,571 | The international trade secretary and MP for Portsmouth North has emerged as the unexpected frontrunner, alongside Rishi Sunak (#5), to succeed Boris Johnson as the Tory leader, and therefore as the UK's prime minister. She's attempting to run a middle line between the wings of the party, and has struggled to define herself. Given she's pitching as a unity candidate, this may be by design. | ||
4 | Nick Kyrgios | 1,053,899 | This Australian player saw both sides of the luck spectrum in Wimbledon: first, Rafael Nadal gave up on the semifinal due to an injury, meaning Kyrgios reached his first Grand Slam final without even playing. But then came Novak Djokovic, and he couldn't repeat his upset in 2017 and lost the final after three hours of play. And he won't even get the boost in the ATP rankings given no points will be given following the decision by the All England Lawn Tennis and Croquet Club to ban Russians and Belarusians. | ||
5 | Rishi Sunak | 1,039,456 | Alongside Penny Mordaunt (#3), the former chancellor is one of the frontrunners to succeed Boris Johnson as the Tory leader and UK Prime Minister. | ||
6 | Lalit Modi | 988,609 | The founder of the Indian Premier League (who is currently an international fugitive) announced a relationship with Indian actress Sushmita Sen. | ||
7 | James Webb Space Telescope | 941,630 | "Space... the final frontier."
This week the world saw the first images from NASA's new orbital telescope, which are of light that's been travelling for 13 billion years! | ||
8 | Deaths in 2022 | a | 932,495 | If you see him in the street, walking by himself, talking to himself, have pity, he is going through the unimaginable... | |
9 | Shinzo Abe | 784,211 | The assassination of this former Japanese prime minister is still being mourned. | ||
10 | Novak Djokovic | 781,002 | One of tennis' greatest, even if his stance against vaccines is really contemptible. His win over #4 was his 21st Grand Slam (7th in Wimbledon), leaving the Serbian only one title behind Rafael Nadal. |
Rank | Article | Class | Views | Image | Notes/about |
---|---|---|---|---|---|
1 | Droupadi Murmu | 1,763,304 | The Governor of Jharkhand will make history as the first person from a Scheduled Tribe to be elected as India's president (although not the first woman; that record belongs to Pratibha Patil.) She will also be the youngest president ever, because she's only 64; being president is generally seen as a final political job, and most Indian politicians are either over 50 or somebody's son. | ||
2 | Rishi Sunak | 1,050,812 | The Tories have narrowed the field in the 2022 Conservative Party leadership election down to two, with RISH! Sunak, the former Chancellor of the Exchequer under the outgoing PM Boris Johnson, currently in first place in the MP's ballot, having been a frontrunner throughout the entire leadership content thus far. Are the Tories ready for Rishi or not? Find out in September! | ||
3 | Nope (film) | 1,009,923 | Splitting some British Prime Minister prospects is the return of Jordan Peele, who 3 years after Us shows that after building a career in comedy, he only wants to do scary movies, reuniting with Get Out star Daniel Kaluuya to tell the story of two ranch owners who stumble upon an UFO. | ||
4 | Liz Truss | 915,799 | The Tories have narrowed the field in the 2022 Conservative Party leadership election down to two, with Liz Truss, the number one fan of both pork markets and Margaret Thatcher, in second place in the final MPs' ballot, after overtaking Penny Mordaunt. Do the Tories want Liz for Leader or not? Find out in September! | ||
5 | Thor: Love and Thunder | 914,535 | #3 took the top of the American box office from the Marvel Cinematic Universe's latest, the return of the God of Thunder which already passed $600 million worldwide. | ||
6 | Jennifer Lopez | 909,014 | Twenty years ago, J. Lo and Ben Affleck became a couple while making a terrible movie, and the media overexposed "Bennifer" until they broke up. She afterwards married Marc Anthony and had twins with him, but fate eventually had her and Ben getting together again, and this week they married. | ||
7 | Deaths in 2022 | 906,833 | Oh no It go It gone Bye-Bye (Bye!) Who I I think I sink and I die! | ||
8 | The Gray Man (2022 film) | 846,311 | Netflix might be losing subscribers, but is still flush with cash to spend in big action movies. This week came out a book adaptation reuniting the star, directors and writers of Captain America: The Winter Soldier (and its bigger sequels), albeit Chris Evans is a bad guy as it instead follows Ryan Gosling as a convicted murderer who is taken out of prison to work as an assassin for the CIA. | ||
9 | Ivana Trump | 806,050 | The socialite mother of Donald Trump Jr., Eric Trump and Ivanka Trump (and yes, the first wife of The Donald) died after falling down the stairs in her home. | ||
10 | Ben Affleck | 708,168 | An actor who replaced #6 with a namesake, Jennifer Garner (the Elektra of his Daredevil, mother of his three kids), and while a return as Batman is not in the cards, one with J. Lo turned out to be. |
Here we are again, and this time I'm actually doing all the work and not just leaving it for someone else to do. I'm so disappointed in myself. Good month for featured pictures and articles, but an awful month for lists – only two, which I'm told is the worst month for lists ever. Luckily, July is already doing much better. Meanwhile, featured topics are usually quite rare (as one would expect, given they're an entire subject matter's worth of featured articles, so having two featured topics is actually very good.
It's not really a coincidence that The Cenotaph appears both in Featured Articles and Featured Pictures, because I like searching the featured article candidates for good-quality images to restore or nominate. Same with James B. McPherson, who was the commander of the new Featured Article, Battle of Raymond. If you see images in prospective or existing featured articles you think might be of featured picture quality, by all means either tell me or nominate them yourself. I've always thought Featured Articles deserve Featured Pictures in them when possible.
Speaking of Featured Pictures, we could probably use a bit more participation there – but, then, I do have a thirteen-image nomination backlog, so that might be a rather self-serving invite.
Seventeen featured articles were promoted this period.
Twenty-six featured pictures were promoted this period, including the ones appearing as this article's footer and header
Two featured topics were promoted this period.
Two featured lists were promoted this period.
In this column, I will outline some of the possible ways to deal with awful citations on Wikipedia by making use of Citation bot. By 'awful' citations, I don't mean 'awful' in the sense that they are dealing with unreliable sources, but rather in the copy editor's sense, where the information is presented in a reader-unfriendly way. You may be surprised to hear just how little technical skill is required!
While the world of bots can be intimidating, making use of Citation bot is actually very simple even if you don't know the first thing about programming. A basic guide is available for readers who want more technical information and less guidance. Here I will focus on the easiest way of using the bot – using the citation expander gadget.
The gadget will add an "Expand citations" options to your sidebar, and a ✔ Citations button to your edit window. You can easily enable it in the gadgets tab of your preferences panel. Go to the "Editing" section, and check the box labelled Citation expander.
After that, all you have to do is find a page in need of some love and run the bot. It will automatically try to improve existing citations as best it can. Note that if this is your first time running the bot, you might be asked to grant it permission to make edits on your behalf. You will have to grant these permissions again if you log out or log in on a different machine.
While there are other ways of activating the bot, for the sake of this tutorial, I will assume that you use the ✔ Citations button of the citation expander. This will let you review the changes made to the article and make sure everything is in order before saving. If you want to use the web interface or click on "Expand citations" in the sidebar, you will need to save the article after the "cleanup step" before running the bot. The bot will then make its changes automatically, and you will need to review them afterwards. While the first method should always work, the others will only work if the bot is unblocked and is vulnerable to edit conflicts.
Let's say you come across a citation that's generally accurate, but is missing some information. Something like
wikitext | {{cite journal |last1=West |first1=Jevin D. |last2=Jacquet |first2=Jennifer |last3=King |first3=Molly M. |last4=Correll |first4=Shelley J. |last5=Bergstrom |first5=Carl T. |year=2013 |title=The Role of Gender in Scholarly Authorship |url=https://doi.org/10.1371%2Fjournal.pone.0066212 |journal=PLOS ONE |volume=8 |issue=7 |pages=e66212}}
|
---|---|
output | West, Jevin D.; Jacquet, Jennifer; King, Molly M.; Correll, Shelley J.; Bergstrom, Carl T. (2013). "The Role of Gender in Scholarly Authorship". PLOS ONE. 8 (7): e66212. |
Nothing in this citation is wrong strictly speaking, but it could be made a lot more useful to readers if it contained standard identifiers. Since we already have a DOI url in |url=
, we only need to click ✔ Citations to run the bot and get
wikitext | {{cite journal |last1=West |first1=Jevin D. |last2=Jacquet |first2=Jennifer |last3=King |first3=Molly M. |last4=Correll |first4=Shelley J. |last5=Bergstrom |first5=Carl T. |year=2013 |title=The Role of Gender in Scholarly Authorship |url=https://doi.org/10.1371%2Fjournal.pone.0066212 |journal=PLOS ONE |volume=8 |issue=7 |pages=e66212 |arxiv=1211.1759 |bibcode=2013PLoSO...866212W |doi=10.1371/journal.pone.0066212 |pmc=3718784 |pmid=23894278}}
|
---|---|
output | West, Jevin D.; Jacquet, Jennifer; King, Molly M.; Correll, Shelley J.; Bergstrom, Carl T. (2013). "The Role of Gender in Scholarly Authorship". PLOS ONE. 8 (7): e66212. arXiv:1211.1759. Bibcode:2013PLoSO...866212W. doi:10.1371/journal.pone.0066212. PMC 3718784. PMID 23894278. |
And we have a nice, well-formatted citation, with many ways to find the article. Here the bot even went the extra mile and flagged the DOI with |doi-access=free
to indicate the DOI will take you to a full free version of the article. This will not always be automatically detected, in which case you can add |doi-access=free
yourself.
This method will work with most URLs that point to a standard identifier, or with citations already using standard identifiers: arXiv, Bibcode, DOI, ISBN, JSTOR, PMCID, and PMID. It will also work with URLs to major repositories, like ScienceDirect and Wiley Online Library, although it will not necessarily be as reliable as the DOI method.
While the bot is not guaranteed to find every DOI and PMID out there, running the bot will often cut down a lot of work. So before doing it all yourself, it's a good idea to run the bot first. Not only will it add missing information, it will also cleanup several common mistakes like |last=Smith,
→ |last=Smith
, |volume=12(3)
→ |volume=12
|issue=3
, or |journal=PLOS GENETICS
→ |journal=PLOS Genetics
. You can then focus on cleaning up the things the bot was not able to figure out, like fixing poorly formatted or incomplete citations, or hunting down missing DOIs and JSTOR ids.
While WP:CITEVAR is a thing worth keeping in mind, plain text citations are often poorly presented, with typos, and limited usefulness. In those case, WP:CITEVAR does not apply, as no consistent style has been used. Consider for example the following
wikitext | G. Coppola + coauthors (2009). "Sérsic galaxy with Sérsic halo models of early-type galaxies: A TOOL FOR N-BODY SIMUILATION". Publications of the ASP. volume 121-879 pp. 437. {{doi|10.1086/599288}}{{bibcode|2009PASP..121..437C}}
|
---|---|
output | G. Coppola + coauthors (2009). "Sérsic galaxy with Sérsic halo models of early-type galaxies: A TOOL FOR N-BODY SIMUILATION". Publications of the ASP. volume 121-879 pp. 437. doi:10.1086/599288Bibcode:2009PASP..121..437C |
There are several things wrong with this one. Coauthors are not listed (or at least the standard et al. is not used). We have an inconsistently capitalized title, with a typo (SIMUILATION
). The journal's name is abbreviated in a non-standard manner, and there are presentation problems with the volume/issue/pages. We also have issues with the presentation of identifiers as well. While it is possible to clean this up by hand, this would take a lot of time.
A much more efficient way of doing the cleanup is to use the bot. We already have identifiers, so the hard part has been done for us; we simply need to feed them to the bot. We can do this in many ways.
wikitext method 1 |
Any of
|
---|---|
wikitext method 2 |
Any of
|
The second method in particular is very easy to use, since you can just right-click on the identifier, and copy paste the URL in the <ref></ref>
tags. However it only works within <ref></ref>
tags. The first method is more useful for lists of works and bibliographies, but will also work in <ref></ref>
tags as long as you don't mind typing a bit more characters and copy-pasting the identifiers (e.g. <ref>{{cite journal |bibcode=2009PASP..121..437C |doi=10.1086/599288}}</ref>
).
With whichever method you prefer, you only need to click ✔ Citations to run the bot and get
wikitext | {{cite journal |last1=Coppola |first1=G. |last2=La Barbera |first2=F. |last3=Capaccioli |first3=M. |year=2009 |title=Sérsic Galaxy with Sérsic Halo Models of Early-type Galaxies: A Tool forN-body Simulations |journal=Publications of the Astronomical Society of the Pacific |volume=121 |issue=879 |pages=437–449 |arxiv=0903.4758 |bibcode=2009PASP..121..437C |doi=10.1086/599288 |s2cid=18540590}}
|
---|---|
output | Coppola, G.; La Barbera, F.; Capaccioli, M. (2009). "Sérsic Galaxy with Sérsic Halo Models of Early-type Galaxies: A Tool forN-body Simulations". Publications of the Astronomical Society of the Pacific. 121 (879): 437–449. arXiv:0903.4758. Bibcode:2009PASP..121..437C. doi:10.1086/599288. S2CID 18540590. |
This is not perfect, but it is very close to the final desired version. We only need to do a bit of retouching (A Tool forN-body Simulations
→ A Tool for ''N''-body Simulations
), and optionally add |doi-access=free
since the DOI link takes us to a free full version of the article, to get
output | Coppola, G.; La Barbera, F.; Capaccioli, M. (2009). "Sérsic Galaxy with Sérsic Halo Models of Early-type Galaxies: A Tool for N-body Simulations". Publications of the Astronomical Society of the Pacific. 121 (879): 437–449. arXiv:0903.4758. Bibcode:2009PASP..121..437C. doi:10.1086/599288. S2CID 18540590. |
---|
If the citation was as poorly formatted as the initial version, it is very likely that WP:CITEVAR does not apply. However, if this was found in a featured article, and was the only poorly formatted citation in an otherwise excellent reference section, returning to a plain text citation is very straightforward. Simply copy-paste the output you get when previewing, with minor modifications
wikitext | Coppola, G.; La Barbera, F.; Capaccioli, M. (2009). "Sérsic Galaxy with Sérsic Halo Models of Early-type Galaxies: A Tool for ''N''-body Simulations". ''Publications of the Astronomical Society of the Pacific''. '''121''' (879): 437–449. {{arXiv|0903.4758}}. {{bibcode|2009PASP..121..437C}}. {{doi|10.1086/599288}}. {{s2cid|18540590}}.
|
---|
What if you come across a citation you know is just wildly inaccurate, or just so outrageously formatted that things barely make any sense?
wikitext | {{cite journal |last1=Ar≥≥on;Jacobin |first1=New Scientist |year=2018 |title=Deflector Selector says nuke asteroids |journal=Elsevier ScienceDirect |volume=pages3165|issue=3165 |pages=6 |bibcode=2018NewSc.237....6A |doi=10.1016/S0262-4079(18)30281-1}}
|
---|---|
output | Ar≥≥on;Jacobin, New Scientist (2018). "Deflector Selector says nuke asteroids". Elsevier ScienceDirect. pages3165 (3165): 6. Bibcode:2014PhT....67d..48W. doi:10.1016/S0262-4079(18)30281-1.{{cite journal}} : CS1 maint: multiple names: authors list (link)
|
Fixing this manually is possible. But you would need to look up the original and pretty much reformat the whole thing. When something is this badly broken, it is good to make sure that whatever is intended to be cited is actually the thing being cited. This could easily be the result of vandalism that resulted in two citations being merged together inadequately. Here, Bibcode:2014PhT....67d..48W and doi:10.1016/S0262-4079(18)30281-1 don't even point to the same citation! However, once you determine which is the correct citation, we can follow the TNT principle as applied to this particular citation: Blow it up and start over!
Let's assume that doi:10.1016/S0262-4079(18)30281-1 is the correct citation. We can then TNT it back to a state that the bot can make sense of
wikitext | {{cite journal |doi=10.1016/S0262-4079(18)30281-1}}
|
---|
and then we only need to click ✔ Citations to run the bot and get
wikitext | {{cite journal |last1=Aron |first1=Jacob |year=2018 |title=Deflector Selector says nuke asteroids |journal=New Scientist |volume=237 |issue=3165 |pages=6 |bibcode=2018NewSc.237....6A |doi=10.1016/S0262-4079(18)30281-1}}
|
---|---|
output | Aron, Jacob (2018). "Deflector Selector says nuke asteroids". New Scientist. 237 (3165): 6. Bibcode:2018NewSc.237....6A. doi:10.1016/S0262-4079(18)30281-1. |
Sometimes the metadata available to the bot isn't perfect, and the bot will mess up something that it can't know is wrong. If the bot keeps messing up something after you've fixed it, for example if it keeps adding a |series=
to a {{cite journal}} template, you can bypass the bot by putting a comment in the problematic parameter
{{cite journal ... |series=<!--Deny citation bot, Journal of Physics is not a book series!-->}}
this will let the bot know it shouldn't try to touch that specific parameter. Likewise if it incorrectly converts a {{cite journal}} to a {{cite book}}, you can put a comment in the template's name
{{cite journal <!--Deny citation bot, Journal of Physics is not a book--> |last=... }}
this will let the bot know it shouldn't try to touch that citation at all.
You can report bugs and issues at the bot's talk page. You can also suggest improvements to the bot if you have some ideas.
The more citations an article has, the longer the bot will need to process the article. If an article only has a few citations, the bot will usually deal with it within a minute. If an article has several hundred citations, the bot can take several minutes to process it, and can even timeout. If that happens, you can edit the article section-by-section to give the bot fewer citations to process at once. You can alternatively click on "Expand citations" in the sidebar instead (see picture on the right), and the bot will eventually make an edit. You might be given a timeout screen, but just come back to the article after an hour and you should see a successful edit. If an edit conflict occurred, just run the bot again.
The "Expand citations" link is also a good way to finish your editing session. Just let the bot run, and go do something else. When you return, the bot will have made an edit if it found something to cleanup, and you can continue from there.
While Citation bot is not perfect and doesn't fix everything, correctly used it is a very powerful tool that can save you a ton of headaches and make your editing experience that much easier. I gave examples above using {{cite journal}}, but the bot will also work with {{cite book}}, {{cite web}} and many others (including {{citation}}). I focused on cleanup in this Tips and Tricks column, but you can easily use these methods to add citations to articles. Simply find a good identifier, put it in a citation template (or a plain URL in <ref></ref>
tags), and unleash the bot!
I'll note as a disclaimer that I've re-ordered certain parameters to make my examples more legible and more understandable to the reader. In the wild, citation parameter order will depend a lot on what input is given to the bot and which parameters are already present in a citation.
Happy editing!
Tips and Tricks is a general editing advice column written by experienced editors. If you have suggestions for a topic, or want to submit your own advice, follow these links and let us know (or comment below)!
Wikidata is a knowledge base associated with Wikipedia. Querying Wikidata to get insights is a very hard job. Fortunately, the Item documentation template can help querying Wikidata in one click using generic queries. The template is now automatically displayed in the header of each item's talk page.
Let's take an example. Imagine I want to complete an article about a small French town like Épinal. From the Wikipedia article, I can get to the Wikidata item Épinal (Q173695) using the menu. Then I can switch to the talk page Talk:Q173695. In the header of the talk page, I should see the item's documentation.
In the first section, I can find a link to a magic query which returns "All claims about Épinal" (try it, and don't forget to press the blue 'play' button). This provides an overview of all I can find about Épinal in Wikidata. For instance I get the list of items located in the administrative territorial entity Épinal, the list of people whose place of birth is Épinal, and the list of people whose place of death is Épinal.
In the first part of the template, I find a link to the query "All claims about Épinal" |
Let's go further to the "Generic queries for administrative territorial entities" section. This section provides generic SPARQL queries for administrative territorial entities such as towns, regions, countries, and districts. It is generated using Template:TP administrative area. Clicking on "Places in Épinal", I can find a full list of items located in Épinal (see here).
In this part, I find many queries based on geography. For instance, the map of places or the list of organizations with their headquarters in Épinal. |
Further down in the page, I find the list of "People born in Épinal, sorted by number of sitelinks" (see here). The number of sitelinks is the number of pages in the different wikipedias. This can be very useful to complete the "Notable people" section of the article.
Here we find queries related to people born in Épinal, dead in Épinal, living in Épinal or buried in Épinal. |
Of course, Wikidata's data is not perfect. We should complete insights from Wikidata with reliable sources. But the Item documentation template makes it easier to get insights from Wikidata in order to complete Wikipedia articles. Any feedback about the template is welcome on the template's talk page.
As Russia's open invasion of Ukraine has entered its sixth month, the lives of Ukrainians – and Ukrainian Wikimedians – are still greatly affected by the war. In this edition, we cover three stories of people during the war – serving in the army, volunteering, and just doing their jobs.
Svitlana Diachok is a teacher, PhD in literature, and the author of several handbooks on literature. She is also an active editor of Wikipedia and a member of Wikimedia Ukraine.
In January, Svitlana won the competition for the position of school principal in a school in the city of Khorostkiv in the Ternopil region – an educational institution with over 560 students and almost 50 teachers.
The next month, Russian full-scale invasion of Ukraine began. Today Svitlana combines administrative work, teaching, writing books and volunteering during the war. In an interview with us, she discussed her work and life in these hard times.
Svitlana Diachok has dedicated her life to teaching. Throughout her career, she went from a primary school teaching assistant to the head of an educational institution – since January, she leads a school in the Ukrainian city of Khorostkiv.
When the full-scale war started, the educational process continued, but in an online format. It was a challenge, but the school was well prepared for distance learning since the beginning of the pandemic, Svitlana recalls. (Khorostkiv is located in the west of Ukraine, a part of the country that has been affected by Russia’s rocket attacks but has not seen on-the-ground fighting. Thus, it’s been a place for internally displaced persons from frontline eastern and southern regions).
At the same time, school employees and students actively engaged in wartime volunteering. They collected food and clothes for soldiers and internally displaced persons, wove camouflage nets for the army, and looked for medicines for maternity hospitals.
Some people who moved from other regions of Ukraine received shelter in one of the buildings of the school led by Svitlana. She says the school helps them with food and other necessities — but also involves them in local activities to help integrate into the local community. For example, they spent a week learning the region’s traditions before Easter.
At the same time, Svitlana continues other professional activities apart from administrative work. She teaches Ukrainian literature in several classes and also writes books.
How does she manage to combine everything? The secret to the correct allocation of time is “using every minute in your life productively”. For example, Svitlana’s daily half-hour commute is not wasted time, but an opportunity to think about an important work problem or make a phone call.
Svitlana says that she always tries to combine several tasks and responsibilities: for example, writing a book and at the same time thinking through ideas about school management.
Svitlana Diachok has been an active Wikipedia editor for over six years and a member of the Wikimedia Ukraine NGO for four years. She is a co-author of the handbook “Using Wikipedia and Wikimedia projects in school” and has organized many activities to involve students in the wikispace.
Svitlana says that she had many plans to integrate Wikipedia into the educational process when she became the head of a large school. Of course, the Russian invasion changed plans, so it hasn’t been possible to carry out everything planned.
Still, Svitlana singles out three achievements that she managed to implement this year. The first is the Wikimarathon for Wikipedia's birthday at the end of January. 12 people took part in a training session, many of them became interested in editing the online encyclopedia.
During the war, through distance learning, Svitlana used Wikipedia in lessons for the 5th and 6th grades. The lesson begins with students reviewing Wikipedia’s main page – students look at who was born on this day and choose one most notable person. For 10–11 years old children, it is important to be involved in the encyclopedia in this way, Svitlana says.
Svitlana also says that, as a teacher of literature, she actively uses Wikiquote – together with her students, they improve Wikiquote articles with quotes from literature works read in class.
If everything goes according to plan, from the beginning of the new school year, Svitlana’s students will also learn to edit and create Wikipedia articles.
Oleg Andros is a photographer, musician, environmental activist, and an active participant of the Wiki Loves Earth photo contest.
Before the war, Oleg was actively involved in nature protection. He lobbied for the creation of nature reserves in Kyiv, the preservation of Zhukiv Island, Lysa Hora and other protected areas in Ukraine. At the same time, he is fond of photography. Since 2000, he has amassed a large archive of photographs, which he periodically uploads to Commons.
In 2021, Oleg took part in the Ukrainian part of Wiki Loves Earth. His photos won all five prizes in the special nomination “Protection of nature sites”.
One of his photos also won a third place in the nomination “Human Rights and Environment” in the international Wiki Loves Earth round. It depicts a picket on November 22, 2013 against deforestation in Ukraine. The action included folk songs and a dramatic duel between a beaver and a lumberjack.
On the eve of Russia’s full-scale invasion, on February 21 this year, Oleg opened his fourth solo photo exhibition “The Touch of Otherworld” at the Little Opera in Kyiv. At the same time, he got a new job – Oleg is an editor at the Kyiv Youth Library.
On February 24, Oleg woke up at six am. His mother told him that the Russians were bombing Vasylkiv airport near Kyiv. He grabbed his essentials and headed to Bila Tserkva through traffic jams.
In 2015, Oleg Andros served in the Armed Forces of Ukraine fighting Russian-backed terrorists in the eastern Donetsk region. As a military reservist, he immediately went to the military office. On the first day of the 2022 Russian invasion, he was assigned to a unit that got sent to the frontline. Oleg's service takes place in various regions: from the Brovary district in the Kyiv region, back when Russian troops were near Kyiv, to Sumy, Kharkiv and Donetsk regions.
“During the Anti-Terrorist Operation [war in eastern Ukraine since 2014] I didn't see much because I served in the brigade headquarters. But I compensated for it during the 2022 invasion. Now I know the sound of different artillery shells; I know what it's like to ride a combat vehicle a few hundred kilometers away”, Oleg Andros says.
Currently, Oleg’s battalion is defending the eastern Donetsk region. In his unit, he performs the duties of the personnel officer, handling administrative work. Oleg is constantly on the front line.
During the war, Oleg continued to participate in the activities of environmental organizations. In particular, in March, he helped evacuate 62 cats from the Kyiv Zoo. There are still 45 animals left in this cat shelter, they are helped by the NGO “Nature First”, co-founded by Oleg.
Oleg hasn’t had the time to contribute to Wikipedia during the invasion, but he found time to take some good photos. One of them was exhibited in a Kyiv library in the spring.
Yuri Perohanych (user Perohanych) is a civil society activist, Wikipedia editor for more than fifteen years, co-founder of the Wikimedia Ukraine NGO, and former member of the international Funds Dissemination Committee.
Russian invasion caught Yuri in Kyiv, where he lives. After a sleepless night in a bomb shelter, he went with his 9-year-old son and wife to Ukraine’s west. The road from the capital to a village in the Lviv region some 600 kilometers away was difficult and took more than 60 hours without sleep (including 30 hours in the car).
Yuri says his family had planned to go to Poland, but they ended up deciding to stay in Ukraine. After the Kyiv region had been liberated, they returned from Western Ukraine to Kyiv.
In the first days of the war, Yuri doubled down on his Wikipedia activity. He quickly began covering the war on Wikipedia; on March 1, he initiated a thematic campaign with a goal to cover the invasion – which has been the most popular topic for Ukrainian Wikipedia readers – and prevent the dissemination of Russian propaganda on Wikipedia.
In the first two weeks, participants of the initiative created over 130 articles; within a month, the number reached 220. Thus, Yuri decided to convert the initiative into a permanent project called “Resistance to the Russian invasion of Ukraine”. Yuri also created a portal of the same name.
The project aims to collect and systematize all articles related to Russia's invasion of Ukraine from February 24, 2022; the armed annexation of Crimea and the war in Donbas, which began in 2014.
Yuri says that this initiative has been the largest project he has ever implemented on Wikipedia. In parallel, he has taken on administrative duties on Ukrainian Wikipedia, receiving temporary admin rights to help with the project’s maintenance and fight vandalism at the time when many editors could not exercise their duties.
Also, Yuri has worked on the promotion of free licenses. Through his connections in the Ukrainian government, Yuri received multiple permissions to publish on Wikiprojects various materials from governmental media under the terms of a Creative Commons license.
In addition to working on Wikipedia, Yuri spends a lot of time on other volunteering. For example, he assists with the purchase and delivery of components for energy bars for soldiers of the Armed Forces of Ukraine and the Territorial Defense Forces.
Yuri’s day job is director of the Association of Information Technology Enterprises of Ukraine. His work involves developing the Ukrainian IT sector and improving Ukraine’s business sector more broadly.
Sometimes, you might want to use an image, but key details aren't known. Let's look at this picture of Tom Taylor from the Library of Congress I stumbled across the other day:
Lovely! Given the lead image of Tom Taylor's article looked like this before:
...this new image will make a great addition (not that the old one's bad, just not as good). And that... surprising attribution of the old photo should probably be filed away to double check. But the new image had a problem: The Library of Congress information page on it has (or possibly had) certain gaps:
“ | Date Created/Published: [Place not identified] : [Publisher not identified], [between 1861 and 1880] | ” |
It also doesn't/didn't list a photographer at all. (Spoilers for later, but contacting the archive about your discoveries is an important step in doing research properly, so there's a chance I'll be describing things that aren't the case anymore, because they listened to me.)
So, how do you deal with this? Well, first thing I do is go into Google's image search and Google "Tom Taylor", and see if another copy of the photo comes up.
... At which point we learn that the list of names on Tom Taylor (disambiguation) is going to be a problem. Especially the actor. Let's try again with "Tom Taylor playwright".
That gets us to a WorthPoint entry – which is nearly useless, but tells us a copy of this image is on eBay. Worth a shot. Searching for Tom Taylor on eBay gets us to here, which is much more useful:
“ | Photo by Lock and Whitfield. Taken from Men of Mark, a Gallery of Contemporary Portraits. Published by Sampson, Low, Marston, Searle and Rivington of Fleet Street c1875 | ” |
That's actually quite useful, and, since there's no real reason to disbelieve it, especially as the seller has a few dozen other prints in this style, which means they probably cut up that book, we have a start. Let's check Lock and Whitfield. Searching for them gets us to the United Kingdom's National Portrait Gallery, with, for example, this portrait of Yeames in the same style. Poking around there, and we can identify Lock and Whitfield as Samuel Robert Lock (1822–1881) and George Carpe Whitfield (1831–1917).
Copyright has checked out, there's some backup for our attribution. We're doing well. Would be better if we had a stronger source, but it's not bad, and it's fairly checkable if we can find the book.
I'd like to say that I then did sensible things to get the rest of the information. Like maybe find the National Portrait Gallery copy of this image with most of the information that I found after all of this was over. I got confused by how the National Gallery presented information, didn't click through, and missed it completely. Which is honestly a good example of how unfamiliarity with an archive – the United Kingdom's National Portrait Gallery has had a somewhat rocky relationship with Wikipedia, so I don't use it much – can cause you to miss things in your research.
What I did was go to Wikidata:Q2329794 and put the image in. While typing the file name, it makes suggestions for files you might mean with little thumbnails, and...
... Well! Lower left hand corner. "Lock and Whitfield". We have a match! And the Rijksmuseum is a great source. Let's go to the link and see if we can confirm the other information we have...
A couple clicks later, and I'm looking at the Rijksmuseum entry of the book Men of Mark – which has all the information we need and more. It even has a publication date for the book!
Update all the image information, and now there's only one thing left to do: On the Library of Congress site, there's a section called "Ask a Librarian". Librarians, in my experience, are delighted when you help identify things in their collections. So, link the page for the image in question, pull up the Rijksmuseum documentation, and send off an email. Because improvements aren't just for Wikipedia.
Now if only I could figure out if Lewis Carroll was really going around photographing playwrights.
(As it turns out – remembering Carroll's real name is Charles Dodgson – he actually photographed a bunch of his famous friends. Who knew?)
A monthly overview of recent academic research about Wikipedia and other Wikimedia projects, also published as the Wikimedia Research Newsletter.
This paper[1] presented recently at the International AAAI Conference on Web and Social Media (ICWSM 2022) analyzes 780 community rule pages (including the English Wikipedia's policies and guidelines) on the five Wikipedias with the largest active editor numbers: English, French, German, Japanese, and Spanish. Examining "almost 100 years of data aggregated across [these] five communities" (i.e. the revision histories of these rule pages and their associated talk pages, from each project's founding until 2020), the authors find that these
... follow similar patterns in rule-related editing over twenty years, having a rapid initial surge in activity followed by stabilization and a shift towards discussing rules rather than editing them. However, the five Wikipedias also follow distinct trajectories. Further, the language editions’ rules overlap less over time, producing increasingly differentiated rule sets even as most activity focuses on widely-shared rules.
In a literature review, the authors (Sohyeon Hwang and Aaron Shaw from Northwestern University, both members of the Community Data Science Collective) note contrasting earlier research results that indicated either that "the self-governing efforts of communities will be similar because they are shaped by shared sociotechnical characteristics" (as earlier research coauthored by Shaw had found in case of some non-Wikipedia wikis, see our review: "Iron Law of Oligarchy" (1911) confirmed on Wikia wikis), or instead "different due to the sheer diversity of communities’ membership, goals, or organizational culture."
Regarding English Wikipedia, the paper extends an earlier analysis by Keegan and Fiesler (see our earlier note: English Wikipedia still engaged in rule-making, but with "strong shift toward deliberation").
The authors summarize their main contributions as follows:
(1) we provide evidence that large, well-established Wikipedia language editions follow similar patterns of rule creation and organizational formalization, replicating and extending prior work that focused predominately on English Wikipedia; (2) we show that communities with the same goals, technical infrastructures, and similar organizational trajectories develop substantial and sustainable institutional variations; and (3) we highlight the importance of broad, widely-shared rules created early on in communities’ histories.
In their first research question, they examine "patterns of rule-making over time". First, they find that
"Rule creation follows similar, but distinct patterns across the wikis in our sample. [...] In general, most rules are created early. For all language editions, years 2–6 see the most rule page creation. Japanese Wikipedia is an exception, with 25% of its rules created in its first year (year 0) [... A closer analysis of these year-0 rules] suggests that Japanese Wikipedia boot strapped its core rules from the older English Wikipedia, rather than pursuing a divergent rule-making approach."
Regarding the edits to existing rules, "The median number of rule-related revisions each year per rule [Figure 2b] rises initially, peaks around year 5, and then declines in all language editions." A plot of the ratio of revisions on rule pages vs. (rule) talk pages (Figure 2c) shows a general downwards trend on all five Wikipedias, indicating that as the projects grew and matured, more discussion was needed to change rules. It indicates that English and German have reached the lowest ratios (but also having remained mostly flat since around 2012), while French, Japanese and (especially) Spanish retain higher ratios.
The authors note that their findings on "rule-related stabilization alongside formalization of self-governance" are consistent with earlier research on (mainly) English Wikipedia that had characterized these such patterns as "“diminishing flexibility to change [rules]” (Keegan and Fiesler 2017), “policy calcification” (Halfaker et al. 2013), and “entrenchment” (Halfaker et al. 2013; TeBlunthuis, Shaw, and Hill 2018)". As these wording choices indicate, these trends have generally been framed as undesirable by various researchers, although a theoretical justification for this is lacking - after all, producing rules and maximizing their change rate is generally not a primary goal of online communities. And while a community with higher hurdles on making and changing rules may be less appealing for contributors who enjoy engaging in these activities, the vast majority of community members who merely follow these rules might prefer stability.
The paper's second research question examines "How do the sets of rules become more or less similar over time" across the five different Wikipedias. The authors rely on interlanguage links to relate corresponding rules, finding that
"About 28% of all rule pages are shared across all five language editions. [...] the majority of rules in all five wikis are shared and connected by ILLs, but the rule sets increasingly contain rules that are unique or shared with just one other language edition. Moreover, the proportion of rules connected by ILLs in each wiki has stabilized [...] the presence of community-specific rules is more obvious in the two larger language editions, English and German. Notably, we find that community-specific rules are not the focus of rule-related revision activity in any community, which instead goes towards rules shared across all five language editions."
In this paper,[2] from Information, Communication & Society, three Netherlands-based sociologists present a historical analysis of bureaucratization and power concentration vs. power diffusion in Wikipedia and the Wikimedia Foundation. It covers the timespan from 1999 (when Nupedia was launched, two years before Wikipedia's founding) until 2017. The analysis is "based on 118 conversations and interviews" with "Wikipedians and board and staff members of both the WMF and local WMF chapters [in particular Wikimedia Nederland] who have played an influential role in Wikipedia’s evolution" and other community members, "as well as extensive archival research" and a literature review. On the theory side, the paper draws from Robert Michels and Max Weber "to study mechanisms pushing towards or away from power concentration and bureaucratization." Overall,
"In line with Weber, we identify a process of progressive bureaucratization. This does not only result from the pursuit of organizational manageability, but from a quest for democratic equality and minimization of domination as well. We introduce the concept of self-organizing bureaucratization to highlight how bureaucratization is the unintended and emergent outcome of efforts to increase democratic accountability."
The authors conclude that "an essential amendment to Michels’s and Weber’s theories is that these processes are not unilinear or mechanical. Our research rather shows an erratic and, above all, contested process."
Other recent publications that could not be covered in time for this issue include the items listed below. Contributions, whether reviewing or summarizing newly published research, are always welcome.
From the abstract:[3]
"[...] this paper adopts a praxeological approach to translation by analysing documented standards across four Wikipedia language communities and the extent to which 16 experienced translators have assimilated them. The findings suggest that Wikipedia guidelines on translation have slight but tangible differences across the communities under investigation. Moreover, the interview data showed a tendency among participants to attach more importance to cross-wiki editing policies than to any local translation guidelines."
From the abstract:[4]
"When the COVID-19 pandemic broke out and mobility restrictions ensued across the globe, it was unclear whether contributions to Wikipedia would decrease in the face of the pandemic, or whether volunteers would withstand the added stress and increase their contributions to accommodate the growing readership uncovered in recent studies. We analyze 223 million edits contributed from 2018 to 2020 across twelve Wikipedia language editions and find that Wikipedia’s global volunteer community responded resiliently to the pandemic, substantially increasing both productivity and the number of newcomers who joined the community. For example, contributions to the English Wikipedia increased by over 20% compared to the expectation derived from pre-pandemic data."
From the English abstract:[5]
"Wikipedians [...] consolidate personal resources to manage comprehensive aggregation of free knowledge. [...] the question of the driving forces of this prosocial behaviour is still open. [...] we conducted a content analysis of a transnational survey. The recipients were 65 authors of multilingual Wikipedia segments (83% males and 17% females) with average experience of 9.9 years compilation of encyclopedic articles.
Results. [... In] most cases Wikipedians find a number of personal significant reasons for participating in the Wikipedia, the reasons resonating with their inner essence.
Conclusion. The internal value orientations of Wikipedians include: self-development (self-improvement, self-assertion, self-realization); reciprocal (mutual) altruism; a tendency to high quality and systematization of knowledge; a pleasure of creation; autonomy; recreation (hobby, entertainment); meaningfulness; preservation of personal heritage. The external value orientations include: preservation and development of the cultural heritage / language segment; promotion and popularization of Wikipedia (its ideology and principles); low transaction costs and convenience (attractiveness) of the system; affiliation; social identity; improvement peace («Weltverbesserungs Antrieb»); building bridges between cultures and languages."
One of the best books published last year is the book The Library. A Fragile History by Andrew Pettegree and Arthur der Weduwen. It is a scholarly book, with a 16 page index and 787 notes, but it is lightly written and very readable. It contains 18 chapters, mostly dedicated to a particular subject like “Idle Books and Riff Raff” (from Oxford to Franeker), “Cardinal Errors” (about Richelieu) and “Reading on the Job” (with the Carnegie story). The authors, both researchers at the University of St. Andrews in Scotland, succeed in painting a clear picture of the history of the library as such, in only 518 pages, drawn upon some outstanding examples. True, they forgot most Asian and African libraries (6 pages on China, 3 on Japan, 1 on Timbuktu), but these will be dealt with in a new book, I presume.
Wikipedia is the Library of the 21st century. At least, it aspires to be, and to give “free access to the sum of all human knowledge” is a clear goal. Though Wikipedia is a tremendous tool of knowledge, Wiki is only starting to summarize some of the knowledge in the world. But it is a start, and I wouldn’t have dedicated ten thousand hours of my life to Wikipedia if I wouldn’t have been convinced that it will prove to be a useful library – somewhere in the future.
Wikipedia has five pillars and a content policy, which states that articles may not contain original research. Rightly so. That makes understandable why universities advise students NOT to cite Wikipedia: scholars should learn to cite the original source, not a shortened and simplified version of it in Wikipedia. Most universities (for example, this one) therefore advise to use the sources and literature references in Wikipedia, but not the text in Wikipedia itself. It comes as no surprise, that Wikipedia advises the same: “Wikipedia is not considered to be a reliable source as not everything in Wikipedia is accurate, comprehensive, or unbiased.”
Wikimedia Commons is a different story. I read the book The Library. A Fragile History, which contained 52 images. Ten of these images (so roughly 20%) were library photographs taken from Wikimedia Commons (see below). Another ten were probably also indirectly taken from Commons, but the original source was given (again: rightly so). It is only logical that scholars use Wikimedia Commons for recent photographs from libraries in Egypt, Turkey, Austria, San Francisco and Manchester. More interesting is to see that three of the images were taken from library collections: no. 3 (Codex Amiatinus), no 8 (National Gallery of Art, Washington) and no. 9 (Braunschweig). The image from the National Gallery of Art was donated during a Wiki Commons project of the NGA. The Braunschweig image was originally uploaded from the website of Arbeitsgemeinschaft historischer Forschungseinrichtungen, closed down in 2013.
Needless to say that photographs like this file wouldn’t have been used in this book if they hadn’t been uploaded by the Dutch Heritage Foundation RCE to Commons in 2013. Any other conclusions? Well, cooperation pays off, and Libraries and Museums are right in working together with Wikimedia Commons - and good photos might end up in books.
A bit of an odd gallery this month: I thought it might be fun to have a look at the parts of theatre which are not all that visible to audiences, including a few of the lethal things theatrical performers had to put up with not so long ago. So let's start our investigation with possibly the most lethal bit of (once) commonly used theatrical equipment:
Star traps were a type of trap door where a sort of see-saw was used to launch a person up from below at high speed – allowing them to do some acrobatic pose in mid air – after which they would come back down to stage level and land on the star trap after the nasty pointy spikes had fallen back into place (hopefully). And if the points hadn't fallen back in place... Well, there's a reason that they're banned now. Bram Stoker knew their dangers well:
“ | ... it's no joke being driven up through the trap as if you was shot out of a gun. The points of the star had to be kept free, and the hinges at their bases must be well oiled, or else there can be a disaster at any time. Moreover, 'tis the duty of someone appointed for the purpose to see that all is clear upon the stage. I remember hearing that once at New York, many years ago now, a harlequin was killed by a 'grip' – as the Yankees call a carpenter – what outsiders here call a scene-shifter – walking over the trap just as the stroke had been given to let go the counter-weights. It wasn't much satisfaction to the widow to know that the 'grip' was killed too. | ” |
This is a good example of the setup of a large modern (or, at least, modernised) theatre. To the the right, one can see the safety curtain partially blocking the view out. While often given a cloth-like look on the audience side, when viewed from the on-stage (where the audience can't see) many of them are clearly big reinforced metal frames. Because of the systems of pulleys and counterweights, they come down quite smoothly, which further gives the impression they're just a normal curtain. Of course, not all of them are metal, some are made from highly fire-retardant fabric. And from the same lethal side of theatre that once brought you the star trap, there were once "safety" curtains made of asbestos. We don't have pictures of those, but we do have pictures of the sane ones:
In these views of iron safety curtains, the first shows one without the fabric covering that normally hides its true nature from the audience, while the second shows one with the fabric covering. Also shown is the handle that drops the safety curtain, or fire curtain in American parlance. The idea of the safety curtain is that, if there's a fire, it separates the backstage from the front of house, which helps cut off the fire's air supply and slow its spread. And what happened before we had these devices in place?
Covent Garden Theatre burned down completely in 1808. This image dates from around 1856. Why so much time between the two? Because this is a picture of it burning down... for the second time, in 1856. Note how the fire is spreading between stage and audience – exactly the scenario safety curtains are meant to prevent.
The safety curtain can be quickly raised and lowered thanks to a system of counterweights and pulleys that allow curtains, backdrops, and even pieces of set to be raised and lowered without substantial difficulty. Metal pipes, called battens, are hung from ropes. The curtains, lighter bits of set, lights, and the occasional special effect device (like a container to drop confetti) can all be hung from them. Further, by lowering them nearer the stage, the need for ladders is greatly diminished.
Finally, we need to build a set. This is traditionally made with a series of flats – freestanding walls that can be painted and decorated – as well as platforms, steps which act like any other set of stairs except for being more mobile. The effect can be quite visually stunning if done well:
Of course, this is a sampler. Perhaps your performance is going to be on a giant rotating set, often divided into halves or thirds, so that any redecoration can be done while acting is going on in the part of the stage facing forwards. This trick is also often done by having a scene in front of a curtain, whether the main curtain of the theatre or a backdrop near the front of the stage. Perhaps it's a minimalist set, where the audience's imagination and actor's reactions are meant to sell the scene. Perhaps you're doing a megamusical and have turned the whole stage into a roller skating rink so your actors can pretend to be toy trains being played with by a child (yes, that's a thing). Theatre can be strange, weird, and endlessly creative, so there's only so much that can be explained in the format of a gallery.
The Russian community's action was the third protest of its kind, after the SOPA/PIPA shutdown on the English Wikipedia last January and the Italian Wikipedia blackout last October over a new privacy bill. The English-language shutdown played a major role in the dumping of the Congressional proposal, and while the Russian and Italian bills still passed, the community-led protests in those two countries appear to have exerted influence in making them less objectionable to the movement's goals of achieving internet freedom.
The Wikimedia Foundation's head of communications, Jay Walsh, posted a message of support to the volunteers of the Russian Wikipedia: "... many in the Wikimedia movement recognize that this legislation is similar to other bills being proposed or passed around the world that could hinder free speech and produce situations where governments could censor information. Non-censorship and freedom of speech are core values of the Wikimedia movement and the Wikimedia Foundation."
Among the questions now are how effective the blackout was and where we go from here in terms of internet freedom in one of the world's biggest and most influential countries. The head of Wikimedia Russia, Vladimir Medeyko, told the Signpost that despite the passage of the law, the blackout had gained wide publicity. "It was reported in newspapers and on all major domestic Russian TV channels, as well as on the Russian CNN channel, Ukrainian TV news, and the Mir company, which also broadcasts in Kazakhstan. Overall, they took a fairly even-handed angle in their reporting."
But Medeyko anticipates no more blackouts in Russia: "I think it would look too political. One action is fine—it's effective. But if we did it again, in the Russian political culture it would be laughed at as an overtly political ploy."
There are two immediate aftermaths, he says: first, some changes were made in the wording of the bill that do slightly reduce the likelihood of misuse; and second, senior government officials gave Wikimedians assurances that the law will not be used to suppress freedom of speech on the internet, and agreed to make efforts to improve the situation by further amending bills or regulations. Further amendments may be scheduled for November and will be considered by two government committees before then—one instigated by Elena Mizulina, a member of the Duma and one of the main authors and proponents of the amendment; and one by Nikolai Nikiforov, the Russian minister for information who, like all ministers, reports to president Putin through prime minister Medvedev, and is not a member of the Duma.
The Russian Wikipedia community has been invited to make submissions to both committees. Medeyko told us, "I caught up with Mizulina immediately after the voting for the bill, during which she assurred us we would have input into the process. Mizulina is the head of the Duma's committee on family, women, and children—one of the overt concerns of the bill was to act against child pornography on the internet. "Both Nikiforov and Mizulina use the Russian Wikipedia as far as I know," he says, "but are unlikely to have edited it."
On a scale from 1 (no freedom) to 10 (complete freedom), Medeyko rates internet freedom in Russia around 5, down from 6 before the amendments. Given this, we asked what he believes are the minimum, politically realistic changes to the law that would give the country acceptable internet freedom. "There should be a clear definition of the reasons that would justify shutting down a site; there should be a feasible procedure to quickly restore a site after fair and open judicial review; and we need independent and just courts—but the last requirement may involve complex issues that are difficult to resolve in the short term." The Russian community will be discussing their input on-wiki, which will be formally put to the government committees by the chapter.
How powerful is the bureaucracy compared with the politicians themselves? Do the bureaucrats make the real decisions? Medeyko says "I think it's a mix. The policians tended to express pro-Wikipedia, pro-internet opinion as a reaction to the blackout, since it's not in their interests to alienate online users in Russia. This is a good start in our negotiations with the bureaucrats."
Medeyko's overall take is optimistic. "The chapter hopes that this phase in our relationship with the government will be productive and will reinforce both freedom on the Russian-language internet and the independence of Wikimedia projects in our language."