Ok, i have create a ticket for update PrivatePageProtection : https://www.mediawiki.org/wiki/Topic:Vtgzx8f5r8dy2ehr
If you can look for help, this is a good extension.

Hi,
For [[Extension:PrivatePageProtection]]
If you can help ?

If i look the maintenance script :

I presume you're only exporting the current revision, not the whole history

I updated to 1.33.3 but, for information, now my _text table is 270 MB.

I cloned and closed this research on my side, after having verified what I discovered.

Concerning the volume of the _text table the problem seems fixed, or, attenuated and not visible at the moment, following a total reinstallation of version 1.33.1 but it forced me to reinstall everything and re-import everything.

I continue to share my experience with Mediawiki, because, it is not impossible that a funny bug can exist anyway.

It seems after research in my table that I would rather have a problem of collation on my tables and that I actually had to, wanting to modify the collation. I found this in the _logging table which no longer traces the name of the users who connect or who create pages, for about a month, during my experiments on table collation, when I modified the snacks of other tables, for joomla, or, for gitea.

In fact, I have a doubt, I still think I made an automatic conversion to utf8mb4_unicode_ci.
I used this script: https://github.com/ZerooCool/charset-utf8mb4-collation-utf8mb4_unicode_ci-mysql-mariadb/blob/master/utf8-utf8mb4.sh

No, the commande OPTIMIZE change nothing.

This is actually a request for assistance, but, that does not mean that there is not a problem in the code base, otherwise, why the maintenance script would have no effect on the weight of the code. the _text table?

OK thank you for your answer.
In this regard, I completed the thread, since the link mediawiki extension.

I understand that this extension is likely to fall by the wayside. I do not have any technical advice to give, although I have been able to use the extension successfully.

With my repo local, i have make the update, but, i have the good version, i mean.
/opt/lampp/bin/php /opt/lampp/htdocs/wiki/maintenance/update.php

I did not specifically update the schema, but, I made the updates by filing a folder with a new version of Mediawiki, which recognizes then that a database exists, and, then asks me to update it.

Strange. For me, it does not work directly for pages created since 1.28

No, i say, with mediawiki 1.28, DeletePageForGood work nice.

Install Mediawiki 1.28
Install DeletePageForGood
TOTALLY delete a page with DeletePageForGood. Work Good.

I test that, only for fun, if i can found the good way.

But this is ok as the ip is the value

If I understand correctly, it's the mediawiki 1.30 documentation that talks about ['ip']

If I understand correctly, it's the mediawiki 1.30 documentation that talks about ['ip']

Yes, this link explain all step ( in french ) :
https://www.visionduweb.eu/wiki/index.php?title=Maintenance_et_securite_de_Mediawiki#Bloquer_les_robots_spammeurs_avec_wgProxyList

I add this comment : https://phabricator.wikimedia.org/T113883

Reproduce the bug - (proposal)
Install Mediawiki 1.28.0
Install DeleteForGood.
Create mediawiki pages.