Please edit this page to leave me a message but note that the Visual Editor does not work on such talk pages and so you will have to use the original Wikitext editor. The simplest way of doing this is to start a new section by using the standard link above or by clicking here.
Old discussions and messages are subject to regular housekeeping. Archives are organised mainly by topic (see right).
The bee has been able to confirm the identity of the bee because of the results of the study. Each person of any age has a reason. He experiences a lack of energy and closeness causes an overabundance of the body and causes Is there a serious loss of wealth? Is it possible for people to focus on this point? The goal is too soft. Every taste is delicious but there's no reason for it.
The bee has proven it by itself. The research results and the fact that people are still young don't provide a solid reason. Experience has no benefit. And closeness causes too much impact and leads to serious losses. Being rich? Is that the reason people focus on this point? The goal is too weak. Everything feels exhausted inside but still serves no purpose. 64.158.132.206 (talk) 19:11, 16 September 2025 (UTC)Reply
@Andrew Davidson Thank you for the thoughtful reply, I really appreciate it! I also took a look at the examples you provided, and I still believe your interactions in such discussions with examples of LLM outputs will provide very valuable insights - and in fact, I think you'll provide a very interesting perspective. Please let me know if you are interested in participating! And if you don't mind, we can also change to emails. Have a great weekend =) Phoebezz22 (talk) 02:31, 11 January 2025 (UTC)Reply
Latest comment: 1 year ago4 comments3 people in discussion
Hi Andrew Davidson!
In due deference to your seniority, you should have been the first editor I bothered in my quest for info, but it has only just occurred to me to check who created the article on the Black Middens. To cut a long story short, I'm trying to tie up a couple of loose ends I've come across regarding the Spanish Battery Rocks, at the estuary of the River Tyne, as an oft-mentioned hazard to shipping in the area. However, I have come up against a series of doubts which render that redlink (or simply a section at another article, a non-starter, at least for the moment. I have already bothered another user, Barabbas1312 who, though kindly tolerant of my imposition has, so far, been unable to shed further light on the matter at hand, beyond confirming that the "name doesn't appear to be used on the relevant Admiralty chart, though the battery itself is marked".
Not knowing the area at all, and as sources are few and far between, one of my main doubts is whether said rocks refer to "your" Black Middens or to the rocks on other side of the headland, where the actual artillery battery was located. If the former, since that article already exists, it might just be a matter of adding/finding a couple of sources that link the two sites, or not, as the case may be. Thanks for your time and, as I commented to Barabbas1312, please don't feel obliged to do anything regarding this matter. Happy Editing! Technopat (talk) 17:08, 16 February 2025 (UTC)Reply
This page about the Spanish Battery shows a map derived from Google. This labels the Black Middens and other specific features fairly clearly and also shows the coastal rocks. My impression is that the Black Middens usually means the reef of rock in the channel where the name label is. The rocks which form the shore around the headland seem to be a more general coastal feature and don't have particular names. So, the rocky shore near to the battery might be considered distinct but I doubt that it warrants a separate article.
We could use an article about the battery as the article Tynemouth Priory and Castle doesn't mention it. We could also use an article about the Tynemouth Volunteer Life Brigade Watch House which was built there specifically because shipwrecks were common. I'll make a start on that now.
A person who might be able to help is Ojsyork who is active in the RNLI and RNLI task force here.
Sorry chaps, can't help. I can find histories of Lifeboat Stations, but any ref. to wreck locations etc I just assume they're correct, and add a link if an article exists.
All the RNLI stations are now done, but I'm still on with List of former RNLI stations, whilst fending off the nonsense created by one other member of the RNLI group!
Greetings All! Many thanks for your prompt replies. As this is your talk page, Andrew Davidson, I hope you don't mind that I respond here also to Ojsyork so as not to have too many loose ends lying around. Yes, regarding that Spanish Battery link, thanks, I have that one and I agree with you regarding the specific reef versus the rocks under the battery and yes, the Watch House merits an article, so if you're happy to do that, great! Look forward to checking it out!
Regrading the RNLI, Ojsyork, I have just started using its Tynemouth's Station history page as a reference to pages on the Category:Lists of shipwrecks by year. Hope you manage to fend off the nonsense-peddler. In the absence of 10-foot bargepoles, boathooks are quite effective, as are sculls... (I once had the privilege of seeing a Thames waterman —and ex-British commando— smack a drunken idiot who had fallen into the Thames on the dodgy ebb tide over the head with a scull so as to stun him and stop him from capsizing the skiff we had gone to rescue him in. One of the highlights of my youth! Sorry, off on one of me tangents... --Technopat (talk) 21:25, 16 February 2025 (UTC)Reply
I found a good detailed source which is visible to me at Google Books so you may be able to read it there too. I have made a variety of other smaller edits and will do more as and when more occur to me.
We ought to start an article about Di Speirs using sources such as this.
And, if you're interested in radio please check out the List of longest-running radio programmes. We should add a Book at Bedtime to that as it's older than the Archers though it did have a break of three years, it seems.
I have been thinking about an article for Di Speirs too. I am very much a part-time editor, though. Thanks for your work on the Book of the Week article. The delete discussion has been closed with no overall discussion, so the article is retained. Snowman (talk) 09:17, 2 June 2025 (UTC)Reply
I saw that Eddie891 had noticed the book that I added as a source and was expecting this to produce a no-consensus result. That's good enough so we can move on to Speirs now. Some people don't like stubs but I'm quite keen on them. The way to get a job done is to start it... Andrew🐉(talk) 09:25, 2 June 2025 (UTC)Reply
Latest comment: 1 year ago3 comments2 people in discussion
I see that this BBC Radio show has been turned into a redirect (effectively deleted) following a merge discussion earlier this year. I would like to restore this article. Do you know how to go about this? Snowman (talk) 10:28, 6 June 2025 (UTC)Reply
Yes, the process of editing a redirect is described at WP:EDRED. I don't recall ever listening to that programme and am not seeing many sources for it but will put it on my watchlist and see what you can do with it. Andrew🐉(talk) 07:12, 7 June 2025 (UTC)Reply
I have listened to the radio show many times. It was redirected following a deletion discussion. I think there has to be a discussion on the talk page before the page can be restored. I have started a discussion on the talk page. Snowman (talk) 09:16, 7 June 2025 (UTC)Reply
You're welcome. Gardening and Wikipedia have some similarity, I reckon – activities like labelling, planting, pruning, seeding, weeding and so forth are common to both and the results can be equally attractive and rewarding. Andrew🐉(talk) 11:09, 24 July 2025 (UTC)Reply
Bach seems timeless and eternal now. Myself, I'm remembering Tom Lehrer who died recently (see ITN). His lyrics are witty and his mastery of the piano seemed excellent. Andrew🐉(talk) 13:35, 28 July 2025 (UTC)Reply
It's not based on logic or evidence. Per WP:ITNSIGNIF, "Whether a topic is significant enough for inclusion in ITN is often contentious. ... It is highly subjective whether an event is considered significant enough..." There is some gerrymandering too... Andrew🐉(talk) 17:51, 5 August 2025 (UTC)Reply
The article will be discussed at Wikipedia:Articles for deletion/Streameast until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article until the discussion has finished.
Latest comment: 1 year ago2 comments2 people in discussion
Hey Andrew Davidson, Your first edit anniversary on this wikimedia project was 4 days ago. Thank you for your valuable contributions and wishing you many more years of amazing contributions to the Wikimedia community:) -❙❚❚❙❙ GnOeee ❚❙❚❙❙✉22:08, 15 October 2025 (UTC)Reply
Thanks. What seems even more interesting is that the 20th anniversary of my account's creation is coming up on 15 February 2026. I must ponder how to celebrate it. Checking, I find that it's the Sunday of the Oxford Wikimeet so that's a possibility. Andrew🐉(talk) 17:32, 18 October 2025 (UTC)Reply
You uploaded File:Killiechassie 1862.png in 2014, but I don't quite understand why you marked it as {{keep local}}. The map being over 100 years old, it should be well within PD, and if not it should have been tagged as such. But perhaps there was a good reason that I am oblivious to.
I have gone ahead and marked the file for Commons export as well as updated the license tag inside {{PD-Art}} to {{PD-100}}. If that was in error, please revert my edit and let's discuss the license situation of the file. Rose Abrams (TCL) 14:24, 17 October 2025 (UTC)Reply
You seem to misunderstand what the template is saying. It is not an obstacle to copying to Commons; it records that "an editor has requested that the local copy be kept too". So, the file may be copied to Commons but the local copy should then be left here.
Reasons for this include:
Commons is a different project with different policies. I'm not exactly sure what they are as I don't tend to go there.
The file is on my watch list here and I like to keep an eye on material that I have created or uploaded.
Having a local copy enables me to annotate or otherwise comment on the content.
I see. I don't really know if "it's easy and convenient for me" is a solid reason to keep a local file, but it's not something I will argue. I'd recommend you to consider the arguments set out on WP:WHYCOMMONS for why not to keep a local file, but it's up to you.
But a more important question for you: Is it possible for you to fill in the fields | source = and | author = on the file page? Since you uploaded the file (albeit 11 years ago), you may remember the website/written work/repository where you found the image originally. It's fine if you cannot, I can always attempt to find the data myself by reverse-searching it online. And regardless of who does it, when that info is known and entered I will copy the file to Commons (while keeping the local copy per your request). Thank you! Rose Abrams (TCL) 15:47, 17 October 2025 (UTC)Reply
OK. I just read through WP:WHYCOMMONS and see that it says, "If you want to prevent images uploaded directly to Wikipedia from being deleted locally after being copied to Commons, use the {{Keep local}} tag." So, that's all good then. Andrew🐉(talk) 22:31, 17 October 2025 (UTC)Reply
I usually upload here rather than elsewhere as this is the main project that I work on and I'm not so familiar with other projects. One specific reason to maintain the file here is that I can then keep an eye on it using my watchlist. In this way I was able to observe the subsequent improvements to the license and resolution of the image and then thanked the editors responsible. This is my standard policy and process and seems to work well. Andrew🐉(talk) 18:14, 19 November 2025 (UTC)Reply
I see. I'm not certain if editor convenience is a good reason to keep a local copy, but I see no consensus about it and don't feel it worth arguing over anyway. So I'll do as planned and make a copy onto Commons while leaving your local copy intact. Have a good day! Rose Abrams (TCL) 20:47, 19 November 2025 (UTC)Reply
That guidance is not sensible as a subject of this sort will naturally attract attention once the article is created. Already other editors have rushed in and they now number seven and counting. The reader should naturally be advised that the topic is tentative until its stability becomes clear. Andrew🐉(talk) 19:28, 17 October 2025 (UTC)Reply
I read the discussion on the Prunella Scales blurb, and had some comments and questions.
I advocate including user metrics when considering ITN items. Why?
The site exists to serve readers.
Reader behavior is a key signal of the quality of the experience the site (and its editors) provide.
Editors are not representative of the broader public.
Editor judgement on newsworthiness/blurbworthiness is inherently and inescapably subjective.
Editors should want to know what readers are interested in.
Editors should want to know how readers engage with content on the homepage to help inform future editorial decisions.
Editors should want metrics to ensure homepage content is broad and balanced.
Metrics help counter personal biases by offering objective data that indicates notability.
Metrics can augment rather than replace editor judgement.
“I was going to jokingly reply to The Kip that viewer statistics would be coming in no time. I didn't think you would actually do it!
Rather than annoy almost every other editor with the repeated use of these, why don't you save everyone the trouble and bookmark WP:TOP25 or better yet download Wikipedia Mobile which shows the top viewed articles of the day (on the front page no less). I will seek community discussion at ITN Talk if I see a pointy use of these stats again. Quite silly really (or beyond that now perhaps).”
This comment seemed harsh, dismissive and intended to chill discussion. While this editor may not see the value of considering metrics, is it necessary to effectively censor discussion of them? Is there any recourse? Is it worth trying to have a discussion about how ITN items should can be discussed? Dr Fell (talk) 23:03, 30 October 2025 (UTC)Reply
Discourse at ITN is uncivil but so it goes. I fancy that some of the editors there are coming around for the second time. The Mills of God grind slow but exceeding fine...
Our readership is obviously important and so you're right that it should be measured. Let's look again at those numbers:
Prunella Scales is doing fine and has had over 400,000 readers in two days now. It's the numbers for some of those other ITN picks that seem lamentable. Clearly just about no-one is reading some of those topics and so we shouldn't be running them.
I'm following the discussion and see that Mathglot has some constructive suggestions. I'm pinging them to compare notes. Here's some points for their consideration.
I'm the original creator of {{annual readership}} and so quite motivated to help develop a successor.
I've listed 50 articles which use the template above. I want to get a full list but am not sure of the best way of capturing it.
I've archived the current code and talk pages so that we can still refer to them.
I've started developing a rough replacement which will give the reader a feel for the readership and link to the pageviews tool. The first draft is at talK:Poles in the United Kingdom. The code is
{{Tmbox
|style = border-spacing:4px
|image = [[File:Open data small color (vector).svg|32px]]
|text = The number of {{plainlink|url=https://pageviews.wmcloud.org/?project=en.wikipedia.org&platform=all-access&agent=user&redirects=0&range=all-time&pages=Poles_in_the_United_Kingdom|name=average daily views}} of this article is about 193.
}}
The average has to be inserted manually but should be fairly stable for a mature article. The page views parameters are defaulted to all-time which should give the full stats since records began in 2015. The reader then gets the big picture.
Hello, Andrew Davidson. Please check your email; you've got mail! The subject is 3Mb tsv. It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.—Mathglot (talk) 22:51, 8 November 2025 (UTC)Reply
Thanks for uploading File:Captain Flag.png. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of non-free use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
Thanks. Some notes for the record. I started the ball rolling for the blurb discussion which was quite protracted – 60K and counting. The nomination was updated and an image of him in his prime cropped for this. The article's lead was updated to highlight his critical significance. The tag-bombing was cleared and the list of works was updated with a reference to a comprehensive bibliography which helped resolve the debate about the need for sources for that section. There was some contention about the choice of lead image and I participated in the discussion for that. And I expanded the paragraph about his death, adding King Charles' statement. So, there was quite a variety of tasks to be done and so it's good that they helped it make the main page.
The readership on the death was over half a million. It will be interesting to see how much the blurb attracts.
Thanks for thinking of me. I see you got your recognition for starting the nomination – well done. But you didn't comment on the blurb option during the discussion – what did you think about that, please? Andrew🐉(talk) 15:31, 4 December 2025 (UTC)Reply
While I know Tom Stoppard, I am not so familiar with theatre as a whole, and especially unfamiliar with ITN's expectations on theatre. I set out to add the initial information on the death, and then decided after looking through the article to source and tweak the paragraph on his only book, which seemed the biggest source gap. (I did not know before that he had written a book.) I do think despite my unfamiliarity that he is quite a significant artistic figure, which seems blurbable, so it seems positive you managed to start the process. If there is "recognition" for me I would prefer it to be for the update and the book sourcing rather than for the nomination, although thinking as I write I did do that nomination on mobile so on second thought perhaps recognition is merited. CMD (talk) 15:49, 4 December 2025 (UTC)Reply
Looking at the readership stats, the blurb seemed to add about 30,000 readers on top of the base trend. I usually reckon ITN generates about 20,000 views so that was a bit better than usual. Andrew🐉(talk) 16:03, 5 December 2025 (UTC)Reply
Latest comment: 11 months ago3 comments3 people in discussion
On 11 December 2025, Did you know was updated with a fact from the article Baek Se-hee, which you recently created, substantially expanded, or brought to good article status. The fact was ... that Baek Se-hee wrote I Want to Die but I Want to Eat Tteokbokki? The nomination discussion and review may be seen at Template:Did you know nominations/Baek Se-hee. You are welcome to check how many pageviews the nominated article or articles got while on the front page (here's how, Baek Se-hee), and the hook may be added to the statistics page after its run on the Main Page has completed. Finally, if you know of an interesting fact from another recently created article, then please feel free to nominate it.
Latest comment: 10 months ago3 comments2 people in discussion
Hi - attempted to ping you but was told that my pinging would not go through so just wanted to manually let you know there is an ANI discussion involving the Talk:Swan Lake discussion you participated in []. Apologies if this is a duplicate ping. Gnomingstuff (talk) 18:09, 6 January 2026 (UTC)Reply
Latest comment: 9 months ago4 comments3 people in discussion
Hello Andrew, I saw on user:pendright’s talk page that your father will be turning 101 shortly, just wanted to congratulate him and wish him an early happy birthday. My Grandfather’s mother in law (of his second wife) has recently turned 101 too, which is amazing, 101 years is an amazing achievement, such a different time of history. May I ask whether he had any involvement in the war, I’m fascinated in that era and have relatives of my own (unfortunately no longer with us) who were involved, unfortauentlt I only met one of them, but it was great to. Have a lovely rest of your week. Mwen Sé Kéyòl Translator-a (talk) 21:09, 16 January 2026 (UTC)Reply
Thanks. If you're talking about WW2, then being born in Jan 1925 made him 14 when the UK joined the war and so he was too young to be very involved. A chap who used to do some gardening for me was a bit older and said that he saw Rommel in the Desert War. There are few such left now, alas. Andrew🐉(talk) 21:57, 16 January 2026 (UTC)Reply
Ah, I meant more during the later years (1944-1945), my great granduncle was a year older than your father and during the later years (at ages 18-19) fought before being wounded (Then again he was conscripted as he was German, I’m not entirely sure whether Britain was conscripting in the later years). I’m not sure whether any early war veterans are still around (veterans who fought at the start in 1939), I think it might only be later ones (and Hitler Youth members who fought during the last years/months, like Pope Benedict 16th).
That’s very interesting about the man you knew who saw Rommel, I don’t know much about the desert war, personally I think it was a waste for Germany (although good for us because we managed to defeat them), The desert war is pretty forgotten compared to other theatres, my Great-Grandfather was part of the RAF in the Ethiopian front (when Britain fought against Italy in Somalia and Ethiopia), which is by far one of the most forgotten theatres too. Mwen Sé Kéyòl Translator-a (talk) 10:19, 17 January 2026 (UTC)Reply
Thank you so much for your kind words and for taking the time to write. Wish your father a Happy next Birthday for me, I hope he is well. All the best - Pendright (talk) 02:48, 18 January 2026 (UTC)Reply
Latest comment: 8 months ago2 comments2 people in discussion
On 23 February 2026, Did you know was updated with a fact from the article Craig (elephant), which you recently created, substantially expanded, or brought to good article status. The fact was ... that an African elephant named Craig had tusks that were so long that they reached the ground? The nomination discussion and review may be seen at Template:Did you know nominations/Craig (elephant). You are welcome to check how many pageviews the nominated article or articles got while on the front page (here's how, Craig (elephant)), and the hook may be added to the statistics page after its run on the Main Page has completed. Finally, if you know of an interesting fact from another recently created article, then please feel free to nominate it.
"... that an African elephant named Craig had tusks that were so long that they reached the ground?"
I was intrigued as to what this meant, do they touch the ground only when he lowers is head or standing/walking normally etc. It is cited in the article at the end of the second sentence to IFAW and the BBC, they discuss the weight and length of his tusks but neither state that they reached the ground - Dumelow (talk) 09:47, 23 February 2026 (UTC)
I rewrote the relevant part of the lead to focus on the tusks and this was then picked up for the hook. Several sources comment on the length of the tusks and the Times describes them as "ground-sweeping" so I've just added a cite to that in the lead.
But, see the talk page for an alt which I suggested and got some support:
ALT ... that a super-tusker named Craig died when his teeth wore out which caused his intestines to rupture?
No, that is extremely depressing. TarnishedPathtalk 12:59, 23 February 2026 (UTC)
The Times story gives it a positive spin
Why Craig the elephant’s death is a victory for conservationists The Kenyan ‘super tusker’ carried nearly 100kg of ivory. The fact that he lived to 54 and died of natural causes is a landmark in the fight against poaching
. That might be turned into a hook but the article would need work to support it. Andrew🐉(talk) 13:12, 23 February 2026 (UTC)
The article blank paper protest was started in 2022 by No Swan So Fine – a prodigious creator of content. I wanted to help out and noticed that the page needed an image and so created one which I added to the article. I then added more content to the article.
The image has been replaced at the article but it occurred to me that it would be an entertaining addition to my user page, enabling me to blow off steam in a catch-all way without getting into the aggravating details of the latest issue, whatever that might be. You're the first person to comment on it, but it did get some thanks, iirc. Ok?
Latest comment: 7 months 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
Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional "Log in with passkey" button will soon be available for users who have already registered a passkey. This update will improve security and user experience. The screen recording demonstrates the passwordless login process step by step.
All wikis will be read-only for a few minutes on Wednesday, 25 March 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.
Updates for editors
Wikimedia site users can now export their notifications older than 5 years using a new Toolforge tool. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced.
Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an early version of an experience that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project.
The Special:Block now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: MediaWiki:Ipbreason-indef-dropdown.
Mobile editors at several wikis can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance account creation experience on mobile and then increase participation.
View all 36 community-submitted tasks that were resolved last week. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia.
Updates for technical contributors
Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent cloud-announce email and update your build configuration as necessary to ensure your tools are compatible.
The API Portal documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to mediawiki.org. Learn more on the project page.
Latest comment: 7 months ago2 comments2 people in discussion
Hello, how are you doing today? I'm sorry for disturbing you, I was wondering if you would like to be friends, I'm new here and j have no reading partner or friends here. Purnama1 (talk) 20:55, 13 April 2026 (UTC)Reply
Hello. I suggest that you start by creating a user page to introduce yourself. This will then indicate what we have in common.
Another possibility is to get a formal mentor. I'm not very familiar with the details of that process and so am not ready to commit to that yet.
You're welcome. My priority was the picture as I didn't like the crop that was there to start with. And then I fleshed out the lead which is the main bit that our readers will actually read.
Off now to an event at which a local symphony orchestra will perform. They don't have an article yet so I'll see if they merit one. More anon...
Latest comment: 5 months ago1 comment1 person in discussion
On 24 May 2026, Did you know was updated with a fact from the article The Boat Race 2026, which you recently created, substantially expanded, or brought to good article status. The fact was ... that Cambridge won all but one of the eight events at the 2026 Boat Race, the exception being the Oxford women's team, who broke their streak of eight consecutive losses? The nomination discussion and review may be seen at Template:Did you know nominations/The Boat Race 2026. You are welcome to check how many pageviews the nominated article or articles got while on the front page (here's how, The Boat Race 2026), and the hook may be added to the statistics page after its run on the Main Page has completed. Finally, if you know of an interesting fact from another recently created article, then please feel free to nominate it.
Latest comment: 4 months ago2 comments2 people in discussion
⚠
Thanks for uploading File:Parkie.webp. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of non-free use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
Latest comment: 4 months ago1 comment1 person in discussion
⚠
Thanks for uploading File:James Burrows.webp. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of non-free use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
Hello, I'm Ilov3gam3z. Although everyone is welcome to contribute to Wikipedia, it's important to be mindful of the feelings of your fellow editors, who may be frustrated by certain types of interaction, such as your addition to Wikipedia:Village pump (proposals). While you probably didn't intend any offense, please do remember that Wikipedia strives to be an inclusive atmosphere. In light of that, it would be greatly appreciated if you could moderate yourself so as not to offend. I do not want to come off as antagonistic here, but at the TWAFI RfC, you have been mildly condescending and dismissive of your fellow editors' arguments. I am not the one making this claim, as multiple other members of this discussion (including myself) have mentioned you seeming to not assume good faith and generally being somewhat condescending. A good example is this comment: "7amithorn is only 2 months old and so still has much to learn". While new editors may be less knowledgeable as old-timers, their ideas should be treated in the same light and tone as any other editors' ideas. Often new editors are exactly what Wikipedia needs to break old consensus and to be bold and try out new ideas, and as such should not be treated poorly. Thank you.Ilov3gam3z (talk) 23:12, 4 July 2026 (UTC)Reply
Latest comment: 4 months ago2 comments2 people in discussion
Let me preface this by saying that I understand your unorthodox view on images as they relate to ITN, and while I disagree with them, that's not what this discussion is about.
You keep posting images within the nomination threads, seemingly to increase the prominence of your points in the threads. Can you please stop doing this? It is quite disruptive, and unlike the other issues that people have asked you to drop, this one has no bearing on what does or doesn't get posted, so I would appreciate it if you could refrain from doing it in the future. Thanks. In solidarity, QuicoleJR (talk) 15:21, 14 July 2026 (UTC)Reply
Such images are used to illustrate particular points and are mainly used as an efficient form of communication. Please see the following articles to understand the general concept(s):
Communicating efficiently is not disruptive as it tends to save time and assist understanding. If such image use were disruptive then I'd expect there to be a PAG which explains this. You don't cite one and I'm not aware of one so your complaint seems groundless.
It seems fitting that we illustrate this conversation and I've chosen an antique etching. It's too wordy for my taste but that seems to have been the laboured style of such humour back then.
That's fine as I like eccentrics such as Stanley Green. I suppose that most hard core Wikipedians are odd fellows in various ways and I've come across many eccentrics at Wikimeets and editathons. But I'm not sure it's the best word in my case. My totem on Wikipedia is the WikiDragon and their key characteristic is that they are bold. I am clearly outspoken and willing to stick my neck out by taking the initiative, making the first move, standing up to be counted or voicing an alternative, contrarian view. It's the opposite of groupthink and so makes waves but it seems needed to open up discussions and arrive at good conclusions.
The other key attribute of dragons is that they have a thick skin and so I'm not quick to take offence. Please feel free to speak your mind too but it's good to be careful about backbiting and so thanks for the courtesy explanation.
I find that we have an article about eccentricity (behavior). I've not looked at it before and see that it needs work. I'm on it...
In another conflict elsewhere, I saw the issue of a general antipathy between editors being described as "bitch eating crackers". The phrase is too crude for my taste but I haven't found a better one yet and it seems to describe the interpersonal friction at ITN quite well. This seems to be a good place to park the thought while I muse on it. Andrew🐉(talk) 12:21, 17 July 2026 (UTC)Reply
Latest comment: 3 months ago1 comment1 person in discussion
Hello Andrew Davidson:
WikiProject Articles for creation is holding a month long Backlog Drive in August!
The goal of this drive is to reduce the backlog of unreviewed drafts to less than a month of outstanding reviews from the current 3+ months. Bonus points will be given for reviewing drafts that have been waiting more than 30 days. The drive is running from 1 August 2026 through 31 August 2026.
The discussion will take place at Wikipedia:Articles for deletion/2026 SpaceX lunar impact until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.
Thanks, it was fun to follow the event as it happened and then the detective work afterwards.. And others get the credit too, especially Kencf0618 who was the primary author of the article. Andrew🐉(talk) 20:04, 24 August 2026 (UTC)Reply
On 1 September 2026, a one-month backlog drive for new pages patrol will begin at a particularly important time for NPP.
The backlog has now passed 30,000 unreviewed articles, a level that has been described in current NPP discussions as exceptionally high and potentially difficult to overcome through normal reviewing alone. Backlog drives are one of the few measures that have historically produced a noticeable reduction in the backlog, so the participation of as many active patrollers as possible will matter this month.
If you can review during September, please make articles your priority. Every article that is reviewed is a meaningful reduction in the backlog. With the queue at its current size, even a relatively small increase in the number of articles each patroller reviews can add up to a substantial difference over the course of the month.
This is a hybrid drive, so redirect reviewing is still included. Redirects can be a useful way for newer patrollers to get comfortable with NPP and can help people build up to reviewing articles. However, the main goal of this drive is to tackle the article backlog, and experienced patrollers are particularly encouraged to spend as much of their available reviewing time on articles as they can.
Barnstars will be awarded based on the number of articles and redirects patrolled.
Each article review will earn 1 point, while each redirect review will earn 0.2 points.
Streak awards will be given out based on consistently hitting point thresholds for each week of the drive.
Barnstars will also be granted for re-reviewing articles previously reviewed by other patrollers during the drive.
If you have been thinking about doing more NPP, this is an especially good month to jump in. Whether you can review a few pages or hundreds, every review helps. And if you are already an active patroller, please consider whether you can put in some additional time during September to help bring the backlog back under control.
Latest comment: 2 months ago1 comment1 person in discussion
On 30 August 2026, Did you know was updated with a fact from the article Evo (AI), which you recently created, substantially expanded, or brought to good article status. The fact was ... that the week after the US announced a new policy for controlling high-risk biological research, an open-source AI experiment to generate new viruses was published which the policy did not prohibit? The nomination discussion and review may be seen at Template:Did you know nominations/Evo (AI). You are welcome to check how many pageviews the nominated article or articles got while on the front page (Evo (AI)), and the hook may be added to the statistics page after its run on the Main Page has completed. Finally, if you know of an interesting fact from another recently created article, then please feel free to nominate it.
It will be the 5th anniversary of the TBAN soon so I was contemplating an appeal at that time. The page has some notes I was making as preparation. For example, I notice a similar proposal being made at ANI for another editor and so my impression is that not much has changed in that arena. As I've not been following that area closely, I was trying to take stock of how things stand now.
Latest comment: 2 months ago2 comments2 people in discussion
Replying here so as not to further clutter the RFC discussion, but thanks for pointing me to the signpost article about using AI to find possible errors in articles. That kind of use case is interesting to me, even though I'm skeptical of relaxing our prohibitions due to the large number of examples of irresponsible use I have seen on-wiki. -- LWGtalk(VOPOV)20:10, 10 September 2026 (UTC)Reply
Latest comment: 2 months 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
The Future Audiences team has started a discussion on English Wikipedia about a proposed new experiment to show a temporary notice about the new Google Preferred Sources feature to Wikipedia readers coming from Google. The experiment is to test whether this notice makes visitors come back to Wikipedia more often. Preferred Sources feature lets users choose websites they trust so Google can highlight content from those sources more prominently in Search and AI experiences. We are interested in testing this on other languages that Google supports and would welcome assistance with starting conversations on other wikis. If interested, please reach out to Future Audiences on the talk page.
Updates for editors
The chat platform Discord is releasing a new self-service framework that websites can use to specify how their links should look when shared on Discord. The Future Audiences team is planning to start using this new framework to improve how Wikipedia links look when shared on Discord, giving better attribution and credit to contributors. The link appearance and behavior won't change in the first phase of this project as we want to first collect some baseline data to assess the impact of future changes. However, if community members who are active on Discord spot any issues, they can reach out on Phabricator or Metawiki.
The Reader Growth team will be running an experiment to test whether compacting article lead sections on mobiles with the addition of a "read more" button improves reader retention. The test will begin on September 17 on Arabic, Spanish, French, Indonesian, Italian, Japanese, Portuguese, Vietnamese, and Chinese Wikipedias and will run for four weeks.
All wikis will be read-only for a few minutes on September 23. 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 week.
View all 28 community-submitted tasks that were resolved last week. For example, an issue where Wikistats for Wikipedias was returning an HTTP 500 error and could not be reached, has now been fixed.
Updates for technical contributors
Developers who maintain a tool that queries the Wikimedia Commons links tables need to update their code to connect to the new x4 database cluster. The links tables have been moved from the s4 cluster to x4, and will no longer receive updates on s4. The page and redirect tables remain available on both clusters. A wiki replica for the x4 cluster will be set up afterwards. The change is being made because the s4 cluster has grown too large to operate efficiently. You can read more.
Running from October 1 to 31, 2026, WikiProject Women in Green (WiG) is hosting a Good Article (GA) edit-a-thon event with the theme Around the World in 31 Days! All experience levels welcome. Participants are invited to work on nominating and/or reviewing GA submissions related to women and women's works (e.g., books, films or organizations created by women) during the event period — and this time, we are extending our focus to encourage more Did You Know (DYK) submissions spotlighting new GA articles about women and women's works. We hope to collectively cover article subjects from at least 31 countries (or broader international articles) by the event's end. GA resources and one-on-one support will be provided by experienced editors, and participants will have the opportunity to earn a special WiG barnstar for their efforts.
You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.
Latest comment: 1 month 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
Users of default skins on desktop and mobile web (Vector 2022 and Minerva respectively) will now be informed if the search suggestions displayed as they type into Search come from page redirects. Previously, users could get confused when the top search suggestions did not match exactly what they had typed. The new redirect notice clarifies that these suggestions are not random, but related to the search. The suggested pages may be redirects to the most relevant destination articles being searched for.
Logged-out Wikipedia users on mobile web will begin to see a bookmark button for saving articles to their reading lists instead of the current Watchstar button. When clicked, the bookmark button prompts users to log in or create an account to save an article for later. An earlier experiment found that the bookmark icon was four times more likely than the Watchstar button to encourage logged-out users to create an account. This change is part of efforts to encourage more readers to become account holders and use features that help them save and return to content.
An experiment will begin on September 29 on Spanish, Arabic, English, and French Wikipedias to simplify the experience users encounter immediately after account creation. The test will explore whether removing friction from the current Welcome Survey helps new users understand what to do next more easily. The experiment will run through the end of October.
The Product and Technology Advisory Council has put out a call for the community to suggest topics that it should consider and discuss with the Wikimedia Foundation. Editors and technical contributors are invited to add topics to the council's talk page.
A bug in the Global Watchlist is causing the page to fail to load for users that have unseen changes on Wikimedia Commons. Developers are working on a fix. Until then, affected users can follow the workarounds described in the relevant help section.
New magic words {{CATEGORYSORT:TIMESTAMP}} and {{CATEGORYSORT:RTIMESTAMP}} are now available for use. They are able to change the default sorting of categories to be based on timestamp of categorization.
View all 20 community-submitted tasks that were resolved last week. For example, the issue where Wikistats for Wikipedias was not reachable has now been fixed.
Updates for technical contributors
The datacenter switchover, scheduled on September 23, has been postponed. The equinox exercise revealed capacity issues, preventing the switch of all services to the other datacenter. The process has been paused, prioritizing investigating that issue, to ensure that we continue to be able to serve our users reliably. A new exercise will be scheduled. Meanwhile, all traffic and edits continue to work as usual.
On September 23, a power loss briefly affected all wikis, creating intermittent issues on both reading and editing modes. This also affected Gerrit. This is unrelated to the datacenter switchover postponement.
Produnto has been deployed to mediawiki.org and some Indic language wikis. We want to hear your feedback on this experimental product. Produnto allows users to use Lua modules hosted in Wikimedia's GitLab. It simplifies the sharing of Lua code between wikis. Instead of copying each individual Lua module from one wiki to another, users will be able to easily share packages across all wikis.
A Cross-wiki code collaboration workshop will be held online on October 2 at 12:30 UTC, bringing together South Asian technical contributors to learn about Produnto and begin piloting it on Hindi, Punjabi, Odia, Telugu, and Malayalam Wikipedias. Produnto is a package manager for deploying Lua modules hosted on GitLab to Wikimedia wikis, and was recently deployed on some pilot wikis.
Latest comment: 1 month ago1 comment1 person in discussion
The administrator elections process has officially started! Qualified editors are encouraged to find at least one experienced nominator. Self-nominations are also allowed. Please review instructions at Wikipedia:Administrator elections/October 2026/Candidates.
Here is the schedule:
September 29–October 5: Nominations phase (we are here)
October 8–12: Discussion phase
October 13–19: SecurePoll voting phase
Please note the following:
The requirements to run are identical to RFA—a prospective candidate must be extended confirmed. However, in practice, few candidates succeed without ~10K edits, some content creation, no recent behavioral issues, and a nominator.
The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
Ask any questions about the process at the talk page. Later, a user talk message will be sent to official candidates with additional information about the process.
If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.
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.
Who are/were the leaders of national organizations in your field? How about national award winners? That's a great place to start looking for article subjects you'd be well-suited to work on.
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.
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: 1 month 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: 27 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.
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
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!
Latest comment: 6 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
The Wikipedia Apps team is preparing to launch Year in Review in early December. Year in Review gives app users a personalized recap of how they read and engaged with Wikipedia throughout the year. The team is looking for volunteers to help make it available in as many languages as possible. Translators can contribute through translatewiki.net. For Android, search for yir under the "Untranslated" tab, and for iOS, search for year-in-review under the "Untranslated" tab.
Following the release of Reading Lists to all Wikipedias in September, logged-in users will soon be able to organize articles saved in their lists into customizable categories. This will enable readers to create collections and revisit saved articles based on their interests, potentially encouraging frequent visits to Wikipedia. The update will roll out to all Wikipedia users between November 9 and 16.
The Wikipedia Apps team is preparing to launch the first of two notification experiments for English Wikipedia readers on Android who have opted in to notifications. The three-week experiment will send notifications suggesting personalized Discover reading lists which are collections of Wikipedia articles recommended based on articles the reader has previously viewed. The goal is to understand whether these recommendations help readers discover relevant content and encourage them to return to the app. No action is required, and users can manage their notification preferences in the app settings. Learn more and share feedback.
A bug in the Global Watchlist was causing the page to fail to load for users who have unseen changes on Wikimedia Commons. The bug has now been fixed. If you temporarily removed commons.wikimedia.org from your personal Global Watchlist settings due to the bug, you can restore it there.
A new Beta feature called "Home" will be deployed to 10 Wikipedias for a limited test. This new feature aims to replace Special:Homepage for newcomers, with additional modules planned for the future to improve upon the current experience. If you want to participate in the test, please sign up. "Home" will be released to all users later this month.
On English and Russian Wikipedias, Source Verification is now available as an experimental Suggestion for experienced editors within Suggestion Mode. It uses an LLM hosted on LiftWing to try to check whether a cited source supports the claim it’s attached to. To try it out, please see these testing instructions. If you are at another language Wikipedia and your community is interested in trying it out, please express your interest.
View all 35 community-submitted tasks that were resolved last week. For example, an issue where dates passed as blank parameters to functions in wikitext were incorrectly interpreted using the month-day-year format instead of the day-month-year format, has now been fixed.
Updates for technical contributors
Starting on 1 December 2026, hCaptcha will be required for edits made via the API by non-autoconfirmed users. If your tool, gadget, or user script makes edits on behalf of newcomer users, see how to update it.
Toolforge has introduced two new beta features. "Toolforge alerts" send email notifications when a tool becomes unavailable, returns errors, or restarts frequently. "Extended logging" makes it easier to investigate problems by providing logs for events such as job creation, deletion, and deployment failures through the toolforge logs command. Both features are opt-in and help tool maintainers become aware of and resolve problems with their tools more quickly. Maintainers can enable alerts and learn how to access extended logs. They are also encouraged to try the features and provide feedback.
A proposal to change how we currently organize the Wikimedia Hackathon 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; the deadline has been extended to November 13th.
Latest comment: 10 hours ago3 comments2 people in discussion
Bruan didn't have engines on the reusued part, its quite literally not a reusable rocket because the rocket part is thrown away. You can disagree about including starship in ITN because it isn't ITN enough but the idea that it's nothing more impactful than the Buran was is simply wrong.
Buran and every system before it had to throw away parts, this is a rocket where we no longer have to throw any part away. In 10 years the impact of that will be as obvious and undeniable as the F9 first stage landing just over 10 years ago is today. TaqPCR (talk) 19:05, 15 November 2026 (UTC)Reply
I only mentioned the Buran because it was on the main page today. It didn't get as far as the Space Shuttle which is the main counter example. That had rockets and so is comparable. The Starship is obviously making progress in various ways but hasn't quite got to full reusability yet.
The way that the Falcon landed on its tail using legs was very impressive and harked back to the visions of SF. The new system of catching with "chopsticks" looks more clunky and I'm not sure why they prefer it. I suppose the weight and size of the Starship is too great for legs to handle without them being too heavy.
"It didn't get as far as the Space Shuttle which is the main counter example. That had rockets and so is comparable."
A much more valid comparison but while Shuttle retained it's engines, every time it launched it threw away it's main tank which cost as much as buying an entire Falcon 9 launch (and probably 5x the cost to SpaceX of launching F9) each time it launched. And the SRBs may have been recovered but they might have literally been cheaper to build new each time.
"The new system of catching with "chopsticks" looks more clunky and I'm not sure why they prefer it. I suppose the weight and size of the Starship is too great for legs to handle without them being too heavy."
Rockets when empty are actually incredibly light. An empty booster is only around 5% the mass of the full stack which is fully supported from the bottom both before liftoff and even as the booster accelerates to nearly 2g. They ditched legs not because it would be impossible to build ones that could support that weight but because legs themselves will always weigh a lot, especially making them reliable. Instead the chopsticks catching them midair only requires two very light pins to hook onto the chopsticks (whose mass doesn't much matter). China did a similar thing with the Long March 10B where the rocket hovers in the middle of this big girder system and then a square of cables strung across the gap close in on it and catch on hooks. It's hard to describe in words but very clear on video (please excuse the music, I couldn't find other ones with the closeup shots). TaqPCR (talk) 20:03, 15 November 2026 (UTC)Reply