I migrated the Wikidata Lexeme Forms tool to OAuth 2 (https://gitlab.wikimedia.org/toolforge-repos/lexeme-forms/-/commit/80583945a8 + https://gitlab.wikimedia.org/toolforge-repos/lexeme-forms/-/commit/43b18b8299) – please log in again, and let me know if you encounter any problems! 

And before I go and apply the same code to my other OAuth tools, as well as cookiecutter-toolforge (https://github.com/lucaswerkmeister/cookiecutter-toolforge) – if anyone wants to have a look at the code and make suggestions for how it could be improved, I’m all ears 

#Toolforge

Migrate to OAuth 2 (80583945) · Commits · toolforge-repos / lexeme-forms · GitLab

OAuth 2 is generally recommended these days [1] and has better rate limiting behavior [2] (Toolforge is currently exempted from the rate limits but I don’t know if that will...

GitLab

🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: https://www.mediawiki.org/wiki/Special:MyLanguage/Developer_Satisfaction_Survey/2026

This year, 207 respondents from the Wikimedia developer community answered questions about:
 #Wikimedia #Toolforge and Cloud VPS
 #MediaWiki code quality
🔌 Wikimedia API use
📜 #Documentation
🔬 Research
🛠️ Developer tools and processes

Does anyone know if #toolforge has a local mount (/public/) for the monthly pageview files? These ones:
https://dumps.wikimedia.org/other/pageview_complete/monthly/2026/2026-01/
Index of /other/pageview_complete/monthly/2026/2026-01/

I am seeing some requests to my tools (PHP-based APIs) take a long time to reply (20-40sec), when the reply should be ~1sec. Anything going on at #Toolforge ?

unfinished thought: it would be quite good to have something like the Toolforge Abandoned Tool policy (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Abandoned_tool_policy) for non-tool Wikimedia code, such as libraries (e.g. #m3api) or applications (e.g. Pattypan?)

this could be a step towards “Off-the-shelf governance models for small FOSS projects” (@pintoch, https://antonin.delpeuch.eu/posts/off-the-shelf-governance-models-for-small-foss-projects/) – if a codebase opts into it (README.md?), there would be an established process for adopting it if the maintainer goes inactive

#Wikimedia #Toolforge

Help:Toolforge/Abandoned tool policy - Wikitech

#Wikisource Export v.3.1.3 released today. If anyone notices anything weird, please let me know!

https://gitlab.wikimedia.org/toolforge-repos/wsexport/-/releases/3.1.3

#Wikimedia #toolforge

3.1.3 · toolforge-repos / wsexport · GitLab

Default to language 'mul' if none can be determined. T389911. Update repo URL in...

GitLab

yesterday evening work with @EvoMRI on the @wdscholia instance on Toolforge. We noted that our main instance only shows half of the results, only @wikidata 'main' part. The 'scholarly' articles part are no longer there. That day has been pending.

We seem very close. I wrote up a status 3 weeks ago: https://chem-bla-ics.linkedchemistry.info/2025/12/31/rescuing-scholia-2-getting-close.html

For this week, plz use https://qlever.scholia.wiki/

We put a banner on the #toolforge instance

#openscience #wikidata #sparql #scholia

Rescuing Scholia #2: getting closer

Three weeks ago, I wrote a the post Rescuing Scholia: will we make it in time?, where I sketched a future without Scholia. Scholia, started almost 10 years ago and I think it is worth keeping around longer.

chem-bla-ics

new QuickCategories feature! you can now use the tool to *create* pages if you want, e.g. to set up a category tree :)

(QuickCategories is a tool to batch-edit categories of pages, using a tabular input syntax similar to QuickStatements. it has already made over two million edits across Wikimedia wikis!)

https://quickcategories.toolforge.org/
https://meta.wikimedia.org/wiki/QuickCategories

#Wikimedia #Toolforge #QuickCategories

Some tools on #Toolforge not reachable for me: scholia.toolforge.org host unreachable for 185.15.56.11, but scholia.toolforge.org also 185.15.56.88 and reachable. Is it my DNS that is wrong?