Let's drop the word "repeated". A user will be reporting a single comment, and it should suffice if they don't check whether the insult they see is one of many or not.

Because this is more of a catch-all, the link for "official policy" may be https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Universal_Code_of_Conduct#3_%E2%80%93_Unacceptable_behaviour (the h2).

What exactly the Russian labels will be to click on to activate that temporary-account-viewer (TAV) rights? and on what tab in Preferences?

For languages that have declension, replacing "24 hours" with $2 doesn't work. The number needs to be separated out from the noun, so "$2 hours". We need to change it on https://translatewiki.net/wiki/MediaWiki:Acct_creation_throttle_hit

Oh, I see that my message caused confusion about a feature I wasn't aware of. My apologies! The engineers are saying that they have converted all LQT pages, and they only need to set LQT to "frozen" (disabled), which is the last step. They will most likely do it next week. That was enough for me to believe that nothing is blocking the deployment of temp accounts scheduled for Nov 12.

(Adding this comment for documentation purposes)

Thanks, Superpes15! Now I wonder what we should do with the onboarding dialog. People will only have one chance to see it (the very moment they open recent changes for the first time after deployment, I believe), so they shouldn't be seeing the English version. If the only solution is to manually create local messages and if doing that would be a tad too time-consuming, then we should deploy next week.

Thank you for your recent edits on translatewiki! At first I thought it would be straightforward to make temporary copies on itwiki, but given the number of messages that, until just earlier today, were missing, I think it'd be better to postpone the deployment until the translations arrive. Fortunately, itwiki is in group1, so Wednesday. The only question is - will all these translations arrive this or next Wednesday?

As some of you may have seen on the annual plan Meta page, we have been integrating our infrastructure with hCaptcha; it's currently live on test2wiki, and we will post more announcements on wikis as well as on Diff in the coming days.

Hey, yeah, I admit, maybe I didn't think this through. I've restored the previous version.

Nope, and thanks for pinging me here; I'm marking it as resolved!

Hey @Nux, thanks for the comment! We are indeed working to improve our captchas (T250227). We believe the new system will address a number of security, accessibility, and compliance issues. Right now, we are preparing a trial, a project page, and the related announcements. I will get back to you within 2–3 weeks. Thanks!

All is good, we may proceed!

In T375086#10934693, @NicoScribe wrote:

Now that there is only one access level, why keep two rights, ipinfo and ipinfo-view-full?

I swear I wrote a pretty long and detailed answer to the same question somewhere, but don't remember where...

The part about the user page is done: https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Anti-abuse_signals/User_Info

Sure, as the link to the project page, I'd suggest https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Anti-abuse_signals/User_Info

This work is done, T395134 is the continuation.

In T380221#10871082, @NicoScribe wrote:

I will be embarrassed if I open a new task and my questions are stupid.