gender-related disputes or controversies or people associated with them
the region of South Asia (India, Pakistan, Afghanistan, Sri Lanka, Bangladesh and Nepal), including but not limited to history, politics, ethnicity, and social groups
Thanks for uploading File:Shrek 2 bronco.wav. 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 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 Article guidance team invites experienced editors of pilot Wikipedias—Arabic, Bangla, Japanese, Portuguese, Persian, Turkish, Simple English, Spanish, and French—to help translate and adapt sample outlines. These outlines will guide editors in creating clear, well-structured, and policy-compliant articles when using the feature once it is launched in May 2026. Simple instructions on how to translate and adapt the outlines are available.
The number of available thumbnail size preferences in MediaWiki is being reduced to three standardized options—Small (180px), Regular (250px), and Large (400px), as part of ongoing efforts to improve performance and reduce strain on thumbnail services. As a result, existing preferences will be mapped to the nearest new size (for example, smaller selections like 120px or 150px will render at 180px, while larger ones like 300px or 360px will render at 400px). The preferences interface will soon be updated to reflect these changes, and users who wish to opt out or provide feedback can do so. [1]
From now on, even when a permission expires automatically, users will receive an Echo notification similar to the standard notification for permission changes. There is a difference between this and Global reminder bot in that the latter reminds users a week before the rights are due to expire, so that they can renew the rights.
View all 32 community-submitted tasks that were resolved last week. For example, the problem where the ULS language selector in Special:Translate would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages. [2]
The Global Watchlist, which lets you view your watchlists from multiple wikis on a single page, continues to improve. For example, watchlists for Wikibase sites such as Wikidata now support EntitySchema elements for better tracking. The Live Updates mode now refreshes the special page every 60 seconds to comply with the updated global API rate limits for improved real-time responsiveness. Additionally, a directionality bug that displayed links as "changes 3" instead of "3 changes" in mixed-direction lists has been fixed. [3][4][5]
Updates for technical contributors
The second phase of global API rate limits has been rolled out to reduce the impact of AI crawlers and ensure fair, sustainable access to Wikimedia resources, prioritising human and mission-aligned traffic. Limits have been shifted from per-hour to per-minute, producing smoother traffic patterns and more predictable API load. Community users are not expected to be affected, and no action is required. Early indications show some User-Agent-based requestors are adjusting behaviour, and around 64% of automated API traffic has been identified. Monitoring continues, and Wikimedia Enterprise remains available for commercial support.
On 13 May, we will start the voting phase. The candidate subpages will close to public questions and discussion, and everyone will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for.
Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
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]
I have re-organized and fixed many grammatical, spelling, and punctuation errors that you have reverted back to multiple times 12. 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]
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 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). — Knightoftheswords18: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. — Knightoftheswords20:58, 31 May 2026 (UTC)[reply]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Community Tech has published new guidance explaining how wishes on Community Wishlist are triaged and prioritized. The documentation is intended to help contributors write stronger proposals by clarifying the factors that influence prioritization decisions. Beyond vote counts, the guidance highlights considerations such as potential impact on the community when determining which wishes move forward.
Updates for editors
The Reader Growth team is launching an experiment to test a new Share Card feature that allows readers to create visually engaging cards from Wikipedia articles or selected article sections and share them online, with each card linking back to the original article to help expand readership and article discovery. The mobile-only A/B test will be available to a portion of readers on Arabic, Chinese, French, Vietnamese, and English Wikipedia to better understand reading and sharing habits, and is scheduled to begin the week of May 18 and run for four weeks.
The Android and iOS Wikipedia apps recently released the 25-day reading challenge into Beta, as part of efforts to drive reader engagement by encouraging users to complete reading milestones. To track their reading streak during the challenge, App users can add a widget featuring Baby Globe to their home screen. The challenge officially begins May 11.
View all 17 community-submitted tasks that were resolved last week. For example, an issue where the global preference for enabling syntax highlighting in wikitext could unexpectedly disable itself after being turned on, has now been fixed. [6]
A missing title error. References show this error when they do not have a title. Please edit the article to add the appropriate title parameter to the reference. (Fix | Ask for help)
A generic name error. References show this error when author or editor name parameters use place-holder names. Please edit the article to include the source's actual author or editor name. (Fix | Ask for help)
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.
Hello, I'm Qwerfjkl (bot). I have automatically detected that this edit performed by you, on the page Chud The Builder, may have introduced referencing errors. They are as follows:
A generic name error. References show this error when author or editor name parameters use place-holder names. Please edit the article to include the source's actual author or editor name. (Fix | Ask for help)
I went through and fixed clutter and organized the article, fixing typos and grammatical errors and improving concision. Why did you roll it back? -- HungryHighway🛣️02:21, 16 May 2026 (UTC)[reply]
I didn't think they were improvements; they had various errors such as spelling and omitted some details I think are key (for instance, why the shooting received coverage). Also, tbf, I don't think the article is long enough to warrant any subsections @HungryHighway. — Knightoftheswords02:24, 16 May 2026 (UTC)[reply]
There were many more errors and filler/clutter in the original text. I've updated to fix a few more issues as well, and removed a few unreliable sources and replaced them with reliable ones. It's long enough and detailed enough to warrant subsections. -- HungryHighway🛣️02:36, 16 May 2026 (UTC)[reply]
Hello and good morning/afternoon. You recently reviewed my DYK nomination for the 2017 Chilean census and mentioned that my QPQ was fulfilled shortly after the nomination, linking to this nomination. However, the qpq for the nomination was this one. I’m asking just to know if a mistake was made from my part, since if that’s the qpq that was actually required for the census nomination, then i miscounted my qpq’s and might be missing a review. R. M. Holda - (talk) 23:15, 16 May 2026 (UTC)[reply]
On 18 May 2026, Did you know was updated with a fact from the article White Bronco chase, which you recently created, substantially expanded, or brought to good article status. The fact was ... that Domino's reported what at the time was its biggest day of sales during O. J. Simpson's white Bronco chase? The nomination discussion and review may be seen at Template:Did you know nominations/White Bronco chase. You are welcome to check how many pageviews the nominated article or articles got while on the front page (here's how, White Bronco chase), 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.
You may prevent the proposed deletion by removing the {{proposed deletion/dated files}} notice, but please explain why in your edit summary or on the file's talk page.
Alcatraz East is still in operation and probably continues to display this car. Could be replaced by a freely licensed image of the same car, failing NFCC #1.
You may prevent the proposed deletion by removing the {{proposed deletion/dated files}} notice, but please explain why in your edit summary or on the file's talk page.
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. [8]
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. [9]
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.
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.
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.
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?
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. [10]
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. [11][12]
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. [13]
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.
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. [14]
