The MediaWiki core feature to protect pages. Including:
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.
I highly doubt this would be enabled in enwiki. We are talking about is let's say Russian, Chinese, Arabic, Persian, and some other wikis with very sensitive material. it is already done in several articles in Russian Wikipedia: Here is article of Putin there https://ru.wikipedia.org/w/index.php?title=%D0%9F%D1%83%D1%82%D0%B8%D0%BD,_%D0%92%D0%BB%D0%B0%D0%B4%D0%B8%D0%BC%D0%B8%D1%80_%D0%92%D0%BB%D0%B0%D0%B4%D0%B8%D0%BC%D0%B8%D1%80%D0%BE%D0%B2%D0%B8%D1%87&action=history
Maybe I've misunderstood this task, but I can't think of a situation where this would be useful for *all* usernames: English Wikipedia oversighters can suppressdelete pages and that seems sufficient. If protection is needed in tandem with suppression, usually only the last couple of editors need their usernames to be suppressed. If all of the usernames are suppressed on a page, wouldn't that cause issues with attribution?
You are right. That seems to work for my needs.
This could probably be accomplished pretty easily with abuse filter(s), using page_restrictions_edit at mw:Extension:AbuseFilter/Rules format § Built-in variables. See enwiki's filter 942 for a working example; the filter could simply be imported and set to tag.
Thanks for clearing this up!
Mentioned in SAL (#wikimedia-operations) [2024-02-05T08:42:34Z] <zabe@deploy2002> Finished scap: Backport for [[gerrit:995232|specials: Remove null comments from formatter on Special:ProtectedPages (T356337)]], [[gerrit:995242|namespaceDupes: Reduce batchsize to 100 for link update]] (duration: 18m 18s)