SMcCandlish
I will respond here to messages you leave, unless you request otherwise. — SMcCandlish Talk⇒ ɖ⊝כ⊙þ Contrib. 05:18, 29 December 2012 (UTC) |
Mini-toolbox
edit- 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-techconnect (Wednesdays, 1–2pm PDT = 16:00–17:00 UTC).
Wrong balance at Community Wishlist Survey
editUnder 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 smartid
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.
- 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
- 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
editHello.
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: 2024-35
editLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Feature news
- Administrators can now test the temporary accounts feature on test2wiki. This was done to allow cross-wiki testing of temporary accounts, for when temporary accounts switch between projects. The feature was enabled on testwiki a few weeks ago. No further temporary account deployments are scheduled yet. Temporary Accounts is a project to create a new type of user account that replaces IP addresses of unregistered editors which are no longer made public. Please share your opinions and questions on the project talk page.
- Later this week, editors at wikis that use FlaggedRevs (also known as "Pending Changes") may notice that the indicators at the top of articles have changed. This change makes the system more consistent with the rest of the MediaWiki interface. [1]
Bugs status
- Editors who use the 2010 wikitext editor, and use the Character Insert buttons, will no longer experience problems with the buttons adding content into the edit-summary instead of the edit-window. You can read more about that, and 26 other community-submitted tasks that were resolved last week.
Project updates
- Please review and vote on Focus Areas, which are groups of wishes that share a problem. Focus Areas were created for the newly reopened Community Wishlist, which is now open year-round for submissions. The first batch of focus areas are specific to moderator workflows, around welcoming newcomers, minimizing repetitive tasks, and prioritizing tasks. Once volunteers have reviewed and voted on focus areas, the Foundation will then review and select focus areas for prioritization.
- Do you have a project and are willing to provide a three (3) month mentorship for an intern? Outreachy is a twice a year program for people to participate in a paid internship that will start in December 2024 and end in early March 2025, and they need mentors and projects to work on. Projects can be focused on coding or non-coding (design, documentation, translation, research). See the Outreachy page for more details, and a list of past projects since 2013.
Learn more
- If you're curious about the product and technology improvements made by the Wikimedia Foundation last year, read this recent highlights summary on Diff.
- To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out:
- Community Configuration - Shaping On-Wiki Functionality Together (55 mins) - about the Community Configuration project.
- Future of MediaWiki. A sustainable platform to support a collaborative user base and billions of page views (30 mins) - an overview for both technical and non technical audiences, covering some of the challenges and open questions, related to the platform evolution, stewardship and developer experiences research.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
Tech News: 2024-36
editLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
- Editors and volunteer developers interested in data visualisation can now test the new software for charts. Its early version is available on beta Commons and beta Wikipedia. This is an important milestone before making charts available on regular wikis. You can read more about this project update and help to test the charts.
Feature news
- Editors who use the Special:UnusedTemplates page can now filter out pages which are expected to be there permanently, such as sandboxes, test-cases, and templates that are always substituted. Editors can add the new magic word
__EXPECTUNUSEDTEMPLATE__
to a template page to hide it from the listing. Thanks to Sophivorus and DannyS712 for these improvements. [2] - Editors who use the New Topic tool on discussion pages, will now be reminded to add a section header, which should help reduce the quantity of newcomers who add sections without a header. You can read more about that, and 28 other community-submitted tasks that were resolved last week.
- Last week, some Toolforge tools had occasional connection problems. The cause is still being investigated, but the problems have been resolved for now. [3]
- Translation administrators at multilingual wikis, when editing multiple translation units, can now easily mark which changes require updates to the translation. This is possible with the new dropdown menu.
Project updates
- A new draft text of a policy discussing the use of Wikimedia's APIs has been published on Meta-Wiki. The draft text does not reflect a change in policy around the APIs; instead, it is an attempt to codify existing API rules. Comments, questions, and suggestions are welcome on the proposed update’s talk page until September 13 or until those discussions have concluded.
Learn more
- To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out:
- Charts, the successor of Graphs - A secure and extensible tool for data visualization (25 mins) – about the above-mentioned Charts project.
- State of Language Technology and Onboarding at Wikimedia (90 mins) – about some of the language tools that support Wikimedia sites, such as Content/Section Translation, MinT, and LanguageConverter; also the current state and future of languages onboarding. [4]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
Tech News: 2024-37
editLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Feature news
- Starting this week, the standard syntax highlighter will receive new colors that make them compatible in dark mode. This is the first of many changes to come as part of a major upgrade to syntax highlighting. You can learn more about what's to come on the help page. [5][6]
- Editors of wikis using Wikidata will now be notified of only relevant Wikidata changes in their watchlist. This is because the Lua functions
entity:getSitelink()
andmw.wikibase.getSitelink(qid)
will have their logic unified for tracking different aspects of sitelinks to reduce junk notifications from inconsistent sitelinks tracking. [7]
Project updates
- Users of all Wikis will have access to Wikimedia sites as read-only for a few minutes on September 25, starting at 15:00 UTC. This is a planned datacenter switchover for maintenance purposes. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [8]
- Contributors of 11 Wikipedias, including English will have a new
MOS
namespace added to their Wikipedias. This improvement ensures that links beginning withMOS:
(usually shortcuts to the Manual of Style) are not broken by Mooré Wikipedia (language codemos
). [9]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
Tech News: 2024-38
editLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Improvements and Maintenance
- Editors interested in templates can help by reading the latest Wishlist focus area, Template recall and discovery, and share your feedback on the talkpage. This input helps the Community Tech team to decide the right technical approach to build. Everyone is also encouraged to continue adding new wishes.
- The new automated Special:NamespaceInfo page helps editors understand which namespaces exist on each wiki, and some details about how they are configured. Thanks to DannyS712 for these improvements. [10]
- References Check is a feature that encourages editors to add a citation when they add a new paragraph to a Wikipedia article. For a short time, the corresponding tag "Edit Check (references) activated" was erroneously being applied to some edits outside of the main namespace. This has been fixed. [11]
- It is now possible for a wiki community to change the order in which a page’s categories are displayed on their wiki. By default, categories are displayed in the order they appear in the wikitext. Now, wikis with a consensus to do so can request a configuration change to display them in alphabetical order. [12]
- Tool authors can now access ToolsDB's public databases from both Quarry and Superset. Those databases have always been accessible to every Toolforge user, but they are now more broadly accessible, as Quarry can be accessed by anyone with a Wikimedia account. In addition, Quarry's internal database can now be queried from Quarry itself. This database contains information about all queries that are being run and starred by users in Quarry. This information was already public through the web interface, but you can now query it using SQL. You can read more about that, and 20 other community-submitted tasks that were resolved last week.
- Any pages or tools that still use the very old CSS classes
mw-message-box
need to be updated. These old classes will be removed next week or soon afterwards. Editors can use a global-search to determine what needs to be changed. It is possible to use the newercdx-message
group of classes as a replacement (see the relevant Codex documentation, and an example update), but using locally defined onwiki classes would be best. [13]
Technical project updates
- Next week, all Wikimedia wikis will be read-only for a few minutes. This will start on September 25 at 15:00 UTC. This is a planned datacenter switchover for maintenance purposes. This maintenance process also targets other services. The previous switchover took 3 minutes, and the Site Reliability Engineering teams use many tools to make sure that this essential maintenance work happens as quickly as possible. [14]
Tech in depth
- The latest monthly MediaWiki Product Insights newsletter is available. This edition includes details about: research about hook handlers to help simplify development, research about performance improvements, work to improve the REST API for end-users, and more.
- To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out:
- Hackathon Showcase (45 mins) - 19 short presentations by some of the Hackathon participants, describing some of the projects they worked on, such as automated testing of maintenance scripts, a video-cutting command line tool, and interface improvements for various tools. There are more details and links available in the Phabricator task.
- Co-Creating a Sustainable Future for the Toolforge Ecosystem (40 mins) - a roundtable discussion for tool-maintainers, users, and supporters of Toolforge about how to make the platform sustainable and how to evaluate the tools available there.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
Tech News: 2024-39
editLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
- All wikis will be read-only for a few minutes on Wednesday September 25 at 15:00 UTC. Reading the wikis will not be interrupted, but editing will be paused. These twice-yearly processes allow WMF's site reliability engineering teams to remain prepared to keep the wikis functioning even in the event of a major interruption to one of our data centers.
Updates for editors
- Editors who use the iOS Wikipedia app in Spanish, Portuguese, French, or Chinese, may see the Alt Text suggested-edit experiment after editing an article, or completing a suggested edit using "Add an image". Alt-text helps people with visual impairments to read Wikipedia articles. The team aims to learn if adding alt-text to images is a task that editors can be successful with. Please share any feedback on the discussion page.
- The Codex color palette has been updated with new and revised colors for the MediaWiki user interfaces. The most noticeable changes for editors include updates for: dark mode colors for Links and for quiet Buttons (progressive and destructive), visited Link colors for both light and dark modes, and background colors for system-messages in both light and dark modes.
- It is now possible to include clickable wikilinks and external links inside code blocks. This includes links that are used within
<syntaxhighlight>
tags and on code pages (JavaScript, CSS, Scribunto and Sanitized CSS). Uses of template syntax{{…}}
are also linked to the template page. Thanks to SD0001 for these improvements. [15] - Two bugs were fixed in the GlobalVanishRequest system by improving the logging and by removing an incorrect placeholder message. [16][17]
- View all 25 community-submitted tasks that were resolved last week.
Updates for technical contributors
- From Wikimedia Enterprise:
- The API now enables 5,000 on-demand API requests per month and twice-monthly HTML snapshots freely (gratis and libre). More information on the updates and also improvements to the software development kits (SDK) are explained on the project's blog post. While Wikimedia Enterprise APIs are designed for high-volume commercial reusers, this change enables many more community use-cases to be built on the service too.
- The Snapshot API (html dumps) have added beta Structured Contents endpoints (blog post on that) as well as released two beta datasets (English and French Wikipedia) from that endpoint to Hugging Face for public use and feedback (blog post on that). These pre-parsed data sets enable new options for researchers, developers, and data scientists to use and study the content.
In depth
- The Wikidata Query Service (WDQS) is used to get answers to questions using the Wikidata data set. As Wikidata grows, we had to make a major architectural change so that WDQS could remain performant. As part of the WDQS Graph Split project, we have new SPARQL endpoints available for serving the "scholarly" and "main" subgraphs of Wikidata. The query.wikidata.org endpoint will continue to serve the full Wikidata graph until March 2025. After this date, it will only serve the main graph. For more information, please see the announcement on Wikidata.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
Tech News: 2024-40
editLatest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
- Readers of 42 more wikis can now use Dark Mode. If the option is not yet available for logged-out users of your wiki, this is likely because many templates do not yet display well in Dark Mode. Please use the night-mode-checker tool if you are interested in helping to reduce the number of issues. The recommendations page provides guidance on this. Dark Mode is enabled on additional wikis once per month.
- Editors using the 2010 wikitext editor as their default can access features from the 2017 wikitext editor by adding
?veaction=editsource
to the URL. If you would like to enable the 2017 wikitext editor as your default, it can be set in your preferences. [18] - For logged-out readers using the Vector 2022 skin, the "donate" link has been moved from a collapsible menu next to the content area into a more prominent top menu, next to "Create an account". This restores the link to the level of prominence it had in the Vector 2010 skin. Learn more about the changes related to donor experiences. [19]
- The CampaignEvents extension provides tools for organizers to more easily manage events, communicate with participants, and promote their events on the wikis. The extension has been enabled on Arabic Wikipedia, Igbo Wikipedia, Swahili Wikipedia, and Meta-Wiki. Chinese Wikipedia has decided to enable the extension, and discussions on the extension are in progress on Spanish Wikipedia and on Wikidata. To learn how to enable the extension on your wiki, you can visit the CampaignEvents page on Meta-Wiki.
- View all 22 community-submitted tasks that were resolved last week.
Updates for technical contributors
- Developers with an account on Wikitech-wiki should check if any action is required for their accounts. The wiki is being changed to use the single-user-login (SUL) system, and other configuration changes. This change will help reduce the overall complexity for the weekly software updates across all our wikis.
In depth
- The server switch was completed successfully last week with a read-only time of only 2 minutes 46 seconds. This periodic process makes sure that engineers can switch data centers and keep all of the wikis available for readers, even if there are major technical issues. It also gives engineers a chance to do maintenance and upgrades on systems that normally run 24 hours a day, and often helps to reveal weaknesses in the infrastructure. The process involves dozens of software services and hundreds of hardware servers, and requires multiple teams working together. Work over the past few years has reduced the time from 17 minutes down to 2–3 minutes. [20]
Meetings and events
- October 4–6: WikiIndaba Conference's Hackathon in Johannesburg, South Africa
- November 4–6: MediaWiki Users and Developers Conference Fall 2024 in Vienna, Austria
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.