Assuming this is no longer an issue per last comment.

https://github.com/supertassu/MajavahBot/commit/9f5341f330602d2379405bf052df68f58bfb75b1

In T268317#6636302, @Akmaie_Ajam wrote:

Hi, I already started a proposal to replace FlaggedRevs with the pending changes protection and extended confirmed protection here: https://id.wikipedia.org/wiki/Wikipedia:Permohonan_pendapat/Pencabutan_validasi_artikel_(proposal_2020)

Thanks. We can move forward once there is consensus for specific changes to be made.

That's https://meta.wikimedia.beta.wmflabs.org/wiki/Special:AbuseFilter/63

In T267035#6597685, @matmarex wrote:

See beta logstash: https://logstash-beta.wmflabs.org/goto/b2d5d6dba1a2543e737a94ccd8df9c50

What do I need to do to view this?

Oops, sorry! Should be fixed by attached patch.

Added to Tech/News in https://meta.wikimedia.org/w/index.php?title=Tech%2FNews%2F2020%2F45&type=revision&diff=20593649&oldid=20593311

Should be fixed in c706f68, can you confirm next time there is an unlock/unblock request? Thanks!

What would be the best way to detect those? Something like 'unblock' in section_title and '/unblock' not in section title?

@tvtonightokc: Please do not assign tasks to people unless they have agreed to it beforehand, see https://mediawiki.org/wiki/Bug_management/Phabricator_etiquette. Thanks!

@Esanders: for the future, could you use https://phab.wmflabs.org/ for testing Phabricator? Thanks!

@FAR: You can use Edit Related Tasks... → Close as Duplicate

I still believe we don't use those events. Is github saying "you are definitely using these events" or "you might be using those"?

@hashar see T261294 T264138

Account disabled. If you reverted the changes I believe there is nothing left, closing.

In T255507#6496186, @DannyS712 wrote:

@Majavah can you please rebase your patch to fix the merge conflicts, and ensure the tests pass? This is one of the remaining uses of $wgUser in core

see also T257968: Certificate for *.beta.wmflabs.org has expired

It looks like the replication has catched up:

possible duplicate of T262691

Hi @Cyberpower678, where did you request the flag? I don't see anything on the Wikipedia:Botit/hakemukset page.

Confirmed, marking as a security bug just in case. I tested this and it can't be used to overwrite existing files but it can be used to create files that have been protected from being created.

What should the talk namespace be named?

In T261133#6443911, @Darwinius wrote:

In T261133#6443906, @Majavah wrote:

[...]

No, it does not. I just tested (again), and nothing of that sort appears. Not in the wikipedia app, not on desktop mode, and not in the mobile mode (which I just tested again 1 minute ago, just to be sure).

In T261133#6443878, @Darwinius wrote:

Another very alarming, dangerous and worrisome thing: Anyone editing unregistered at wiki.pt both through the Wikipedia app, and through Visual Editor (mobile or desktop) is not aware in the least that they are revealing their IP to the world. There is no warning, no information, nothing. The person simply saves the edition, and their IP gets revealed without any kind of warning nor consent. You can imagine the kind of (even possibly fatal) danger this kind of thing represent, even to registered editors who log out by accident and do not realize they are logged out when they edit? There have already been documented cases of people persecuted in their workplace and menaced with judicial process for doing controversial editions unregistered at wiki.pt. It's not even theoretic anymore.

That page does seem to exist according to wikireplicas:

MariaDB [frwiktionary_p]> select * from page where page_title = 'avk:espanafamik' limit 1;
+---------+----------------+-----------------+-------------------+------------------+-------------+----------------+----------------+--------------------+-------------+----------+--------------------+-----------+
| page_id | page_namespace | page_title      | page_restrictions | page_is_redirect | page_is_new | page_random    | page_touched   | page_links_updated | page_latest | page_len | page_content_model | page_lang |
+---------+----------------+-----------------+-------------------+------------------+-------------+----------------+----------------+--------------------+-------------+----------+--------------------+-----------+
| 3950044 |              0 | avk:espanafamik |                   |                0 |           0 | 0.506491162847 | 20200829144159 | 20200708044957     |    27077959 |      217 | wikitext           | NULL      |
+---------+----------------+-----------------+-------------------+------------------+-------------+----------------+----------------+--------------------+-------------+----------+--------------------+-----------+
1 row in set (9.73 sec)

Would it be possible to add a setting to allow enabling/disabling this feature per user?

The app does not use the events that are being removed so I believe those deprecations do not affect this app. Sorry for any e-mail spam caused, I have no idea why these notifications were sent.

There was a missing closing div tag which I fixed. It looks to be working now.

Now that this is technically possible to configure, should it be done as a default on all Thanks installations or on WMF config only?

No worries, for the future see https://www.mediawiki.org/wiki/Gerrit/Commit_message_guidelines

The bot didn't post because there was a line ending between Bug: and Change-Id:. I fixed that.

Hi! Wikimedia Phabricator is only for reporting issues in the wiki software MediaWiki, not for reporting about content issues. You can be bold and correct the error yourself (there is an edit button on top of all pages) or post on that article's talk page and wait for someone else to fix the problem.

The extension was disabled, leaving this task open so the cause of this bug can be fixed

I also got one last night.