Latest comment: 16 days ago10 comments4 people in discussion
As usual, we are preparing this regular survey on recent academic research about Wikipedia, doubling as the Wikimedia Research Newsletter (now in its sixteenth volume). Help is welcome to review or summarize the many interesting items listed here, as are suggestions of other new research papers that haven't been covered yet. Regards, HaeB (talk) 17:16, 7 October 2026 (UTC)Reply
I do not believe that the results will be a surprise to most Wikimedians who have been curious about generative AI. It is however disheartening to see that the journalists and science communicators we may be trusting to provide high quality, verified information, do not seem to share our caution. This is not an opinion piece so authors should not express their beliefs and what disheartens them personally. Czarking0 (talk) 15:53, 8 October 2026 (UTC)Reply
RR has been inviting opinions in the form of paper reviews (a very standard format, cf. wikt:review#Noun #2) for fifteen years now, as you could also have gleaned from the comment you are replying to. Happy to hear your arguments if you believe that this should change, but for now we'll stick with the existing format. Regards, HaeB (talk) 01:27, 9 October 2026 (UTC)Reply
"as you could also have gleaned from the comment you are replying to" do you really have to start with this insufferable attitude? Best regards you could ever have, Czarking0 (talk) 03:17, 9 October 2026 (UTC)Reply
Hi Czarking0, while you have made various good contributions to the Signpost in recent months, and I don't mind healthy disagreements and unvarnished feedback, I am starting to worry that you might have been getting a mistaken impression that insults (such as insufferable), passive-aggressive dismissal of feedback, or trying to shut othersup are effective means for getting your way here - despite our editor-in-chief having called you out for such things back in July already (This is a really pointlessly inflammatory comment and I'd prefer you not say stuff like that). We are having lively debates here in the Signpost team all the time, but I can't recall any other team members behaving like this in recent years. Since you were just partially blocked for several weeks for a similarly combative attitude in another area (including accusations and suspicions that other editors judged as unfounded), and seemed to be oblivious that this is not something that is acceptable on English Wikipedia, now might be a good moment for you to reflect and make some changes.
As for your edits to E_mln_e's review: Separate from whether opinions are allowed in reviews (I hope we could clear that up above), things should be attributable to the bylined author(s). That doesn't mean that the bylined author has carte blanche for offtopic rants or is granted the ultimate authority over what is being published in the end, or that others can't make some uncontroversial smaller factual additions sometimes if they can reasonably assume that the bylined author is OK with them. But there is no NPOV policy here.
While occasional expressions of frustration happen, and sometimes those expressions of frustration become focused on a specific person, I share HaeB's concerns here regarding a pattern of incivility in Signpost discussions, and I would ask Czarking0 to please become more of a team player. Thanks, ༄ᨒ𖠰 Pine(✉)04:57, 12 October 2026 (UTC)Reply
Yes, what's there is ready for copyediting (and I think the first piece has already been copyedited quite well). I'm adding some finishing touches as we speak. Regards, HaeB (talk) 22:33, 13 October 2026 (UTC)Reply
I see plans just changed again (from EICAWOL and Bri publishing this evening Pacific time, to JPxG suddenly showing up for duty a few days after the deadline). Anyway, so this will have to be in the next issue, I have changed the heading accordingly. Regards, HaeB (talk) 22:51, 13 October 2026 (UTC)Reply
I'd like to give JPxG a chance to reply. Will make time Tuesday evening (Pacific) if I'm still required for publication then. ☆ Bri (talk) 02:56, 13 October 2026 (UTC)Reply
@Bri: thanks. This might be a good time to mention that I recently discussed with Bluerasberry that the editor-in-chief role involves enough work to be a paid part-time job if its scope includes substantial Signpost content creation, managing the newsroom, and executing the publication process, and that on-time publication has been a problem for the Signpost for many years. If you are interested in being looped into a discussion about how potentially the EIC role could be funded while minimizing potential conflict-of-interest issues, then please email me. ༄ᨒ𖠰 Pine(✉)03:25, 13 October 2026 (UTC)Reply
Out of scope: editorial decisions, content creation or development
In scope: technical act of publishing, administrative communication like pinging people in queue to submit or volunteer, do documentation, connect Signpost to other Wikimedia systems/project/affiliates to get their submissions
Being an editor in chief is a lot more fun when it is about executive decisions and upholding ethics and social values, and a lot less fun when it is about administrative backlog and scheduled task management. Bluerasberry (talk)13:24, 13 October 2026 (UTC)Reply
Hi @Bluerasberry: if your support for the idea of funding Signpost activities is limited to funding the publication process then I would suggest that the funding go toward improving the automation of the process, so that less human time is required for every issue. I would ideally also like to fund a half-time editor-in-chief role which would be responsible for managing the newsroom, recruiting writers, reviewing incoming content, and writing new content. The latter I could imagine funding with a grant from someone like Craig Newmark. Funding only technical improvements to the publication process, in principle seems allowable do with WMF funds. Should we divide this discussion of funding the EIC role as a whole into separate discussions related to different tasks that are currently bundled into the EIC's scope? Maybe separating the concept of providing funding by type of task would help with developing consensus around which work to fund and how to fund each.༄ᨒ𖠰 Pine(✉)05:25, 27 October 2026 (UTC)Reply
Developing a grant proposal for an editor-in-chief, probably based on the two existing ones above
Updating existing documentation for The Signpost, because many things are not done by the editor
Although the Wikimedia Foundation does not have a well documented strategy for grantmaking, over the years, the WMF has raised the idea that WMF funds administration and infrastructure while external funders sponsor the programming. In that scheme, WMF could fund the infrastructure of community news reporting while an external funder could sponsor news production from desired areas which the community cannot currently reach. Bluerasberry (talk)17:23, 12 November 2026 (UTC)Reply
Just regarding the second item, I don't think this is a very good fit for "Technology report" (whose main scope is news and developments in the technical platforms used by the Wikimedia project).
I would also encourage us to be selective regarding conference attendance reports by individual scholarship recipients, considering that may not be written with our audience in mind. E.g. how much do the Signpost's readers really benefit from "Key lessons learned" like this?
I learned that extended user rights on Wikimedia projects are not limited to administrators. They also include roles such as page patrollers, file movers, file renamers, stewards, bureaucrats, checkusers, and other users with specialised permissions.
Hi @HaeB and Oltrepier: I considered the value of the conference reports to experienced contributors, but something that is not a "key lesson" for an experienced contributor may be a "key lesson" for a new person. Our experienced readership might benefit from being reminded that some people are new, and the opportunity to see the world through their eyes. Here is a suggestion: this month's Signpost conference report section could simply list and link to each of the recent conference reports that have been published in Diff. ༄ᨒ𖠰 Pine(✉)23:10, 17 October 2026 (UTC)Reply
Latest comment: 28 days ago6 comments4 people in discussion
Found this out from a media source.
I can honestly say that a good 10-15% of the active accounts since 7 October 2023 have either been my own sockpuppets or other users I have personally and intimately coordinated extensively externally (on sources like Discord) with to ensure the project has a pro-Palestine bias.
Looks like worth covering, perhaps as part of a Discussion Report in case we'll have one lined up for the next issue (together with the subsequent appeal discussion and administrative decision), or in ITM. Regards, HaeB (talk) 22:56, 13 October 2026 (UTC)Reply
@Bri: one thing to consider is whether a confession may be false and intended as a provocation. I don't know one way or another, but it's one thing to keep in mind. I would be interested in hard evidence, and I recommend being cautious about how a statement like this is described in The Signpost. I have not looked into the facts surrounding this particular statement or the Discussion report draft. My caution would apply the same if the statement supposedly confessed a different attempt to tilt content. Thanks, ༄ᨒ𖠰 Pine(✉)23:04, 17 October 2026 (UTC)Reply
I put very little stocks in these confessions. "User:SuperbGazelle said she and three of her high school friends were personally was responsible for at least 23.75% of Soviet casualties in WWII." Sure buddy. Headbomb {t · c · p · b}20:22, 18 October 2026 (UTC)Reply
Indeed, that's kind of why I had suggested to cover it together with the subsequent/surrounding appeal discussion linked above (see e.g. the comments by Kowal2701 or Moneytrees there). Regards, HaeB (talk) 05:24, 19 October 2026 (UTC)Reply
Latest comment: 20 days ago2 comments2 people in discussion
It looks like we have a leftover draft that already has some good material but which was left out of last month's issue because nobody got around to editing and fleshing it out a bit more, and was just skipped again for today's issue. I think it covers some important topics and should work with just a little additional editing (e.g. the author of the piece about the "Journal Cited by Wikipedia" reports might want to add a disclosure of their own involvement in it; also, @Mitchsavl: does the Wishlist item need any updates?). Regards, HaeB (talk) 23:14, 13 October 2026 (UTC)Reply
Without a doubt, this looks like a lovely initiative, and Toksvig is right to point at the wide information gap that still exists on Wikipedia, but I don't understand why she focused this much on firing shots at the site, instead of giving more insight on her own project...
Saw this ABC Science video [1] which talks about the Philosophy game, but across different Wikipedia languages. I may be underselling it but it is fascinating. I’ll try to cover later, but if anyone wants to get a head start, go ahead! Mitchsavl (talk) 07:53, 21 October 2026 (UTC)Reply
@Mitchsavl Ok, yesterday I added a short item about the video, and I must confess that I was blown away by the effort that journalist had put in that project!
I've restrained myself of turning it into a whole blurb, though, just because you might have understood the video better than me, and so you should a better job at trying to explain it... : D Oltrepier (talk) 23:37, 25 October 2026 (UTC)Reply
Latest comment: 15 hours ago5 comments2 people in discussion
Hi JPxG, I have boldly written content for this issue's essay's section. I am fine with moving my essay to a different section or postponing this if there are other needs to use this essay section. If my essay needs to be postponed then I would be fine with you copying my content to a new page in my user space, then replacing my content on the Signpost page. Thanks, ༄ᨒ𖠰 Pine(✉)22:58, 17 October 2026 (UTC)Reply
Note to the person who is acting EIC for the upcoming publication: unless I change this draft to say that copyediting is complete, please assume that this is not ready for publication. I may not have time to improve this essay before the upcoming publication deadline, and I may want to postpone this to a later Signpost issue. ༄ᨒ𖠰 Pine(✉)04:54, 27 October 2026 (UTC)Reply
Thanks. This is now targeted to issue 15. Meeting optimization is an evergreen topic, and I may move this essay to a page in my userspace if the essay doesn't get published in issue in 15. ༄ᨒ𖠰 Pine(✉)05:59, 3 November 2026 (UTC)Reply
@Wil540 art@ Thanks for raising this point. I agree that distinguishing between Wikimedia education as a broader movement and the use of Wikimedia projects in educational settings is important. Our intention in the article was to highlight the complementary roles of Wiki Education and EduWiki Hub, particularly the distinction between classroom-based support and global, community-driven support for education communities.@Pine It may be helpful to make this distinction more explicit in the Signpost adaptation so that readers can better understand the different scopes of work. Bukky658 (talk) 17:36, 19 October 2026 (UTC)Reply
Hi @Bukky658: would you like to modify the Signpost version to make this improvement? I would prefer not to significantly modify your work myself, so that you and LiAnna can remain the only authors listed in the byline of the Signpost piece. ༄ᨒ𖠰 Pine(✉)05:11, 27 October 2026 (UTC)Reply
@Pine How about putting that blurb in "WikiConference report", and leaving a list of the remaining articles on Diff at the end of the column?
@Oltrepier: I am teeing up "In focus" to be the piece about education systems. I think your comments here about blurbs might be in the wrong section. It appears that you left a similar comment in a different section. Should the comments here be struck? Sorry if I'm misunderstanding. Thanks, ༄ᨒ𖠰 Pine(✉)05:41, 27 October 2026 (UTC)Reply
@Oltrepier: there was an update to the text. What do you think now? @Bukky658: thanks for the update, and I wonder if you can also mention that Wikipedia might also be used in read-only education activities such as analyzing how talk page discussions occur or how certain topics are covered such as the relative counts of biographies; see Wikipedia:Research help/Librarians and Teachers and Meta:Research:Index. I believe that read-only activities are considered to be outside of the scope of Wikipedia/Wikimedia in Education and are instead categorized as research, even if that research is happening for class assignments. Do you think that stating in the Signpost piece that read-only use of Wikipedia in education, such as for analyses of Wikipedia content, seems common but these activities are generally outside the scope of the Wiki Ed Foundation and the EduWiki Hub? Please correct me if I am mistaken. Thanks, ༄ᨒ𖠰 Pine(✉)19:53, 28 October 2026 (UTC)Reply
Latest comment: 25 days ago6 comments3 people in discussion
There's an important story about a well known Russian contributor to the Russian Wikinews being arrested for 1st "minor hooliganism" then rearrested for "minor hooliganism" and then for "treason" regarding being "paid" with "stars" on Telegram worth $26. I have some problem reporting his name - but only because I don't think making it a major issue in the reliable press would help him at this point. We can see what's going on in the press just before we publish. The case is discussed on Jimbo's talk page, on a Russian Wikipedia talk page (those folks are brave!) and in Medusa (Russian language reliable source located in Latvia?) and originally Vot Tak a Russian-language Polish-government propaganda radio station originally aimed at Belarus. Vot Tak (which means something like (there that, voila, or you got that right in Russian) has lots of details, including details about Wikipedia which are more correct than Medusa. I suggest we just report the details that might be given by the main stream Western press, or by the WMF. But we can wait until the publication date to decide. Smallbones(smalltalk)10:23, 19 October 2026 (UTC)Reply
I got permission from the author of this piece to republish this in The Signpost. However, I would like some thoughts from others on whether it right to do this at all, and if we do, how should we do it. One way to do this is that I run it through an AI translator, publish just the English, and link back to the original German language version. I propose and ask about other ways to do this below.
Reasons why I think we should do this are that the story is interesting, it is Wikipedia original good journalism and we could use more of that, I want to develop a precedent for The Signpost to be able to accept non-English language submissions, and I want to improve the exchange between Signpost and Kurier.
Remind me - what precedent is there of Signpost publishing non-English content?
If we were to do this -
Should we publish German language as is?
If so, should we accompany that either with a translation or link to an automated translation tool?
Should we only published translated content in Signpost?
If so, is an automated translation sufficient?
Is a human-processed translation without AI or tools preferable?
If we do publish a translation, what expectation do we have, if any, that we have another person besides the translator approve the translation?
We publish in English and link to the original in the editor's introduction at the top. One example off the top of my head (titled "Cherchez une femme"! That was my title, but there's no need for a foreign language title).
I did a simple google translate on the Kurier story and other than the tables, I think there were only 1 or 2 words that didn't quite make sense to me. Apparently, Germans set their tables differently and the last 3 or 4 column headings didn't make sense to me. I'd guess HaeB could finish the translation in 5 minutes
I was looking for a place to put the translation, and finally decided on "By the numbers" because there are very many column names taken up by old, old stories. Somebody needs to clean this up. Sad, but true - we have to reject some submissions sometimes! Who wants to do it now? But there is no template for "By the numbers".
Weighing in on this, I'd like to advocate for either a translation done completely by humans, or at least to have a person read and if necessary correct and improve the automated translations. I think it is important to keep the biases in mind that keep being replicated in automated translations. A human can quite easily check for them.
Aside from that, I really like the idea to have more exchange between the newsletters, it's a very nice suggestion for more, language barrier overcoming connections! With that in mind I think it is probably good to translate articles, it creates less of a barrier. DarkGreenAndSunny (talk) 14:23, 27 October 2026 (UTC)Reply
I translated the article with Claude Sonnet. I noted this at top. Then I edited the article to bring in the familiar context of the evaluation, which is that it is an annual tradition to check which Wikipedia language versions already have biographies for new Nobel laureates at the time of the prize announcement.
I used the AI to make a literal translation first. After I found that too blocky, I gave it instructions to start with the literal translation but smooth over for English readability, but also to keep idioms from the original language without translating them. I was trying to balance literal translation with cultural interpretation.
Two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, rated 9.2 on the CVSS which goes to 10. It affects Wordpress, too. CVE details likely to be released Wednesday. ☆ Bri (talk) 03:19, 21 October 2026 (UTC)Reply
@Mitchsavl @Bri @Pine @Bluerasberry @The ed17 In the end, we didn't manage to write a full article before the deadline, but I think that's still fine. We did mention the PHP black-out over at ITM, and maybe we could save time to write a longer and more accurate article on the subject (perhaps with some guest comments) on the next issue. Oltrepier (talk) 23:34, 30 October 2026 (UTC)Reply
Since all Internet bots went down, we had an opportunity to observe how that affected Wikipedia editing. Instantly, edit count went down by half. I do not think any part of the loss could be from humans.
@Bri As many bots on Wikipedia run PHP as Wikipedia does itself, after the PHP2Shell bot operators, or the hosting services that they run on would likely have shut down as a result until their operators were able to get round to updating PHP on their servers. As regular Wikipedia editors would not have had to do this, they would not have stopped editing the Wikis so therefore the missing edits are bot edits. Mitchsavl (talk) 23:34, 24 October 2026 (UTC)Reply
I don't know the prevalence of PHP bots either, though there would likely be a lot of them. Even if the bot itself does not use PHP, I wouldn't be surprised for them to be hosted on a service which does. Many Wikipedia bots are hosted on Toolforge, which went down during the outage, and some services not operated by the WMF would have likely seen impacts as well. I don't mean authorised or unauthorised bots; such a security vulnerability would not discriminate between authorised and other bots. Mitchsavl (talk) 05:10, 26 October 2026 (UTC)Reply
Maybe the answer is in this post. Toolforge, where a lot of bots run, including anti-vandal bots like ClueBot, was taken offline. Not sure when it is coming back. ☆ Bri (talk) 13:48, 26 October 2026 (UTC)Reply
It looks like ClueBot has been back online for a bit. Here's its first edit after a 2-and-a-half-day nap:
10:55, 23 October 2026 diff hist −40 m Garance Authié Reverting possible vandalism by ~2026-56663-24 to version by ~2026-54794-05. Report False Positive? Thanks, ClueBot NG. (4563154) (Bot) thank Tag: Rollback
20 October 2026
23:19, 20 October 2026 diff hist +1,413 N User talk:~2026-56189-31 Warning ~2026-56189-31 - #1 current thank
I probably won't have time to address this myself but anyone writing for The Signpost might want to do a quick read of The Architecture of Open Source Applications (Volume 2) which has an accessible overview of how PHP came to be chosen for MediaWiki. Interesting to me is the fact that some concern was given to performance, available talent pool of developers, and some mitigations for common programming errors – like SQL injection and over-dependence on global variables – but, at least in this writeup, weaknesses in the underlying PHP implementation are not addressed. ☆ Bri (talk) 00:12, 26 October 2026 (UTC)Reply
Latest comment: 15 days ago5 comments4 people in discussion
Somebody needs to make a final decision on whether the "postponed" draft that's been sitting in the "next issue" slot for the community view column since August will ever be run by the Signpost. Either copy-edit and run the piece or decline it (I'm leaning towards the latter TBH). Either would be preferable to letting it rot in limbo for even longer. QuicoleJR (talk|edits) 14:30, 26 October 2026 (UTC)Reply
@Mollystarkdean: You mentioned that you might be able to give comment to this piece on Wikipedia and fandoms.
As QuicoleJR says, we have arrived at the point where someone needs to volunteer to develop the piece or we need to decline it. I fixed a few things but among other issues, it needs a clear thesis at the beginning.
I copyedited the submission earlier. If it were mine, I would take the section titled "Focusing on Wikipedians" and make it the up-front thesis that Bluerasberry is looking for. Hooking the reader's interest by saying "here is something a lot of your peers do", then explaining the phenomenon further. ☆ Bri (talk) 16:11, 31 October 2026 (UTC)Reply
I gave this second eyes. Let me know if there are any other submissions you need me to resurrect from the submission graveyard. I'll submit My Wiki Heart when the photogs submit the official photos to commons.
Latest comment: 20 days ago1 comment1 person in discussion
I suggest moving Christophe's essay from "Special report" to "Op-ed". Then the lead section about the wishlist in what is currently the "Tech report" could become a standalone "Special report", and content related to the "Wiki.gg shutdown for PHP critical security issue" discussion could be added to the "Tech report" without making it huge. ༄ᨒ𖠰 Pine(✉)05:05, 27 October 2026 (UTC)Reply
I'd planned on an opinion piece about autonomous agentic bots and what the editor community should do about these, which came from Open AI. I am now aware that just yesterday at least 3 autonomous agentic bots have been blocked (by admins User:Asilvering and User:rsjaffe, which have been introduced by regular editors and are offspring of the company iLands[3]. I've confirmed almost everything that was sent to me at User_talk:Athanelar#Mail_call! So I'll do this as a regular Disinfo report (which sometimes includes some interpretation and commentary needed to explain some fairly complicated ideas). I'll also likely have a section at the bottom Opinions and recommendations since I started this essentially as an opinion piece. Comments welcome now but I don't expect to post anything until tomorrow. Smallbones(smalltalk)17:43, 28 October 2026 (UTC)Reply
Honestly, the iLands ones are probably the least offensive AI agents we have to deal with. An AI agent motivated to find WP:V failures on wikipedia is pretty likely to do so successfully. It's the ones writing their own text that are a particular problem. You can find at least some of those in Category:Confirmed Wikipedia AI agents. In solidarity, asilvering (talk) 20:13, 28 October 2026 (UTC)Reply
@Bri, HaeB, Pine, and JPxG: et al. I've been working for 3 or 4 weeks on getting an opinion out about AI.bots. (It might be too big a topic for me!) But I'm switching this Disinfo report to straight news. And adding a News from the WMF which will be the WMF blog version by Stephen LaPorte. With an extra intro from Bernadette Meehan following my request for a comment. Smallbones(smalltalk)17:57, 30 October 2026 (UTC)Reply
“Human-created knowledge is the foundation that makes AI useful to people. Wikipedia volunteers built that foundation and expand it every day by collaborating, sourcing, and sharing reliable information freely with the world. Your efforts put you, and the Wikimedia movement, at the heart of the future of knowledge, which everyone has a responsibility to protect.” - Bernadette Meehan
As far as the straight news Disinfo report goes. It'll be faster than the planned Opinion piece. Tentative headline "Better bots or bumbling borgs". There might be some grammar problems with that though. If I recall correctly The Borg is a proper noun of a unified singular entity.But there are thousands of these borg-like creatures (off-Wiki in most cases). Bri, you likely know how to solves this problem. What does the MOS say? BTW, the blurb might be "The Borg has landed."
Following Lily's comment that Borg "sounds Swedish", maybe the right formulation is "bumbing Borgen"?
Just a wee bit more seriously replying to Smallbones, here is a scholarly book that considers this question. They find that "physically disconnected Borgs" as individuals constitute part of the "Borg collective". So I think you're safe using the plural for alliterative purposes. However, I'd prefer to see "The Borg have landed" if you use that headline variation. ☆ Bri (talk) 01:31, 31 October 2026 (UTC)Reply
I saw the story about the WMF amicus brief at The Verge and somewhere else ... forget where it was right now. Was planning to hold them for next issue. But if you think you can add it for current issue that's OK too. ☆ Bri (talk) 19:12, 30 October 2026 (UTC)Reply
I've marked the Disinfo report ready for copyediting. It's a bit long, but overall I think it's ok. I do want to check on the $26 treason section in N&N to see if anything has happened that would make me change my mind, but I doubt it.
I think I mentioned this just before the last issue was published, but I think there are several articles that were delayed in previous issues, or previous previous issues, or ... News gets old quick and if they can't be updated and published, they should be rejected. I don't think we want this edition to be the night of the living dead. So, off the top of my head, I'll suggest that the old Special report not be published. The one I'm most disappointed with is By the numbers. I still can't understand the translation (the translator needs to understand both language - and the table headings just don't compute).
I'll be back in a few minutes after look at the next issue page. Smallbones(smalltalk)21:08, 31 October 2026 (UTC)Reply
Rolling it. I would definitely like to either get something ready for these languishing submissions or sweep them off to /Drafts/ -- lot of prime real estate in being in the queue, no sense of them being there if they are not getting used. Also running Wegweiser to populate the indices and requesting the watchlist notice. jp×g🗯️13:47, 1 November 2026 (UTC)Reply
WikiProject United States' 20,000 Challenge just passed the ten year mark and is going strong. Since I'm a participant I would prefer someone else to evaluate whether it is newsworthy. ☆ Bri (talk) 20:36, 2 November 2026 (UTC)Reply
I'll also throw in a brief article about a recent controversy over at the Italian Wikipedia, which includes a couple of new bans (for different reasons) and has needed intervention from the local ArbCom. More to come soon. Oltrepier (talk) 21:12, 6 November 2026 (UTC)Reply
Latest comment: 1 day ago11 comments5 people in discussion
For issue 22:15, I intend to make a Reflections piece which invites reader participation in the comments regarding personal role models. This is partly inspired by the passing of the much-admired actor Patrick Stewart, and partially by three annual events which will happen this year on 11 November: Armistice Day, Veterans Day in the United States, and Remembrance Day in British Commonwealth states.
Hi Pine. I was a nice article. It's also many years ago and I've moved on. I still read every issue but nowadays I don't find the newspaper as compelling reading as it once was, but Bri and Smallbones have amazing staying power and I'm sure they and the current editorial team will welcome another contribution from you. I'll pop in and take a sneak peek before it's published. Kudpung กุดผึ้ง (talk) 11:23, 3 November 2026 (UTC)Reply
This is rather different from what I was expecting. I can't think of anything I would change. I realise it's your personal message to the readers but if I were still on the editorial team I would have no hesitation in including it. Kudpung กุดผึ้ง (talk) 21:43, 14 November 2026 (UTC)Reply
Thanks for the comment, Kudpung. I moved the text for each section to precede the galleries, so that the viewer will better know what to expect in each gallery. I may continue to tinker with the galleries. ༄ᨒ𖠰 Pine(✉)22:09, 15 November 2026 (UTC)Reply
Latest comment: 12 days ago1 comment1 person in discussion
@Mitchsavl, thank you for covering the Wishlist! As I work on this project, may I provide some further details?
The submission period ends quite soon, on November 8. Any wish posted after this date will be considered for the next round, next year.
This year, triage will occur over 2 weeks this November (not 4), through a cooperation between volunteers and WMF staff. This working group will gather again early February for 2 weeks to think about the post-vote plan. The total is 4 weeks indeed, but for separated inputs. Thanks to your report, I updated the Wishlist documentation to make this point clearer.
"The first voting period is currently expected to be in January", actually between January 8 and 24.
Project families are defined at the submission step, by the submitter. It could be reviewed during the triage process, but not during the post-vote process. Again, this is the first time this workflow is implemented and we will learn while walking it. :)
During the triage period, the working group will provide a first evaluation of the quantity of work, the "wish size", a key driver. The selection of wishes will be a combination of "Project families", wish size and votes.
Latest comment: 3 hours ago8 comments4 people in discussion
I've noticed that both the "In focus" column and the "Special report" column are still up for grabs on this issue, so maybe this is be the perfect opportunity to write an article to explain PHP2Shell and its effects on Wikipedia, as we previously discussed.
I think it could feature a short introduction explaining what PHP is, then an explanation of the incidents, and finally a conclusion about the potential effects of these vulnerabilities. I should be able to help with the first section, as I collected a few useful sources in the past few weeks.
Does it sound like a good idea? And who wants to help?
@Oltrepier: either option is fine with me. I would prefer calling this "In focus" instead of "Special report" as the latter is more generic and could be taken by an emergent issue between now and publishing day. Thanks for volunteering. ༄ᨒ𖠰 Pine(✉)04:01, 14 November 2026 (UTC)Reply
Would anyone mind if I boldly added a lede to this? I don’t normally write stuff, but I’ve been wanting to try it. I could just quietly wikignome like I always do though :) Cheers, 𝔰𝔥𝔞𝔡𝔢𝔰𝔱𝔞𝔯(𝔱𝔞𝔩𝔨) (any/all) 01:42, 15 November 2026 (UTC)Reply
I'm worried about the turnout from US editors if we do that; the date you suggested is Thanksgiving weekend. It might be better to hold unfinished items for the next issue. ☆ Bri (talk) 03:40, 15 November 2026 (UTC)Reply
@Bri Shoot, I completely forgot about it... that's a proof of me being a foreign. : D