♟ MZMcBride

This ticket should be closed as won't fix. "Vector 2022" and similar names were terrible from the start and that was obvious to nearly everyone. The issue isn't that skins are difficult to rename, the issue is that a very small number of people have chosen incredibly poor names for skins.

I spent a few minutes puzzling over this last night. The class only being applied to the first link and only when a timestamp is present made it extra enjoyable to debug.

Reverting misguided closure.

Reverting misguided closure.

This would be even more of an issue if we implement per-category editnotices this way. By targeting templates like Template:Large category TOC, vandals could literally affect millions of pages. We would likely have to semi or template-protect these templates from editing, which would IMO be an undesirable outcome.

Sorry for the bot spam noise.

@valhallasw if you can update https://www.mediawiki.org/wiki/Wikibugs to make it clearer...I think that'd be the only pending thing before we can close this task.

By "rearrange table columns", do you mean like dragging them to move in a user defined manner or sorting the columns based on a value in a specific row (as opposed to sorting rows based on the value in a specific column)

It seems like the regular error page is being rendered now, at least:

I really want to ask: Why we does not have a bot to globally block known proxies? It may be meaningful to bring ST47ProxyBot and so on to global blocking known proxies.

I'm a volunteer and my IRC bot was working its way through a very large queue due to these blocks. Some user many years ago decided to stalk every action on Meta-Wiki in their private IRC channel. That's why I happened to notice and I'll fix the bot when the queue clears and then probably move on with my life.

Is issuing thousands of global blocks per day now an accepted standard practice?

Apparently yes, and that something that should be discussed on meta and not here.

Closing since I don't see anything actionable here.

Hmm, have you asked stewards, as they might know best? :)

Hi! This resurfaced during the weekend. It is not a single issue (despite appearances), rather the message "upstream connect error or disconnect/reset before headers. reset reason: overflow" that we see can be a symptom of various causes. It is not resolved yet and has a chance of reappearing over the next few days/weeks while we work on what we hope will be a set of more permanent solutions.

This issue is still happening.

We would like to change the default skin version on a new set of pilot wikis from legacy Vector to the most recent version of Vector as per the results of community consultation.

@matmarex: Patch demo is awesome, thank you so much!! I just used it with https://gerrit.wikimedia.org/r/c/mediawiki/core/+/762099 and I was able to spin up a new wiki in 59 seconds and easily test my changes.

Thank you all for investigating this issue. Confirming that I have not touched this script in months, honestly I'd forgotten all about it again. The source code is here: https://github.com/mzmcbride/daily-article.

Legoktm awarded T17212: Allow self-renames a The World Burns token.

The undeniable truth of software engineering and computer security is that bugs happen. While techniques like automated testing and code review are used to try to prevent bugs from entering production, and deployment stages are used to minimize the impact of new bugs, those techniques are not capable of preventing every bug (and thus, every security issue) from hitting production servers. This is because all code is written by humans and humans are imperfect.

Trying to eliminate all security problems is a noble goal, but it is also a futile one. Instead, it is much more important to ensure that there is an effective response to those security problems once they are discovered. The forced logouts are an example of that plan in action. The only ways to prevent them would be to expect perfection from human developers, to stop developing and improving MediaWiki, or to stop adequately responding to security incidents. Those are all worse options.

Isn't this the third or fourth time everyone has been forcibly logged out in the past year? How is this acceptable? Why does this keep happening and who's taking responsibility to ensure that it stops happening?

Hm, why would being called autistic be considered a personal attack?

Can we stop using this task entirely please? It has been filed in 2017 for a project to migrate out of Gerrit to Phabricator Differential.

This task has been inactive for 3 years, so I'm closing it please reopen if this still needed.

This task appears to be a duplicate of at least one or more of these tasks:

Mozilla recently shut down its IRC server and switched to Matrix: https://wiki.mozilla.org/Matrix.

I appreciate the effort being made toward maintaining capability. Since 2011, I've run the "snatch" IRC bot that sits on irc.wikimedia.org and relays to the "snitch" IRC bot on irc.freenode.net.

I'm unconvinced any proposal here is paying down technical debt. Perhaps refinancing or doing some kind of balance transfer.