User talk:Knightoftheswords281

It is approximately 6:57 pm [refresh] where this user lives (Greater Houston, Texas, United States)

This is Knightoftheswords281's talk page, where you can send them messages and comments.

Add new text under old text.
New to Wikipedia? Welcome! Learn to edit; get help.

Start a new topic

Pre-2023: 2020 2022

2023: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2024: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2025: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2026: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

This page has archives. Topics inactive for 30 days are automatically archived 2 or more at a time by if there are more than 4.

It is approximately 6:57 pm [refresh] where this user lives (Greater Houston, Texas, United States)

May 2026

Hello, I'm OneReaction5890. I noticed that one or more of your recent contribution attempts to Talk:2024 Lebanon war have been disallowed by an edit filter as they did not appear constructive. If you only meant to make test edits, please use your sandbox for that. If you think I made a mistake, or if you have any questions, you may leave a message on my talk page. If you believe the edit filter disallowance was a false positive, please report it. Feel free to ask for assistance at the Teahouse whenever you like. Your history seems to me clean otherwise. I don't know, I just look at Special:AbuseLog time to time and saw your username, so I don't think you intended this. Have a good day otherwise! | One Reaction was here. Got a complaint? 18:50, 11 May 2026 (UTC)[reply]

Hello. This is a message to let you know that one or more of your recent contributions did not appear to be constructive and have been reverted. Please take some time to familiarise yourself with our policies and guidelines. You can find information about these at our welcome page which also provides further information about contributing constructively to this encyclopedia. If you only meant to make test edits, please use your sandbox for that. If you think I made a mistake, or if you have any questions, you may leave a message on my talk page. Edit warring, repeatedly reverting significant grammatical and organizational changes on Chud The Builder -- HungryHighway🛣️ 05:42, 16 May 2026 (UTC)[reply]

WP:DTR, but also the onus is on you and Ell22Moore (talk · contribs) to include these sweeping, massive changes to the article. Furthermore, nothing has been reverted HungryHighway (talk · contribs). — Knightoftheswords 05:48, 16 May 2026 (UTC)[reply]

I have re-organized and fixed many grammatical, spelling, and punctuation errors that you have reverted back to multiple times 1 2. If you keep up the disruptive editing we will be tagging an administrator to deal with it. -- HungryHighway🛣️ 06:47, 16 May 2026 (UTC)[reply]

Please stop your disruptive editing.

If you are engaged in an article content dispute with another editor, discuss the matter with the editor at their talk page, or the article's talk page, and seek consensus with them. Alternatively you can read Wikipedia's dispute resolution page, and ask for independent help at one of the relevant noticeboards.
If you are engaged in any other form of dispute that is not covered on the dispute resolution page, seek assistance at Wikipedia's Administrators' noticeboard/Incidents.

If you continue to disrupt Wikipedia, you may be blocked from editing. You added uncited claims in the article Chud The Builder, added promotional content that editors on the talk page reached a consensus that was unnecessary. This is also your third reversion of constructive edits within 24 hours. -- HungryHighway🛣️ 16:54, 17 May 2026 (UTC)[reply]

Please do not attack other editors, as you did at Wikipedia talk:Manual of Style/Biography. Comment on content, not on contributors. Personal attacks damage the community and deter users. Please stay cool and keep this in mind while editing. Thank you. ~~ AirshipJungleman29 (talk) 17:20, 31 May 2026 (UTC)[reply]

Please stop attacking other editors, as you did on Wikipedia talk:Manual of Style/Biography#Inconsistent Handling of Chosen Names “Slave Names”. If you continue, you may be blocked from editing. Comment on content, not on other contributors or people. Accusing others of editing for "slacktivism points" and calling other editors "ignorant," and declaring that "no one cares" about the topic being discussed, is not acceptable. Despite his canvassing, which he has apologized for, your labeling of zaydupree as "deluded" and a "race hustler" is also not appropriate. Additionally, your usage of the outdated terminology "blacks" may be interpreted as racially insensitive. For these reasons, another editor has reverted your RfC closure; please do not attempt to reinstate it. Royz-vi Tsibele (talk) 17:36, 31 May 2026 (UTC)[reply]

@Royz-vi Tsibele: Sorry but I don't entertain this idea that zaydupree is not a race hustler. Anyone who engages in unironic "slave name" discourse is very clearly ignorant about the topic at hand since the term is completely bogus. Slaves were not given the dignity of having surnames; virtually all slaves had none or were at best referred to by their master's surname like Nat Turner. This was part of the dehumanization campaign. Surnames were adopted following emancipation and were largely chosen by the ex-slaves with nominal connections independent of their masters. It even says this in our own article regarding the topic. So definitionally, treating the term "slave name" as a term to refer to names following emancipation is definitionally ignorant, not even in a pejorative way.

Given btw that aside from the race warrior content, zay is mostly known for being a linguistics guy, I especially doubt that he's entirely doing this in good faith. He's part of the same clique on TikTok that try to act like warriors on behalf of all blacks (whose offensiveness depends far too much to make a blanket implication of me being insensitive) by like crucifying people with cotton plants in their homes (actual movement on there). This to me is on the same level of entertaining Tommy Robinson-esque talking points. As far as I know, the only real distinction between zaydupree and Chud the Builder is that the latter shot someone and the former academicizes his language. Perhaps as @AirshipJungleman29: implied, "slacktivism" may have been a bit too far per WP:AGF, but I still maintain that this seems like a bunch of nonblack editors attempting way too hard to not appear racist just to appease a gaggle of race warriors online pretending to speak on behalf of all black people (they certainly don't for me, and again, deadnames and """slave names""" are nowhere near comprable). — Knightoftheswords 18:01, 31 May 2026 (UTC)[reply]

@Knightoftheswords281 Your personal opinion on the validity of "slave name" discourse does not matter here. What matters is that you personally attacked, and continue to personally attack, fellow editors on the basis of their character and racial identity, the latter of which you seem to be assuming with no evidence. You have no idea which editors are of which race, and it should have no effect on the validity of their arguments. Decrying an entire group of editors as "ignorant" or "race warriors" is simply uncivil and not how disagreements on Wikipedia should be handled. Furthermore, your continued aggressive attacking of zaydupree is not appropriate; despite his initial canvassing and regardless of his views, the arguments of the editors you disagree with do/should not rely on the personal characteristics of the initial proposer, and as such your continued lambasting is completely unwarranted. Your continued usage of the outdated racial terminology "blacks" is also a source of concern for me, as well as comparing a TikToker to an actual attempted murderer.

I hope you understanding where I am coming from here, and I request that you apologize for your conduct and affirm that you will no longer rely on personal attacks of any kind, whether towards fellow editors or persons off-site. Otherwise, I may have to reach out to admin, although I would much rather not have to do that. Royz-vi Tsibele (talk) 19:26, 31 May 2026 (UTC)[reply]

Your personal opinion on the validity of "slave name" discourse does not matter here; you're right, too bad its not an opinion but fact. Any RS description of "slave names" will only just mention the naming practices used under enslavement, and will sometimes even notice that its a misconception that people "inherited" names from enslaved ancestors. The entertaining of the latter idea is essentially the basis for this whole discourse, otherwise we wouldn't be here. And yes, this does seem to be entertained by several nonwhite folks on this wiki; at least three editors there are white (and I knew these editors beforehand, so this isn't digging), one of whom is mixed (literally named wasianpower, lol), and a frequent point in said discussion was that there weren't too many black people participating. That's just factual observations, not just a personal attack; the only one I ever made was the slacktivism comments which I've retracted. The race warrior comments very obviously referred to the type of people like zaydurpee online, which can only be construed as PAs against other editors if you include the obviously canvassed votes that appear to be the only reason why some analyzed this as "having enough support" to advance this issue.

Again, I maintain that there is no real distinction between guys like this and your average new rightist on Twitter, certainly in the level of damage that will be inflicted on the project if we get bullied into changing guidelines due to agenda-pushing external mobs mobilized by them. We're potentially changing the layout of countless articles all since one guy either doesn't know (as a man most known for being a linguistics guy on TikTok!) or doesn't care that virtually no one alive in America is carrying a "slave name." I mean, one thing that is rly pissing me off is that this is being framed by both him, his followers, and editors like you on here, as being "for black people." Like trans people, women, and blacks are being put on the same level because of deadnaming, maiden names, and... "slave names"? Like is this not obviously ridiculous? People in this man's comments and here are acting like this is some deeply offensive thing to black people as a whole, when I'd say that this is at best an obscure topic that most blacks don't give thought to that much, assuming they're even aware of it.

Listen, I'll apologize for the slacktivism comment, and perhaps for the MOSBIO closure, which was prolly done in haste and with a wee bit too much anger, but I'm not going to entertain this weird exercise in appeasing contrived outrage. Again, I think we're locking ourselves in a dire predicament when we're implementing changes like this based on "one guy on TikTok with an agenda said something." Especially when you consider the fact that most non-Wikipedians are broadly ignorant of the guidelines, which can not only be seen in his videos, but the comments. For instance, one commenter on TikTok stated that Wikipedia only recognizes black peoples' name changes when they're a rapper, since they'll use their stage name, citing Snoop Dog as an example. This is despite the fact that this is incredibly dependent on MOS:SURNAME and varies (see Metro Boomin, Juice Wrld, XXXTentacion as examples). Now imagine if we were revising wiki policy based on that? At the end of the day, I said what I said and apologized for what needed to be apologized for; if that warrants an ANI discussion, than you can try. — Knightoftheswords 20:58, 31 May 2026 (UTC)[reply]

Tech News: 2026-21

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

Weekly highlight

The Abstract Wikipedia team has identified five potential pilot wikis to assess their interest in adopting abstract articles on their wikis. The pilots are Malayalam, Bengali, Dagbani, Arabic, and Indonesian Wikipedia. The feedback period will be open until May 22. If your community is interested in becoming a pilot, let us know on Meta.

Updates for editors

An experiment to show Reading Lists to logged-out readers on mobile web will launch on May 18 across German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu Wikipedias, and will run for one month. The effort supports broader goals of helping readers save and organize articles for later reading, while encouraging habits that could lead to future Wikipedia contributions.
To support a bookmark button in the Reading List beta feature, the "Tools > Action" menu has been updated to display icons, including the watch star indicator that helps editors identify temporarily watched articles. The icons now also match those used on mobile, improving consistency across platforms. The change is currently limited to the actions menu and mainly affects editors with privileged user rights. [1]
Suggestion Mode was released as an A/B test for newcomer editors on the mobile website at ~15 Wikipedias. The experiment will measure the impact that Suggestion Mode has on the proportion of newcomer mobile web edit sessions that result in constructive (un-reverted) article edits. The experiment will also evaluate the feature's impact on editor retention, and monitor changes in revert and block rates.
View all 27 community-submitted tasks that were resolved last week. For example, an issue in the Wikipedia Android app where images could sometimes fail to load after opening a recommended reading list notification, has now been fixed. [2]

Updates for technical contributors

The Wikidata Platform team has published its backend replacement recommendation and accompanying technical architecture for the migration of the Wikidata Query Service (WDQS) away from Blazegraph. Feedback is invited until May 25th 2026, especially on potential gaps and impacts on advanced use cases. Wikidata community members and WDQS users are also encouraged to help identify high-impact tools and workflows that may need attention on this page. Feedback can be shared on the Migration talk page or during the next office hour. See the WDP team newsletter for more details.
Detailed code updates later this week: MediaWiki

In depth

On English, French, Japanese, and a few other Wikipedias, there was a trial of hCaptcha, a third-party bot detection service. The trial showed that hCaptcha effectively detects and deters some bad-faith automated activity, on its own and by giving checkusers and stewards signals to look into. Because the results were positive, hCaptcha will be rolled out across all wikis over the next few weeks. See the hCaptcha project page for technical information about the implementation and privacy protections. Learn more.
The latest Community Tech update is now available, with progress across several Community Wishlist initiatives, including Reading Lists expansion from the mobile app to the website, new language support for "Who Wrote That" and the Personal Dashboard, improvements to 3D rendering and Charts, and upcoming work on talk page sorting, audio playback, and editing workflows. The update also shares current priorities, wishlist status trends, and opportunities for community feedback on future focus areas and the Wikimedia Foundation’s 2026–2027 Annual Plan. Read the full newsletter for details.

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

MediaWiki message delivery 20:20, 18 May 2026 (UTC)[reply]

The Signpost: 22 May 2026

News and notes: Offline: Osama Khalid still in prison
He has been imprisoned since 2020 for his Wikipedia edits. A fresh campaign is calling for his release.

In the media: Indonesian editors, you shall return!
And lawspam, may you be away.

Disinformation report: Who is a typical paid editor? Who are their typical clients?
Remember the golden rule!

Recent research: WikiLambda the Ultimate
Does Abstract Wikipedia help fight "One ring to rule them all" solutions for knowledge access - or does it implement one itself?

Traffic report: This is where I'll be, so heavenly, so come and dance with me Michael!
A real off the wall thriller, invincible, can't beat it, or is it dangerous and just bad?

Forum: WikiAnnotate: help us build a dataset of article quality evaluations
A research project to build better automated article assessment tools.

In focus: Demystifying the 2026-27 Annual Plan
A guide to WMF's Tech Annual Plan for the next year.

Opinion: Wikipedia isn't a battleground. So why does it feel like one?
Do we really have to fight?

Serendipity: Wikinews: Into the Wikiverse
The early suggestions for what the wiki could have been.

Special report: Wikimedia Foundation closes Wikinews after 21 years
Displaces 700 active editors among 31 language editions.

Community view: Wikipedia's traffic drop: more on languages and freshness
Which topics are dropping, and is the pattern the same everywhere?

Gallery: Earth Day and Mother's Day
Earth Day was on 22 April, and Mother's Day was on 10 May (in the US and many other countries).

Comix: Brother, can you spare a page?
What would you say?

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 05:16, 22 May 2026 (UTC)[reply]

Tech News: 2026-22

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

Weekly highlight

Following a successful account creation experiment, an improved logged-out edit warning message will be deployed to all Wikimedia wikis in the first week of June. The change will only affect logged-out users on mobile web who open an editing session. The updated experience is designed to encourage account creation more clearly, while still allowing users to edit with temporary accounts. Results from the experiment showed a significant increase in account creation, with a 27% relative lift among users shown the updated message. As expected, as more people funnel into account creation, temporary accounts decreased by a relative 16%. The experiment did not show any significant changes in constructive edit rates or other monitored contributor metrics. [3]

Updates for editors

For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Members of these groups will be unable to disable the last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the next few weeks, users without 2FA will be removed from these groups. Notably, this applies to bureaucrats. See the linked tasks for deployment schedules. [4][5]
WMDE Technical Wishes will run an A/B test on 10 wikis, testing potential improvements for Reference Previews. The experiment will run for ~2 weeks at the end of May / beginning of June and will affect 10% of desktop readers on the participating wikis.
After two successful experiments, the Reader Growth team is rolling out an Image Browsing beta feature for all Wikipedias on mobile on May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta feature will include a carousel of all an article's images at the top of the article, with controls for editors to exclude images from the article's carousel or to exclude an article from the feature entirely.
View all 30 community-submitted tasks that were resolved last week. For example, three dimensional STL files were being rendered incorrectly by the media viewer 3D extension which is now fixed. [6]

Updates for technical contributors

The legacy CSS classes tleft and tright have been replaced with floatleft and floatright as the former do not work consistently across all MediaWiki platforms, notably mobile web and mobile apps. Projects relying on these classes are encouraged to review related usage and plan for migration. Please note that floatleft and floatright may also be deprecated in future, although there are currently no plans to do so. Read more.
Detailed code updates later this week: MediaWiki

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

MediaWiki message delivery 21:50, 25 May 2026 (UTC)[reply]

May 2026 ANI Notice

There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. Royz-vi Tsibele (talk) 22:43, 31 May 2026 (UTC)[reply]

Tech News: 2026-23

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

Updates for editors

The Reader Experience team is conducting an experiment to show the reading lists feature, which is still in development, to logged-out mobile readers to test whether it encourages account creation at a higher rate compared to the watchstar button. The experiment was launched on May 18th on German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu wikis, and it will run for a month.
The Wikimedia Apps team released Phase 1 of the redesigned Home Feed to the Android Beta app. The new Home Feed includes a refreshed "Community" tab and a personalized "For You" tab featuring daily updated reading recommendations. The redesign is part of a broader effort to improve content discovery and create more engaging learning experiences in the Wikipedia apps.
View all 18 community-submitted tasks that were resolved last week. For example, an issue where images could fail to load for some suggested edits on Special:Homepage, leaving the thumbnail stuck in a loading state, has now been fixed. [7]

Updates for technical contributors

Detailed code updates later this week: MediaWiki

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

MediaWiki message delivery 21:07, 1 June 2026 (UTC)[reply]

ITN recognition for 2026 Namhkam Township explosion

On 4 June 2026, In the news was updated with an item that involved the article 2026 Namhkam Township explosion, which you nominated. If you know of another recently created or updated article suitable for inclusion in ITN, please suggest it on the candidates page. Schwede 66 07:34, 4 June 2026 (UTC)[reply]

Tech News: 2026-24

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

Weekly highlight

Wikimedia Enterprise has increased the free usage limits for its API offerings. The monthly request limit for the On-demand API has increased from 5,000 to 50,000 requests, while the Snapshot API limit has increased from 15 to 30 requests per month. In addition, Structured Contents snapshots are now available for free accounts. These changes expand access to Wikimedia Enterprise data for developers, researchers, and organizations using Wikimedia content. [8]

Updates for editors

The refreshed Explore Feed, now called the Home Feed, is rolling out to 50% of users of the Wikipedia Android app. The Home Feed helps readers discover relevant content through two new tabs: Community and For You. The Community tab provides a scrollable feed of curated content and updates from the broader Wikimedia community and movement, while the For You tab offers a full-screen, swipeable experience that shows content tailored to a user's interests. The redesign is part of a broader effort to improve discovery and enhance the learning experience in the Wikipedia app.
The Which came first? daily trivia game is now available in the beta version of the Wikipedia iOS app in English, German, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish. The game uses historical events from Wikipedia's "On This Day" content and challenges readers to guess which of two events happened first. The game was previously released on Android. Communities interested in making the game available in their languages can read the instructions and requirements.
Sub-referencing, a new MediaWiki feature that allows editors to reuse references with different details, will begin rolling out to Wikimedia wikis following a successful pilot phase. Deployment will start on 8 June for most Group 1 wikis and French Wikipedia, with additional Wikipedia language editions receiving the feature over the coming months. Communities are encouraged to prepare by checking for untranslated Cite extension messages in their language and reviewing any use of Reference Tooltips, which may require updates to support the new functionality. Wikis using Reference Previews do not need to take any action. Communities may also wish to create the cite-tracking-category-ref-details tracking category as a hidden category using __HIDDENCAT__ (or a dedicated template), and connect it to the corresponding Wikidata item d:Q129764848. [9]
The Page Previews experiment on mobile web has concluded. The team decided not to roll out the feature after the results showed no statistically significant impact on reader retention, as the primary success metric was retention improvement. Page Previews, which are already available on desktop and in the apps, display a thumbnail, lead paragraph, and link to the full article when readers tap a blue link. The experiment tested this experience on mobile web across six Wikipedias.
The user interface icon library will be updated later this week or next week. Most of the ~300 icons have been slightly refined and ~30 new icons have been added. These changes improve the icons to make them more consistent and comprehensible, and provide more visual balance when they are used in groups.
The Universal Language Selector (ULS) interface in MediaWiki, which helps users select content in other languages, has been updated. The new version improves speed and accessibility, and users of Wikimedia projects can now pin languages for quicker language switching. The deployment to Wikimedia sites will happen gradually in the coming weeks. You can test it now as a beta feature by selecting beta features in your profile preferences and share your feedback on the project page.
View all 21 community-submitted tasks that were resolved last week. For example, an issue where the Pageviews Analysis dashboard on pageviews.wmcloud.org stopped updating graph data in May 2026, affecting all users, has been fixed. [10]

Updates for technical contributors

The function signature for mw.util.addPortletLink() has been simplified. Developers can now pass a configuration object instead of a list of positional parameters when creating portlet links. The previous function signature remains supported for backwards compatibility. For example, instead of: mw.util.addPortletLink('p-cactions', '#', 'Stub', 'ca-stubtag', 'Add a stub tag to this page'); use mw.util.addPortletLink('p-cactions', { href: '#', text: 'Stub', id: 'ca-stubtag', tooltip: 'Add a stub tag to this page' });. Script maintainers are encouraged to review existing uses of addPortletLink() and update them where appropriate. This change will be available on all wikis from 11 June. Thanks to community volunteer Gerges for contributing this improvement. [11]
Community Wishlist discussion: Product & Technology introduced changes meant to increase the number and complexity of wishes fulfilled, including the disbanding of the Community Tech team. They are engaging in discussions about a proposed direction for the wishlist from community members. Includes ways to structure annual voting, better tracking of wishes, removing focus areas, and staffing updates.
Detailed code updates later this week: MediaWiki

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

MediaWiki message delivery 21:28, 8 June 2026 (UTC)[reply]

ITN recognition for 2026 Guinean parliamentary election

On 12 June 2026, In the news was updated with an item that involved the article 2026 Guinean parliamentary election, which you nominated and updated. If you know of another recently created or updated article suitable for inclusion in ITN, please suggest it on the candidates page. Schwede 66 17:29, 12 June 2026 (UTC)[reply]

Tech News: 2026-25

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

Weekly highlight

The Reader Growth team has launched an Image Browsing beta feature on the mobile web version of all Wikipedias. The feature shows an image carousel at the top of articles with 3 or more images. Editors can configure this feature with the following controls: to hide a specific image from a page, either use class=notpageimage excluding it from thumbnail previews, or class=noviewer excluding it from MediaViewer. The carousel can also be disabled from a page entirely, with the magic word __NOMEDIAVIEWERCAROUSEL__. To submit feedback or flag bugs, please visit the project page.
Wikitables can now be sorted in descending order on the first click by adding data-sort-order="desc" to the header cell. Previously, by default, clicking a column header for the first time sorts it in ascending order. This addition to a Wikitable gives it more control and flexibility, while the default behavior for subsequent clicks remains unchanged. [12]

Updates for editors

The Article guidance feature is currently being tested with some editors creating new articles on the Simple English, French, and Turkish Wikipedias. The experiment will soon begin on the Arabic and Bangla Wikipedias as well. This feature gives editors community-curated guidance to help them create articles that follow community standards. Experienced editors can continue creating or adapting outlines for specific article types that are commonly created by less experienced contributors. The outlines guide less experienced editors in creating high-quality articles. A quick guide to markups used in outlines can be found on this page. Example outlines that can be adapted and instructions for how to adapt them are on this section of the project page.
Wikis that wish to replace the "indefinitely" button in Special:Block for temporary accounts (for example, wikis that block temporary users only until account expiration) will be able to do so by creating MediaWiki:ipb-indefinite-expiry-temporary-account with the block duration they want. [13]
View all 41 community-submitted tasks that were resolved last week.

Updates for technical contributors

By the end of June, a valid user-agent string will be required for automated dumps downloads from the dumps.wikimedia.org website. Automated requests that provide a generic or empty user-agent will be blocked. This extends enforcement of the long standing user-agent policy. Access to dumps through Wikimedia Cloud Services will not change.
The roll out of global API rate limits is now complete, with limits enforced across all APIs and at the documented levels for all groups. Bots running in Toolforge/WMCS or with the bot user right on any wiki remain exempt. All bots should continue to follow the documented best practices to avoid being rate limited.
The API Portal wiki will be read only starting this week (June 15-18). The following week (June 22-25), all API Portal wiki URLs will redirect to Wikimedia APIs on mediawiki.org. Learn more on the project page.
Detailed code updates later this week: MediaWiki

Meetings and events

On June 17th at 6pm UTC the WMF will be holding Discord call focused on a code review. We've heard through the Developer Satisfaction Survey that volunteers are struggling with code review and we'd like to discuss these experiences with the goal of surfacing workable solutions. You can join the call via the Wikimedia Community Discord server.
The Latin American Wikimedia Conference will host a regional hackathon that will bring together the Wikimedia movement’s technical community including developers, system administrators, data scientists, and users with extended rights. Interested technical contributors can apply for a scholarship to participate until June 21 at midnight (Bolivia time, UTC-4).
Sign up for Wikimania Team Challenges to join this special event. The Team challenges will take place online and in person from July 21 to 22, before Wikimania conference. Everyone is welcome, regardless of skills or Wikimania registration. Teams will work on 10 important challenges supporting the Wikimedia community. For details, visit the Team Challenges page and register there. Registration closes on June 20th at 11pm UTC.

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

MediaWiki message delivery 16:46, 15 June 2026 (UTC)[reply]

ITN recognition for Niño Guerrero

On 17 June 2026, In the news was updated with an item that involved the article Niño Guerrero, which you nominated. If you know of another recently created or updated article suitable for inclusion in ITN, please suggest it on the candidates page. Spencer^T•C 06:20, 17 June 2026 (UTC)[reply]

The Signpost: 21 June 2026

From the editors: Ways for beginners to support The Signpost community journalism
Pointing the way to your contribution to The Signpost!

News and notes: Community Tech development team disbanded
And English Wikipedia reaches a milestone in number of highly active editors.

Disinformation report: PR for the people?
Or, "PR using PR for PR"?

Recent research: Proposed tagging system for AI involvement; successful and unsuccessful AI tools for contributors
And other new research publications.

In the media: Who won a 14th century battle and who won the 2026 Iran war?
Media take issue with portrayals of recent and medieval history on Wikipedia. Plus a team supporting Wikipedians gets dissolved, and a few other things.

Community view: Putting the Wish into the Wishlist
A history of the Wikimedia community's request process to Foundation developers.

In focus: A global standard for Neutral Point of View
Wikipedians are commenting on a proposed global standard for neutral point of view.

On the bright side: Flowers, blue helmets, reefs, pride, and Juneteenth
Nice things around the world.

Op-ed: Breathe, Don’t Panic, there is a different story about Wikimedia + AI futures
We can build a strategy about AI that doesn't just center on readers; there are still plenty of humans to write the encyclopedia and work on diverse global knowledge.

Opinion: Wikimedia Foundation staff develop union and Wikimedia user community reacts
Why should editors support the Wiki Workers United union drive? Lessons the Wikimedia movement can learn from other labor struggles.

Technology report: Community Tech team is disbanded, controversy erupts
WMF disbands Community Tech, sparking community backlash over the future of the Wishlist and concerns about unionization.

Traffic report: 'Cause this is thriller, thriller night
Horror movies and Michael Jackson dominate theaters in the lead-up to the World Cup.

WikiConference report: Report of Volunteer Supporters Network Annual Meeting 2026
Outreach staff of Wikimedia chapters host a global discussion.

Comix: Take your turn
In a maze of twisty little edits, all alike.

Humour: Group of banned T-shirt makers comes out of hiding to sell new Wikipedia-themed merchandise
It ain't WikiProject United Nations, but you will find some PUNs.

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 03:18, 21 June 2026 (UTC)[reply]

June 2026

Hello, I'm Jolielover. I noticed that you recently removed content from Wikipedia:Administrators' noticeboard/Incidents without adequately explaining why. In the future, it would be helpful to others if you described your changes to Wikipedia with an accurate edit summary. If this was a mistake, don't worry; the removed content has been restored. If you would like to experiment, please use your sandbox. If you think I made a mistake, or if you have any questions, you can leave me a message on my talk page. The edit summary 'fix' did not adequately explain why you removed 227,000 bytes, so in the future, please add an appropriate edit summary. I assume this was an accidental removal? jolielover♥talk 10:18, 21 June 2026 (UTC)[reply]

No, this was a purposeful (and somewhat WP:BOLD) transfer of content to Wikipedia:Possible off-wiki canvassing by User:Larry Sanger on the advice of a few editors and my own intuition. @Jolielover — Knightoftheswords 10:19, 21 June 2026 (UTC)[reply]

Yeah... just came back to drop my head in shame. Though I disagree with it being moved to a new page, I do now see what you were doing. Apologies. jolielover♥talk 10:21, 21 June 2026 (UTC)[reply]

But I still think the move is quite bold and there doesn't seem to be consensus for it, at least from Wikipedia:Possible_off-wiki_canvassing_by_User:Larry_Sanger#Move_this_discussion_to_its_own_page?. Only 4 people who participated in this discussion. jolielover♥talk 10:23, 21 June 2026 (UTC)[reply]

Given the gravitas and potential precedent of this situation, I think this discussion should be moved into its own subsection for future reference, in addition to the concerns expressed by the users above. I'm restoring the removal on ANI, but if there's enough contestations of the decision, I'm fine with it going back onto ANI. @Jolielover — Knightoftheswords 10:26, 21 June 2026 (UTC)[reply]

Alright jolielover♥talk 10:28, 21 June 2026 (UTC)[reply]

BRD has happened. Please don’t let this turn into an edit war. Morwen (talk) 10:29, 21 June 2026 (UTC)[reply]

Following up here. @Knightoftheswords281, it looks like the move has worked out, but doing it BOLDly is exactly what I avoided by opening the discussion. Consensus has basically been established now, but in the reverse order. The proposal I started should have been given longer, especially for something of this magnitude. That being said, I respect that you went ahead and did it regardless. (By the way for future reference, the sub-page should have included "AN/I" in full after "Wikipedia:". See this.) 11WB (talk) 14:15, 21 June 2026 (UTC)[reply]

"Consensus has basically been established now"

I don't think it is very strong, and don't respect that any of this went ahead. Selbstporträt (talk) 14:47, 21 June 2026 (UTC)[reply]

I was referring to the still open MfD. 11WB (talk) 14:50, 21 June 2026 (UTC)[reply]

To refer to a still open MfD as "basically established" seems unorthodox.

Enough of that. I've made myself clear enough. Selbstporträt (talk) 14:52, 21 June 2026 (UTC)[reply]

"Wikipedia:SANGERGATE" listed at Redirects for discussion

The redirect Wikipedia:SANGERGATE has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 June 21 § Wikipedia:SANGERGATE until a consensus is reached. jolielover♥talk 10:46, 21 June 2026 (UTC)[reply]

I deleted the redirect under criteria WP:G10 as an attack page. Do not create links that attack or disparage people. And if you try any more procedural funny business with the Sanger ANI you're getting blocked till its over. CaptainEek ^{Edits Ho Cap'n!}⚓ 20:26, 21 June 2026 (UTC)[reply]

Created that per WP:FRAMGATE, but I realize that only was created a week later, so yeah, prolly would have supported that. Somewhat irked by the block threat, but it's clear that the move process was a bit of a mess, so I apologize. — Knightoftheswords 21:26, 21 June 2026 (UTC)[reply]

Blocking would not be appropriate as the page split did eventually gain consensus at MfD, @CaptainEek. I will say though, that BOLDly moving it from a large noticeboard before the proposal discussion had finished, was what caused most of the disruption and really should have been handled by somebody with technical experience. It's all done now though, so it ultimately worked out. 11WB (talk) 06:23, 22 June 2026 (UTC)[reply]

You've been trouted.

Whack!

You've been whacked with a wet trout.

Don't take this too seriously. Someone just wants to let you know that you did something silly.

11WB (talk) 06:40, 22 June 2026 (UTC)[reply]

Tech News: 2026-26

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

Weekly highlight

Growth features are now available at Wikidata. This update enables access to Mentorship (if configured), Impact module, the Help Panel, and a simplified Newcomer Homepage (without Suggested Edits). Wikidata administrators are still configuring the features through Community Configuration.

Updates for editors

The special page Special:RangeCalculator has been created. It allows users to find an IP range without needing to rely on external tools. Until now, this tool was only available to CheckUsers. [14]
Sub-referencing is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to most small and medium-sized Wikipedia language versions on June 23. The FAQ lists possible actions to take on your wiki to support the deployment. Check the rollout plan for the next deployment steps. [15]
Starting next week, users will get a notification when they are blocked or unblocked from editing, or if this block changes. [16]
View all 32 community-submitted tasks that were resolved last week.

Updates for technical contributors

Starting next week, abuse filters that are set to "require CAPTCHA verification" will begin to also affect users with the skipcaptcha right, which includes most autoconfirmed users. Bots are exempted. This change only affects edits that trigger an abuse filter. The skipcaptcha right will continue to exempt users from having to solve CAPTCHAs in the ordinary course of using the wikis. [17]
Reference documentation for the Lift Wing API has moved from the API Portal to the interactive REST Sandbox.
The API Portal wiki is now closed. For API documentation, see Wikimedia APIs on mediawiki.org. All API Portal wiki URLs (https://api.wikimedia.org/wiki/) will redirect to the mediawiki.org page starting June 22. [18]
Detailed code updates later this week: MediaWiki

Meetings and events

Join an online call on 25 June at 2:30pm UTC to meet the current Wikimedia interns for Google Summer of Code and Outreachy. Interns will provide an overview of their projects and a brief demo of their work so far. Attendees are encouraged to share ideas and connections in their community.

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

MediaWiki message delivery 13:03, 23 June 2026 (UTC)[reply]