One of the first things that a budding historian learns is the value of good research skills. The second is how to take those results and pull them together into a comprehensive and readable work that can be shared with others. It is no coincidence that these are two skills that Wikipedia volunteers also quickly discover are of invaluable worth when creating or improving a Wikipedia article. As such, it should be of no surprise that Oregon State University instructor Dr. Stacey Smith chose to have her students in her course practice their research and writing skills by contributing content to Wikipedia during the fall of 2018, where their work on African American abolitionists can be read by the entire world. Their work resulted in the creation of multiple new articles on people who lacked articles and the improvement of several that already existed on Wikipedia.
One of the new articles is about William Lambert, a prominent African-American citizen and abolitionist in Detroit, Michigan during the mid to late 19th century. He was born free and was educated by a Quaker schoolmaster, who not only gave him an excellent education but also introduced Lambert to the abolitionist movement. In his twenties Lambert was living in Detroit and working in a tailor shop. It was here that he met George DeBaptiste, with whom he would work and collaborate with on abolitionist matters and on the Underground Railroad. Lambert is perhaps most well known for assisting the fugitive slave Robert Cromwell, who escaped his owner John Dun and fled to Canada, where he could live in freedom. Lambert was responsible for exerting his influence and placing Dun in jail, giving Cromwell the ability to successfully reach Canada. This wasn’t without repercussion, as these actions influenced politicians to pass the Fugitive Slave Act in 1850, which greatly reduced the ability for slaves to escape the cruelty of slavery.
Another Wikipedia article that students created was about Louisa Matilda Jacobs, an African American abolitionist and civil rights activist and the daughter of famed fugitive slave and author, Harriet Ann Jacobs. Her mother was a mistress to congressman and newspaper editor Samuel Tredwell Sawyer, Louisa’s father. Harriet was the slave of Dr. James Norcom, who tried to force her into a sexual relationship by threatening her children. She fled, expecting that Norcom would sell her children. This expectation was correct as Sawyer purchased the children and helped them make their way to safety and freedom. Jacobs was eventually reunited with her mother and the two fled to Boston, where she was educated at home until her father paid for her to attend a seminary school in New York. She returned to Boston, where she received training to become a teacher. With her mother, Jacobs founded Jacobs Free School, a Freedmen’s School in Alexandria, Virginia. In 1866 she opened a second one in Georgia called the Lincoln School. She was also active in the activism movement and spoke about women’s suffrage on an American Equal Rights Association lecture tour alongside Susan B. Anthony and Charles Lenox Remond. She also worked as a matron of the National Home for the Relief of Destitute Colored Women and Children and at Howard University.
Interested in adapting a Wikipedia writing assignment to fit your course? Visit teach.wikiedu.org for all you need to know to get started.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Problems
Changes later this week
{{REVISIONID}} magic word will no longer work. This is for performance reasons. When you preview a page it will return "" (empty string). When you read a page it will return "-" (dash). For now this will only affect content namespaces. [8]
Meetings
Future changes
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
The European Union (EU) Commission’s proposal for a Regulation on preventing the dissemination of terrorist content online runs the risk of repeating many of the mistakes written into the copyright directive, envisioning technological solutions to a complex problem that could bring significant damage to user rights. The proposal includes a number of prescriptive rules that will create frameworks for censorship and potentially harm important documentation about terrorism online. It would further enshrine the rule and power of private entities over people’s right to discuss their ideas.
However, there are still ways to shape this proposal to further its objectives and promote accountability. The report on the proposal will be up for a vote in the Civil Liberties and Justice Committee (LIBE) in the European Parliament on 8 April, and Wikimedia urges the committee to consider the following advice:
According to the draft, any platform that hosts third party content—from social media to Wikimedia projects like Wikipedia and potentially to services hosting private files—needs to describe how it deals with content that may be related to terrorism in its own terms of service. While people can talk about terrorism in different forms and for different purposes, such as for research, awareness raising, and news reporting, the regulation would force platforms to decide what is and what is not an acceptable way to have these conversations.
Yet, the law should not mirror websites’ approach to curbing illegal content by applying their terms of service because this would remove incentives to do better. The proposed regulation would oblige all platforms to act in a similar manner, regardless of the content they host or their operational model. That includes Wikipedia, where a rigorous set of top-down policies may interfere with its robust and effective system of transparent community dispute resolution over content.
Instead, legislators should clearly define illegal terrorist content and leave hosting service providers little room for interpretation.
Similarly to the new copyright directive, the regulation envisions the use of automated tools to proactively detect, identify and disable access to terrorist content. Deciding what is and what is not expression that condones terrorism is a complicated matter and context is crucial in deciding whether content is illegal under anti-terrorist laws. Such decisions need to be made by courts, not by algorithms which may or may not be subject to human oversight.
Where law enforcement relies on code, the code becomes the law. That goes against how our free knowledge projects operate, with vibrant and open deliberation on what should have its place on Wikipedia, and what shouldn’t. Platforms’ content moderation should build on a proper framework that involves well-prepared people, not only machines.
Freedom of expression is a right that can only be exercised by the practice of expressing one’s thoughts, ideas, or opinion. Boundaries are only applied when that expression is deemed unacceptable. Content filtering works on exactly the opposite premises—prematurely stifling expression before it has a chance to be heard and assessed.
Any reference to measures that may lead to proactive content filtering should be removed from the proposal. Upload filters overturn jurisprudence and legal practices in all jurisdictions that recognize freedom of expression as a human right. They operate in secrecy and their decisions are shrouded in trade secrets of companies running them. Relying on these technologies may stop some of the communication we don’t want, but it is not worth the price of undermining the foundation of free expression.
The proposal envisions that, in addition to content removal orders, the competent authority can issue a referral to request a company check whether content violates their terms of service. Platforms will face penalties if they do not speedily address these referrals, which creates a strong incentive to act non-transparently and remove content that may in fact be legal.
The measure should be removed from the proposal. Instead, authorities tasked with tackling terrorist content should be required to focus on cases where the terrorist context is evident and issue an order to remove the piece of content in question. Lawmakers need to leave room for the less evident cases to be discussed as acceptable freedom of expression.
The LIBE Committee will vote on a few good changes that have been proposed, most notably the removal of proactive measures and referrals. Providing an exclusion for content disseminated for educational, artistic, journalistic or research purposes is a good idea. However, if the dissemination of terrorist content does not need to be intentional to be removed (as in calling for aiding and abetting terrorist activities), a lot of important information may still get caught up in a surge of removals. We hope that the committee responsible for ensuring respect for civil liberties in EU legislation, will rise to the occasion. We will continue to monitor the legislative process for this regulation and remain committed to defending and promoting free knowledge.
Anna Mazgal, EU Policy Adviser, Wikimedia Germany (Deutschland)
Jan Gerlach, Senior Public Policy Manager, Wikimedia Foundation
26/03/2019-01/04/2019
The Magic Roundabout – in OSM with some “mapping for the renderer” 1 | © Alby (CC BY-SA 2.0)
highway=cycleway in Japan. The vote ends 14 April.
leisure=inflatable_park for playgrounds with inflatable equipment and asks for comments on his proposal.
highway=track, and Bryan Housel, iD maintainer, responded “I basically just disregard everything on the tagging mailing list and the OSM wiki”. This was used as an example in the discussion referred to in the previous item…
amenity=* in an adjustable radius around the current location – of course based on OSM.
bus_bay can be added to the node of the stopping position of the bus – or it can be added to the road, representing the full length of the bay. JOSM’s PT_Assistant plugin provides support for adding them conveniently on ways with its double split map mode.
| Where | What | When | Country |
|---|---|---|---|
| Kawagoe | 川越お花見マッピングパーティ2019 | 2019-04-06 |
|
| La Riche | La Riche (37)#Ateliers d’initiation à OpenStreetMap | 2019-04-06 |
|
| Kyoto | お花見!オープンデータソン in 京都 | 2019-04-07 |
|
| Rennes | Réunion mensuelle | 2019-04-08 |
|
| Bordeaux | Réunion mensuelle | 2019-04-08 |
|
| Essen | Mappertreffen | 2019-04-08 |
|
| Taipei | OSM x Wikidata #3 | 2019-04-08 |
|
| Toronto | Toronto Mappy Hour | 2019-04-08 |
|
| Lyon | Rencontre mensuelle pour tous | 2019-04-09 |
|
| Munich | Münchner Stammtisch | 2019-04-09 |
|
| Salt Lake City | SLC Mappy Hour | 2019-04-09 |
|
| Viersen | OSM Stammtisch Viersen | 2019-04-09 |
|
| Cologne | Stammtisch Köln | 2019-04-10 |
|
| Buenos Aires | Taller Introducción a JOSM en FOSS4G-AR 2019 | 2019-04-10 |
|
| Leoben | Stammtisch Obersteiermark | 2019-04-11 |
|
| Zurich | OSM Stammtisch Zurich | 2019-04-11 |
|
| Berlin | 130. Berlin-Brandenburg Stammtisch | 2019-04-12 |
|
| Salt Lake City | University of Utah Campus Mapping Party | 2019-04-13 |
|
| Biella | Incontro mensile | 2019-04-13 |
|
| Cologne Bonn Airport | Bonner Stammtisch | 2019-04-16 |
|
| Lüneburg | Lüneburger Mappertreffen | 2019-04-16 |
|
| Reutti | Stammtisch Ulmer Alb | 2019-04-16 |
|
| Toulouse | Rencontre mensuelle | 2019-04-17 |
|
| Karlsruhe | Stammtisch | 2019-04-17 |
|
| Bremen | Bremer Mappertreffen | 2019-04-22 |
|
| Salt Lake City | SLC Map Night | 2019-04-23 |
|
| Nottingham | Nottingham pub meetup | 2019-04-23 |
|
| Joué-lès-Tours | Rencontre Mensuelle | 2019-04-23 |
|
| Barcelona | #geomobBCN | 2019-04-24 |
|
| Montpellier | Réunion mensuelle | 2019-04-24 |
|
| Düsseldorf | Stammtisch | 2019-04-24 |
|
| Phone/Video Conferencing | Mappy Hour US | 2019-04-24 |
|
| Lübeck | Lübecker Mappertreffen | 2019-04-25 |
|
| Montpellier | State of the Map France 2019 | 2019-06-14-2019-06-16 |
|
| Angra do Heroísmo | Erasmus+ EuYoutH_OSM Meeting | 2019-06-24-2019-06-29 |
|
| Minneapolis | State of the Map US 2019 | 2019-09-06-2019-09-08 |
|
| Edinburgh | FOSS4GUK 2019 | 2019-09-18-2019-09-21 |
|
| Heidelberg | Erasmus+ EuYoutH_OSM Meeting | 2019-09-18-2019-09-23 |
|
| Heidelberg | HOT Summit 2019 | 2019-09-19-2019-09-20 |
|
| Heidelberg | State of the Map 2019 (international conference) | 2019-09-21-2019-09-23 |
|
| Grand-Bassam | State of the Map Africa 2019 | 2019-11-22-2019-11-24 |
|
Note: If you like to see your event here, please put it into the calendar. Only data which is there, will appear in weeklyOSM. Please check your event in our public calendar preview and correct it, where appropriate.
This weeklyOSM was produced by Nakaner, NunoMASAzevedo, Polyglot, Rogehm, SK53, SunCobalt, TheSwavu, YoViajo, derFred.
One of the key mechanisms that allows Wikipedia to maintain its high quality is the use of inline citations. Through citations, readers and editors make sure that information in an article accurately reflects its source. As Wikipedia’s verifiability policy mandates, “material challenged or likely to be challenged, and all quotations, must be attributed to a reliable, published source”, and unsourced material should be removed or challenged with a citation needed flag.
However, deciding which sentences need citations may not be a trivial task. On the one hand, editors are urged to avoid adding citations for information that is obvious or common knowledge—like the fact that the sky is blue. On the other hand, sometimes the sky doesn’t actually appear blue—so perhaps we need a citation for that after all?
Scale up this problem to the size of an entire encyclopedia, and it may become intractable. Wikipedia editors’ time is limited and their expertise is valuable—which kinds of facts, articles, and topics should they focus their citation efforts on? Also, recent estimates show that a substantial proportion of articles have only a few references, and that one out of four articles in English Wikipedia does not have any references at all. This suggests that while around 350,000 articles contain one or more citation needed flags, we are probably missing many more.
We recently designed a framework to help editors identify and prioritize which sentences need citations in Wikipedia. Through a large study that we conducted with editors from English, Italian and French Wikipedia, we first identified a set of common reasons why individual sentences in Wikipedia articles require citations. We then used the results of this study to train a machine learning model classifier that can predict whether or not any given sentence needs a citation —and why—on the English Wikipedia. It will be deployed in the next 3 months to other language editions.
By improving the identification of where Wikipedia gets its information from, we can support the development of systems to help volunteer-driven verification and fact-checking, potentially increasing Wikipedia’s long-term reliability and making it more robust against biases, information quality gaps and coordinated disinformation campaigns
Why do we cite?
To teach machines how to recognize unverified statements, we first needed to systematically classify the reasons why sentences need citations.
We started by examining policies and guidelines related to verifiability in the English, French, and Italian Wikipedias and attempted to characterize the criteria for adding (or not adding) a citation described in those policies. To verify and enrich this set of best practices, we asked 36 Wikipedia editors from all three language communities to participate in a pilot experiment. Using WikiLabels, we collected editors’ feedback on sentences from Wikipedia articles: editors were asked to decide whether a sentence needed a citation and to specify a reason for their choices in a free-text form.
Our methods and our final set of reasons for adding or not adding a citation can be found on our project page.
Teaching a machine to discover citation gaps.
Next, we trained a machine learning model to discover sentences needing citations, and characterize them with a matching reason.
We first trained a model to learn from the wisdom of the whole editor community how to identify sentences that need to be cited. We created a dataset of English Wikipedia’s “featured” articles, the encyclopedia’s designation for articles that are of the highest quality—and also the most well-sourced with citations. Sentences from featured articles that contain an inline citation are considered as positives, and sentences without an inline citation are considered as negatives. With this data, we trained a Recurrent Neural Network that can predict whether the sentence is positive, (should have a citation), or negative (should not have a citation) based on the sequence of words in the sentence. The resulting model can correctly classify sentences in need of citation with an accuracy of up to 90%.
Explaining algorithmic predictions
But why is the model up to 90% accurate? What is the algorithm looking at when deciding whether a sentence needs a citation?
To help interpret these results, we took a sample of sentences needing citations for different reasons, and highlighted words the model considered the most when it classified the sentences. In the case of “opinion” statements, for example, the model assigned the highest weight to the word “claimed”. In the “statistics” citation reason, the most important words to the model are verbs that are often used in reporting numbers. In the case of scientific citation reasons, the model pays more attention to domain-specific words like “quantum”.
Predicting why a sentence needs a citation
Similar to the “reason” field of the [citation needed] tag, we want our model to also provide full explanations of citation reasons. Therefore we created a model that can classify statements needing citations with a reason. We first designed a crowdsourcing experiment using Amazon Mechanical Turk to collect labels about citation reasons. We randomly sampled 4,000 sentences that contain citations from Featured articles, and asked crowdworkers to label them with one of the eight citation reason categories we identified in our previous study. We found that sentences more likely need citations when they are related to scientific or historical facts, or when they reflect direct/indirect quotations.
We modified the neural network designed in the previous study, so that it can classify an unsourced sentence into one of the 8 citation reason categories. We retrained this network using the crowdsourced labeled data, and found that it provides reasonable accuracy (precision at 0.62) in predicting citation reasons, especially for classes with a substantial amount of training data.
Next steps: predicting “citation need” across languages and topics
The next phase of this project will involve modifying our models so that they can be trained for any language available in Wikipedia. We will use these multilingual models to quantify the proportion of unverified content across Wikipedia editions, and map citation coverage across different article topics, in order to help editors identify areas where adding high quality citations is particularly important.
We plan to make the source code of these new models available soon. In the meantime, you can check out the research paper, recently accepted at The Web Conference 2019, its supplementary material with detailed analysis of the citation policies, and all the data we used to train the models.
We would love to hear your feedback and comments, so please reach out to us on our project page to help us improve it.
Miriam Redi, Research Scientist, Wikimedia Foundation
Jonathan Morgan, Senior Design Researcher, Wikimedia Foundation
Dario Taraborelli, former Director of Research, Wikimedia Foundation
Besnik Fetahu, Post-doctoral Scientist, L3S Lab Hannover
The authors would like to thank the community members of the English, French, and Italian Wikipedias, along with workers from Amazon Mechanical Turk, for helping with data labeling and for their precious suggestions.
—I suppose you are an entomologist?—I said with a note of interrogation.
—Not quite so ambitious as that, sir. I should like to put my eyes on the individual entitled to that name! A society may call itself an Entomological Society, but the man who arrogates such a broad title as that to himself, in the present state of science, is a pretender, sir, a dilettante, an impostor! No man can be truly called an entomologist, sir; the subject is too vast for any single human intelligence to grasp.
The Poet at the Breakfast Table (1872) by Oliver Wendell Holmes, Sr.
|
|
A collection of biographies with surprising gaps (ex. A.D. Imms) |
|
|
|
Eleanor Ormerod, an unexpected influence in the rise of economic entomology in India |
|
|
| Kunhikannan died at the rather young age of 47 |
In the field of natural sciences the Hindus did not make any progress. The classifications of animals and plants are very crude. It seems to me possible that this singular lack of interest in this branch of knowledge was due to the love of animal life. It is difficult for Westerners to realise how deep it is among Indians. The observant traveller will come across people trailing sugar as they walk along streets so that ants may have a supply, and there are priests in certain sects who veil that face while reading sacred books that they may avoid drawing in with their breath and killing any small unwary insects. [Note: Salim Ali expressed a similar view ]He then examines science sponsored by state institutions, by universities and then by individuals. About the last he writes:
Though I deal with it last it is the first in importance. Under it has to be included all the work done by individuals who are not in Government employment or who being government servants devote their leisure hours to science. A number of missionaries come under this category. They have done considerable work mainly in the natural sciences. There are also medical men who devote their leisure hours to science. The discovery of the transmission of malaria was made not during the course of Government work. These men have not received much encouragement for research or reward for research, but they deserve the highest praise., European officials in other walks of life have made signal contributions to science. The fascinating volumes of E. H. Aitken and Douglas Dewar are the result of observations made in the field of natural history in the course of official duties. Men like these have formed themselves into an association, and a journal is published by the Bombay Natural History Association[sic], in which valuable observations are recorded from time to time. That publication has been running for over a quarter of a century, and its volumes are a mine of interesting information with regard to the natural history of India.
This then is a brief survey of the work done in India. As you will see it is very little, regard being had to the extent of the country and the size of her population. I have tried to explain why Indians' contribution is as yet so little, how education has been defective and how opportunities have been few. Men do not go after scientific research when reward is so little and facilities so few. But there are those who will say that science must be pursued for its own sake. That view is narrow and does not take into account the origin and course of scientific research. Men began to pursue science for the sake of material progress. The Arab alchemists started chemistry in the hope of discovering a method of making gold. So it has been all along and even now in the 20th century the cry is often heard that scientific research is pursued with too little regard for its immediate usefulness to man. The passion for science for its own sake has developed largely as a result of the enormous growth of each of the sciences beyond the grasp of individual minds so that a division between pure and applied science has become necessary. The charge therefore that Indians have failed to pursue science for its own sake is not justified. Science flourishes where the application of its results makes possible the advancement of the individual and the community as a whole. It requires a leisured class free from anxieties of obtaining livelihood or capable of appreciating the value of scientific work. Such a class does not exist in India. The leisured classes in India are not yet educated sufficiently to honour scientific men.It is interesting that leisure is noted as important for scientific advance. Edward Balfour, mentioned earlier, also made a similar comment that Indians were too close to subsistence to reflect accurately on their environment! (apparently in The Vydian and the Hakim, what do they know of medicine? (1875) which unfortunately is not available online)
|
|
|
Entomologists meeting at Pusa in 1919 Third row: C.C. Ghosh, Ram Saran, Gupta, P.V. Isaac, Y. Ramachandra Rao, Afzal Husain, Ojha, A. Haq Second row: M. Zaharuddin, C.S. Misra, D. Naoroji, Harchand Singh, G.R. Dutt, E.S. David, K. Kunhi Kannan, Ramrao S. Kasergode, J.L.Khare, Jhaveri, V.G.Deshpande, R. Madhavan Pillai, Patel, A. Mujtaba, P.C. Sen First row: Capt. Froilano de Mello, Robertson-Brown, S. Higginbotham, C.M. Inglis, C.F.C. Beeson, Gough, Bainbrigge Fletcher, Bentley, Senior-White, T.V. Rama Krishna Ayyar, C.M. Hutchinson, Andrews, H.L.Dutt |
|
|
|
|
Entmologists meeting at Pusa in 1923
Fifth row (standing) Mukerjee, G.D.Ojha, Bashir, Torabaz Khan, D.P. Singh
Fourth row (standing) M.O.T. Iyengar, R.N. Singh, S. Sultan Ahmad, G.D. Misra, Sharma,Ahmad Mujtaba, Mohammad Shaffi
Third row (standing) Rao Sahib Y Rama Chandra Rao, D Naoroji, G.R.Dutt, Rai Bahadur C.S. Misra, SCJ Bennett (bacteriologist, Muktesar), P.V. Isaac, T.M. Timoney, Harchand Singh, S.K.Sen
Second row (seated) Mr M. Afzal Husain, Major RWG Hingston, Dr C F C Beeson, T. Bainbrigge Fletcher, P.B. Richards, J.T. Edwards, Major J.A. Sinton
First row (seated) Rai Sahib PN Das, B B Bose, Ram Saran, R.V. Pillai, M.B. Menon, V.R. Phadke (veterinary college, Bombay)
|
|
It’s been quite a long time (four and a half years in fact) since I looked at the state of the African language Wiktionaries. For those new to Wiktionary, the idea is that it will describe all words of all languages using definitions and descriptions in the particular language edition. An ambitious task!
So, how are the projects progressing?
A portion of the Octateuch in Ethiopian
| Language | 30/5/2010 | 15/5/2011 | 29/10/2014 | 22/3/2019 | % + |
|---|---|---|---|---|---|
| Malagasy | 4,253 | – | 3,599,084 | 5,482,632 | 52.33% |
| Afrikaans | 14,669 | 14,731 | 15,794 | 20,831 | 31.89% |
| Swahili | 13,000 | 13,027 | 13,903 | 14,029 | 0.91% |
| Wolof | 2,689 | 2,693 | 2,310 | 2,312 | 0.09% |
| Somali | – | – | – | 1,635 | – |
| Sotho | 1,389 | 1,398 | 1,343 | 1,343 | 0.00% |
| Lingala | – | – | – | 673 | – |
| Zulu | 131 | 510 | 586 | 599 | 2.22% |
| Igbo (incubator) | – | – | – | 375 | – |
| Kinyarwanda | 306 | 306 | 367 | 366 | – |
| Tsonga | 359 | 363 | 92 | 359 | 290.22% |
| Oromo | 218 | 264 | 322 | 335 | 4.04% |
| Swati | 371 | 377 | 290 | 292 | 0.69% |
| Amharic | 319 | 377 | 206 | 217 | 5.34% |
| Egyptian Arabic (incubator) | – | – | – | 195 | – |
In short, although it’s been so long since the last update, there’s not much to show. The only project to more than double its articles in four and a half years is Tsonga, off a minute base. Malagasy has always had a huge amount of bot activity, and is still growing from a large base, and Afrikaans shows some signs of life. But overall, the state of the African language Wiktionaries can be described as dormant.
Perhaps the African language Wikipedias will fare better?
| Language | 26/6/2015 | 5/9/2017 | 30/6/2018 | 2/4/2019 | % + |
|---|---|---|---|---|---|
| Malagasy | 79,329 | 84,634 | 84,996 | 91,528 | 7.68% |
| Afrikaans | 35,856 | 46,824 | 50,275 | 76,965 | 53.11% |
| Swahili | 29,127 | 37,443 | 42,773 | 49,555 | 15.86% |
| Yoruba | 31,068 | 31,577 | 31,672 | 31,867 | 0.62% |
| Egyptian Arabic | 14,192 | 17,138 | 18,605 | 20,405 | 9.67% |
| Amharic | 12,950 | 13,789 | 14,286 | 14,558 | 1.90% |
| Northern Sotho | 1,000 | 7,823 | 8,050 | 8,018 | -0.40% |
| Somali | 3,446 | 4,727 | 4,898 | 5,456 | 11.39% |
| Shona | 2,321 | 2,851 | 3,630 | 4,278 | 17.85% |
| Hausa | 1,345 | 1,525 | 1,856 | 3,494 | 88.25% |
| Lingala | 2,062 | 2,915 | 3,023 | 3,113 | 2.98% |
| Kabyle | 2,296 | 2,887 | 2,844 | 2,986 | 4.99% |
| Kinyarwanda | 1,780 | 1,810 | 1,823 | 1,821 | -0.11% |
| Kikuyu | – | 1,349 | 1,357 | 1,358 | 0.07% |
| Igbo | 1,019 | 1,384 | 1,320 | 1,392 | 5.45% |
| Kongo | – | 1,176 | 1,179 | 1,193 | 1.19% |
| Wolof | 1,023 | 1,157 | 1,166 | 1,184 | 1.54% |
| Luganda | – | 1,153 | 1,162 | 1,169 | 0.60% |
| Zulu | 683 | 942 | 959 | 1,067 | 11.26% |
| Language | 26/6/2015 | 5/9/2017 | 30/6/2018 | 2/4/2019 | % + |
The Zulu Wikipedia is the latest addition to the 1000 club, having reached this milestone just before Wikimania last year, and progress has been steady since then.
At first glance, Hausa looks like it’s in great shape, with an 88% increase in the number of articles. But this is misleading, as many of these are one line articles on football players, the entirety of which translates as, for example, “Kenny Allen (footballer) is an English football player.” No disrespect to Kenny Allen, but I’m not sure he and the 100s of other footballers listed there are critical components of Hausa knowledge. There’s a move to delete these articles (you can see the impressive list here while it’s up), but even if they survive, it’s not a sign of a healthy project.
Leaving aside Hausa, it’s once again Afrikaans, growing at an impressive 53% over the period, that provides an example for the rest. At current rates, it’s on track to pass Malagasy and reclaim its position on top in about a year or so.
Besides Afrikaans, only Shona, Swahili, Somali and Zulu show a growth rate above 10%, while quite a few sit idle.
Moving on to the South African language editions specifically:
| Language | 26/6/2015 | 5/9/2017 | 30/6/2018 | 2/4/2019 | % + |
|---|---|---|---|---|---|
| Afrikaans | 35,856 | 46,824 | 50,275 | 76,965 | 53.11% |
| Northern Sotho | 1,000 | 7,823 | 8,050 | 8,018 | -0.40% |
| Zulu | 683 | 942 | 959 | 1,067 | 11.26% |
| Xhosa | 356 | 708 | 738 | 789 | 6.91% |
| Tswana | 503 | 639 | 641 | 641 | 0.00% |
| Tsonga | 266 | 526 | 562 | 585 | 4.09% |
| Sotho | 223 | 523 | 539 | 546 | 1.30% |
| Swati | 410 | 432 | 439 | 467 | 6.38% |
| Venda | 151 | 256 | 256 | 265 | 3.52% |
| Ndebele (incubator) | – | 12 | 12 | 11 | -8.33% |
| Language | 26/6/2015 | 5/9/2017 | 30/6/2018 | 2/4/2019 | % + |
Afrikaans remains the only project that could be described as a usable Wikipedia – the other languages are still very much in the formative stages. Zulu is also showing signs of life. Besides these two, only Xhosa and Swati see growth rates above 5%. It’s sad to see the stalling of Northern Sotho, while Ndebele shows no signs of getting out of the incubator anytime soon.
2019 has been proclaimed the Year of Indigenous Languages by the UN, but so far there’s not much sign of a change in the status of the African language projects. Later today sees the South African Centre for Digital Language Resources, in collaboration with the Academy of African Languages and Science from the University of South Africa, present an interactive day workshop on contributing to Wikipedia in South African languages. It’s great to see this initiative, which arose with no help that I’m aware of from Wikimedia South Africa. I’m always hopeful with events like these. Generally very few people to stay around to edit Wikipedia, but as projects like Northern Sotho and Swahili show, one person can make a huge difference in the early stages, and it justs needs a committed editor to stick around. It’s a lonely job editing in the early stages, wondering if it’s worthwhile, no community, no idea if their work is being read. Hopefully someone will take on the challenge!
If you are looking to contribute, but don’t know where to start, please reach out to Wikimedia South Africa and we’d be happy to assist.
Image from Wikimedia Commons
This April 2, on #AprilFactsDay, we’re reminded of the importance of trustworthy information. How can we equip the next generations of information consumers and producers with the skills they need to participate in our rapidly changing digital landscape?
Wikipedia is one of the most trusted sites among the cacophony online. That’s because it’s built on the principle of verifiability; its community-made policies take a strict stance against promotion and advertising; and the volunteers that curate its content value neutrally presented and well-referenced facts. Information that doesn’t adhere to these standards is deleted as soon as one of Wikipedia’s thousands of devoted volunteers encounters it.
But there are still gaps in information on Wikipedia, which can be harder to spot than false information. That’s where instructors and students in our Student Program are making a difference. Higher education instructors use our tools and assignment templates to teach students how to identify gaps on Wikipedia and use what they’re learning in class to correct those gaps.
That’s what Dr. Ada Palmer did with her 32 students at the University of Chicago last fall term. Students added 90,000 words of well-researched content to Wikipedia about “how new information technologies trigger innovations in censorship and information control.” *
Did you know, for example, that food producers can more easily sue their critics in certain states in the US because of food libel laws? The laws are often criticized as a restriction of first amendment rights.
And newspaper theft, a form of censorship, occurs when an individual, organization, or government removes a large portion of a publication without the consent of the publisher in order to prevent others from reading it. The Wikipedia article now highlights some notable cases, as well as the strategies that various states and cities in the US employ to counteract it.
Margaret Sullivan of the Washington Post calls April 2 (also known as Fact-Checking Day) “a global counterpunch on behalf of truth.” She also writes that it’s an opportunity to get the public more involved in the processes of informational evaluation that journalists undertake daily.
In a Wikipedia writing assignment, students participate in fact-checking Wikipedia, looking for informational gaps, and correcting those gaps for the benefit of millions of readers. Wikipedia writing is fact-checking in action, with an added praxis of making the digital informational landscape better.
In the case of Dr. Palmer’s students, the assignment is also an opportunity to educate others of their rights in the face of false information and censorship.
In general, a Wikipedia writing assignment provides students with an opportunity to learn to critically evaluate information and participate in modes of knowledge creation that they typically accept passively. When Stanford Graduate School of Education found in 2016 that most students can’t tell the difference between a credible news website and a fake news site, a lot of instructors sprung into action to understand how they could help reinforce these skills in their students. Critical media literacy is an essential part of education and a skill that every instructor in higher education has the power to teach.
The ability to access trustworthy and free information equips citizens to know and protect their rights. Access, however, is just the first step. Access plus judgement – the ability to discern reliable from unreliable information – is what truly makes a digital citizen.
Read more about how our work at Wiki Education combats fake news and how you can help. And for more information about Dr. Palmer’s course, visit the University of Chicago’s course page here or their Youtube channel.
Interested in adapting a Wikipedia writing assignment to fit your course? Visit teach.wikiedu.org for all you need to know.
For a few weeks, a CI job had PHPUnit tests abruptly ending with:
returned non-zero exit status -11
The connoisseur [ 1 ] would have recognized that the negative exit status indicates the process exited due to a signal. On Linux, 11 is the value for the SIGSEGV signal, which is usually sent by the kernel to the process as a result of an improper machine instruction. The default behavior is to terminate the process (man 7 signal) and to generate a core dump file (I will come to that later).
But why? Some PHP code ended up triggering a code path in HHVM that would eventually try to read outside of its memory range, or some similar low level fault. The kernel knows that the process completely misbehaved and thus, well, terminates it. Problem solved, you never want your program to misbehave when the kernel is in charge.
The job had recently been switched to use a new container in order to benefit from more recent lib and to match the OS distributions used by the Wikimedia production system. My immediate recommendation was to rollback to the previous known state, but eventually I have let the task to go on and have been absorbed by other tasks (such as updating MediaWiki on the infrastructure).
Last week, the job suddenly began to fail constantly. We prevent code from being merged when a test fails, and thus the code stays in a quarantine zone (Gerrit) and cannot be shipped. A whole team could not ship code (the Language-Team ) for one of their flagship projects (ContentTranslation .) That in turn prevents end users from benefiting from new features they are eager for. The issue had to be acted on and became an unbreak now! kind of task. And I went to my journey.
returned non-zero exit status -11, that is a good enough error message. A process in a Docker container is really just an isolated process and is still managed by the host kernel. First thing I did was to look at the kernel syslog facility on our instances, which yields:
kernel: [7943146.540511] php[14610]:
segfault at 7f1b16ffad13 ip 00007f1b64787c5e sp 00007f1b53d19d30
error 4 in libpthread-2.24.so[7f1b64780000+18000]
php there is just HHVM invoked via a php symbolic link. The message hints at libpthread which is where the fault is. But we need a stacktrace to better determine the problem, and ideally a reproduction case.
Thus, what I am really looking for is the core dump file I alluded to earlier. The file is generated by the kernel and contains an image of the process memory at the time of the failure. Given the full copy of the program instructions, the instructions it was running at that time, and all the memory segments, a debugger can reconstruct a human readable state of the failure. That is a backtrace, and is what we rely on to find faulty code and fix bugs.
The core file is not generated. Or the error message would state it had coredumped, i.e. the kernel generated the core dump file. Our default configuration is to not generate any core file, but usually one can adjust it from the shell with ulimit -c XXX where XXX is the maximum size a core file can occupy (in kilobytes, in order to prevent filling the disk). Docker being just a fancy way to start a process, it has a setting to adjust the limit. The docker run inline help states:
--ulimit ulimit Ulimit options (default [])
It is as far as useful as possible, eventually the option to set is: --ulimit core=2147483648 or up to 2 gigabytes. I have updated the CI jobs and instructed them to capture a file named core, the default file name. After a few runs, although I could confirm failures, no files got captured. Why not?
Our machines do not use core as the default filename. It can be found in the kernel configuration:
name=/proc/sys/kernel/core_pattern
/var/tmp/core/core.%h.%e.%p.%t
I thus went on the hosts looking for such files. There were none.
Or maybe I mean None or NaN.
Nada, rien.
The void.
The result is obvious, try to reproduce it! I ran a Docker container doing a basic while loop, from the host I have sent the SIGSEGV signal to the process. The host still had no core file. But surprise it was in the container. Although the kernel is handling it from the host, it is not namespace-aware when it comes time to resolve the path. My quest will soon end, I have simply mounted a host directory to the containers at the expected place:
mkdir /tmp/coredumps docker run --volume /tmp/coredumps:/var/tmp/core ....
After a few builds, I had harvested enough core files. The investigation is then very straightforward:
$ gdb /usr/bin/hhvm /coredump/core.606eb29eab46.php.2353.1552570410 Core was generated by `php tests/phpunit/phpunit.php --debug-tests --testsuite extensions --exclude-gr'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f557214ac5e in __pthread_create_2_1 (newthread=newthread@entry=0x7f55614b9e18, attr=attr@entry=0x7f5552aa62f8, start_routine=start_routine@entry=0x7f556f461c20 <timer_sigev_thread>, arg=<optimized out>) at pthread_create.c:813 813 pthread_create.c: No such file or directory. [Current thread is 1 (Thread 0x7f55614be3c0 (LWP 2354))] (gdb) bt #0 0x00007f557214ac5e in __pthread_create_2_1 (newthread=newthread@entry=0x7f55614b9e18, attr=attr@entry=0x7f5552aa62f8, start_routine=start_routine@entry=0x7f556f461c20 <timer_sigev_thread>, arg=<optimized out>) at pthread_create.c:813 #1 0x00007f556f461bb2 in timer_helper_thread (arg=<optimized out>) at ../sysdeps/unix/sysv/linux/timer_routines.c:120 #2 0x00007f557214a494 in start_thread (arg=0x7f55614be3c0) at pthread_create.c:456 #3 0x00007f556aeebacf in __libc_ifunc_impl_list (name=<optimized out>, array=0x7f55614be3c0, max=<optimized out>) at ../sysdeps/x86_64/multiarch/ifunc-impl-list.c:387 #4 0x0000000000000000 in ?? ()
Which @Anomie kindly pointed out is an issue solved in libc6. Once the container has been rebuilt to apply the package update, the fault disappears.
One can now expect new changes to appear to ContentTranslation.
[ 1 ] ''connoisseur'', from obsolete French, means "to know" https://en.wiktionary.org/wiki/connoisseur . I guess the English language forgot to apply update on due time and can not make any such change for fear of breaking back compatibility or locution habits.
The task has all the technical details and log leading to solving the issue: T216689: Merge blocker: quibble-vendor-mysql-hhvm-docker in gate fails for most merges (exit status -11)
(Some light copyedits to above -- Brennen Bearnes)
Today we're publishing our first report of the performance experienced by visitors of Wikimedia websites, focused on the Autonomous Systems visitors are connecting from.
This report will be updated monthly, with historical data made available. The goal is to watch the evolution of these metrics over time, allowing us to identify improvements and potential pain points.
In order to make a fair assessment of the autonomous systems' performance, real user metrics collected from web browsers are normalised, in order to avoid differences such as average device power for a given network's users potentially skewing the results. For example, an ISP with more expensive data plans might have users with more expensive, better performing devices on average. This is way we compare data points only for similar effective device CPU power between providers. We also separate the mobile and desktop experiences, because they serve different content, with a notable difference in the median page weight, which directly impacts performance metrics. We wouldn't want the mobile/desktop mix of a given provider to influence the results.
If you look at the report, you might wonder why some autonomous systems' underlying mobile networks show up under "desktop" and some wired internet providers appear under "mobile". The explanation is that the internet providers either sell home internet devices that are effectively mobile network modems, resulting in people using their desktop computers (and as a result, the desktop websites) over a mobile network. Or the providers have mobile device users automatically connect to the same provider's WiFi routers when users are in reach of one.
One caveat about this report is that in countries that are physically large, like the United States, the country-wide aggregation in no way reflects important regional differences there might be for a given network. The main reason why we can't look at smaller regions is that we have simply no way of knowing where mobile users are connecting from, short of collecting geolocation data. Since we care deeply about our user's privacy and their experience, it doesn't feel appropriate at this time to ask users for their precise location in order to generate this type of finer-grained data. Such a scheme would also suffer from self-selection bias. There's already a lot of work to be done with the data aggregated at the national level!
We hope that this public report will help network operators understand their customers' real performance characteristics when it comes to browsing one of the web's largest websites. We are welcoming of peering requests networks might want to propose, should they seek to improve their connectivity to our datacenters.
Dr. Irene Chen gave her chemistry students a unique opportunity to practice science communication. She incorporated a Wikipedia writing assignment into her course at UC Santa Barbara this last fall. The course discussed major breakthroughs in nucleic acids research – information that students then channeled into relevant Wikipedia articles where details were missing. Eight students added a total of 13,600 words to Wikipedia this way, a process requiring that they synthesize research in the most concise, essentialized way possible.
3,600 of those words were channeled into Wikipedia’s article about systematic evolution of ligands by exponential enrichment, a chemical process also known as in vitro selection. Before the student began improving the article, it was almost entirely made up of an introduction and no other informational sections. That was even noted on the article’s Talk page, where volunteers discuss their desired changes. Dr. Chen’s student responded directly to the issue by adding sections about the details of the procedure. Those new sections include information about how chemists generate a single stranded oligonucleotide library and then how that library is incubated to allow binding with the oligonucleotide-target. The student also added information about tracking the progress of the resulting reaction.
Another student expanded Wikipedia’s article about minimum inhibitory concentration (MIC), which before was also just an introduction and few references. 1,200 words later, the article boasts an additional 10 sources, as well as background information about the history and clinical usage of the MIC concept. As the article states, MIC “is the lowest concentration of a chemical, usually a drug, which prevents visible growth of bacterium,” a definition supported by a review paper published in 2005 about the treatment of bacterial infectious diseases. The article has been viewed almost 13,000 times since the student made changes – many more than would a typical term paper!
Students tend to invest more in their work when they realize it can be accessed by millions. They understand the responsibility to represent information accurately and take their new-found role of ‘knowledge creator’ seriously. They’re a great group to do this work well, especially in the sciences. Students can translate complex course topics for a general audience who might be learning about the topic for the first time because they remember what that was like. They do a great service to the world by sharing expertise they have access to (both through their professor and their library resources) with Wikipedia’s worldwide readership. That matters, and they understand that.
Interested in incorporating a Wikipedia writing assignment into your course? Visit teach.wikiedu.org for all you need to know to get started. Or hear from instructors who have done this here.
19/03/2019-25/03/2019
Map for young parents | 1 | © Leaflet | Map data © OpenStreetMap contributors, CC-BY-SA, Map Tiles © OpenStreetMap
landuse=forest nor natural=wood such as for example a cemetery? These can be tagged using landcover = trees along with their default landuse tags.
| Where | What | When | Country |
|---|---|---|---|
| Sydney | Sydney OSM get together | 2019-03-30 |
|
| UCL Louvain-la-Neuve | National Mapathon | 2019-03-30 |
|
| ULIEGE Liège | National Mapathon | 2019-03-30 |
|
| Bochum | Mappt die Innenstadt – Mappingtag für Einsteiger*innen und Fortgeschrittene | 2019-03-31 |
|
| Stuttgart | Stuttgarter Stammtisch | 2019-04-03 |
|
| Bochum | Mappertreffen | 2019-04-04 |
|
| Nantes | Réunion mensuelle | 2019-04-04 |
|
| Dresden | Stammtisch Dresden | 2019-04-04 |
|
| Heidelberg | DisasterMappers Night of Geography | 2019-04-05 |
|
| Cayenne | Rencontre mensuelle | 2019-04-05 |
|
| La Riche | La Riche (37)#Ateliers d’initiation à OpenStreetMap | 2019-04-06 |
|
| Kyoto | お花見!オープンデータソン in 京都 | 2019-04-07 |
|
| Rennes | Réunion mensuelle | 2019-04-08 |
|
| Bordeaux | Réunion mensuelle | 2019-04-08 |
|
| Essen | Mappertreffen | 2019-04-08 |
|
| Taipei | OSM x Wikidata #3 | 2019-04-08 |
|
| Toronto | Toronto Mappy Hour | 2019-04-08 |
|
| Lyon | Rencontre mensuelle pour tous | 2019-04-09 |
|
| Munich | Münchner Stammtisch | 2019-04-09 |
|
| Salt Lake City | SLC Mappy Hour | 2019-04-09 |
|
| Viersen | OSM Stammtisch Viersen | 2019-04-09 |
|
| Cologne | Köln Stammtisch | 2019-04-10 |
|
| Buenos Aires | Taller Introducción a JOSM en FOSS4G-AR 2019 | 2019-04-10 |
|
| Leoben | Stammtisch Obersteiermark | 2019-04-11 |
|
| Zurich | OSM Stammtisch Zurich | 2019-04-11 |
|
| Berlin | 130. Berlin-Brandenburg Stammtisch | 2019-04-12 |
|
| Salt Lake City | University of Utah Campus Mapping Party | 2019-04-13 |
|
| Biella | Incontro mensile | 2019-04-13 |
|
| Salt Lake City | SLC Map Night | 2019-04-16 |
|
| Cologne Bonn Airport | Bonner Stammtisch | 2019-04-16 |
|
| Lüneburg | Lüneburger Mappertreffen | 2019-04-16 |
|
| Reutti | Stammtisch Ulmer Alb | 2019-04-16 |
|
| Toulouse | Rencontre mensuelle | 2019-04-17 |
|
| Karlsruhe | Stammtisch | 2019-04-17 |
|
| Montpellier | State of the Map France 2019 | 2019-06-14-2019-06-16 |
|
| Angra do Heroísmo | Erasmus+ EuYoutH_OSM Meeting | 2019-06-24-2019-06-29 |
|
| Minneapolis | State of the Map US 2019 | 2019-09-06-2019-09-08 |
|
| Edinburgh | FOSS4GUK 2019 | 2019-09-18-2019-09-21 |
|
| Heidelberg | Erasmus+ EuYoutH_OSM Meeting | 2019-09-18-2019-09-23 |
|
| Heidelberg | HOT Summit 2019 | 2019-09-19-2019-09-20 |
|
| Heidelberg | State of the Map 2019 (international conference) | 2019-09-21-2019-09-23 |
|
| Grand-Bassam | State of the Map Africa 2019 | 2019-11-22-2019-11-24 |
|
Note: If you like to see your event here, please put it into the calendar. Only data which is there, will appear in weeklyOSM. Please check your event in our public calendar preview and correct it, where appropriate.
This weeklyOSM was produced by PierZen, Polyglot, Rainero, Rogehm, SK53, SunCobalt, TheFive, TheSwavu, YoViajo, adrianxoc, derFred, jinalfoflia, k_zoar, muramototomoya.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Changes later this week
Meetings
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
In February 2018, a user reported that some topics created by users on Flow discussion boards were not appearing in the Recent Changes feeds, including EventStreams and the IRC-RC feed. Various automated patrol systems rely on EventStreams, so the bug meant a number of edits bypassed those systems on Flow-enabled wikis.
When approaching a bug like this, there are typically three things I do:
Unfortunately the problem was not reproducible in the MediaWiki Vagrant development environment. Nor were there any relevant messages in the logs. Since reproducing the issue locally wasn't possible, we merged some diagnostic code but still had nothing. Early on, @SBisson suggested a hypothesis about the code path involved in emitting the event:
if ( user is trusted ) return true else let's load the revision from replica, return true based on the the status of the revision oh it doesn't exist (yet), return false
But we could not reproduce this, nor could we identify exactly where this might occur since the code paths for this functionality had many points where execution could stop silently.
One of the useful tools in our stack is the X-Wikimedia-Debug header. I knew about this header (and its browser extensions) from verifying changes that were being SWAT'ed into production but I had not thought to use it for tracking down a production bug.
I was using the browser extension with the "Log" checkbox ticked (and still not finding anything useful in Logstash to help isolate this bug) when I realized that I could also profile the problematic request. When you check the box to profile a request, XHProf will profile the code that's executed and make the result available for viewing via XHGui.
Typically you do this to understand performance bottlenecks in your code, as get a complete list of all functions executed during the request, along with the time and memory usage associated with each function.
I followed the steps to reproduce and then switched on the "Profile" option before posting a new topic on an empty Flow board. Now, I had a profiled request which provided me with information on all the methods called, including which method called another (click on a method call to see its parent and children method calls). From here I could follow the path traversed by Flow's event emitting code, and see exactly where the code execution halted.
With this knowledge, I went back to my local environment, this time using MediaWiki-Docker-Dev, which has database replication set up as part of its stack (MediaWiki Vagrant does not). I set some breakpoints in the code I suspected was causing the problem, and then found that in RevisionActionPermissions.php#isBoardAllowed(), we had this code:
$allowed = $this->user->isAllowedAny( ...(array)$permissions ); if ( $allowed ) { return true; } return !$workflow->isDeleted();
For a new topic on a blank flow board, $permissions is deletedtext, which would return true for privileged users. But for unprivileged users, Flow would check !$workflow->isDeleted();, and this evaluated as false because the code was querying the database replica, and the title did not exist there yet.
The submitted solution was to patch isDeleted() to query the master DB when in the context of a POST request, since we know the title would exist in the master DB. With this patch in place, events were once again emitted properly and the bug was fixed.
A few of my conclusions from this experience:
Kosta Harlan
Senior Software Engineer
Growth Team
Learn more about the X-Wikimedia-Debug header and browser extension on Wikitech.
The working group to consider future CI tooling for Wikimedia has finished and produced a report. The report is at https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/CI_Futures_WG/Report and the short summary is that the release engineering team should do prototype implementations of Argo, GitLab CI/CD, and Zuul v3.
How do we get Wikipedia to every corner of the world?
How can we share the joy of free knowledge with people who have never heard of our website?
In 2018, we asked Wikipedia’s volunteer editing communities all over the world to think creatively about expanding the reach of the free online encyclopedia.
Through a crowdsourcing campaign called “Inspire New Readers”, we collected 362 ideas from more than 500 participants. From these, the Wikimedia Foundation funded eight projects through our rapid grants program.
Half of the proposals that we received focused on using social media and videos to generate additional reach, while the other half were for offline promotion. This campaign gave us many insights on what works well for projects that focus on raising awareness and we have now launched a new rapid grant type. We hope that community organizers continue to work on bringing Wikipedia to everyone.
Of the eight projects funded, four focused on online promotion, and four focused on offline promotion.
One example of online promotion is the video created by the Punjabi Wikimedians community. In it, a group of animals go to Lahore with their teacher, learning facts from Wikipedia along the way. The video went viral: it was seen by almost half a million people. The impact on Punjabi Wikipedia’s main page also exceeded expectations, with page views increasing by 357% during the campaign.
An example of an offline campaign to raise awareness of Wikimedia projects is one carried out by Maithili Wikipedia community: “The Wikipedia Rickshaw”, which had the goal of engaging new readers in Rajbiraj, a province in Nepal. For this campaign, the local community ran rickshaw announcements about Maithili Wikipedia in the city, held offline meetups, and hired billboards at various locations throughout the city. During the campaign, there was a 25% increase in siteviews for this language version Wikipedia.
These eight projects are a good example of why it is important to reach potential new readers in their language, and where they are: traffic can be easily impacted in smaller language version Wikimedia projects. You can read more about all projects funded in the campaign report.
What other lessons stem from these awareness projects? What about the performance of videos, versus slide shows, versus images in social media campaigns? To dive deeper on the impact social media campaigns can have, we focused on two other marketing initiatives led by communities in Asia: Bengali Wikisource, and Tamil Wikipedia. The Bengali Wikisource community created 2 videos and 1 image with text, which were then a/b tested. After testing them, the videos proved to have better results, increasing traffic to the site by 86% during the campaign. The Tamil Wikipedia community created a slideshow on Facebook, using good quality images from Wikimedia Commons. They tested Facebook banners against the slideshows and learned that the slideshows worked better. Through this optimization, they were able to increase traffic to the site by 22% during the campaign.
You can read more about these two initiatives, including lessons learned on audience segmentation through geography and language, in the community marketing experiments impact report.
These marketing initiatives are important to the growth of Wikipedia and other wiki projects: awareness is the first step in building new users, support, and ultimately participation in Wikimedia projects. We know that low awareness of Wikipedia is associated with low usage, and without usage people will never become contributors or advocates for free knowledge.
It is now easier to apply for grants for projects that focus on raising awareness of Wikimedia projects. With the insights from the two impact reports, we have created two sets of guidelines that focus on projects to raise awareness: one for general promotion campaigns, and one for video campaigns. This documentation is part of the rapid grants program, which now offers an extension of $1,000 over the limit of this grant program (a total of $3,000 USD) for video creation. In these guidelines, you will find details of what the grant will pay for, typical outcomes, things you’ll need, and a list of example projects for guidance.
We hope that these new guidelines inspire community organizers to continue working to make Wikipedia visible in every corner of the world.
María Cruz, Communication & Outreach Project Manager, Community Relations, Community Engagement
Wikimedia Foundation
Writing blog is neither my job nor something that I enjoy, I am thus late in the Quibble updates. The last one Blog Post: Quibble in summer has been written in September 2018 and I forgot to publish it until now. You might want to read it first to get a glance about some nice changes that got implemented last summer.
I guess personal changes that happened in October and the traditional norther hemisphere winter hibernation kind of explain the delay (see note [ 1 ]). Now that spring is finally there ({{NPOV}}), it is time for another update.
Quibble went from 0.0.26 to 0.0.30 which I have cut just before starting this post. I wanted to highlight a few changes from an overall small change log:
The first inception of Quibble did not have much thoughts put into it with regard to speed. The main goal at the time was simply to gather all the complicated logic from CI shell scripts, Jenkins jobs shell snippets, python or javascript scripts all in one single command. That in turn made it easier to reproduce a build but with a serious limitation: commands are just run serially which is far from being optimum.
Quibble would now run the lint commands in parallel for both extensions/skins and mediawiki/core. Internally, it forks run composer test and npm test in parallel, that slightly speed up the time to get linting commands to complete.
Another annoyance is when testing multiple repositories together, preparing the git repositories could takes several minutes. An example is for an extension depending on several other extensions or the gated wmf-quibble-* jobs which run tests for several Wikimedia deployed extensions. Even when using a local cache of git repositories (--git-cache) the serially run git commands take a while. Quibble 0.0.30 learned --git-parallel to run the git commands in parallel. An example speed up using git cache, several repositories and a DSL connection:
| git-parallel | Duration |
|---|---|
| 16 | 30 seconds |
| 1 | 50 seconds |
The option defaults to 1 which retain the exact same behavior / code path as before. I invite you to try --git-parallel=8 for example and draw your own conclusion. Wikimedia CI will be updated once Quibble 0.0.30 is deployed.
Parallelism added by myself, @hashar, and got partly tracked in T211701.
Some part of the documentation referred to a Wikimedia CI containers that were no more suitable for running tests due to refactoring. The documentation as thus been updated to use the proper containers: docker-registry.wikimedia.org/releng/quibble-stretch-php72 or docker-registry.wikimedia.org/releng/quibble-stretch-hhvm. -- @hashar
In August, Wikidata developers used Quibble to reproduce a test failure and they did the extra step to capture their session and document how to reproduce it. Thank you @Pablo-WMDE for leading this and @Tarrow, @Addshore, @Michael, @Ladsgroup for the reviews - T200991.
You can read the documentation online at:
Note: as of this writing, the CI git servers are NOT publicly reachable (git://contint1001.wikimedia.org and git://contint2001.wikimedia.org).
Some extensions or skins might have submodules, however we never caught errors when they failed to process and kept continuing. That later causes tests to fail in non obvious way and caused several people to loose time recently. T198980
The reason is Quibble simply borrowed a legacy shell script to handle submodules and that script has been broken since its first introduction in 2014. It relied on the find command which still exit 0 even with -exec /bin/false. The reason is that although /bin/false exit code is 1, that simply causes find to consider the -exec predicate to be false, find thus abort processing further predicates but that is not an error.
The logic has been ported to pure python and now properly abort when git submodule fails. That also drop the requirement to have the find command available which might help on Windows. -- @hashar
The configuration injected by Quibble in LocalSettings.php is now a single file when it previously was made of several small PHP files glued together by shelling out to php. The inline comments have been improved. -- @Krinkle
MediaWiki installer uses a slightly stronger password (testwikijenkinspass) to accommodate for a security hardening in MediaWiki core itself. -- @Reedy T204569
The Gerrit URL to clone the canonical git repository from has been updated to catch up with a change in Gerrit. Updated r/p to simply /r. -- @Legoktm T218844
PHPUnit generates JUnit test results in the log directory, intended to be captured and interpreted by CI. -- @hashar T207841
footnotes
[ 1 ] Seasons are location based and a cultural agreement, they are quite interesting in their own. They are reversed in the Norther and Southern hemisphere, do not exist at the equator while in India they define six seasons. Thus when I refer to a winter hibernation, it really just reflect my own biased point of view.
[ 2 ] Parallelism is fun, I can never manage to write that word without mixing up the number of r or l for some reason. As a sideway note, my favorite sport to watch is parallel bars (enwiki).
|
| G. Niethammer |
|
|
Siwek, artist who documented life at Auschwitz before working as a wildlife artist. |
He revered the ancient cultures of India and the East, or at least his own weird vision of them.
These were not private enthusiasms, and they were certainly not harmless. Cranky pseudoscience nourished Himmler’s own murderous convictions about race and inspired ways of convincing others...
Himmler regarded himself not as the fantasist he was but as a patron of science. He believed that most conventional wisdom was bogus and that his power gave him a unique opportunity to promulgate new thinking. He founded the Ahnenerbe specifically to advance the study of the Aryan (or Nordic or Indo-German) race and its origins
|
| SS-Sturmbannführer Schäfer at the head of the table in Lhasa |
Even as recently as 2015, the University of Salzburg withdrew an honorary doctorate that they had given to the Nobel prize winning Konrad Lorenz for his support of the political setup and racial beliefs. It should not be that hard for scientists to figure out whether they are on the wrong side of history even if they are funded by the state. Perhaps salaried scientists in India would do well to look at the legal contracts they sign with their employers, especially the state, more carefully. The current rules make government employees less free than ordinary citizens but will the educated speak out or do they prefer shackling themselves. From time immemorial, human beings have obsessed over knowledge. It’s one of our most precious resources, and our most jealously guarded. We’ve accumulated it gathering in circles under trees and squeaky chairs in sloped lecture halls, distributed it in etchings on stone tablets and inky letters on paper pages, even sought to hide it by blindfolding interlopers and erecting paywalls out of code.
Today, the gates that keep knowledge in the hands of the few are coming down. As a global society, we are more literate, cooperative, and connected than ever before. By reading this right now, you are doing more than your early ancestors could have fathomed.
How has that access to knowledge shaped your life?
Who would you be without what you know?
Is the right to seek knowledge freely currently protected where you live?
What might a future with complete access to the sum of the world’s knowledge look like?
What forms of knowledge are most important to you—and does your society recognize and value them?
After all, knowledge isn’t just a set of random facts (“Hey Alexa, what’s the population of Budapest?”), nor is it only the theorems you memorized in school or the coding languages you use at work. It’s family recipes and whisper networks, the ways you tie your shoes and the muscles you recognize by name. It’s contested, nuanced, often inextricable from power and control. It affects the decisions we make, our health and happiness, even how we relate to each other.
With your help, the Wikimedia Foundation wants to illustrate the expansive role of knowledge in human life. Send us your creative submissions on the theme of what open access to knowledge means to you. We’re accepting work in five categories: short films, visual art (including illustrations, photography, 3D renderings, etc.), poetry, short fiction, and creative essays. The deadline to submit is 11:59pm on 30 April 2019.
In June, we’ll showcase the top entries under a Creative Commons license in our Heart of Knowledge digital anthology zine, share selected works through the Wikimedia Foundation’s YouTube channel and blog, and host an awards ceremony at the Wikimedia Foundation headquarters in San Francisco, California. The top submission in each category, as determined by our panel of judges, will also win a prize worth up to $350.
Adora Svitak, Communications Fellow
Wikimedia Foundation
*Please contact asvitak@wikimedia.org if you need an alternative method of submission.
We’re excited to announce that we’re becoming a member of the W3C, the main international standards organization for the World Wide Web.
Founded by Tim Berners-Lee in 1994, W3C works with hundreds of organizations to ensure that the web’s basic building blocks—like HTML or CSS—remain consistent across browsers, platforms, and more. You can learn more about what W3C does over on Wikipedia.
Joining the W3C fits right into our 2030 strategy, which calls on the Wikimedia movement to “become the essential infrastructure of the ecosystem of free knowledge, and [ensure that] anyone who shares our vision will be able to join us.”
The underlying technologies and standards of the web are a core part of the infrastructure that can facilitate knowledge equity, and so to achieve our vision, we need to participate and collaborate in designing the future of the web.
As part of working groups, we will be collaborating directly with other major stakeholders on the web. Through attending meetings, providing feedback, helping with the drafting of standards, and performing some of the technical work necessary to put standards together (as well as participating in the decision-making process of their design), we’re going to contribute to shaping a future of the web that helps everyone create and share free knowledge.
“We are pleased to welcome the Wikimedia Foundation among our membership,” says Alan Bird, W3C’s Global Business Development Leader. “With their 2030 strategy and interests in so many of the areas we advance on the web, we anticipate that the Wikimedia Foundation’s participation will be key in building the services and structures that enable web users.”
And we too are looking forward to collaborating with them.
Gilles Dubuc, Senior Software Engineer (Contractor), Performance, Technology
Wikimedia Foundation
Note: this post has been published on 03/28 but has been originally written in September 2018 after Quibble 0.0.26 and never got published.
The last update about Quibble is from June 1st (Blog Post: Quibble in May), this is about updating on progress made over the summer.
Since the last update, Quibble version went from 0.0.17 to 0.0.26:
For --commands one pass them as shell snippets such as: --commands 'echo starting' 'phpunit' 'echo done'. A future version of Quibble would make it only accept a single argument though it can be repeated. Or in other terms, in the future one would have to use: --command 'echo starting' --command 'phpunit' --command 'echo done'.
The MediaWiki PHPUnit test suite to use is determined based on ZUUL_PROJECT. --phpunit-testsuite lets one explicitly set it, a use case is to run extensions tests for a change made to mediawiki/core and ensure it does not break extensions (ZUUL_PROJECT=mediawiki/core quibble --phpunit-testsuite=extensions mediawiki/extensions/BoilerPlate). On Wikimedia CI they are the wmf-quibble-* jobs.
You can get great speed up by using a tmpfs for the database. Create a tmpfs and then pass --db-dir to make use of it. With a Docker container one would do: docker run --tmpfs /workspace/db:size=320M quibble:latest --db-dir=/workspace/db.
In the future, I would like Quibble to be faster, it runs the commands in a serialized way and would be made faster by parallelizing at least some of the test commands (edit: done in 0.0.29).
Changelog for 0.0.17 to 0.0.26
To celebrate the 100th anniversary of the enactment of the 19th amendment, the National Archives and Records Administration (NARA) is opening a museum exhibit called Rightfully Hers: American Women and the Vote. It will highlight both the told and untold history of women’s suffrage in America. Consider that even before the amendment’s passage, some women could vote for certain state and national offices depending on where they lived. And still other women (often women of color) could not vote even after it was ratified. The history of a nationwide policy change extends well beyond the letter of the law. Shifts must happen culturally and locally, too. Our course is working to capture and share those rich and complex stories.
NARA is collaborating with Wiki Education to make sure Wikipedia best represents the full history of women’s suffrage. Through our virtual course, historians, librarians, and citizen archivists have gathered together to learn the Wikipedia editing skills required to present these stories to the public where they’re looking for it.
Suffragist history often focuses on the well-known white players: Susan B. Anthony, Elizabeth Cady Stanton, Margaret Fuller. It’s important to highlight the full story and the activists working consciously towards universal suffrage. That’s exactly what Wiki Scholars in our course did when they improved the Wikipedia biography of activist Ida B. Wells.
Wells laid the groundwork for creating change and fostering attitudes of acceptance leading up to the amendment. She founded the Alpha Suffrage Club in Chicago in 1913. The group helped young black women, who were excluded from mainstream suffrage debates, engage politically in and for their communities. The club also played a role in electing city and state officials of color. The two Wiki Scholars worked together across their respective disciplines of expertise to make sure Wells is well-represented on Wikipedia. Now, her article boasts many new sections and sources, providing a more complete picture of her life, legacy, and impact within the suffrage movement.
Another Wiki Scholar in our NARA course expanded Wikipedia’s coverage of Native American civil rights, which remained restricted even after the passage of the 19th amendment.
Wiki Scholars also created previously non-existent Wikipedia biographies for lesser-known suffragists who made big impacts. Helen Hoy Greely, for example, was an accomplished activist whose career spanned over five decades. Etta Haynie Maddox fought for women to be able to take the bar exam and practice law in the state of Maryland; she was the first woman in Maryland to practice law. And Mary McHenry Keith was a lawyer and social justice advocate, whose life and career also weren’t represented on Wikipedia before the course.
Another Wiki Scholar poured their energy into a brand new article about the Prison Special, a train tour around the United States which drew attention to the stories of women who had been arrested, detained, or incarcerated as a result of participating in protests that promoted suffrage. The article was featured on Wikipedia’s main page on January 20th, and received 4,000 page views that day alone.
The collaborative experience of our course fosters personal and professional skills identified by the American Historical Association that historians with PhDs said they wished they had learned in grad school. Read all about how our NARA course will help you hone your abilities to collaborate, communicate your field to the public, improve your intellectual self-confidence, and more.
Interested in taking our course? Visit our landing page and sign up to receive updates about start dates. We’ll have another course this spring! To read about the personal experience of one Wiki Scholar, click here.
Today, the European Parliament voted 348–274 to pass a new copyright directive that includes problematic rules that will harm free knowledge. They did so after years of discussions, revisions, and more recently street protests. We believe that this is a disappointing outcome, the impacts of which will certainly be felt for years to come.
As Articles 15 and 17 (formerly 11 and 13) of the directive will take effect across the European Union (EU), we expect to see direct repercussions on all online activities. Article 15 will require certain news websites to purchase licenses for the content they display. As a result, many websites that helped people find and make sense of the news may choose not to offer this type of service, making it harder to find high-quality news items from trusted sources online. Article 17 will introduce a new liability regime across the EU, under which websites can be sued for copyright violations by their users. This will incentivize websites to filter all uploads and keep only “safe” copyrighted content on their sites, eroding essential exceptions and limitations to copyright by making platforms the judges of what is and isn’t infringement.
Still, there are elements to celebrate in the new directive. A new safeguard for the public domain will ensure that faithful reproductions of public domain works remain uncopyrighted, even as they are digitized. Museums, archives, and libraries will now be able to provide digital access to out-of-commerce works that have not yet fallen into the public domain. Research organizations and cultural heritage institutions will be able to engage in text and data mining on works they have lawful access to.
While we are disappointed, the fight is not over. The impact of the copyright directive will be determined by how lawmakers in each country choose to implement it. As the copyright directive is implemented into national law over the next two years, it presents an opportunity for Europeans to proactively engage with policymakers and ensure national copyright protects internet freedom and empowers everyone to participate in knowledge. Many countries will be opening up their copyright law for amendments for the first time in years. Now is the time to advocate for the good and try to mitigate the harmful parts of the new EU Copyright Directive, and Wikimedia is committed to this task.
Although Articles 15 and 17 remain in the directive, Wikimedians are already working to ensure that they are implemented safely and interpreted in the best possible light in national law, while also pushing for safeguards that benefit the public like freedom of panorama or user-generated content exceptions.
It is disappointing that, in the end, the majority of members of the European Parliament chose not to listen to the millions of voices in Europe concerned about the direction this directive has taken. We look forward to making sure that national lawmakers in the EU member states will understand how their actions in future national legislation will affect internet freedom. Stay tuned to our blog and our public policy portal for future updates and ways you can help.
Jan Gerlach, Senior Public Policy Manager, Legal
Allison Davenport, Technology Law and Policy Fellow, Legal
Wikimedia Foundation
Wikimedia Commons, the repository for educational media content that hosts most of the images used on Wikipedia, has announced its photo of the year.*
Nearly 3,500 people chose between 57 images in the final round of the competition. Jason Weingart’s Evolution—a composite timelapse showing the development and frightening expansion of a tornado—took the top prize.
Coming in second was David Gubler’s photo of a lonely bucket train in Chile, and in third was Daniela Rapava’s remarkable shot of a soap bubble being overcome by ice.
I got in touch with all three winners to learn more about the winning photographs.
• • •
Weingart created the picture of the year (above) from eight images he took while stormchasing in Dodge City, Kansas, United States, in May 2016. Of those, seven show the tornado itself, while the one on the far left demonstrates the storm’s structure.
Weingart, who lives near Austin, Texas, then used Photoshop to blend them together for the final presentation. “I wanted to be the first person to use timelapse photography to document tornadogenesis,” he says.
The high quality of the individual shots stemmed from Weingart’s choice to rig his camera to take one photograph for every second of video, which meant that he wasn’t stuck trying to cull individual frames from all his footage. (That video is available on YouTube.)
Weingart originally designed and uploaded it to Wikimedia Commons for the Wiki Science Competition, a contest designed to encourage the upload of scientific educational media for use on Wikipedia and elsewhere. “My intention was to inspire people to learn more about the weather,” he says.
Amusingly, however, far more people probably saw this shot after it was uploaded to Reddit and Facebook with the caption “[a] mass of tornadoes.” He has no idea who did this, and if we’re honest, it doesn’t seem likely that he ever will. However, it went so viral afterwards that it has its own dedicated page on Snopes, the famed fact-checking website. Their verdict was that the photo had been miscaptioned.
So what is Weingart’s takeaway from all this? “A great lesson for people … is to fact-check things before you click share.”
More of Weingart’s work can be found on his website.
• • •
Second place went to David Gubler’s lonely ore train, a freight movement that winds its way through Chile’s remote Atacama Desert once or at most twice per day and terminates at the Bolivian border. Finding the train was the easy part, as it runs at the same time every day. Actually getting this photo was a bit harder, as even though the train doesn’t move particularly quickly, he and a friend would drive to a good photography location, grab the shot, jump back in the car, leapfrog ahead of the train, and rinse and repeat.
Gubler thinks that his photo stood out to voters in the picture of the year competition because it “the combination of the colorful locomotives, red desert, snow-capped peak and blue sky is very appealing,” he says, and “the exotic scenery itself may have sparked interest, as I guess many voters are not very familiar with the Atacama Desert.”
You can find more of Gubler’s work over on Wikimedia Commons.
• • •
Finally, Daniela Rapava took third place in the picture of the year competition. A native of Slovakia, one of Rapava’s favorite subjects to photograph are frozen bubbles like this. She’s been doing it since 2014, and they remind her of the planets people are able to glimpse from Observatory Rimavska Sobota, where she took this particular shot.
The bubble is made from water, detergent, and sugar, making it just robust enough to remain intact even while outdoors. It took about seven minutes to frost over in the below-freezing weather that day.
Rapava’s other work is available on her website.
Ed Erhart, Senior Editorial Associate, Communications
Wikimedia Foundation
*Photos of the year are selected from the preceding calendar year’s worth of new “featured” pictures, a marker of high quality that is awarded after a community vetting process. You can see all of the previous pictures of the year, going back to 2006, on Wikimedia Commons.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Problems
Changes later this week
Meetings
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
12/03/2019-18/03/2019
OpenStreetMap protest against Art 13 of the EU Copyright Directive 1 | © OpenStreetMap
type=route containing child relations should be preferred over superrelations.
associatedStreet in Germany.
boundary=aboriginal_lands for official reservations for aboriginal, indigenous or native peoples, he has published another post titled “Aboriginal areas are finally on the map!” as OSM’s major map style Carto is now displaying such areas.
lanes:both_ways= 1 and turn:both_ways = left.
| Where | What | When | Country |
|---|---|---|---|
| Greater Vancouver area | Metrotown mappy Hour | 2019-03-22 |
|
| Tokyo | ミャンマーに絵本と地図を届けよう~ミャンマーに届ける翻訳絵本作り&自由な世界地図作り~ | 2019-03-23 |
|
| Cork | Mapping Party @ UCC | 2019-03-23 |
|
| Bremen | Bremer Mappertreffen | 2019-03-25 |
|
| Joué-lès-Tours | Rencontre Mensuelle | 2019-03-25 |
|
| Graz | Stammtisch Graz | 2019-03-25 |
|
| Portmarnock | Erasmus+ EuYoutH_OSM Meeting | 2019-03-25-2019-03-29 |
|
| Zurich | Missing Maps Mapathon Zurich | 2019-03-27 |
|
| Montpellier | Réunion mensuelle | 2019-03-27 |
|
| Université libre de Bruxelles (ULB) | National Mapathon | 2019-03-27 |
|
| UCL Louvain-la-Neuve | National Mapathon | 2019-03-27 |
|
| KUL Leuven | National Mapathon | 2019-03-27 |
|
| UMONS Mons | National Mapathon | 2019-03-27 |
|
| Montrouge | rencontre locale des contributeurs de Montrouge et alentours | 2019-03-27 |
|
| Lübeck | Lübecker Mappertreffen | 2019-03-28 |
|
| VUB Brussel | National Mapathon | 2019-03-28 |
|
| Mannheim | Mannheimer Mapathons | 2019-03-28 |
|
| ULIEGE Liège | National Mapathon | 2019-03-28 |
|
| UNAMUR Namur | National Mapathon | 2019-03-28 |
|
| UGENT Gent | National Mapathon | 2019-03-28 |
|
| Düsseldorf | Stammtisch | 2019-03-29 |
|
| UCL Louvain-la-Neuve | National Mapathon | 2019-03-30 |
|
| ULIEGE Liège | National Mapathon | 2019-03-30 |
|
| Bochum | Mappt die Innenstadt – Mappingtag für Einsteiger*innen und Fortgeschrittene | 2019-03-31 |
|
| Stuttgart | Stuttgarter Stammtisch | 2019-04-03 |
|
| Bochum | Mappertreffen | 2019-04-04 |
|
| Nantes | Réunion mensuelle | 2019-04-04 |
|
| Dresden | Stammtisch Dresden | 2019-04-04 |
|
| La Riche | La Riche (37)#Ateliers d’initiation à OpenStreetMap | 2019-04-06 |
|
| Kyoto | お花見!オープンデータソン in 京都 | 2019-04-07 |
|
| Rennes | Réunion mensuelle | 2019-04-08 |
|
| Bordeaux | Réunion mensuelle | 2019-04-08 |
|
| Essen | Mappertreffen | 2019-04-08 |
|
| Taipei | OSM x Wikidata #3 | 2019-04-08 |
|
| Lyon | Rencontre mensuelle pour tous | 2019-04-09 |
|
| Munich | Münchner Stammtisch | 2019-04-09 |
|
| Salt Lake City | SLC Mappy Hour | 2019-04-09 |
|
| Viersen | OSM Stammtisch Viersen | 2019-04-09 |
|
| Cologne | Köln Stammtisch | 2019-04-10 |
|
| Montpellier | State of the Map France 2019 | 2019-06-14-2019-06-16 |
|
| Angra do Heroísmo | Erasmus+ EuYoutH_OSM Meeting | 2019-06-24-2019-06-29 |
|
| Minneapolis | State of the Map US 2019 | 2019-09-06-2019-09-08 |
|
| Edinburgh | FOSS4GUK 2019 | 2019-09-18-2019-09-21 |
|
| Heidelberg | Erasmus+ EuYoutH_OSM Meeting | 2019-09-18-2019-09-23 |
|
| Heidelberg | HOT Summit 2019 | 2019-09-19-2019-09-20 |
|
| Heidelberg | State of the Map 2019 (international conference) | 2019-09-21-2019-09-23 |
|
| Grand-Bassam | State of the Map Africa 2019 | 2019-11-22-2019-11-24 |
|
Note: If you like to see your event here, please put it into the calendar. Only data which is there, will appear in weeklyOSM. Please check your event in our public calendar preview and correct it, where appropriate.
This weeklyOSM was produced by Nakaner, Polyglot, Rogehm, SK53, Softgrow, SunCobalt, TheSwavu, YoViajo, derFred, kartonage, muramototomoya.
Subscriptions
| Feed | RSS | Last fetched | Next fetched after |
|---|---|---|---|
| Ø | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Ad Huikeshoven On Open Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| All The Modern Things - Article | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| All Things Linguistic | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Andy Mabbett, aka pigsonthewing | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Bawolff's rants | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Bina's blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Blue Rasberry | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Bookcrafting Guru | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| brionv | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Catching Flies | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Category:Wikimedia | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Clouds & Unicorns | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Cometstyles.com | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Comments for maudite codes | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Content Translation Update | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| cookies & code | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Data Hacks | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Design at Wikipedia | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| dialogicality | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Doing the needful | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Durova | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Ed's Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Einstein University | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Endami | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| English Wikisource | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Fae | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| FOSS – Small Town Tech | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Gap Finding Project | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Geni's Wikipedia Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://blog.anubite.co.uk/index.php/category/mediawiki/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://blog.us.glamwiki.org/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://jimbojw.com/wiki/index.php?title=Blog&action=feed&tags=mediawiki | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://logic10.tumblr.com/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://medicalfuturist.com/tag/wikipedia/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://midea.nmc.org/author/loribyrdphillips/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://saml.rilspace.org/taxonomy/term/69/0/feed | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://sleepyhead.org/tagged/wikipedia/rss | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://stryn.hol.es/blog/tag/wikimedia/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://thingelstad.com/tag/mediawiki/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://www.scrubnugget.com/categories/wikipedia/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://www.wikilove.in/feeds/posts/default | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://www.wikipediatrends.com/blog/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://www.wikisym.org/category/wikimedia/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://yaronkoren.com/blog/?feed=rss2 | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| http://yuvi.in/blog/category/wiki/feed/ | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| https://feeds.feedburner.com/enwikizine | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| https://theglamwikiexperience.blogspot.com/feeds/posts/default | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| in English – Wikimedia Suomi | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Infodisiac | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| International Wikitrekk | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Laura Hale, Wikinews reporter | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Leave it to the prose | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Localizando-me | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Luis Villa: Open Law and Strategy | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Make love, not traffic. | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Maria Codes | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| mariobehling.de - wiki | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Mark Rauterkus & Running Mates ponder current events | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Med BACHOUNDA محمد بشوندة | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| MediaWiki | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| mediawiki – Addshore | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| MediaWiki – BlueSpice Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| MediaWiki – Chris Koerner | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| MediaWiki – It rains like a saavi | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| MediaWiki – Ryan D Lane | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| MediaWiki and Wikimedia – etc. etc. | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| MediaWiki Testing | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Ministry of Wiki Affairs | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Musings of Majorly | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| My Outreachy 2017 @ Wikimedia Foundation | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| NonNotableNatterings | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Notes from the Bleeding Edge | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Nothing three | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Okinovo okýnko | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Open Codex | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Open Source Exile | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Open Source Research | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Original Research | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Outreachy Internship – Gueleu Farida | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Pablo Garuda | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Pau Giner | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| PediaPress Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Personal – The Moon on a Stick | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Planet Wikimedia – Entropy Wins | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Planet Wikimedia – OpenMeetings.org | Announcements | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| planetwikimedia – copyrighteous | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Political Bias on Wikipedia | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| project-green-smw | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Ramblings by Paolo on Web2.0, Wikipedia, Social Networking, Trust, Reputation, … | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Robin's Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Rock drum | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Score all the things | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Semantic MediaWiki – news | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Sentiments of a Dissident | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Stories by Megha Sharma on Medium | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Stories by Neha Jha on Medium | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Sue Gardner's Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Sumana Harihareswara - Cogito, Ergo Sumana | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Tech News weekly bulletin feed | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Technical & On-topic – Mike Baynton’s Mediawiki Dev Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Technology – Wikimedia Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| The Academic Wikipedian | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| The Ash Tree | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| The Lego Mirror - MediaWiki | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| The life of James R. | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| The speed of thought | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| The Whelming | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| the Wikimedia UK blog! | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| The Wikipedian | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| TheDJ writes | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| This Month in GLAM | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Thoughts For Deletion | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Timo Tijhof's Posts | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Ting's Wikimedia Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Vinitha's blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| weekly – semanario – hebdo – 週刊 – týdeník – Wochennotiz – 주간 | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| What is going on in Europe? | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wik-eh-pedia – No maps for these territories | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – Blog – Nick Jenkins | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – David Gerard | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – Gabriel Pollard | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – Hay Kranen | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wiki – notconfusing | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – Our new mind | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – stu.blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – The life on Wikipedia – A Wikignome's perspecive | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – Wiki Strategies | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki – Ziko's Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wiki Education | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wiki Loves Monuments | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wiki Northeast | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wiki Playtime - Medium | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wiki tools – Timo Tijhof | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wiki-en – [[content|comment]] | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikibooks News | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikidata – Wikimedia Deutschland Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – andré klapper's blog. | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – apergos' open musings | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – Bitterscotch | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia – DcK Area | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia – Guillaume Paumier | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – Harsh Kothari | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – Kevin Payravi: Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – millosh’s blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – Neverness | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia – Open and Free Source! | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – Open World | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – Software Research and the Industry | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia – The Woodwork | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikimedia – Thomas Dalton | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia – Tim Starling's blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia – Witty's Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia (en) – Random ruminations of a ruthless 'riter | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia Commons – Frank Schulenburg | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia DC Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia Foundation | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia India Blog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia Security Team | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia | ഗ്രന്ഥപ്പുര | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikimedia-en – lyzzy sucht das wunderland | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikinews Reports | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia & Linterweb | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia – Aharoni in Unicode | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikipedia – Andrew Gray | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia – Andy Mabbett, aka pigsonthewing | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia – Blossoming Soul | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia – Bold household | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikipedia – Going GNU | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia – mlog | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia – ragesoss | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikipedia – The Longest Now | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikipedia – Thoughtingal | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia – wllm | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia - nointrigue.com | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia Notes from User:Wwwwolf | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedia Weekly | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikipedian in Residence for Gender Equity at West Virginia University | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| WikiProject Oregon | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikisorcery | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Wikistaycation | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wikitech – domas mituzas | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| wmf – Entries in Life | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Words and what not | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| Writing Within the Rules | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| XD @ WP | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |
| {{Hatnote}} | XML | 17:37, Tuesday, 09 2019 April | 18:37, Tuesday, 09 2019 April |