The draft you've written is very similar to the article that was deleted based on consensus atWikipedia:Articles for deletion/Gizelle Bryant. In fact, the deleted article has even more content and assertions of notability than your draft, so I'm not so sure it would survive another AfD. That being said, the draft is protected against recreation by s specificsock, so if the draft is reviewed and approved I (or another admin) can lower the protection so it can be moved.--Ponyobons mots16:51, 2 October 2025 (UTC)[reply]
Hi Ponyo, I found your page from a few days ago when you blockedStudDoctor9000 (talk·contribs) for being a sockpuppet (I was involved in the conversation that originally led to the master being blocked). Apologies if I should take this straight to a notice board, but I was wondering if we could get some page protection atSalt Lake City International Airport? There's an IP editor who, every few days, edits the page with the same edits. The edits are not constructive and I have constantly reverted the edits since the user started doing this, which has been going on for almost 2 years now (here's one I reverted from October 2023:[1]). I eventually brought it to the talk page over a year ago in June 2024 (seen here:[2]) which eventually led to the page being protected for 2 months[3]. This stopped the IP for a bit, but they eventually started up their edits again this past May[4] and have been doing it consistently ever since. I've left constant talk page messages and warnings on several of the IPs, but the user never responds and they have never once used an edit summary. Just wondering what you think would be the best way to have this handled or if we can get the page protected again (for longer this time if possible). Again, I apologize if I should go straight to a notice board, I'm just not sure the best course of action given how long this has been going on. Thanks! (VenFlyer98 (talk)23:19, 2 October 2025 (UTC))[reply]
Hey. Thought you should be aware that it appearsUser:AreyanT101 is block evading withthis edit. I'm not particularly interested in playing whack-a-mole with however many IPs this person will inevitably use, so I've requested temporary ECP.GSK(talk •edits)02:20, 4 October 2025 (UTC)[reply]
Oh, that was independently of any block evasion. I just think they should be required to create an unblock request and thought you might have been afraid of blocking indefinitely in response to someone reverting you. Thanks for the ping!~ ToBeFree (talk)23:49, 6 October 2025 (UTC)[reply]
Hi Ponyo! I see you regularly revert this longtime bugger who originally edited asUser:Abdulaziz999982 and later resorted to socks. Can you please use your powers and check if these three accountsUser:BDN2,User:BD85 andUser:Marzst are somehow the same person? Because like inDeidré Laurens, the IP i mentioned edited in which they changed the subject title due to a move which was very recently done by BDN2, resulting in a revert by myself due to being arbitrary and lacked consensus for the new title. Thankyou.zoglophie•talk•16:26, 4 October 2025 (UTC)[reply]
More : Lookhere, their edits are one after another, changing names without any consensus in the respective talk pages of the subjects. Same in 2024 African Badminton Championships page history. I'm sure there are many more examples which definitely prove both of them are actually the same and longtime vandal Abdul.zoglophie•talk•02:36, 5 October 2025 (UTC)[reply]
On behalf of the Kwara State University Wikimedia Fan Club, I would like to request review and unblocking of one of our members’ accounts on wikipedia.Her accounts appear to have been blocked, and we believe this may have happened unintentionally. This user is active contributor in Wikimedia projects and members of our university club
@Pet002: There was no error in the blocking, and the reason for the block is noted on Grace0011's user talk page. Grace0011 wasincorrectly linking hundreds upon hundreds of common terms contrary to Wikipedia's Manual of Style. This was brought to their attention repeatedly, including with a short-term block, yet they continued without responding to any of the concerns raised by fellow editors. The path forward to an unblock is for Grace0011 to post an appeal on their talk page that demonstrates an understanding as to why they were blocked and will communicate with others when concerns are raised, as is required on this collaborative project. This is further explained atWP:GAB.--Ponyobons mots19:04, 16 October 2025 (UTC)[reply]
Hello, Ponyo. Please check your email; you've got mail! It may take a few minutes from the time the email is sent for it to show up in your inbox. You canremove this notice at any time by removing the{{You've got mail}} or{{ygm}} template.
That will go through OTRS. You don't need to provide email notifications when emailing the oversight team as it will show up in the queue automatically.--Ponyobons mots18:59, 17 October 2025 (UTC)[reply]
i noticed that you have blocked sockpuppets, however, you are putting this template on the bottom of the page, which is WRONG. Next time, put this template on a section that says "October 2025". On AquilatorG10's talk page you put the template on a completely unreleated topic!🧀 CheeseGuy 🧀11:27, 18 October 2025 (UTC)[reply]
There is a substantial backlog of unsourced articles on Wikipedia, and we need your help! The purpose of this drive is to add sources to these unsourced articles and make a meaningful impact.
Barnstars will be awarded based on the number of articles cited.
Remember to tag your edit summary with#NOV25, both to advertise the event and tally the points later usingHashtag Summary Search.
Not really. I saw your message, starting digging through their contribs, and other StayCalmOnTress socks kept popping up in the histories. Soyou were the one ahead, I just caught up!--Ponyobons mots22:31, 23 October 2025 (UTC)[reply]
Latesttech 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 Wikipedia iOS app has launched an A/B/C test of improvements made to the tabbed browsing feature for select regions and languages. The test, named “More dynamic tabs”, explores new tab experiences and includes “Did you know” and “Because you read” article recommendations. You canread more on the project page.
Autoconfirmed users onsmall andmedium wikis with the CampaignEvents extension can now useEvent Registration without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages.
View all 31 community-submitted tasks that wereresolved last week. For example, the issue of flashing colors when holding or pressing the arrow keys under the dark mode settings in Vector 2022 has been fixed.[12]
Updates for technical contributors
The CampaignEvents extension will be deployed to all remaining wikis during the week of 17 November 2025. The extension currently includes three features: Event Registration, Collaboration List, and Invitation List. For this rollout, Invitation List will not be enabled on Wikifunctions and MediaWiki unless requested by those communities.Visit the deployment page to learn more.
The SwaggerUI-based REST sandbox experience is now live on all wiki projects. The sandbox can be accessed through theSpecial:RestSandbox page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on theproject launch page.[13]
Transform endpoints with a trailing slash path in the MediaWiki REST API are now marked as deprecated. They will remain functional during this time, but removal is expected by the end of January 2026. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found and tested using theREST Sandbox. See theMediaWiki REST API Deprecation page for more detailed information about the API deprecation policies and procedures.
A dedicatedchangelog now exists for the MediaWiki REST API. The changelog provides an overview of these changes, making it easier for developers to keep track of improvements and iterations. Announcements will also continue to flow through the standard communication channels, including Tech News and email distribution lists, but can now be more easily referenced from a central location. If you have feedback about the style, structure, or content of this changelog, pleasejoin the discussion.
Administrators can delete the tracking category which was previously added by the JsonConfig extension, as it is no longer used. See the categories linked fromQ130635582. It is OK if there are still pages listed in the category as that is just a caching issue, and they will be automatically cleared out the next time each page is edited.[14]