Before thinking to nuclearize the Etherpad (which, btw - WHY is made in this way :D lol)

Esattamente. L'opzione "alla Matomo" sarebbe ottimo.

I offer a doubloon to whoever wants to fix this.

Good idea. Thanks Stefano and Fabio <3

I've no time for this in the next months. Apologies.

Nel frattempo che ringrazio per le prossime risposte, ripristino descrizione e titolo e aggiungo nota di disambiguazione in cima. Scusate le notifiche.

Aggiungo a @Francesca_Lissoni_WMIT: non ho ben capito perché, qui sopra, nel 2024, dopo questo mio messaggio in cui chiedevo se si stesse parlando della disabilitazione del tracciamento https://phabricator.wikimedia.org/T351755#9857642 - ecco, mi chiedo perché nessuno abbia pensato di rispondermi di no. In serenità. Per esempio dicendomi che non era possibile / non era in lavorazione / non era voluto. Altrimenti stiamo parlando di due argomenti diversi.

@samuele.masetto (o a chi sa): ringraziando ancora per lo sviluppo - vi ringrazio se potrete rispondere alla domanda di prima: cioè se, senza fretta, posso chiedervi 1 esempio di 1 link, prima/dopo. Solo questo.

Ciao Samuele, grazie per il tuo punto di vista - che non conoscevo. Ripristino subito, premettendo che mi trovo in una situazione molto anomala, perché questo task è stato aperto nel 2023, esattamente 10 giorni dopo una mia segnalazione a WMIT sulle newsletter (vedere commento sopra dove spiego la cosa → https://phabricator.wikimedia.org/T351755#9857642). Da qui, credevo steste lavorando su questo.

Not our fault.

Access not working.

Sembra che il problema sia tornato. Ho ricevuto una newsletter titolata "Sondaggio su microgrant e sportello volontari di Wikimedia Italia" in cui tutti i link sono ancora offuscati da CiviCRM 🌈

P.S. this was still happening also in CiviCRM, for years, at least since 2023 to 2025, because our CiviCRM was configured to do the same aggressive tracking. Follow-up task:

Just to clarify: to do not scare the WMF meme department: when this task will be closed, this means everybody could still design a rickroll audio loop (if the meme department approves it), AND, changing preview will just do not loop it forever anymore 🌈

In T99759#11512444, @Aklapper wrote:

...on pages viewing such memes already embedded.

But the meme sound is still played though when in Comment Preview, a bunch of times on top of each other when scrolling.

Hi @NanoH: have you gained a nice Wikitech account? 👍 When you are ready, you can try to login here: https://wikitech.wikimedia.org/

I don't remember anything about this but ssh morfema.wikimedia.it still works. Thanks again NanoH! <3

P.S. in the mentioned Track discussion I see a WordPress developes suggesting this privacy-friendlier YouTube plugin, which adopts the "nocookie" domain:

Nice idea - maybe this edition we can adopt an Open Source tool (so I can also participate!)

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!