This user is busy in real life and may not respond swiftly to queries.I've got things going on in my life right now that mean I'm going to be focussing on the fun, stress-reducing aspects of this hobby for a while and actively trying to avoid anything complicated, depressing, demanding, or stressful. If you ping me or leave a message and I don't respond, and then you see I've in the meantime created an entire article about an Asian chili sauce, that's why.
Admins: If you think an admin action I've taken recently is wrong or unhelpful, or one I've taken in the past is no longer useful, go ahead and undo or change it without feeling like you have to talk to me first. An explanation in the edit summary is always helpful, but I trust your judgement.
This page has archives.Topics inactive for 30 days are automatically archived 1 or more at a time by Lowercase sigmabot IIIif there are more than 5.
Scam Watch
Warning: There is an on-going scam targeting people who would like Wikipedia to have an article about them. See this scam warning for detailed information. No ethical Wikipedia editor or administrator will offer to create an article for money. If you've been scammed please send details to paid-en-wp@wikipedia.org to help others who could be future victims of this scam.
Latest comment: 29 days ago3 comments2 people in discussion
You see, Chitterlings vs Chitlins shows this is a can of worms in USA too. Hey, Can of Worms would be a great brand name for a new tinned intestines company.
I hope the scouse thing settles well. And sorry I bailed. It was just too much for me.
And I supported!. Now That's Guts! (also a good name for a tinned...)
Food names are such a rabbit hole. For one thing it's all mixed up with nationalistic issues. Everyone wants the dish to be called what they call it, and if their version is slightly different, they want a separate article even though it's the same damn dish or was developed from the same predecessor. So we end up with Scouse, Lobscouse, and Lobby. When all three could just be handled at Lobscouse. Oh, well. We tried. Valereee (talk) 11:58, 4 October 2026 (UTC)Reply
You're so right. I've listened to Turkish and Greek friends throughout my life talk about dishes, and it's always "It's Turkish, not Greek!", "It's Greek, not Turkish!", and boy, oh boy, are they ever passionate about it. Best, Anna Frodesiak (talk) 14:01, 4 October 2026 (UTC)Reply
Latest comment: 28 days ago2 comments2 people in discussion
Hello Valereee - fyi, the editor introducing the topic on talk:flavonoids and other polyphenol articles indeed has a major conflict of interest, needs to disclose this on talk page requests, and should not be editing COI-related articles. The editor revealed his true identity on his user page (Ggck2 was indef blocked on 31 May for COI, then successfully appealed, and for username evasion as Ggux, 2016-22), and for promoting polyphenols as nutrient candidates and biologically active (no MEDRS support for either status). These are topics of the user's professional publications, teaching at a university, and the work of academic and industry colleagues - fulfilling continuous COI. Some 90% of all edits by Ggck2 and Ggux were on a narrow group of polyphenol topics and talk pages. Ggck2 could clearly contribute more widely to Wikipedia, but chooses to fervently advocate specific topics for his professional goal and opinion to elevate visibility of certain polyphenols, seen particularly in the history of Talk:Flavan-3-ol, a sign of WP:SPA and WP:ADVOCACY. Zefr (talk) 16:40, 5 October 2026 (UTC)Reply
@Zefr, ah! Okay, I'll just stay out of that one, then, as I would have simply assumed that as long as they weren't citing to their own research, they could be treated as an expert. Didn't realize they were doing advocacy. Thanks! Valereee (talk) 16:43, 5 October 2026 (UTC)Reply
Latest 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
The process for this year’s Community Wishlist has been published, incorporating community feedback. The wish submission process will end on November 8. This year, a working group (open for volunteering) that includes community members familiar with the technical aspect of our wikis alongside Wikimedia Foundation staff, will take care of the triage process. The triage is expected to be completed by late November. Votes for wishes will start in January.
Updates for editors
Editors using the visual editor will now see a warning when they paste text that is likely to have initially been copied from one of five external generative AI chatbots into Wikipedia. This feature is known as LLM Paste Check. It is a type of Edit Check that is community configurable. The check looks for markers in the copied HTML and is not using content watermark detection. Edits will also be tagged so that patrollers can review them more closely. The feature helps newcomers add content that respects Wikipedia’s policies and makes it easier for experienced editors to identify problematic edits. Communities with local policies about LLM usage can adjust the wording and policy that is linked. The team apologizes that this was rolled out without a delay for translations.
Editors can now easily access the web visual editor directly from the iOS and Android apps. When opening the editor, users will be given a choice between visual editing and source editing. If they choose visual editing, they will be sent to a mobile web window in their phone's browser. After completing their edit, a banner will give them the option to return to the app. This enables readers to make quick contributions while casually reading.
Users of the Wikipedia Android and iOS apps will now see a one-time account creation prompt after they have used the app for two consecutive weeks. This prompt explains the benefits of having an account. It is intended to help more casual readers become logged-in users who return to the apps regularly.
Editors on group1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on Recent Changes and Watchlist when a link to another language version of a page is added, removed, or changed in its Wikidata item. This change will begin on October 5 at 07:00 UTC as a two-week trial to reduce high-volume, low-value notifications and make important changes easier to identify. Editors who rely on these notifications can read more on the project page and share feedback or concerns on the talk page.
View all 36 community-submitted tasks that were resolved last week. For example, an issue where mentors who removed themselves from the mentorship program could still have mentees assigned to them and receive questions, has now been fixed. Mentees will now be reassigned when a mentor leaves the program.
Updates for technical contributors
Wikimedia Brasil has published its Development Best Practices Framework (ABPD). It is a guide for staff, contractors and volunteers building technical tools and projects. It covers the project lifecycle, security, accessibility, personal data protection and responsible AI use, and explains how movement-wide guidelines were adapted to a local context. They encourage other affiliates to reuse it and adapt it. Read more in the Diff post.
A new, canonical base URL for Wikimedia APIs will soon be introduced. The new canonical route follows a {projectName}/api/ pattern and will act as an alternative path for current REST APIs (for example: {projectName}/w/rest.php/). Both versions will be callable for all existing APIs, but the new structure will be the preferred path for newly created API modules. This change will be non-breaking for most users. The existing pathways will remain available for all existing endpoint requests. However, some endpoints may return URLs following the new pattern in response bodies. Changes will be available on test wiki first, with the rollout expected to cover all wikis by the end of October.
On 13 Oct, we will start the voting phase. The candidate subpages will close to public questions and discussion, and everyone will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for.
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
October 13–19: SecurePoll voting phase (we are here)
Scrutineering phase
In the voting phase, the candidate subpages close to public questions and discussion, and everyone who qualifies to vote has a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for. Please note that the vote totals cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate's vote total during the election. The suffrage requirements are similar to those at RFA.
Once voting concludes, we will begin the scrutineering phase, which will last for a few days, perhaps longer. Once everything is certified, the results will be posted on the results page (this is a good page to watchlist), and transcluded to the main election page. In order to be granted adminship, a non-recall candidate must have received at least 70.0% support, calculated as Support / (Support + Oppose), and a minimum of 20 support votes. Recall candidates must achieve 55.0% support. Because this is a vote and not a consensus, there are no bureaucrat discussions ("crat chats").
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 20 days ago1 comment1 person in discussion
Latest 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
Starting October 13, wikis can change the default pattern for auto-generated reference names in VisualEditor (currently <refname=":1"/>). They will be able to use human-readable, content-based reference names that are more helpful to contributors using the source editor (e.g. <refname="Miller2026-1"/>). VisualEditor reference name patterns can be defined using MediaWiki system messages, JSON, templates and modules (more information). Admins can enable these changes via community configuration. This is a community wish implemented by WMDE Technical Wishes.
Sub-referencing is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to English Wikipedia on October 14 and to remaining Wikimedia Foundation wikis by end of October (likely October 21). The FAQ lists possible actions to take on your wiki to support the deployment. This is a long-standing community wish implemented by WMDE Technical Wishes.
Updates for editors
Moderator Tools will be removing the list view of the Watchlist and defaulting everyone to the changelog view. Previously, there were two versions of how the Watchlist is shown to mobile web users: the list view, where editors could see watched articles in a list format, and the changelog view, where editors could see changes to watched articles in a log format, controlled by a user's Advanced Mobile Control settings. This has created issues for code-base maintenance: two different displays means two sets of code to manage. By defaulting to the changelog view, we are simplifying the codebase and avoiding the likelihood of missing bugs.
The Wikipedia Android app is testing a way to listen to article introductions in the “For you” feed. A text-to-speech model reads the existing article text aloud without rewriting it or adding any content. The 30-day experiment will begin in the Wikipedia Beta app during the third week of September, then move to the regular Wikipedia Android app in October for a limited group of eligible users. A small portion of app users (those with English feeds and at least one topic interest) will have access to the feature. This experiment is part of broader efforts to give app readers options in how they consume content in order to deepen engagement and user retention. Learn more and share feedback.
CodeMirror syntax highlighting was enabled by default for all logged out and newly registered users on the English Wikipedia on September 14. With no signs of adverse effects, the same change is being proposed to be made globally across all wikis in a few weeks. If you have concerns or feedback, or if your wiki would like to opt out, please see the help page.
Last week, language link changes were removed from Recent Changes and Watchlist feeds on Wikivoyage, Wikisource, Wikiversity, Wikiquote and Wiktionary. As no adverse effects have been observed, the Wikidata For Wikimedia Projects plans to roll out this change globally to all Wikipedias. This is scheduled for October 13 at 07:00 UTC, after which editors will no longer see when a link to another language version of a page is added, removed, or changed in its Wikidata item. Editors who rely on these notifications can read more on the project page and share feedback or ask to opt out their wiki on the talk page.
View all 28 community-submitted tasks that were resolved last week. For example, an issue where accidentally touching the graph while scrolling on the Pageviews tool on mobile could unintentionally zoom in has now been fixed. Click-and-drag zoom is now disabled on touch devices.
Updates for technical contributors
There are three major changes coming to dumps: the legacy content dumps deprecated in January 2026 will now be sunset, the replacement MediaWiki Content File Exports will be delayed to implement a “safety buffer”, and they are now also available as 7zip-compressed files. Users will need to switch the URL they download their dump from. For more information, timeline and migration instructions, see Legacy content dumps sunset.
The Wikimedia Foundation discovered unauthorized activity by OpenAI agents on Wikimedia projects, including edits to wikis, attempts to exploit a public note-taking tool, and heavy automated traffic. Read the blog post on Diff for more details about the activity and the Foundation’s response.
Meetings and events
Save the date for the next Wikimedia Hackathon! We’ll be meeting in lovely Tirana, Albania for the 2027 Wikimedia Hackathon from April 9–11, 2027. Scholarship and staff sponsorship applications are currently being accepted through Pretix and will close on October 30, 2026. General registration will open in January 2027.
Latest comment: 14 days ago1 comment1 person in discussion
Latest 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
To measure the impact of incorporating some community-requested features on logged-out reader retention, a test for Image Carousel will be pushed to logged-out readers. With the Image Carousel feature, readers browse community-uploaded images, selected by editors as relevant to specific articles. The test starts on November 20.
An experimental notice will be pushed to 0.5% of logged-out mobile readers who come to English Wikipedia from Google, asking them to add Wikipedia as a Google Preferred Source. The test is to see if this notice increases reader retention and encourages people who use Google Search to visit Wikipedia more often. It will run from October 15–29 and will be assessed for its impact on retention and referrals.
View all 26 community-submitted tasks that were resolved last week. For example, an issue where Quarry returned an “Access denied” error when users tried to run SQL queries, preventing queries from running normally, has now been fixed.
Updates for technical contributors
Due to a long-standing bug, applications that use the OAuth 2 client credentials flow to act on their owners’ behalf are treated as if they are logged out. This will be fixed for new applications registered on or after Monday, October 19. Some affected applications need to re-register.
A proposal to hold the Wikimedia Hackathon every three years, with regional hackathons in between, has been shared. It explores making the event more accessible to technical communities in different regions. Share your feedback on the proposal’s talk page before November 6.
I brought more music to the main page;) - check out my story: Rossini was in Wildbad, and began to compose again. A short video] shows how his music is kept alive there by a festival at historic places. - If you turn to places, there was a dumpling pictures a while ago. -- Gerda Arendt (talk) 17:08, 26 October 2026 (UTC)Reply
Very nice! I think I remember seeing a dumpling pic a while back, usually when I find a photo of yours of a dish we don't have a photo for, I add it to commons and the article. Valereee (talk) 06:44, 27 October 2026 (UTC)Reply
Latest comment: 7 days ago1 comment1 person in discussion
Latest 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
An experiment launched on September 29 is testing article recommendations for new account holders who also identify as readers. By suggesting articles to read, similar to recommendations in the Wikipedia app for logged-in readers, the experiment aims to encourage new account holders to read and return to the website regularly, with the goal of increasing internal referrals by 1%. See the related Community Wishlist proposal.
Several Wikimedia services were taken offline last week because of a security vulnerability in PHP. This is because they need to be updated before they are safe to put back online. This is not a problem just for the Wikimedia movement but affects a lot of websites. You can follow updates on Wikitech. Cloud VPS and Toolforge will take longer to bring back online. This is to make sure that applications which run on Cloud VPS or Toolforge are not affected. Tool developers can see updates and more information on the Cloud-announce mailing list.
Last week we shared that to measure the impact of incorporating some community-requested features on logged-out reader retention, a test for the Image Carousel feature would be pushed to logged-out readers. Due to an issue, we will be restarting the test, but it will be live on October 26, not November 20 as initially announced.
Updates for editors
A new bot detection system to better identify automated traffic that disguises itself as human visitors, is coming to the Wikimedia wikis. This might cause sudden changes to visitor statistics starting from 26 October, going back to 20 June 2026.
The Score extension which renders musical notation inside wiki pages, has been temporarily disabled on all wikis due to a security issue. Affected pages will display a notice instead of musical scores, but the underlying code remains intact. No action is needed from editors, and a fix is in progress. A separate announcement will follow when the extension is re-enabled. Read more on Phabricator.
View all 18 community-submitted tasks that were resolved last week. For example, the issue where CodeMirror syntax highlighter appears to have been enabled in error for existing editors has been fixed.
Updates for technical contributors
All wikis will be read-only for a few minutes on Wednesday, October 28 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Scholarship and sponsorship applications for the 2027 Wikimedia Hackathon will close on Friday, October 30th. Submit your application through Pretix before the deadline!
Our three high scorers in the final round, who each got over 1,000 points, happen to all be among the top 8 as well:
Generalissima(submissions) with 2846 round points from 40 good articles, 4 pieces of featured content (including 2 featured articles), 11 DYK articles, and various reviews.
Bgsu98(submissions) with 2603 round points from 43 good articles, 5 pieces of featured content (1 featured article and 4 featuyred lists), and various reviews.
Vestrian24Bio(submissions) with 1141 round points from 20 good articles, a good topic, a featured list, and 30 good article reviews.
The top eight scorers will receive awards shortly. The following special awards will be made, based on high performance in particular areas of content creation. These prizes are awarded to the competitor who scored the highest in any particular field over the course of the competition.
Olliefant(submissions), who withdrew during the competition but who had 38 featured-content reviews in round 2. Olliefant also had 43 good article reviews in round 1.
Next year's competition will begin on 1 January. You are invited to sign up to participate. We are also looking for an experienced editor to help write the bimonthly newsletter. If you would like to help write next year's newsletters, please contact Epicgenius at his talk page.
The WikiCup is open to all Wikipedians, both novices and experienced editors, and we hope to see you all in the 2027 competition. Until then, it only remains to once again congratulate our worthy winners, and thank all participants for their involvement!
Latest comment: 1 day ago1 comment1 person in discussion
In our November 2026 newsletter, there was a mistake in calculating the final tournament point rankings (which have been updated here). We regret the error.
Following an RfC, election to ArbCom now requires at least 60% support. Successful candidates normally serve two-year terms, with one-year terms retained for filling vacancies. Proposals to change the election rules may now be added throughout the year and discussed on the talk page; formal discussion remains in September.
Following an RfC, first-time reviewers’ reviews require an experienced reviewer’s check, and GA requirements now include alt text and accessible tables. Featured articles may receive GA status during removal discussions if they meet GA criteria. Backlog drives will run every five months, with a points leaderboard and awards for the top five participants.
Miscellaneous
Self-nominations for the Arbitration Committee are open until 11 November 2026.
.jpg)
.jpg)
.jpg)
