The MediaWiki core feature to protect pages. Including:
Unassigning myself because this is ready for estimation as far as I'm concerned.
Right now we're using the hex equivalent of the depreciated color-base--subtle. We can use color-subtle for this (#A2A9B1).
It would look like this:
Tagging Trust and Safety Product Team as something we might want to look at (cc @Niharika @Madalina) at some point. Would also be useful to get Stewards' perspective on this (cc @Urbanecm).
Change #1069706 had a related patch set uploaded (by Wargo; author: Wargo):
[mediawiki/core@master] Allow (un)watch restricted pages
Simply allowing multiple, overlapping protections on a page would solve for this and other use cases.
Instead of semiprotection being restored after temporary full protection expires, ANY longer-term protection should be restored when ANY shorter-term protection expires. That way full protection could fall back to an already existing ECP or semi, or ECP protection could fall back to an already-existing semiprotection.
I'm about to leave WMF, and I wanted to leave a comment here summarizing the design spec for this desired functionality.
Note some data models do not support categories (such as items), so having categories on them, while potentially useful, may give users impression that Item pages can be categorized.
Cross ref: T368207: Remove entries from wgSemiprotectedRestrictionLevels for arwiki which shows some abnormality by having a builtin "semi-protect" concept where there are multiple protection levels.
The red edit box is an on-wiki customization for enwiki. This would need to be fixed on-wiki (hence not tracked on Phabricator), if anyone still cares a decade later.
Decline this since https://www.mediawiki.org/wiki/Manual:Administrators#Protection explicitly states MediaWiki namespace restriction will work in addition to protection.
"
Perhaps some superprotect or other more-than-sysop people can be imagined, but no case is known.
"
Change #995192 merged by jenkins-bot:
[mediawiki/skins/Vector@master] watchstar: use mw.util.isInfinity() instead of comparing to 'infinity'
going to investigate the feasibility of this at the WMF Hackathon in a few weeks
It appears that wd admins are not willing to issue indefinite (or even long) semi-protection even for "the most common items since many contributors in the projects are not autoconfirmed on Wikidata and will not be able to add new articles if needed".
(Per the list in Russian Wikipedia, in more than a thousand pages. A code-based solution would be better at protecting privacy at such a number of pages at large, and would make it easier to revert this action when the political situation in Russia/Belarus changes.)
@Ladsgroup is correct about this — this is already happening on an ad hoc basis in some cases where there may be concerns about editor safety for sensitive material.