I have closed an English Wikipedia RfC (permalink) finding consensus to apply signature validation to existing signatures ($wgSignatureValidation = 'disallow';), provided affected users are notified a month in advance.

All regularly scheduled tasks have been migrated to Kubernetes.

Ah; sorry. Thank you!

From Wikipedia talk:Requests for comment/Rollback of Vector 2022 § Proposal for next steps following the closure of the Vector 2022 RfC § April 6th Response:

The modal should have extremely neutral wording, such as "Wide width / Narrow width" instead of "Unlimited width / Existing width" ("existing" is biased). And "Select wide width / Select narrow width" instead of "Revert to unlimited text width / Keep existing width" ("revert" and "existing" are biased). Then this unbiased data can be used to figure out what width readers prefer. Hope this helps. –Novem Linguae (talk) 22:56, 6 April 2023 (UTC)

Thanks, @Aklapper! I added separator characters, which correctly formatted the text description on my end, but apparently this is inconsistent even between browsers/OSs/etc. (effectively the same problem as this task, but on a different scale; haha). Here's what my description was supposed to look like:

Thanks for letting me know about this. I'll take a look and migrate it over when I can.

In T300560#7906988, @Esanders wrote:

If implemented as a ButtonGroupWidget it would look something like this:

I can try to do this — I've got a fix mostly working (using pywikibot.data.api.PropertyGenerator and yielding pywikibot.Categorys, with preloadpages if content) already.

This appears to be resolved now (possibly by T293665).

Thanks, @WMDE-Fisch! This looks like it should work correctly now.

That's disappointing. I tried to email their support address, but the email bounced (apparently it's a Google Group that doesn't accept emails). I suppose this will have to be reverted.

In T299247#7623124, @4nn1l2 wrote:

I'll do it. But please provide an example of a suitable file on PeerJ. Thanks.

I've just changed the JS config file and the XML to point to the new title.

I've seen this happening too; it was previously fine.

I think that this could be solved by having some syntax to prevent page previews from removing content in parentheses. For example, perhaps some usage of nowiki or HTML character codes for parentheses, as I tried unsuccessfully. Please correct me if I'm wrong.

(I was the one at the Village Pump.) It looks like the renames didn't entirely work — has this happened with other users?

@Aklapper: I think they're at least related. In T293707, it's only in the page history, but not in diffs, and with a locally created page (a soft redirect). Here, it's in diffs, and it's with a global user page, not one that's locally created.

@Legoktm, thanks for taking care of this!

I'm pretty sure this is new; at least, I hadn't noticed this before. And it's gigantic; I would have noticed it.

Enwiki, wikidata, and meta are all loading normally for me now (frontend & API).

From T291312, some other errors I have experienced:

• upstream connect error or disconnect/reset before headers. reset reason: connection failure
• upstream connect error or disconnect/reset before headers. reset reason: overflow
• upstream request timeout

Per mw:Topic:Wfpiphhllpj4ogy8, it works if "(UTC)" is added to the string passed to it.

For me, this can be fixed by adding:

/* jshint maxerr:10000 */

(or with any other number large enough) to the top of the file in question.

This appears to still be happening at English Wikipedia (w:en:User:Tol/Sparkle.js).