In September 2025, Wikimedia Italia concluded the A/B testing between the latest stable version of OnlyOffice (already adopted) and the same for Collabora Online (proposed).

Yep @A_smart_kitten I agree with you that I wouldn't invest days of work in a partial solution that speeds up just 20 rules. I evaluated that speculation first because it was at first glance the easiest and safer.

In T108586#11417857, @Aklapper wrote:

In T108586#11414050, @valerio.bozzolan wrote:

I would be surprised to see a big number. I expect ~10 results, so no real benefit probably.

P.S. in phabricator.wikimedia.org - has it ever been necessary to manually disable Herald rules for de-activated ("disabled") users? Just to know whether to open another upstream feature request (yum).

In T108586#11259630, @A_smart_kitten wrote:

Noting that after asking upstream (https://we.phorge.it/Q207) about the possibility of Herald rules running asynchronously

In T410824#11398504, @Aklapper wrote:

Does this also happen using safe mode via https://en.wikipedia.org/w/index.php?title=Wikipedia:Sandbox&action=edit&safemode=1 ?

Sorry, fixed typos about Highlighting.

Passando da MediaWiki 1.25.2, ed effettuando l'avanzamento intermedio
obbligatorio a MediaWiki 1.35, ed arrivando a MediaWiki 1.44, ci
saranno davvero tante novità. Alcune intangibili, ma molto, molto
pratiche, fra cui **almeno 6 risoluzioni di sicurezza che ci
riguardano.

Since 1.35 is a mandatory step for people coming from 1.21, and since the possible pitfall "Main slot of revision not found in database" and the possible solution populateContentTables.php are not mentioned in the UPGRADE file;

I'm updating an ancient MediaWiki 1.21. The latest LTS forced me to first update to 1.35.

The owner of the domain does not reply our emails anymore.

I would say: go with both points (ticket + migration plan). Thanks Stefano.

Using shared resources (and shared CPUs) contabo can not guarantee any minimal performance.

I'm also very curious what WikiCite users think about this task and about the last comment.

Maybe we can title this task like "Reusing a reference should be easier and more efficient" - so to describe the problems, before proposing the solution.

(Ottimo per i test di aggiornamento 👍 grazie)

FYI @Ferdi2005

The wiki https://wiki.wikimedia.it has security issues - it would be lovely to plan a wiki upgrade (and wiki migration? away from old server intreccio ?). Thanks for comments and ideas and for your time <3

At the moment this task is in charge of nobody. Ideally we should activate our supplier "Nano Hosting" to take care of this.

Uh! thanks! this, isn't it? (Uhm I've received no notifications)

(Avevo disattivato quella spunta proprio perché non volevo ricevere alcuna email con tracciamenti invasivi)

Sembra veramente molto bello e promettente! Posso provare a ricevere una mail di prova? (boz at reyboz.it) Grazie mille 🙏

P.S. I'm the author of that GitHub issue (just as anti-scam verification lol)

I've unfortunately no answer to that question my friend.

Yeah I would say: just fork the GitLab repository, and push your commits in your fork, so a button should appear to propose a merge request 👍

Nice! If you have any screenshot, feel free to post so in your GitLab merge request 👍

I don't know if somebody could be so kind to share a link of the responsible
source code file, so to attract more eyes on it

In T279639#11121810, @Moebeus wrote:

Annual reminder, still here :)

Ehm I mean this

After 5 hours of troubleshooting. It was just this :D

In T390522#10956972, @Aklapper wrote:

@valerio.bozzolan: itWikiCon-2020 is an archived project tag. Please associate an active project tag so this open task can be found on a workboard - thanks!

Is there any particular technical reasons for picking PHP 8.3, instead of PHP 8.2 which is available in Debian stable, or PHP 8.4 which will be available in next Debian stable?

In T43498#11070387, @TheDJ wrote:

I think if people want to pick this up again, you first need to give a very good answer to the question: WHY and HOW would you use this, instead of using the information from CommonsData (which is clearly the preferred route) or from the wiki text itself (which is the traditional route and the one most of the community still see as 'canonical')

We can mark this as resolved 👍 I think Inmagik already closed GitHub since months. Thanks 👍

Thank you for tagging this task with good first task for Wikimedia newcomers!

Uhm. Let's flag as open. I've not done anything in 2 years here.

@GiovanniPen (who raised a metadata question from the chat): note that both patches were abandoned so this task risked the "wontfix".

We can try to improve the task to first explain the need, not the solution.

I've contacted c68 for a live demo of Nextcloud+Collabora. The invitees of this demo are board+staff at least.

(Also reported by Piergiovanna Grossi from mailing list "tech" 👍 - P.S. to access the mailing list archive, you must subscribe - https://mailman.wikimedia.it/private/tech/2025-July/001554.html )

Congratulations! (Just my curiosity: how long it took to upgrade the database? minutes? hours? Thanks)

OK. Piccolo memo di questo ↓ poiché quel video, prima della recessione del contratto, era accessibile, e onestamente se nessuno nel direttivo/staff ha ancora chiamato Ergonet per tentare un recupero dati, ho difficoltà a non accusare il direttivo e lo staff di sabotaggio.

Per esempio, qui avrei un'intervista a cui dovrei ri-accedere urgentemente (che ho condotto a Deborah De Angelis circa il 5 giugno - 3 settimane fa - per l'evento MERGE-it)

Gli utenti su Greenlight invece dovranno necessariamente registrarsi nuovamente sulla piattaforma (https://meeting.wikimedia.it/) e ricreare le stanze necessarie.

Dalla regia chiedono cosa è successo ai link in entrata ai vecchi video Moodle/BigBlueButton. Era stata prevista una migrazione di questi contenuti?

This week I'm not available. I activated this extra Zabbix item, kernel.openfiles.

Unclaiming this to avoid cookie-licking phenomenon. Sorry. Probably out of my perimeter.

In T395114#10913215, @Lorangeo wrote:

I think a task about the CPU spikes on the Phabricator host related to AI-bots would be better instead of talking here. In any case, a possible actionable thing is working on this promising patch, to greatly reduce the amount of links for scrapers:

If Diffusion is not worth exposing to the Internet because damn AI bots are causing operations burnout, a quick and dirty mitigation is to change the visibility policy of the Diffusion application from visible to Public to visible to All users.

P.S. I've added 2-3 DNS entries right now, again server error after 2 additions. I need to just add: lab, stock and en. I will retry later.

Lol do you have really wikimaxi.org? You are a genius @Lorangeo.

Whooops better than later, here the picture I've captured, now on Wikimedia Commons: https://commons.wikimedia.org/wiki/File:Lets_turn_Wikimedia_dark_-_Wikimedia_Hackathon_2024.jpg

So, I think this task can be closed loool since the author contributed here directly. This seems very promising thanks 👍

The user proposed a patch:

Notified to Association + Staff mailing list, right now

Forse con l'aiuto di @dario.crespi.wmit possiamo registrare Simona Cannataro a Phabricator, così che Emerald possa metterla in copia alle (poche) email email tecniche.

I've fixed some interwikis to adopt HTTPs. After that, I noticed that we already have the extension that allows sysops to update these URLs... this can be done from here:

Con l'aiuto di @Ysogo sarebbe molto utile pianificare un nuovo piccolo incontro tecnico, poiché Ferdinando durante il Wikimedia Hackathon 2025 ha notato che non è così semplice capire come tirare su il frontend

This can be considered as resolved. Let's continue upstream: