In T411355#11432445, @PatchDemoBot wrote:

Test wiki created on Patch demo by ItamarWMDE using patch(es) linked to this task:
https://e70b5ea7b9.catalyst.wmcloud.org/w/

After some digging around I got these findings so far:

It seems as though that the status message key for locally blocked users and ips is the same message key, however, the message params are different. Perhaps we could differentiate using these somehow (though it feels completely wrong to do so)

Great, thank you for looking into it! Yeah, ESLint seems like the obvious choice.

Thank you everyone!

The scripts being discussed are not the PHP maintenance scripts, but the bash scripts currently invoked by airflow:

Notebooks are at: https://gitlab.wikimedia.org/repos/wmde/wikibase-reuse/wikidata-dump-subsetting/-/tree/main?ref_type=heads

I ran some presto queries on the full dump in the analytics cluster, here are the actual entity counts as of 2025-07-28:

Running a preliminary proof of concept on a dataset of about 500,000 entities, reveals that <~0.02 % are actually being excluded by this condition (471524 out of 471591 are not instances of scholarly articles or astronomical objects). Should we consider checking for instances of transitive subclasses as well (direct subclasses of Q13442814 or Q6999 as well as subclasses of those subclasses). The following SPARQL Query reveals that there are 1577 of those: https://w.wiki/F2fy.

Hi @S8321414 I'm sorry but I'm not in the Wikidata team anymore. please feel free to reach out to @karapayneWMDE or @Lydia_Pintscher for tasks that require integrating new languages in Wikidata. Wishing you all the best.

Hi @Unite_together! Thank you for your interest in expanding the Wikibase REST API to include WikibaseLexeme. As a general note, the Wikibase REST API follows an architectural pattern called “Hexagonal Architecture”. You can read more about it and how we follow it in the following links:

eep, this seemed to have fudged up sitelinks and api testing for me.

From my (still) very limited understanding, and from tracking down some code paths emanating from WikibaseCirrusSearch's buildEntitySearchQuery any search term santization (especially with regards to reserved chars) is either irrelevant - due to the fact that the used query builders rely on match and it's variants, and none seem to be using the "scary" query_string builder - or appears to be handled in various ways in CirrusSearch (which is where they probably should be handled any way).