In T363581#9748213, @daniel wrote:

How will this be kept in sync with tables.json in MW core and extensions? Would it be possible to periodically scan for disrepancies?

Someone on enwiki suggested making interwiki prefixes case-sensitive and having "mos": point to the project while "MOS:" is a pseudo-namespace. This isn't how either concept currently works, and will probably break things elsewhere

Note: since search box will try case-insensitive matches, users can type mos:var in lowercase and be redirected to the correct manual of style page. Such workflow will break.

Oh, I found the specific cause and thus updated the title. This is still a valid task; see task linked for why I want to search them.

In T363538#9747520, @Peachey88 wrote:

Convert the MOS: enwiki pseudo-namespace to a real namespace (which overrides interwikis)

Regardless this should happen, fake namespaces just causes issues.

List of pages that will be affected:

Note: Chinese Wikipedia also has such pseudo-namespace.

MediaWiki users get less bogged down with Wikimedia-specific detail.

The current available way to create venv:

• webservice python3.11 shell to create a "build shell"
• inside the new shell, run python -m venv venv
• the venv can now be used outside the "build shell"

See https://www.mediawiki.org/wiki/Autoblock#Tracking

This is not a software issue.

If this is reported by the blocked user, this may be because of cookie block, and will gone if browser cookie is cleared.

As a reference:

Note: currently accounts can not be directly created in loginwiki. https://login.wikimedia.org/wiki/Special:CreateAccount

Note there are several kinds of perceptual hashes and before we do any actual development we need to first compare the effectiveness and performance of different kinds of hashes.

MathCaptcha no longer exists.

Note: Edit recovery feature supports recovering edits for anonymous and temporary users, if the feature is enabled by default (however it is currently disabled by default in Wikimedia wikis). So you need also to check whether edit recovery is enabled by default.

In T137291#9708587, @Bawolff wrote:

Clearly this is no longer going to happen.