User talk:SMcCandlish

Archives

---

1, 2, 3, 4, 5, 6

Mini-toolbox

• The Phabricator Workboard for Tech News
• MW Editing team e-meetings, via Google Hangouts (Tuesdays, noon–12:30pm PDT = 20:00 UTC during DST, 19:00 otherwise, but often half an hour earlier).
• MW Tech Advice e-meetings, via IRC at #wikimedia-tech^connect (Wednesdays, 1–2pm PDT = 16:00–17:00 UTC).

Wrong balance at Community Wishlist Survey

Moved discussion to: Talk:Community Wishlist Survey#Feedback on CWS process

Under one item of our wishlist you write “Community Wishlist Survey is rather broken, in accepting only what has the most votes this year, which is never, ever going to be stuff template editors need.” That is a valid point that deserves wider attention. How would you suggest this to be fixed? One fix I can see would be to put effort and effect in proportion. A wishlist without any regard for cost will tend to favor the most expensive items, regardless of how many useful items can be had at the same price. ◅ SebastianHelm (talk) 13:45, 16 December 2020 (UTC)

@SebastianHelm: Yes, there's definitely that effect.

• That one's challenging to address, since assumptions about difficulty of implementing something are often – maybe even usually? – wrong (just ask any software engineer, especially one tasked with changing existing features or adding new ones to an existing product mostly written by other people). I'm reminded of the voter guide I get in the mail; there's a dedicated legislative analysis office that comes up with estimated costs and complications of implementing various ballot measures. WMF having someone[s] on staff doing this for CWS proposals and Phab requests in general might help, but it might be easy to be wrong and get fired/sacked. >;-)
• The no. 1 thing to me is true prioritization. Mission-critical things, e.g., accessibility solutions, HTML (and other) standards-compliance fixes, security improvements, and other key proposals which meet with support should take precedence over all attempts to add new features or "polish the chrome" on things that already are properly functional. Secondarily, improvements to existing features people definitely use (wishlist, search, editing tools) should generally have higher priority (among accepted proposals) than requests for all-new features.
  • This, to me, is where the process (not just CWS, but WMF's MW development in general) has failed the worst. It's also deeply entwined in why I resigned as a WMF Tech Ambassador to en.WP; the short version of my statement on my user page about this is: WMF is acting like a software company with a customer base and a marketing plan (what it wants customers to go for), instead of behaving as a globally important NGO with a constituency and a mission to serve the actual needs of that constituency. Some of the standards compliance things have been open tickets for 15+ years, across multiple bug-tracker systems, and some attempts to "fix" them have simply introduced more compliance problems, cutting off our nose to spite our face. There's a competence problem of some kind happening somewhere, even if most of the devs are amazing. But whoever thought it was good idea to have : equate to <dd> and render visually as an indent, and do this in absence of a proper <dl> list structure was foolish. Of course it would get abused for purely visual indentation not d-list construction, especially if no alternative was provided to do indentation properly. But it was an even worse idea (one I just now learned about, in the mobile skin) to replace that abuse of <dd> with abuse of <blockquote>, which is strictly reserved for actual quotations. The <div> generic element exists for a reason, and is super-mega-obviously the one to use here (though on talk pages the HTML 5 element <article> might be a better choice, especially with smart id stuff for thread building; this can probably just be ripped wholesale from any good blog, forum, or other CMS that is open-source.
  • No one who is unwilling to totally absorb the HTML and CSS specs has any business working on HTML and CSS code (including code that generates that code) at a professional level. I don't mean fire/sack anyone, just move them to something they're actually competent at, and put experts on the tasks the non-experts have been screwing up. Seriously, the kind of screwups involved are things that would not have been tolerated at a regular meritocracy-driven open source project; they would have been fixed years ago, and a bad mistake, like moving from abuse of one element to abuse of another instead of use of the proper one, would likely never have happened.
  • A conceptually similar issue (which I raised with a WMF person at w:en:WP:VPTECH, I think, within the last month) is WMF's internal hostility to VPNs, and inability to distinguish them from other kinds of services, nor to recognize the value they provide for security in an increasingly mobile but increasingly vulnerable computing and communications environment. The current practice of just blacklisting almost every block of IP addresses that happen to resolve to machines that provide VPN out-node services (generally blacklisted because of other services they provide) is downright stupid. It betrays a sort of "stuck in 2004" ignorance about how the technology works. Not just the necessity of VPNs these days, but the simple fact that any given IP address is apt to resolve to multiple [virtual] servers, even by multiple entities, and any given "server" is apt to have multiple sometimes unrelated IP addresses, all due to cloud computing, and software/servers-as-a-service models. It's rather like trying to block travel from Massachusetts because you heard about a bank robber who was born in Massachusetts, and also block entry to banks while you're at it, because anyone going into one might be a robber. This is not how to address sockpuppetry and other abuse problems, anymore than just massacring the entire populations of Nigeria and India is how to address the problem of online scams often coming from or passing through Nigeria and India.
• CWS proposals that pertain primarily to WMF projects should get pretty much all priority; stuff that's extraneous to that (e.g. features for bending MW into a blogging platform) should be left to third-party development, other than any necessary hooks for that development. And even then only if both WMF and the overall community think spending any time at all on that hook is worthwhile. Just because someone can conceive of a way to torque MW into being something it was not supposed to be doesn't make it a good idea.
• But there also need to be more CWS categories, or subcategories, that independently rank proposals within them. The current ones are mostly too sweeping, and net together many unrelated things (plus they become so long they are difficult to get through).
  • E.g., almost all requests for template/module tools are stuffed under "Editing", which is not at all what most people are thinking about for that category (they're thinking of public-facing content, the form we used for creating it, and the tools that operate on the content in that form, like add markup with a button press, etc.).
  • It even needs to split between source-mode editing and VisualEditor. Some of the proposals this year are VE-only, but are not labeled as such, and end up being confusing.
• Then there's the issue of the same proposals being made for 5 or 10 years in a row and always being supported but never implemented. Support assessment needs to be cumulative (within reason; some of the proposals mutate a little over time, but the entire WMF community is good at assessing shifting consensus over time, so this is not much of a challenge).
• Not-quite-relatedly, there are often also essentially duplicate proposals (I saw at least three this year: one pair already identified as such by someone; one pair flagged as such by me, though I only did that one way; and one pair unmarked because I was exhausted by the end and couldn't be bothered). Just as en.Wikipedia's Arbitration Committee (and several other processes, have clerks), someone should be tasked with clerking this stuff and merging proposals that are too similar (just present the options as variants, and if the proposal in general passes, the exact version to implement can be another discussion for another time, if that's not already clear from the CWS comments). I think there actually is some clerking going on already, since I have seen translation and other work get done. Maybe whoever's doing it needs an assistant.
• One other thing: this survey is so daunting it is very difficult to actually get through it all. It might be more practical to stagger it, e.g. put out the Editing section one month and the Search section another month, and so on, so one does not have to spend literally an entire waking day to wade through it all.
• We're getting too little input from too few editors. In part this is because of the issue in the bullet above this, but in part it's due to lack of local-project awareness and engagement. One radical change in approach could be for projects to host their own wishlists, or have RfCs for items to add, and then forward this on the bigger, cross-project process. There are numerous ways this could be reshaped, and each would present its own strengths and weaknesses.
• Some of it could also be more top-down. The devs will have ideas about what really needs to get done, what is nearing completion and pretty easy to do, what is virtually impossible, and some other matters, like what WMF's executive team and/or board are hoping for (which the community often doesn't know anything about in detail until too late) and solicit feedback more directly.
• Frankly, WMF needs to be willing to spend more money on getting stuff done. It has a lot of money, and isn't really spending enough of it on mission-critical things. I come from a "tech nonprofit" background (EFF and CRF), so I know very well what that problem looks like. A common version is over-spending on executive salaries and perqs (also for the board), like luxury furniture and first-class travel, at the expense of sufficient program staff (the average tech, communications, and other program staffer at such organizations is in dire need of at least one assistant, often a department, and the organization will not realize this until that over-worked and under-paid person burns out and leaves, and the org finds that person has to be replaced with 2 or 4 or 8 to get the same work done).

I could probably come up with more ideas and observations (see, e.g., w:en:User:SMcCandlish/Discretionary sanctions 2013–2018 review for an example of the kind of policy analysis I can do when I devote enough time to it, and even that's two years out of date and would cover several more more things than it does if I revised it significantly).
 — SMcCandlish ☺ ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ< , 02:21, 17 December 2020 (UTC)

Wow, I had no idea there was so much behind it – and you're hiding it in the comment to one wish! How best to tackle all of this? Does it even make sense to try and find a solution for one problem that only addresses a small shard of the whole?

Good point about the clerical tasks. I would see those as part of project management; why aren't WMF's PMs doing that?

You're right that the sheer amount of wishes is daunting. It may be a good idea to stagger it, but ultimately the workload stays the same. Not sure how to actually reduce the workload. Maybe similar to what we wrote in the wish for preferences: Mark everything for which a wish exists with a “🎁” symbol – in the UI and the manual – which links to the wish under discussion. So users will see wishes at the right moment and the right place, and only for those functionalities that they use or are interested enough to RTFM. I think this may also address the issue of getting input from too few editors. ◅ SebastianHelm (talk) 22:58, 17 December 2020 (UTC)

This thread would probably have more impact at Talk:Community Wishlist Survey, so I've copied it over there.  — SMcCandlish ☺ ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  04:14, 19 December 2020 (UTC)

Democratic authoritarianism

Hello.
Your formulation of the concept at en:Wikipedia talk:There is no justice made you one of the most respected en.Wikipedians by me. BTW I am astonished that such criticism of the regime has been possible in mainstream essays as late as in 2016. Incnis Mrsi (talk) 08:17, 29 January 2021 (UTC)

@Incnis Mrsi: Thanks, and I'm glad you liked it. :-) I worked most of that material into w:en:Wikipedia:Advice for hotheads, which covers several other things, including explosive behavior, false civility, and attempts to "argue Wikipedia into capitulation". I'll take the liberty of engaging in some coffee-fueled morning rambling:

As for essays, there's long been a lot of tolerance for conflicting viewpoints between various of them. We even have pairs of directly contradictory ones (or seemingly so, until you see that they address different kind of issues/incidents/questions). But ones that just do not at all align with the community's norms tend to get userspaced (or deleted at MfD if they're so off-kilter they have a NOTHERE vibe).

On the more philosophical "democratic authoritarianism" thing (not exactly the term I would use, but I see what you mean), and how it relates to an entity like WMF and a project like Wikipedia, I'm reminded of Twitter and Facebook kicking Trump and friends off their platforms (way later than they should have). They are privately owned companies with terms of use/service and a public to answer to. Various people in Trump's camp are claiming they are being "censored". They're making legally incorrect First Amendment arguments (the 1A only applies against censorship by the state, and doesn't let someone force their expression to be carried by private-sector third parties). WMF is in a similar boat. It isn't in a position to allow PoV pushers and other disruptive parties free reign, to allow defamatory material in articles on living people, and so on. WP is more like a newspaper or magazine publisher. PeTA and Greenpeace do not have a legal or "moral" right to force The Wall Street Journal to print their advocacy material, and the Family Research Council and the Eagle Forum can't require Huffington Post to given them equal "air time".

There are some grey areas, the common carriers. The gist is that various private or somewhat privatized entities have quasi-monopoly privileges, in exchange for infrastructure rollout, and liability shields for content they did not create, in exchange for not being permitted to monitor and censor. Some are arguing that social networking sites should be like this, should operate like package delivery services and telephone companies, as passive conduits for anything people want to send through them. I think this would be disastrous, since even with such sites trying to enforce ToU/ToS against against racist rabblerousing, black-market trading, insurrection and terrorism planning, etc., etc., the effect on our society of social media's propensity for creating borderless "reality bubbles" that inculcate us-vs.-them thinking, radicalization, and the spread and belief in patent falsehoods has just about ripped society apart over the last decade, and it's not looking to get better immediately if at all. If anything, non-state actors in the online information and communication space need to be more rather than less restrictive about what they'll permit on their systems, And that goes for far-left stuff too; the trans right activists making death threats against TERFs, or supposed antifa people agitating to burn down courthouses and cops' homes, should have their accounts nuked right along with anti-abortionists doxxing clinic workers in hopes they'll be tracked down and murdered, or white-nationalist "militia" nuts planning racist hate crimes.

The fundamental difference between a common carrier and a social networking site (in the broad sense, including webboards, collaborative content projects, etc.) is the public, memetic component. You can't recruit 10,000 people to join your telephone call or share in the goods inside a package you ordered from Amazon. There is no broad threat to society from having privacy and freedom of expression in one's phone calls and postal mail (even if certain crimes can be organized that way). There's obviously a big one inherent in using technology to create "permeably-walled-garden" propaganda and indoctrination farms, abusing private-sector services that were intended to make people's lives better and happier.

I have a lot of concerns about people system-gaming WP's "assume good faith" position through crafty "civil PoV-pushing" techniques to essentially bend WP articles to propagandistic purposes. It's already happening in a lot of topics, and it's hard to do much about it. All the pushers have to do is bait neutrality-minded editors into doing something explicitly uncivil, then get them banned from the topic area so the PoV pushers can just own it. This POVRAILROAD technique is precisely what was happening in the recent Flyer22 ArbCom case. The "AGF is not a suicide pact" maxim is going to have to be taken more seriously. WP is not longer a project eagerly accepting thousands of new editors per month from SlashDot and other nerdy forums to attempt the wacky idea of building a free encyclopedia. Eventualism essentially expired in the late 2000s at the latest. WP is a free encyclopedia, one of the most-read information sources in the world by the general public, and is under constant pressure to say non-neutral things on thousands of topics. We can still assume good faith, at first and for a while, but that has to stop with regard to a particular party when we see clear evidence to the contrary in their behavior. I should stop here or this will just get longer and longer. >;-)
 — SMcCandlish ☺ ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:00, 29 January 2021 (UTC)

Tech News: 2023-17

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The date-selection menu on pages such as Special:Contributions will now show year-ranges that are in the current and past decade, instead of the current and future decade. This feature request was voted #145 in the 2023 Community Wishlist Survey. [1]

Problems

• Due to security issues with the Graph extension, graphs have been disabled in all Wikimedia projects. Wikimedia Foundation teams are working to respond to these vulnerabilities. [2]
• For a few days, it was not possible to save some kinds of edits on the mobile version of a wiki. This has been fixed. [3][4][5]

Changes later this week

• All wikis will be read-only for a few minutes on April 26. This is planned for 14:00 UTC. [6]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 25 April. It will be on non-Wikipedia wikis and some Wikipedias from 26 April. It will be on all wikis from 27 April (calendar).

Future changes

• The Editing team plans an A/B test for a usability analysis of the Talk page project. The planned measurements are available. Your wiki may be invited to participate. Please suggest improvements to the measurement plan at the discussion page.
• The Wikimedia Foundation annual plan 2023-2024 draft is open for comment and input until May 19. The final plan will be published in July 2023 on Meta-wiki.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:03, 24 April 2023 (UTC)

Tech News: 2023-18

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The content attribution tools Who Wrote That?, XTools Authorship, and XTools Blame now support the French and Italian Wikipedias. More languages will be added in the near future. This is part of the #7 wish in the 2023 Community Wishlist Survey. [7][8][9]
• The Video2commons tool has been updated. This fixed several bugs related to YouTube uploads. [10]
• The Special:Preferences page has been redesigned on mobile web. The new design makes it easier to browse the different categories and settings at low screen widths. You can also now access the page via a link in the Settings menu in the mobile web sidebar. [11]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 May. It will be on non-Wikipedia wikis and some Wikipedias from 3 May. It will be on all wikis from 4 May (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 01:45, 2 May 2023 (UTC)

Tech News: 2023-19

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Last week, Community Tech released the first update for providing better diffs, the #1 request in the 2022 Community Wishlist Survey. This update adds legends and tooltips to inline diffs so that users unfamiliar with the blue and yellow highlights can better understand the type of edits made.
• When you close an image that is displayed via MediaViewer, it will now return to the wiki page instead of going back in your browser history. This feature request was voted #65 in the 2023 Community Wishlist Survey. [12]
• The SyntaxHighlight extension now supports wikitext as a selected language. Old alternatives that were used to highlight wikitext, such as html5, moin, and html+handlebars, can now be replaced. [13]
• Preloading text to new pages/sections now supports preloading from localized MediaWiki interface messages. Here is an example at the Czech Wikipedia that uses preload=MediaWiki:July. [14]

Problems

• Graph Extension update: Foundation developers have completed upgrading the visualization software to Vega5. Existing community graphs based on Vega2 are no longer compatible. Communities need to update local graphs and templates, and shared lua modules like de:Modul:Graph. The Vega Porting guide provides the most comprehensive detail on migration from Vega2 and here is an example migration. Vega5 has currently just been enabled on mediawiki.org to provide a test environment for communities. [15]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 May. It will be on non-Wikipedia wikis and some Wikipedias from 10 May. It will be on all wikis from 11 May (calendar).
• Until now, all new OAuth apps went through manual review. Starting this week, apps using identification-only or basic authorizations will not require review. [16]

Future changes

• During the next year, MediaWiki will stop using IP addresses to identify logged-out users, and will start automatically assigning unique temporary usernames. Read more at IP Editing: Privacy Enhancement and Abuse Mitigation/Updates. You can join the discussion about the format of the temporary usernames. [17]
• There will be an A/B test on 10 Wikipedias where the Vector 2022 skin is the default skin. Half of logged-in desktop users will see an interface where the different parts of the page are more clearly separated. You can read more. [18][19]
• jquery.tipsy will be removed from the MediaWiki core. This will affect some user scripts. Many lines with .tipsy( can be commented out. OO.ui.PopupWidget can be used to keep things working like they are now. You can read more and read about how to find broken scripts. [20]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:36, 9 May 2023 (UTC)

Tech News: 2023-20

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• Citations that are automatically generated based on ISBN are currently broken. This affects citations made with the VisualEditor Automatic tab, and the use of the citoid API in gadgets and user scripts. Work is ongoing to restore this feature. [21]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 May. It will be on non-Wikipedia wikis and some Wikipedias from 17 May. It will be on all wikis from 18 May (calendar).
• Starting on Wednesday, a new set of Wikipedias will get "Add a link" (Gorontalo Wikipedia, Hausa Wikipedia, Hakka Chinese Wikipedia, Hawaiian Wikipedia, Fiji Hindi Wikipedia, Croatian Wikipedia, Upper Sorbian Wikipedia, Haitian Creole Wikipedia, Interlingua Wikipedia, Interlingue Wikipedia, Igbo Wikipedia, Iloko Wikipedia, Ingush Wikipedia, Ido Wikipedia, Icelandic Wikipedia, Inuktitut Wikipedia, Jamaican Patois Wikipedia, Javanese Wikipedia). This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally. [22]

Future changes

• There is a recently formed team at the Wikimedia Foundation which will be focusing on experimenting with new tools. Currently they are building a prototype ChatGPT plugin that allows information generated by ChatGPT to be properly attributed to the Wikimedia projects.
• Gadget and userscript developers should replace jquery.cookie with mediawiki.cookie. The jquery.cookie library will be removed in ~1 month, and staff developers will run a script to replace any remaining uses at that time. [23]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:45, 15 May 2023 (UTC)

Tech News: 2023-21

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The "recent edits" time period for page watchers is now 30 days. It used to be 180 days. This was a Community Wishlist Survey proposal. [24]

Changes later this week

• An improved impact module will be available at Wikipedias. The impact module is a feature available to newcomers at their personal homepage. It will show their number of edits, how many readers their edited pages have, how many thanks they have received and similar things. It is also accessible by accessing Special:Impact. [25]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 23 May. It will be on non-Wikipedia wikis and some Wikipedias from 24 May. It will be on all wikis from 25 May (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:55, 22 May 2023 (UTC)

Tech News: 2023-22

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Citations can once again be added automatically from ISBNs, thanks to Zotero's ISBN searches. The current data sources are the Library of Congress (United States), the Bibliothèque nationale de France (French National Library), and K10plus ISBN (German repository). Additional data source searches can be proposed to Zotero. The ISBN labels in the VisualEditor Automatic tab will reappear later this week. [26]
• The page Special:EditWatchlist now has "Check all" options to select all the pages within a namespace. This feature request was voted #161 in the 2023 Community Wishlist Survey. [27]

Problems

• For a few days earlier this month, the "Add interlanguage link" item in the Tools menu did not work properly. This has now been fixed. [28]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 30 May. It will be on non-Wikipedia wikis and some Wikipedias from 31 May. It will be on all wikis from 1 June (calendar).
• VisualEditor will be switched to a new backend on small and medium wikis this week. Large wikis will follow in the coming weeks. This is part of the effort to move Parsoid into MediaWiki core. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [29]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:03, 29 May 2023 (UTC)

Tech News: 2023-23

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The RealMe extension allows you to mark URLs on your user page as verified for Mastodon and similar software.
• Citation and footnote editing can now be started from the reference list when using the visual editor. This feature request was voted #2 in the 2023 Community Wishlist Survey. [30]
• Previously, clicking on someone else's link to Recent Changes with filters applied within the URL could unintentionally change your preference for "Group results by page". This has now been fixed. [31]

Problems

• For a few days last week, some tools and bots returned outdated information due to database replication problems, and may have been down entirely while it was being fixed. These issues have now been fixed. [32]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 June. It will be on non-Wikipedia wikis and some Wikipedias from 7 June. It will be on all wikis from 8 June (calendar).
• Bots will no longer be prevented from making edits because of URLs that match the spam blacklist. [33]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:52, 5 June 2023 (UTC)

Tech News: 2023-24

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The content attribution tools Who Wrote That?, XTools Authorship, and XTools Blame now support the Dutch, German, Hungarian, Indonesian, Japanese, Polish and Portuguese Wikipedias. This was the #7 wish in the 2023 Community Wishlist Survey. [34]
• The Search Preview panel has been deployed on four Wikipedias (Catalan, Dutch, Hungarian and Norwegian). The panel will show an image related to the article (if existing), the top sections of the article, related images (coming from MediaSearch on Commons), and eventually the sister projects associated with the article. [35]
• The RealMe extension now allows administrators to verify URLs for any page, for Mastodon and similar software. [36]
• The default project license has been officially upgraded to CC BY-SA 4.0. The software interface messages have been updated. Communities should feel free to start updating any mentions of the old CC BY-SA 3.0 licensing within policies and related documentation pages. [37]

Problems

• For three days last month, some Wikipedia pages edited with VisualEditor or DiscussionTools had an unintended __TOC__ (or its localized form) added during an edit. There is a listing of affected pages sorted by wiki, that may still need to be fixed. [38]
• Currently, the "Sort this page by default as" feature in VisualEditor is broken. Existing {{DEFAULTSORT:...}} keywords incorrectly appear as missing templates in VisualEditor. Developers are exploring how to fix this. In the meantime, those wishing to edit the default sortkey of a page are advised to switch to source editing. [39]
• Last week, an update to the delete form may have broken some gadgets or user scripts. If you need to manipulate (empty) the reason field, replace #wpReason with #wpReason > input. See an example fix. [40]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 June. It will be on non-Wikipedia wikis and some Wikipedias from 14 June. It will be on all wikis from 15 June (calendar).
• VisualEditor will be switched to a new backend on English Wikipedia on Monday, and all other large wikis on Thursday. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [41]

Future changes

• From 5 June to 17 July, the Foundation's Security team is holding a consultation with contributors regarding a draft policy to govern the use of third-party resources in volunteer-developed gadgets and scripts. Feedback and suggestions are warmly welcome at Third-party resources policy on meta-wiki.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 14:51, 12 June 2023 (UTC)

Tech News: 2023-25

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Flame graphs are now available in WikimediaDebug. [42][43]

Changes later this week

• There is no new MediaWiki version this week.
• There is now a toolbar search popup in the visual editor. You can trigger it by typing \ or pressing ctrl + shift + p. It can help you quickly access most tools in the editor. [44][45]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:08, 19 June 2023 (UTC)

Tech News: 2023-26

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Action API modules and Special:LinkSearch will now add a trailing / to all prop=extlinks responses for bare domains. This is part of the work to remove duplication in the externallinks database table. [46]

Problems

• Last week, search was broken on Commons and Wikidata for 23 hours. [47][48]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 27 June. It will be on non-Wikipedia wikis and some Wikipedias from 28 June. It will be on all wikis from 29 June (calendar).
• The Minerva skin now applies more predefined styles to the .mbox-text CSS class. This enables support for mbox templates that use divs instead of tables. Please make sure that the new styles won't affect other templates in your wiki. [49][50]
• Gadgets will now load on both desktop and mobile by default. Previously, gadgets loaded only on desktop by default. Changing this default using the |targets= parameter is also deprecated and should not be used. You should make gadgets work on mobile or disable them based on the skin (with the |skins= parameter in MediaWiki:Gadgets-definition) rather than whether the user uses the mobile or the desktop website. Popular gadgets that create errors on mobile will be disabled by developers on the Minerva skin as a temporary solution. [51]
• All namespace tabs now have the same browser access key by default. Previously, custom and extension-defined namespaces would have to have their access keys set manually on-wiki, but that is no longer necessary. [52]
• The review form of the Flagged Revisions extension now uses the standardized user interface components. [53]

Future changes

• How media is structured in the parser's HTML output will change in the coming weeks at group2 wikis. This change improves the accessibility of content. You may need to update your site-CSS, or userscripts and gadgets. There are details on what code to check, how to update the code, and where to report any related problems. [54]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 16:19, 26 June 2023 (UTC)

Tech News: 2023-27

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• As part of the rolling out of the audio links that play on click wishlist proposal, small wikis will now be able to use the inline audio player that is implemented by the Phonos extension. [55]
• From this week all gadgets automatically load on mobile and desktop sites. If you see any problems with gadgets on your wikis, please adjust the gadget options in your gadget definitions file. [56]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 4 July. It will be on non-Wikipedia wikis and some Wikipedias from 5 July. It will be on all wikis from 6 July (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 22:51, 3 July 2023 (UTC)

Tech News: 2023-28

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Section-level Image Suggestions feature has been deployed on seven Wikipedias (Portuguese, Russian, Indonesian, Catalan, Hungarian, Finnish and Norwegian Bokmål). The feature recommends images for articles on contributors' watchlists that are a good match for individual sections of those articles.
• Global abuse filters have been enabled on all Wikimedia projects, except English and Japanese Wikipedias (who opted out). This change was made following a global request for comments. [57]
• Special:BlockedExternalDomains is a new tool for administrators to help fight spam. It provides a clearer interface for blocking plain domains (and their subdomains), is more easily searchable, and is faster for the software to process for each edit on the wiki. It does not support regex (for complex cases), nor URL path-matching, nor the MediaWiki:Spam-whitelist, but otherwise it replaces most of the functionalities of the existing MediaWiki:Spam-blacklist. There is a Python script to help migrate all simple domains into this tool, and more feature details, within the tool's documentation. It is available at all wikis except for Meta-wiki, Commons, and Wikidata. [58]
• The WikiEditor extension was updated. It includes some of the most frequently used features of wikitext editing. In the past, many of its messages could only be translated by administrators, but now all regular translators on translatewiki can translate them. Please check the state of WikiEditor localization into your language, and if the "Completion" for your language shows anything less than 100%, please complete the translation. See a more detailed explanation.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 11 July. It will be on non-Wikipedia wikis and some Wikipedias from 12 July. It will be on all wikis from 13 July (calendar).
• The default protocol of Special:LinkSearch and API counterparts has changed from http to both http and https. [59]
• Special:LinkSearch and its API counterparts will now search for all of the URL provided in the query. It used to be only the first 60 characters. This feature was requested fifteen years ago. [60]

Future changes

• There is an experiment with a ChatGPT plugin. This is to show users where the information is coming from when they read information from Wikipedia. It has been tested by Wikimedia Foundation staff and other Wikimedians. Soon all ChatGPT plugin users can use the Wikipedia plugin. This is the same plugin which was mentioned in Tech News 2023/20. [61]
• There is an ongoing discussion on a proposed Third-party resources policy. The proposal will impact the use of third-party resources in gadgets and userscripts. Based on the ideas received so far, policy includes some of the risks related to user scripts and gadgets loading third-party resources, some best practices and exemption requirements such as code transparency and inspectability. Your feedback and suggestions are warmly welcome until July 17, 2023 on on the policy talk page.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 19:54, 10 July 2023 (UTC)

Tech News: 2023-29

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• We are now serving 1% of all global user traffic from Kubernetes (you can read more technical details). We are planning to increment this percentage regularly. You can follow the progress of this work.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 July. It will be on non-Wikipedia wikis and some Wikipedias from 19 July. It will be on all wikis from 20 July (calendar).
• MediaWiki system messages will now look for available local fallbacks, instead of always using the default fallback defined by software. This means wikis no longer need to override each language on the fallback chain separately. For example, English Wikipedia doesn't have to create en-ca and en-gb subpages with a transclusion of the base pages anymore. This makes it easier to maintain local overrides. [62]
• The action=growthsetmentorstatus API will be deprecated with the new MediaWiki version. Bots or scripts calling that API should use the action=growthmanagementorlist API now. [63]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:08, 17 July 2023 (UTC)

Tech News: 2023-30

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• On July 18, the Wikimedia Foundation launched a survey about the technical decision making process for people who do technical work that relies on software that is maintained by the Foundation or affiliates. If this applies to you, please take part in the survey. The survey will be open for three weeks, until August 7. You can find more information in the announcement e-mail on wikitech-l.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 25 July. It will be on non-Wikipedia wikis and some Wikipedias from 26 July. It will be on all wikis from 27 July (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 02:20, 25 July 2023 (UTC)

Tech News: 2023-31

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Synchronizer tool is now available to keep Lua modules synced across Wikimedia wikis, along with updated documentation to develop global Lua modules and templates.
• The tag filter on Special:NewPages and revision history pages can now be inverted. For example, you can hide edits that were made using an automated tool. [64][65]
• The Wikipedia ChatGPT plugin experiment can now be used by ChatGPT users who can use plugins. You can participate in a video call if you want to talk about this experiment or similar work. [66]

Problems

• It was not possible to generate a PDF for pages with non-Latin characters in the title, for the last two weeks. This has now been fixed. [67]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 1 August. It will be on non-Wikipedia wikis and some Wikipedias from 2 August. It will be on all wikis from 3 August (calendar).
• Starting on Tuesday, a new set of Wikipedias will get "Add a link" (Georgian Wikipedia, Kara-Kalpak Wikipedia, Kabyle Wikipedia, Kabardian Wikipedia, Kabiyè Wikipedia, Kikuyu Wikipedia, Kazakh Wikipedia, Khmer Wikipedia, Kannada Wikipedia, Kashmiri Wikipedia, Colognian Wikipedia, Kurdish Wikipedia, Cornish Wikipedia). This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally. [68]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:54, 31 July 2023 (UTC)

Tech News: 2023-32

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Mobile Web editors can now edit a whole page at once. To use this feature, turn on "Advanced mode" in your settings and use the "Edit full page" button in the "More" menu. [69]

Changes later this week

• There is no new MediaWiki version this week.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:21, 7 August 2023 (UTC)

Tech News: 2023-33

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Content translation system is no longer using Youdao's machine translation service. The service was in place for several years, but due to no usage, and availability of alternatives, it was deprecated to reduce maintenance overheads. Other services which cover the same languages are still available. [70]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 August. It will be on non-Wikipedia wikis and some Wikipedias from 16 August. It will be on all wikis from 17 August (calendar).
• Starting on Wednesday, a new set of Wikipedias will get "Add a link" (Latin Wikipedia, Ladino Wikipedia, Luxembourgish Wikipedia, Lak Wikipedia, Lezghian Wikipedia, Lingua Franca Nova Wikipedia, Ganda Wikipedia, Limburgish Wikipedia, Ligurian Wikipedia, Lombard Wikipedia, Lingala Wikipedia, Latgalian Wikipedia, Latvian Wikipedia, Maithili Wikipedia, Basa Banyumasan Wikipedia, Moksha Wikipedia, Malagasy Wikipedia, Armenian Wikipedia, Kyrgyz Wikipedia). This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally. [71]

Future changes

• A few gadgets/user scripts which add icons to the Minerva skin need to have their CSS updated. There are more details available including a search for all existing instances and how to update them.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 05:59, 15 August 2023 (UTC)

Tech News: 2023-34

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The GDrive to Commons Uploader tool is now available. It enables securely selecting and uploading files from your Google Drive directly to Wikimedia Commons. [72]
• From now on, we will announce new Wikimedia wikis in Tech News, so you can update any tools or pages.
  • Since the last edition, two new wikis have been created:
    • a Wiktionary in Pa'O (wikt:blk:) [73]
    • a Wikisource in Sundanese (s:su:) [74]
  • To catch up, the next most recent six wikis are:
    • Wikifunctions (f:) [75]
    • a Wiktionary in Mandailing (wikt:btm:) [76]
    • a Wikipedia in Ghanaian Pidgin (w:gpe:) [77]
    • a Wikinews in Gungbe (n:guw:) [78]
    • a Wiktionary in Kabardian (wikt:kbd:) [79]
    • a Wikipedia in Fante (w:fat:) [80]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 22 August. It will be on non-Wikipedia wikis and some Wikipedias from 23 August. It will be on all wikis from 24 August (calendar).

Future changes

• There is an existing stable interface policy for MediaWiki backend code. There is a proposed stable interface policy for frontend code. This is relevant for anyone who works on gadgets or Wikimedia frontend code. You can read it, discuss it, and let the proposer know if there are any problems. [81]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:25, 21 August 2023 (UTC)

Tech News: 2023-35

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• As part of the changes for the better diff handling of paragraph splits, improved detection of splits is being rolled out. Over the last two weeks, we deployed this support to group0 and group1 wikis. This week it will be deployed to group2 wikis. [82]
• All Special:Contributions pages now show the user's local edit count and the account's creation date. [83]
• Wikisource users can now use the prpbengalicurrency label to denote Bengali currency characters as page numbers inside the <pagelist> tag. [84]
• Two preferences have been relocated. The preference "Enable the visual editor" is now shown on the "Editing" tab at all wikis. Previously it was shown on the "Beta features" tab at some wikis. The preference "Use the wikitext mode inside the visual editor, instead of a different wikitext editor" is now also shown on the "Editing" tab at all wikis, instead of the "Beta features" tab. [85][86]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 August. It will be on non-Wikipedia wikis and some Wikipedias from 30 August. It will be on all wikis from 31 August (calendar).
• New signups for a Wikimedia developer account will start being pushed towards idm.wikimedia.org, rather than going via Wikitech. Further information about the new system is available.
• All right-to-left language wikis, plus Korean, Armenian, Ukrainian, Russian, and Bulgarian Wikipedias, will have a link in the sidebar that provides a short URL of that page, using the Wikimedia URL Shortener. This feature will come to more wikis in future weeks. [87]

Future changes

• The removal of the DoubleWiki extension is being discussed. This extension currently allows Wikisource users to view articles from multiple language versions side by side when the <=> symbol next to a specific language edition is selected. Comments on this are welcomed at the phabricator task.
• A proposal has been made to merge the second hidden-categories list (which appears below the wikitext editing form) with the main list of categories (which is further down the page). More information is available on Phabricator; feedback is welcome!

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 14:00, 28 August 2023 (UTC)

Tech News: 2023-36

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• EditInSequence, a feature that allows users to edit pages faster on Wikisource has been moved to a Beta Feature based on community feedback. To enable it, you can navigate to the beta features tab in Preferences. [88]
• As part of the changes for the Generate Audio for IPA and Audio links that play on click wishlist proposals, the inline audio player mode of Phonos has been deployed to all projects. [89]
• There is a new option for Administrators when they are changing the usergroups for a user, to add the user’s user page to their watchlist. This works both via Special:UserRights and via the API. [90]
• One new wiki has been created:
  • a Wikipedia in Talysh (w:tly:) [91]

Problems

• The LoginNotify extension was not sending notifications since January. It has now been fixed, so going forward, you may see notifications for failed login attempts, and successful login attempts from a new device. [92]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 September. It will be on non-Wikipedia wikis and some Wikipedias from 6 September. It will be on all wikis from 7 September (calendar).
• Starting on Wednesday, a new set of Wikipedias will get "Add a link" (Eastern Mari Wikipedia, Maori Wikipedia, Minangkabau Wikipedia, Macedonian Wikipedia, Malayalam Wikipedia, Mongolian Wikipedia, Marathi Wikipedia, Western Mari Wikipedia, Malay Wikipedia, Maltese Wikipedia, Mirandese Wikipedia, Erzya Wikipedia, Mazanderani Wikipedia, Nāhuatl Wikipedia, Neapolitan Wikipedia, Low German Wikipedia, Low Saxon Wikipedia, Nepali Wikipedia, Newari Wikipedia, Norwegian Nynorsk Wikipedia, Novial Wikipedia, N'Ko Wikipedia, Nouormand Wikipedia, Northern Sotho Wikipedia, Navajo Wikipedia, Nyanja Wikipedia, Occitan Wikipedia, Livvi-Karelian Wikipedia, Oromo Wikipedia, Oriya Wikipedia, Ossetic Wikipedia, Punjabi Wikipedia, Pangasinan Wikipedia, Pampanga Wikipedia, Papiamento Wikipedia, Picard Wikipedia, Pennsylvania German Wikipedia, Palatine German Wikipedia, Norfuk / Pitkern Wikipedia, Piedmontese Wikipedia, Western Punjabi Wikipedia, Pontic Wikipedia, Pashto Wikipedia). This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally. [93][94]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:33, 4 September 2023 (UTC)

Tech News: 2023-37

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• ORES, the revision evaluation service, is now using a new open-source infrastructure on all wikis except for English Wikipedia and Wikidata. These two will follow this week. If you notice any unusual results from the Recent Changes filters that are related to ORES (for example, "Contribution quality predictions" and "User intent predictions"), please report them. [95]
• When you are logged in on one Wikimedia wiki and visit a different Wikimedia wiki, the system tries to log you in there automatically. This has been unreliable for a long time. You can now visit the login page to make the system try extra hard. If you feel that made logging in better or worse than it used to be, your feedback is appreciated. [96]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 September. It will be on non-Wikipedia wikis and some Wikipedias from 13 September. It will be on all wikis from 14 September (calendar).
• The Technical Decision-Making Forum Retrospective team invites anyone involved in the technical field of Wikimedia projects to signup to and join one of their listening sessions on 13 September. Another date will be scheduled later. The goal is to improve the technical decision-making processes.
• As part of the changes for the Better diff handling of paragraph splits wishlist proposal, the inline switch widget in diff pages is being rolled out this week to all wikis. The inline switch will allow viewers to toggle between a unified inline or two-column diff wikitext format. [97]

Future changes

• All wikis will be read-only for a few minutes on 20 September. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [98]
• The Enterprise API is launching a new feature called "breaking news". Currently in BETA, this attempts to identify likely "newsworthy" topics as they are currently being written about in any Wikipedia. Your help is requested to improve the accuracy of its detection model, especially on smaller language editions, by recommending templates or identifiable editing patterns. See more information at the documentation page on MediaWiki or the FAQ on Meta.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:08, 11 September 2023 (UTC)

Tech News: 2023-38

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• MediaWiki now has a stable interface policy for frontend code that more clearly defines how we deprecate MediaWiki code and wiki-based code (e.g. gadgets and user scripts). Thank you to everyone who contributed to the content and discussions. [99][100]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 19 September. It will be on non-Wikipedia wikis and some Wikipedias from 20 September. It will be on all wikis from 21 September (calendar).
• All wikis will be read-only for a few minutes on September 20. This is planned at 14:00 UTC. [101]
• All wikis will have a link in the sidebar that provides a short URL of that page, using the Wikimedia URL Shortener. [102]

Future changes

• The team investigating the Graph Extension posted a proposal for reenabling it and they need your input.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 19:19, 18 September 2023 (UTC)

Tech News: 2023-39

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Vector 2022 skin will now remember the pinned/unpinned status for the Table of Contents for all logged-out users. [103]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 26 September. It will be on non-Wikipedia wikis and some Wikipedias from 27 September. It will be on all wikis from 28 September (calendar).
• The ResourceLoader mediawiki.ui modules are now deprecated as part of the move to Vue.js and Codex. There is a guide for migrating from MediaWiki UI to Codex for any tools that use it. More details are available in the task and your questions are welcome there.
• Gadget definitions will have a new "namespaces" option. The option takes a list of namespace IDs. Gadgets that use this option will only load on pages in the given namespaces.

Future changes

• New variables will be added to AbuseFilter: global_account_groups and global_account_editcount. They are available only when an account is being created. You can use them to prevent blocking automatic creation of accounts when users with many edits elsewhere visit your wiki for the first time. [104][105]

Meetings

• You can join the next meeting with the Wikipedia mobile apps teams. During the meeting, we will discuss the current features and future roadmap. The meeting will be on 27 October at 17:00 (UTC). See details and how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 16:51, 26 September 2023 (UTC)

Tech News: 2023-40

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• There is a new user preference for "Always enable safe mode". This setting will make pages load without including any on-wiki JavaScript or on-wiki stylesheet pages. It can be useful for debugging broken JavaScript gadgets. [106]
• Gadget definitions now have a new "contentModels" option. The option takes a list of page content models, like wikitext or css. Gadgets that use this option will only load on pages with the given content models.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 3 October. It will be on non-Wikipedia wikis and some Wikipedias from 4 October. It will be on all wikis from 5 October (calendar).

Future changes

• The Vector 2022 skin will no longer use the custom styles and scripts of Vector legacy (2010). The change will be made later this year or in early 2024. See how to adjust the CSS and JS pages on your wiki. [107]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 01:26, 3 October 2023 (UTC)