Oct 10 2023
Just wanted to add an external voice to this task - we (at Weird Gloop) are observing "Math extension cannot connect to Restbase" on a regular basis on our hosted wikis (example link). $wgMathFullRestbaseURL hasn't been changed, so we're using Wikimedia's Restbase API for our rendering. We're considering running our own Restbase server if the instability seems to be related to WMF's infrastructure, but if there's a core issue with Restbase/the Math extension then this wouldn't do much for us. We'd also not really like to support Restbase going into the future, given that WMF is deprecating it.
Oct 2 2023
Now that Turnstile is generally available, I've pushed a patch that implements it into ConfirmEdit. The code for it is very similar to ReCaptchaNoCaptcha, but I felt uncomfortable with inheriting anything from ReCap's classes given that it does have a couple of (mostly server-side API) differences, and T324925 would do a better job at genericifying JS-based captcha implementations. I tested the code on MediaWiki 1.40 across account creation, source editing, and visual editing.
Jul 19 2023
Just adding my two cents here that as an external wiki farm, we'd also like to see user renaming support wiki farms properly, especially now that it is integrated into core. We use a fork of the Renameuser extension, but to upgrade to 1.40, it means that we're likely going to have to make patches to the core implementation instead.
Jul 17 2023
Is there any interest in backporting the fix for this issue to 1.40 once reviewed & merged? I'm not sure if there's a formal process for requesting that, but it is seemingly likely to cause issues on more external MediaWiki installations than just ours.
Jul 14 2023
Jul 10 2023
Jun 10 2023
I made an account on the beta cluster - this is how the page looks to me with JS disabled.
Hey @Jdlrobson, I just had a look at the page you linked on the beta cluster but I don't actually get the same as you when JS is disabled. However, I'm not logged in, so I'm wondering if that makes a difference in what you see on that page. Maybe try with an incognito window/logged out? (or maybe there's some other variable at play here)
May 30 2023
May 27 2023
FWIW, ?action=purge on https://en.m.wikipedia.org/wiki/Korean_drama appeared to fix the issue on that page for me.
May 25 2023
Is there a reason that "will not be carried over" is used here instead of "will not be attributed"? I'm a native English speaker so I can't really speak for those who have it as a second (or third) language, but it seems like it makes sense to remove any potential confusion and ambiguity with the wording - especially for those people. Obviously this isn't just limited to the mobile site/app, but I'm not sure where else this is being discussed.
May 22 2023
@abi_ Hey! Translatewiki should have a pending invitation for the repo at https://github.com/jayktaylor/mw-discord/invitations.
May 21 2023
May 19 2023
May 18 2023
Aug 24 2022
Feb 22 2022
Feb 21 2022
Jun 2 2021
Sep 12 2019
Looks like @Rxy has a revert patch here: https://gerrit.wikimedia.org/r/c/operations/puppet/+/535987/
Nov 15 2018
I'd like to see this. We use CodeMirror (and LinkSuggest), but the latter doesn't work with CodeMirror.
Oct 23 2018
I think that regardless of how effective CentralAuth's global locks are, implementing something in the GlobalBlocking extension that allows users to be blocked would be worthwhile, especially for independent wikis who don't utilize CentralAuth.
Sep 23 2018
Jan 26 2018
@Volker_E Well, anywhere that the help buttons are used in conjunction with a form, whether that be a custom gadget/script that utilises OOUI or an extension. Whenever I've used forms elsewhere (outside of MW), tab has cycled through each input on the page, not any guidance or help text. It's a slight annoyance from my perspective that there are extra key presses required to cycle to each input, especially when there is a form with a lot of inputs and each have their own help buttons.
@Volker_E Can we set the button to an access key instead to retain that accessibility? It just doesn't make a whole lot of sense to cycle to the help elements on tab, especially when you're trying to quickly fill in a form. Alternatively, another solution where we can keep this functionality but move it away from tab, as I know access key can behave differently per browser.