(For the record: I don't do PAWS for a sensitive rights such as delete.py — especially that I was a steward at that moment I preferred doing almost everything on my device — but yeah can't repro now)

I believe I've moved everything I want.

I treat revibot, -i, -ii all to be same stuff so merging into one. Gotta attempt fix asap.

I'll probably need to copy and upload the current tc-rc version, but seems like fixing T320006: Migrate revibot from Toolforge GridEngine to Toolforge Kubernetes is more pressing for me, so hold on for some moment.

(Sorry for the long delay in response)

My circumstances (at present) do not allow me to do much non-mobile work (there's a long story but I do not wish to be logged perpetually in phab logs) so if it needs to be shut down, so be it, and if someone has spare time to do that, that's also fine.

Yeah, [8701d83f-51e1-4140-967e-42ade58b0294] 2022-09-29 08:38:44: Fatal exception of type "Wikimedia\Rdbms\DBQueryError" for trying to add oversight on testwiki. But since I can modify my rights for confirmed at metawiki, it seems it is about modifying cross-wiki user rights.

The problem with it is, as I said on the ML, when Wikimedia network is down, there is simply no way to send out the down notices, so it will be pretty useless for the purposes. So it has to be on other DC or hosted externally (ie. Some chapter).

(To be honest, I am very surprised that someone other than me was using the redirection, lol)

Was doing some cleanups for my now-defunct server (which was handling the redirect) and I forgot to do "publish" and went to bed.

See also T231937: Suppressing (or hiding) global accounts creates local blocks that can get out of sync.

Possibly related: T224341: Locked account can receive password reset email.

IIRC mostly because the lock+suppression does not propagate the hidden status by default, and S uses local gadget to propagate the suppression status. Gadget doesn't really care what happens after the lock, and it can't know if they are unlocked/un-hidden later.

Echoing Martin:

Week 5, year 2021 exists at 위키백과:질문방/2021년 제5주.

Note: The pages for Jan~Feb was created by someone @ Korean Wikipedia
Community, so I just created for the remainder of 2021.

All the 2020 items were created. The future (2022 onward) tasks which I am not sure.

about a month late, but creating march~december 2021 weekly pages.

Can you confirm this is about https://ca.wikimedia.org or somewhere else?

HTTPS is about HTTPS within Wikimedia sites. Removing.

@Sotiale was hit by this in zhwiki.

Account disabled.

From the description

However I'm concerned that something like this might be too ambitious for us at this time.

Deployed. (Thanks Martin)

hmm no, the syntax is {{YYYY}}년 제{{WW}}주, so it would become 2020년 제11주. so I guess the syntax is 'kowiki' => '위키백과:질문방/{{#time:o}}년 제{{#time:W}}주',.

This now requires 52 weekly pages, instead of 12 monthly pages, due to the community resolution at T254364: Change Korean Wikipedia archive model to weekly (Growth team not handling 254364 is blocking the actual move from the community, though.)

@kostajh is ^ sufficient or do you need something more?

Quite a few animals, train stations (specifically in Japan), cities in China (the mainland), and otherwise diverse topics. One "1946 (Year)" page.

Korean Wikipedia community has a requirement that any and all mentors must be eligible to run for an Request for Admin[1], due to not-enough-experienced editors offering bad answers to questions. I would expect anyone who can claim mentee to meet some higher-than-autoconfirmed criteria to claim mentee.

It might be that:

That is probably...

It might not be just password reset: I see insecure content warning on everywhere in wp-admin.php, but not on the actual blog.

From the task description

New format is 위키백과:질문방/YYYY년 제WW주. (when WW is below 10, there's no 0 preceding, so Week 9 is 제9주, not 제09주.)

In T254364#6280679, @revi wrote:

@MMiller_WMF: it's been decided by the time this was filed, waiting for WMF to change the logic.

@MMiller_WMF: it's been decided by the time this was filed, waiting for WMF to change the logic.

MacOS Mojave, FF 77.0.1 (stable), can reproduce.

Looks like abuselog also has this "collapse" thing. I want to ask for the same thing (no collapsing at all) - across the whole interface. Maybe give me some checkbox on prefs. I don't want to work-around all of the collapsible-boxes which continues to increase.

In T254649#6199347, @Beetstra wrote:

Should we not get rid of the word ‘spam’? It is a blocklist for external links, which are often, but certainly not only, spam

To simplify, I started single thread on VP, with a project summary at the top of the section (first subsection). I am sending out notifications to mentors via MassMessage in a short time.