Change #1052350 merged by jenkins-bot:

[mediawiki/extensions/Babel@master] quickfix: make blocks readable in dark theme

https://gerrit.wikimedia.org/r/1052350

For the latter, probably needs T360494 for colors that are close to the existing ones.

I added a quick fix, as suggested by @Jdlrobson. But I think for the dark theme the colors need improvement.

Change #1052350 had a related patch set uploaded (by Iniquity; author: Iniquity):

[mediawiki/extensions/Babel@master] quickfix: make blocks readable in dark theme

https://gerrit.wikimedia.org/r/1052350

Adding notheme class to this element should make it readable.

Thinking more I think we can also consider possibility of allowing .ttf/.otf without any preview or use as a webfont as the first step, considering https://commons.wikimedia.org/wiki/Category:Noto_fonts it's already obvious what it can be useful for, archiving source fonts in addition to dumped glyph of each set and with the vision to reverse that and only keep the source font remove all the glyph dumps (or no longer uploading newer).

Change #1049489 merged by jenkins-bot:

[research/recommendation-api@master] Update repo docs to match LiftWing API GW docs

https://gerrit.wikimedia.org/r/1049489

Change #1049489 had a related patch set uploaded (by Kevin Bazira; author: Kevin Bazira):

[research/recommendation-api@master] Update repo docs to match LiftWing API GW docs

https://gerrit.wikimedia.org/r/1049489

Sorry for the repeated messages, hopefully this is the last of them for now.

Now the custom text logic seems to work more or less on the extension https://github.com/ebraminio/FontHandler which hopefully can show better what I'm suggesting here,

Thanks for digging this up @kevinbazira ! I glanced through and much of it was the Content Translation Extension (which Language is working on porting) or copies of configuration from that repo. I did leave a message around the beta-labs settings from CodeSearch because that felt like something that should be removed when appropriate (T365347#9910134) and could possibly be missed. The only piece I wasn't sure about was the uMatrix code. And then maybe some other random uses but they all seemed to be older, unmaintained repos. Feel free to reach out obviously where you feel useful but based on the searches you pulled together, I feel like we're in a pretty good place!

Here is a very very initial proof of concept of a MediaWiki extension I suggest,

Super! The deprecation message you prepared is thorough. It will help users transition smoothly.

here's the API Gateway documentation for the content translation recommendation API hosted on LiftWing: https://api.wikimedia.org/wiki/Lift_Wing_API/Reference/Get_content_translation_recommendation

:face-palm: I completely missed that. Thanks @kevinbazira ! For posterity, I used Global Search (query) to find user-script usages of the old API and either left a message or asked Amir S. to fix them (as he had been involved with their creation):

• https://es.wikipedia.org/wiki/MediaWiki_discusi%C3%B3n:Gadget-WikiProject.js#Nueva_recommendation_API
• https://ur.wikipedia.org/wiki/%D9%85%DB%8C%DA%88%DB%8C%D8%A7%D9%88%DB%8C%DA%A9%DB%8C:TourwikiRecommend.js
• https://sd.wikipedia.org/wiki/%D8%B0%D8%B1%D9%8A%D8%B9%D8%A7%D8%AA_%D9%88%DA%AA%D9%8A:TourwikiRecommend.js
• https://fa.wikipedia.org/wiki/%D9%85%D8%AF%DB%8C%D8%A7%D9%88%DB%8C%DA%A9%DB%8C:TofawikiRecommend.js

Yes @Isaac, here's the API Gateway documentation for the content translation recommendation API hosted on LiftWing:
https://api.wikimedia.org/wiki/Lift_Wing_API/Reference/Get_content_translation_recommendation

@kevinbazira will we have a page on the API Gateway to link to as documentation purposes (something like this)? I've been helping a few folks who are migrating user scripts and other uses of the old Cloud VPS endpoint to the new LiftWing one and it'd be nice to have a page showing the expected parameters etc.