home.social

#toolforge — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #toolforge, aggregated by home.social.

  1. I migrated the Wikidata Lexeme Forms tool to OAuth 2 (gitlab.wikimedia.org/toolforge + gitlab.wikimedia.org/toolforge) – please log in again, and let me know if you encounter any problems! :blobfoxnerd:

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

    #Toolforge

  2. 🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: mediawiki.org/wiki/Special:MyL

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

  3. 🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: mediawiki.org/wiki/Special:MyL

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

  4. 🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: mediawiki.org/wiki/Special:MyL

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

  5. 🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: mediawiki.org/wiki/Special:MyL

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

  6. 🗳️📊 The results from the 2026 Wikimedia developer satisfaction survey are now available at: mediawiki.org/wiki/Special:MyL

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

  7. Does anyone know if #toolforge has a local mount (/public/) for the monthly pageview files? These ones:
    dumps.wikimedia.org/other/page

  8. 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 ?

  9. unfinished thought: it would be quite good to have something like the Toolforge Abandoned Tool policy (wikitech.wikimedia.org/wiki/He) 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, antonin.delpeuch.eu/posts/off-) – if a codebase opts into it (README.md?), there would be an established process for adopting it if the maintainer goes inactive

    #Wikimedia #Toolforge

  10. 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: chem-bla-ics.linkedchemistry.i

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

    We put a banner on the #toolforge instance

    #openscience #wikidata #sparql #scholia

  11. 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!)

    quickcategories.toolforge.org/
    meta.wikimedia.org/wiki/QuickC

    #Wikimedia #Toolforge #QuickCategories

  12. if you used cookiecutter-toolforge to create a :toolforge: tool in the last year, please apply the following accessibility fix that I accidentally introduced with the Bootstrap 5 migration: github.com/lucaswerkmeister/co

    #Toolforge

  13. It's hailing this morning in #Perth, and I'm snug inside attempting to clean up some of the WA BMD #genealogy tool, after migrating it to #Toolforge.

    wabmd.toolforge.org/

  14. Anyone having #toolforge problems as well? DB and container affected for me.

  15. I have switched PetScan to use the new @wikidata term store DB. There *should* be no side effects as it is still the same DB for the moment, but please let me know if something funny happens there.
    #toolforge

  16. Celebration! The #wmhack25 was the occasion to onboard User:Arcstur as a maintainer of #EditGroups! I'm super grateful for him for already helping out with a big cleanup of the deployment process :)

    #Wikidata #toolforge #wikitech

  17. Celebration! The #wmhack25 was the occasion to onboard User:Arcstur as a maintainer of #EditGroups! I'm super grateful for him for already helping out with a big cleanup of the deployment process :)

    #Wikidata #toolforge #wikitech

  18. Celebration! The #wmhack25 was the occasion to onboard User:Arcstur as a maintainer of #EditGroups! I'm super grateful for him for already helping out with a big cleanup of the deployment process :)

    #Wikidata #toolforge #wikitech

  19. Celebration! The #wmhack25 was the occasion to onboard User:Arcstur as a maintainer of #EditGroups! I'm super grateful for him for already helping out with a big cleanup of the deployment process :)

    #Wikidata #toolforge #wikitech

  20. Celebration! The #wmhack25 was the occasion to onboard User:Arcstur as a maintainer of #EditGroups! I'm super grateful for him for already helping out with a big cleanup of the deployment process :)

    #Wikidata #toolforge #wikitech

  21. The upcoming Wikimedia database changes this year will affect many of my tools. Some will "just" be SQL rewrites, but everything concering `wbt_` will need a complete, conceptual rewrite of the affected sections.

    First estimate is at least 12 Rust-based tools, and likely dozens of PHP ones.

    I am once again asking for your support, both in patience and in issue reports.

    lists.wikimedia.org/hyperkitty

    @wikidata #toolforge

  22. Is #toolforge having a DNS issue?

    ```
    Input/output error: failed to lookup address information: Temporary failure in name resolution
    ```

  23. At 10am ET, I'll be speaking about "10 years of Toolforge" at WikiConference North America!

    wikiconference.org/wiki/Submis

    It'll be streamed at room3.wcna.wiki/ (and recorded too)!

    #Toolforge #WikiConfNA

  24. How on earth do I get a shell with php on #toolforge these days?

    `webservice shell` appears to have stopped working.

    There is something about raw k8s jobs but there must be a more user-frieldnly way, surely...

    wikitech.wikimedia.org/wiki/He

  25. toolforge_i18n 0.1.0 is out! This is the first version that doesn’t say “please don’t use this yet :)” :D

    It’s not perfect yet, but I don’t have anything specific left to improve – I think I just need feedback from others. So if you have (or are going to create) a Toolforge tool written in Python that you want to make translatable – especially if it uses Flask – consider trying out the library, and let me know if there are any problems: pypi.org/project/toolforge-i18

    #Toolforge #i18n #Python #Flask

  26. I am running an updated version of PetScan right now, please ping me with any anomalies
    #toolforge

  27. What are the plans around #redis usage in the #wikitech #toolforge, especially after the license change? Will we switch to a fork? Also, does it actually make sense to have a redis instance shared between many tools, when redis provides (AFAICT) no user isolation at all, meaning that the tools can overwrite each other's data (on top of potentially competing for resources like connections or memory)? The docs encourage prefixing keys, but it can't be enforced, right? wikitech.wikimedia.org/wiki/He

  28. If you do batch editing on #wikidata or #wikicommons, beware that the batch undo functionality of #editgroups is currently broken and it's not clear when it can be restored. Details here: wikidata.org/wiki/Wikidata_tal? #redis #toolforge

  29. If you do batch editing on #wikidata or #wikicommons, beware that the batch undo functionality of #editgroups is currently broken and it's not clear when it can be restored. Details here: wikidata.org/wiki/Wikidata_tal? #redis #toolforge

  30. If you do batch editing on #wikidata or #wikicommons, beware that the batch undo functionality of #editgroups is currently broken and it's not clear when it can be restored. Details here: wikidata.org/wiki/Wikidata_tal? #redis #toolforge

  31. If you do batch editing on #wikidata or #wikicommons, beware that the batch undo functionality of #editgroups is currently broken and it's not clear when it can be restored. Details here: wikidata.org/wiki/Wikidata_tal? #redis #toolforge

  32. If you do batch editing on #wikidata or #wikicommons, beware that the batch undo functionality of #editgroups is currently broken and it's not clear when it can be restored. Details here: wikidata.org/wiki/Wikidata_tal? #redis #toolforge