Introducing global preferences across Wikimedia wikis

Translate this post

There are a lot of Wikimedia wikis. Wikipedia is the best-known of them all, but there’s also Commons, Wikiquote, Wikisource, Wiktionary, and more.

Also, each of these sites is available in multiple languages. Wikipedia, for example, has nearly 300 language editions. The newest launched just this week.

Until this month, each wiki and language version had individual preference settings. This caused some serious frustration for people who contribute to multiple wikis.

Want to set your timezone to your new vacation location? You had to update your preferences on all four wikis. Want to stop getting spammed by a harassing user? You had to visit every single wiki to block them so you don’t get constant notifications from them. Want to try out a new skin? Well, you had to go to every wiki to change its appearance.

Thankfully, this era has ended with the Community Tech team’s deployment of global preferences.


Global Preferences was a long-sought request from power users who used multiple wikis to do their work. It was officially filed as a request for the first time in July 2008, and was requested many times in the years after. The earliest known attempt to provide this feature was made by Andrew Garrett in April 2009, back when code reviews for MediaWiki used to happen on a local level. Garratt’s version was built into the CentralAuth extension, which seemed like a handy place because it was doing login unification across all wikis anyway. Unfortunately, it was quickly rolled back because there was no reasonable user interface for it.

Three years passed with more requests for this feature, but it wasn’t seriously considered again until an aspiring Google Summer of Code intern stumbled upon it in 2012. They started a conversation on a Wikimedia mailing list to see if this was still something people considered useful, to which Bináris replied with one of my favorite quotes: Would be the most useful thing since sliced bread!”. However, it quickly became apparent that this project was too much work for a newcomer to take on and thus, it was dropped again.

Almost nineteen months later, this project had the good fortune of being picked up by long-time Wikimedia developer Legoktm, who wrote the MediaWiki extension GlobalPreferences to provide a simple way to establish global preferences. They would live in their own table and local preferences would be overridden when a global preference value was present. Simple enough, right? Well, it was, until you started considering what the user interface should be like. Should there be only one preferences page with an additional checkbox for what should be global? Should there be a different special page on a central wiki to keep things simpler? Or maybe we should have one on every wiki? How would you design it in a way that’s easy to understand and use? These questions sparked several interesting conversations with lots of good ideas.

The earliest implementation of this feature looked something like this:

Or the more crazy…

As you can see, this didn’t look all that glamorous, especially as the number of options increased. The global preferences extension was still far from being complete. It needed significant refactoring for MediaWiki core’s preference handling for global preferences to be deployed on Wikimedia wikis. This was a prospect scary enough to give experienced editors cold feet.

Three more years passed. Finally, in late 2016 JAn Dudík proposed this project for the Community Wishlist Survey, an annual initiative where community members are invited to submit project proposals they deem useful and vote on them. Global preferences ranked #4 on the results list with 84 support votes, and therefore landed with the Community Tech team, whose mandate is to work on the top 10 projects from the Community Wishlist. Bright eyed and bushy tailed, the team started discussions about the project in earnest. Several different solutions were discussed before the team settled on using the GlobalPreferences extension, as it had several clear advantages over using something outside the Wikimedia projects. It made a Special page available on all wikis, eliminating the need for a central wiki that users would need to navigate to, and it worked out of the box when new wikis or preferences were added.

One clear need that came up during the discussions was allowing users to set local overrides on a per-wiki basis. For example, a user who speaks English and Russian fluently might prefer their default language to be English on every wiki except on the Russian Wikipedia, where they would rather see Russian. After putting out a call for feedback from the community, there was an overwhelming response in favor of local overrides for all preferences.

In absence of a designer on the team, the-then product manager for the project Danny Horn decided to take matters into his own hands for fixing the design issues that had been blocking this project for years. The checkboxes for enabling a preference to be global were aligned in one column, on the left. A ‘Select all’ button was added on top to allow making all preferences on the page global. This made the UI for Special:GlobalPreferences almost identical to the UI for Special:Preferences, except for the addition of the extra column of checkboxes.

The leading checkboxes enable the preference as global. So in this screenshot, if the first checkbox for ‘Hide minor edits from recent changes’ is checked, it makes the value of the second checkbox (checked or unchecked) for that preference as its global value. After having multiple discussions with people who were interested in the project, the design was largely approved to be worked on.

The way we implemented local per-wiki overrides is by giving the users checkboxes underneath globally set preferences on Special:Preferences. This serves a dual purpose:

  1. It makes it immediately clear to the user that a preference is global (versus those which aren’t)
  2. It allows the user to set local exceptions, if they want.

The bulk of the engineering work on the project was undertaken by the then newest engineer on the Community Tech team, Sam Wilson. A major chunk of the work on the project, especially the scary refactoring for MediaWiki core, was later done by Community Tech’s Max Semenik.

In early February 2018, the extension was enabled on the beta cluster for our users to test and provide feedback. After five months and multiple deployment hurdles, it was finally enabled on all Wikimedia wikis on 9 July 2018. You can now go to Special:GlobalPreferences on the wiki of your choice and set your preferences once and for all on all Wikimedia wikis. You can also go to Special:Preferences on any wiki to set local exceptions for any preference for that wiki.

Thirteen hearts, ten thumbs-up, two mountains of wealth, a doubloon, a confetti, a goat token, and ten years later, we did it. This is one of the longest and most impactful projects the Community Tech team has ever undertaken. We have a lot of people to thank, without whom this project wouldn’t ever have been complete—especially the community who voted this project up in the survey and helped us make it come to life with their feedback and suggestions as the project developed.

And finally, as with every project, this too has lots of scope for improvement. Global preferences should be the default preference experience for new users, as with other similar websites. There’s also scope for design improvements. We’re hopeful that this feature will continue to evolve and improve with the help of our communities.

Niharika Kohli, Product Manager, Contributors
Wikimedia Foundation

Archive notice: This is an archived post from the News section on, which operates under different editorial and content guidelines than Diff.

Can you help us translate this article?

In order for this article to reach as many people as possible we would like your help. Can you translate this article to get the message out?