This user is a regular and doesn't mind if you template him.
This user's talk page is monitored by talk page watchers. Some of them even talk back. Their input is welcome, and their help with messages that I cannot reply to quickly is appreciated.
Latest comment: 20 years ago3 comments2 people in discussion
Hello TonySt, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are a few good links for newcomers:
I hope you enjoy editing here and being a Wikipedian! Please sign your name on talk pages using four tildes (~~~~); this will automatically produce your name and the date. If you have any questions, check out Wikipedia:Where to ask a question or ask me on my talk page. Again, welcome!
Now, about WP:AIV. Feel free to put test4 on someone's page, but test5 should be for admins. Also, make sure you do the template right, and get the article name right. So it's {{vandal|IPaddress}} and the article was Christopher murt not Christopher Mutt (or at least the one I found). Wikibofh22:12, 4 December 2005 (UTC)Reply
Latest comment: 2 months ago3 comments2 people in discussion
Hello again, Stark! I have just noticed in your contributions that you use {{uw-unsourced}} while reverting unsourced BLP edits using C.V.P.I. I recommend using {{uw-biog}}, which makes it more obvious that the user has edited a BLP instead of a standard article in where uw-unsourced can be used. Have a nice day, and good luck coding that! – SimpleObjects-9ei 🏖️/☀️/🥵 19:34, 16 July 2026 (UTC)Reply
Oh yeah Stark, also be careful when a user uses C.V.P.I. to revert an edit of a user with a highly offensive or egregious username, as Interceptor is set to warn users after reverting an edit using it. One time I saw this kind of thing to happen was in Argentina national football team when Hamimh2 reverted an edit of an offensive username and we don't want to waste admins' time having to revdel the creation logs of the "User talk:Grossly offensive username" pages. SimpleObjects-9ei 🏖️/☀️/🥵 (see talk) 23:24, 26 July 2026 (UTC)Reply
Hello! A tip: after an editor is reported to AIV it stops using their username in edit summaries, and no longer warns the editor unless you choose a level in the dashboard. Also, if you manually report an editor to AIV via the dashboard, CVPI does not mention their username in the edit summary of the report to AIV. If it's an LTA with an offensive name, I usually just manually report via the dashboard before making any reverts (and I usually don't revert them more than once per article). TonySt23:47, 26 July 2026 (UTC)Reply
Latest comment: 1 month ago3 comments3 people in discussion
The da Vinci Barnstar
Thank you for creating one of the greatest Wikipedia tools of all time! It makes RC patrolling so much easier, and works identically on mobile! Axolitl (talk|contribs) 05:24, 22 July 2026 (UTC)Reply
Latest comment: 2 months ago3 comments2 people in discussion
For what it's worth, the Santorum quote was in the wrong place in the article, but it's entirely real and very sourceable. "We have to make the best out of a bad situation." Jan. 20, 2012 interview with Piers Morgan on CNN, during his run for president. --jpgordon𝄢𝄆𝄐𝄇01:13, 27 July 2026 (UTC)Reply
Latest comment: 2 months ago3 comments3 people in discussion
Hi, I saw your message. As a chess player, emory tate is undisputely one of the greatest chess players and any chess player will tell you that, unfortunately these gentlemen keep on revoking my edit for reasons I am unsure of. ~2026-41795-39 (talk) 04:18, 27 July 2026 (UTC)Reply
I tried to defend you when Mario was labelling you a vandal, but you're not making this easy. Stop trying to add stuff when it gets reverted. Go to the article talk page instead. Wikipedia is not the free for all anarchist project that it used to be. I know Emory Tate has his fans but he wasn't an all time great or anything like that. He was a master with highly variable results due to his double-edged style. MaxBrowne2 (talk) 04:35, 27 July 2026 (UTC)Reply
Latest comment: 2 months ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
Content Translation now supports dark mode, fulfilling a Community Wishlist request. This brings the tool in line with the accessibility features available in the Vector 2022 and Minerva skins, helping reduce visual fatigue for users translating content.
DiscussionTools' source mode and the 2017 wikitext editor will now offer autocomplete for links ([[), templates ({{), HTML and parser tags (<), and magic words (__), making it quicker and easier to insert links, templates, and other wiki markup while editing.
The Readers Growth team has concluded its experiment with mobile page previews and will not roll out the feature. Page Previews are a pop-up bottom sheet that appears when readers tap a blue link, showing a thumbnail, lead paragraph, and an option to open the article. The experiment showed flat retention and negative indicator metrics, suggesting that mobile web readers preferred navigating directly to linked articles rather than using page previews.
The Reader Experience team has seen encouraging early results from the Reading Lists feature, with 93% of participating users reporting that it was useful. Reading Lists help active readers save articles for future reading and support their learning goals on Wikimedia projects. The team plans further improvements before expanding the feature to more users.
The Explore Feed Refresh initiative was tested with new and casual Wikipedia app readers. The refreshed feed helps readers discover new and relevant content. After a 10.5% increase in engagement with the feed, Wikimedia Apps team has decided to scale the Home Feed redesign to iOS with the learnings from the Android release applied.
View all 23 community-submitted tasks that were resolved last week. For example, an issue where subject names in the Article Guidance feature were displayed with incorrect capitalization on French Wikipedia, has now been fixed. Subject names will now follow the correct capitalization rules for the language.
Updates for technical contributors
After running several Account Creation Experiments to improve registration completion rates, a new version of the username field on Create Account has been rolled out. It includes a popover summarizing the username policy to provide clearer guidance during account creation. As part of this change, the messages createacct-helpusername and createacct-username-help that several communities have configured will no longer be used. If communities want to customize the guidance shown in the new popover, they can instead edit the following messages: createacct-username-policy-popover-bullet1, createacct-username-policy-popover-bullet2, and createacct-username-policy-popover-bullet3.
Later this week, the CodeMirror syntax highlighter will offer themes. The themes can be picked from a dropdown menu in the full CodeMirror preferences dialog. For wikitext, available themes are default, colorblind-friendly (previously the colorblind preference option on Special:Preferences#mw-prefsection-editing) and no-highlighting. For code languages (i.e., CSS/JavaScript/JSON/Vue/Lua), there are several themes available. These same themes will eventually be available for wikitext, too.
From now on, wikis can restrict editing in the "User" namespace to only the page owner and certain user groups. Read the configuration documentation to learn more.
Latest comment: 2 months ago2 comments2 people in discussion
I noticed that a message you recently left to a newcomer may have been unduly harsh. Please remember not to bite the newcomers. If you see others making a common mistake, consider politely pointing out what they did wrong and showing them how to correct it. It may take some time, but it helps us retain new editors. Thank you. Please do not bite newcomers. You keep reverting my edits without putting anything on the talk page. I understand you thought that a brief quotation was a copyright issue but Zi fixed that by using the wikipedia template for dictionary.com —Preceding unsigned comment added by ~2026-41649-10 (talk) 05:11, 29 July 2026 (UTC)Reply
Hello! As I mentioned on your talk page, you cannot copy text from your sources. Everything you contribute here needs to be written in your own words. Please do not copy and paste text from copyrighted sources, even with a reference. --TonySt05:16, 29 July 2026 (UTC)Reply
Latest comment: 4 days ago14 comments8 people in discussion
You are a remarkable editor in many ways. I think you would be a good administrator, and you appear to be well qualified. You personify an administrator without tools and have gained my support already! Interested in becoming an administrator? Check out some RfA advice, or ask a nominator about next steps!
Truthfully I imagine most editors, myself included, can't ever be completely certain of whether they themselves are experienced enough for the bit, regardless of years. It's something only other experienced users can judge, really. The only thing I'm sure of is I will never stop finding new things to learn about the project. --TonySt18:27, 3 August 2026 (UTC)Reply
Man. I've gotta admit. Tony's one of the reasons I started getting into anti-vandalism. He's literally a grade A+ editor and it will be super awesome to see him help out with the blocking here. — B.J (talk) 04:38, 5 August 2026 (UTC)Reply
Without Tony's counter-vandalism script, I barely would a help with stopping vandalism. Interceptor has been helpful beyond belief and Tony is always so friendly and welcoming. I would 100% support an adminship campaign for possibly the best vandalism fighter Wikipedia has. In solidarityDafootballguyWant to talk?23:49, 10 August 2026 (UTC)Reply
I always see good reports at UAA from you and hearing positive things about from other admins about your readiness to run:). Would love to see you with a mop.
While it's not the de facto criterion some people make of it, having a GA under the belt can be a big help during an election/RfA (perhaps your lovely The Maine Woods). A bit more information on your user page can help teach new users what userpages are for and find the technical tools you've developed. In solidarity, —Femke (talk) 🐦 12:56, 16 August 2026 (UTC)Reply
Latest comment: 2 months ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
The Reader Experience team has developed a patch demo that wraps the page toolbar onto two lines when there is not enough horizontal space for all the buttons. This aims to reduce crowding in the Vector 2022 toolbar, which can occur on some language Wikipedias at certain screen widths.
The Reader Experience team is planning to launch Reading Lists, a Community Wishlist item, which is currently available to try in beta, as a full feature in September. Before then, volunteer translator help is needed for string translations into a number of languages. The feature supports reading and learning goals on Wikipedia.
Next week, the table of contents on Wikimedia Commons file pages will be improved by consolidating the file page table of contents with the page table of contents. This will make it easier to understand a file page’s structure, navigate to specific sections, and share links to individual sections.
View all 24 community-submitted tasks that were resolved last week. For example, an issue where some TIFF images failed to load after clicking their thumbnail, causing a broken image to be displayed instead of the full-size image, has now been fixed.
Updates for technical contributors
The variable and function selector in AbuseFilter has been updated to support search and autocomplete. It will allow filter maintainers to find the desired variable or function more quickly.
The MJPEG and VP8 formats are removed from the video player. The MP4 format (MPEG-4 Part 2) is added instead, which provides higher quality videos to older iPhone devices. It may take a few weeks to retroactively update all existing videos. The default format for modern devices stays the same (VP9/WebM).
Latest comment: 1 month ago3 comments2 people in discussion
Good morning. I see your feedback about inclusion of information about the silver from the USS Arizona.
Can you suggest a way to include the information about the silver?
The article was written in 1994 when I did the initial cataloging of the silver in the Capitol Museum which the Museum turned into a booklet about the service. It is factual in the sense that I handled each piece for descriptions (markings, measurements, weights), talked to Pearl Harbor survivors, salvage divers, etc. The article about the Miner is about the finding of the missing bronze that was part of the silver service.
Hi @LPinAZ! Thanks for reaching out. Your best bet is to leave a message with the links (and the context for where they come from) on the article's talk page (click here) to let editors know about these resources. Interested editors can use the information to write content about USS Arizona, and they would then cite your articles with citations supporting the information they add. Thank you for stopping by:) TonySt20:43, 10 August 2026 (UTC)Reply
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
A new ChartWizard is now available on Wikimedia Commons for users interested in creating charts from their own data. The wizard makes the Chart extension more beginner-friendly by allowing editors to create charts, such as bar and pie charts, without needing to use JSON. Users can still switch to the JSON editor if they prefer. Feedback on the new tool is welcome on the wish talk page.
View all 19 community-submitted tasks that were resolved last week. For example, an issue where the Wikipedia iOS app’s Picture of the Day widget displayed the same image every day instead of updating daily, has now been fixed.
Updates for technical contributors
Math formula SVG images will soon be generated in the browser instead of on the server. MathML continues to be generated on the server and renders in the browser without JavaScript. Wikibooks will see this change on 12 August, Wikisource on 19 August and Wikipedia from 20-27 August. You can try this by selecting "MathML with SVG image (client side MathJax rendering)" in your preferences. This change is part of deprecating RESTBase and deprecating Mathoid.
Category pages will soon support sorting entries by the time they are added to a category. This will make it easier to find recently or long-standing categorized pages. It will also improve workflows for maintenance categories such as deletion backlogs and other time-based review tasks. You can use cldsort=timestamp URL argument in category view to sort the entries.
Gadgets and user scripts on Wikimedia wikis may now use ES2018 features and ES2019 features in JavaScript code. Previously, the platform only allowed up to ES2017. MediaWiki validates the source code to protect functionality from syntax errors and to ensure scripts are valid in all supported browsers.
Hey @Dafootballguy! Thank you for stopping by:) I'm going to talk about these in reverse order.
It's intentional that it doesn't auto-report when you use a "auto level" button in the dashboard, since many items in the dashboard correspond to behavior that usually doesn't belong at AIV. For your example, if they're blanking whole articles over and over and they're at max level, I'd recommend just using the normal red vandalism button in the toolbar to rollback & auto report, since you're (probably correctly) interpreting their repeated wholesale blanking as vandalism.
I'm pretty firmly in the camp that semiautomated diff viewers should require rollback rights, since they can cause a lot of problems if used ineptly or in bad faith. Earning rollback rights is a relatively good indication that an editor is ready to use these tools.
CVPI does have a dark mode, but it follows your device's settings. So if your phone/computer is set to light mode, it appears as light mode, and if your device is set to dark mode it switches to dark mode instead. At least, that's the way it's supposed to work -- if that's not how it's working for you please let me know and I might ask you for details about your device so I can fix the bug:) TonySt15:39, 12 August 2026 (UTC)Reply
@Dafootballguy, I'll keep the "dark mode toggle" idea in mind for the menu -- I can see where there might be cases when it's useful to have dark mode enabled even if you have your device set to light mode.
For your scripting question: common.js is (usually) used as a place where we import scripts, rather than where scripts are written or stored. If I were you, I would move the content filter script into a new .js file (maybe at User:Dafootballguy/ImageContentFilter.js). Then you could install it into your common.js by adding importScript('[[User:Dafootballguy/ImageContentFilter.js]]'); as a new line to your common.js. TonySt17:47, 12 August 2026 (UTC)Reply
@Dafootballguy, apologies, at the end of your common.js, remove the brackets from the script name. So instead of importScript('[[User:Dafootballguy/ImageContentFilter.js]]'); it should be importScript('User:Dafootballguy/ImageContentFilter.js');TonySt18:19, 12 August 2026 (UTC)Reply
I'd recommend that you add the script to the list yourself, but only after testing it extensively to make sure it works as you expect:) TonySt23:17, 12 August 2026 (UTC)Reply
It's possible that another script in your common.js is interfering with the way CVPI creates its interface. If the problem only started two days ago you might try reverting to a version of your common.js from before that time. CVPI hasn't had any changes to its code this month. TonySt20:51, 16 August 2026 (UTC)Reply
I hope you don't take this the wrong way, but I would recommend you become a little more comfortable with JS before that step, since tools in projectspace are expected to be hand-vetted and robust (especially if they modify pages). That being said, I don't think there's a set process to create a projectspace page for a tool. TonySt22:17, 20 August 2026 (UTC)Reply
I had another editor help with it and fix all of the bugs. While I'd like to improve it, it's still pretty useful. What else needs to be done? (I don't take it the wrong way, helpful criticism is always helpful.) In solidarity, Dafootballguy (Want to talk?) 22:25, 20 August 2026 (UTC)Reply
My only advice is to just make sure you're comfortable enough with the code and the language to make adjustments if anyone identifies any issues. TonySt22:46, 20 August 2026 (UTC)Reply
Latest comment: 1 month ago1 comment1 person in discussion
Hi thanks for msg.
Brevity is probably best so: I added about 8 words to the page then put what follows as backup in the form to substantiate:
‘Chaos was described by Edward Lorenz as: ‘When the present determines the future but the approximate present does not approximately determine the future.’ Tech systems that determine the approximate present are not competent to ‘determine the future path of life’ - the phrase is mathematically illiterate and morally vacant.´
All true I think.
The few words I added to the page were something like:
‘Edward Lorenz’s definition of chaos is relevant here.’
All true too I think.
One could argue of course, but I don’t see anything false from me. Do say if you do.
AI successionism seems to me a ruse.
My few words were deleted within (my guess) less than a minute. I thought that sabotage of W principles so told the deleter so.
I love and admire Wikioedia and have always defended it - from the first. I oppose sabotage.
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Worklist feature for the Event Registration tool is now live on all Wikimedia wikis. With Worklist, event organizers can add the articles their event will focus on directly to the event page. The Worklist also powers Event Pathways which notifies other editors of the upcoming or ongoing event when they edit an article featured in the event's Worklist. This is the minimum viable version (MVP), and feedback is welcome. Organizers are encouraged to try the feature. A hands-on Worklist Setup Workshop will take place on 18 August at 16:00 UTC and 19 August at 11:00 UTC.
Updates for editors
Special:ShortPages displays short pages by their size, but in many cases it gets filled with disambiguations and soft redirects, making it harder to find the short articles themselves. Starting this weekend, you will be able to choose not to include an article in the special page by adding the magic word __EXPECTSHORTPAGE__.
One new wiki has been created: a Wikipedia in Bole (w:bol:)
Starting the week of August 17, the page toolbar will wrap onto two lines when there is not enough horizontal space for all the buttons. This is a fully merged patch from the Reader Experience team which aims to reduce crowding in the Vector 2022 toolbar, that may occur on some language Wikipedias at certain screen widths.
View all 16 community-submitted tasks that were resolved last week. For example, uploading large files to Wikimedia Commons has become more stable and less prone to failure following some fixes related to the “Could not acquire lock” upload error.
Updates for technical contributors
Debian Bullseye will reach the end of its Long Term Support on 31 August 2026. Some Cloud VPS projects still have instances running Debian Bullseye. Maintainers of those projects are encouraged to migrate to Debian Bookworm or Debian Trixie. A migration guide is available to help with the process, and users may also want to consider whether their workload is better suited to Toolforge. If you need help or cannot complete the migration by 31 August, please contact the Cloud VPS admins as soon as possible. Read more.
Hi @Sonomacountyeditor! I did see the references, including the ones you removed. Please stop attempting to blanket remove well-sourced mentions of Jewish history from food articles (or any other type of article, for that matter). --TonySt22:07, 17 August 2026 (UTC)Reply
I didn't remove any sources, so if that occurred I do apologize. I removed an attribution as 1. it's false and 2. the cultural differences are detailed later on in the body, it is not appropriate for the intro unless we do that for every variant. Sonomacountyeditor (talk) 22:09, 17 August 2026 (UTC)Reply
The campaign brings together Wikimedians interested in improving coverage of organised labour, workers, trade unions, and labour history. We have confirmed collaborations with Wikipedia language editions in English, Dutch, Persian, Serbo-Croatian and French. If you want to add other language editions or other wiki projects you are strongly encouraged to do so! This event spans geography and languages!
This is a one-time invitation. You're receiving it because you previously signed a petition related to Wiki Workers United (WWU). We hope you'll join us!
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
The Special:CreateAccount page has been simplified as part of ongoing work to modernize the account creation experience. The panel showing project statistics no longer appears next to the form on desktop and mobile web. Multiple account creation experiments show that a simpler form helps newcomers complete registration.
In order to improve page performance, images now load when they are viewed. This means images lower down an article will not load if a reader never scrolls to that part of the page, which may affect some image-related metrics.
View all 42 community-submitted tasks that were resolved last week. For example, an issue where image thumbnails in Abstract Wikipedia could fail to display after the corresponding file was moved on Wikimedia Commons, has now been fixed. Thumbnails will now update correctly when files are moved.
Updates for technical contributors
User Info card is a feature that helps patrollers see information about user accounts. So far, it has been available only in places such as page history, logs and recent changes. Now, it's possible to place it in the page content as well, using the {{#uic:}} parser function. It can be particularly useful in templates like {{Userlinks}} (or their specialized variants), as it will make it easier to see the context about a user on various noticeboard pages. The card will be displayed only to users who have it enabled in their preferences.
Due to user security and privacy risks, we have disabled access to Special:MyPage URLs when specifically using action=raw. If you are impacted by this, consider whether you can use an alternative approach. Special:MyPage URLs can still be accessed and used without action=raw. Specified user page URLs (e.g. User:Myusername) can still be used with action=raw.
Due to an update, the thumbnailing software has been improved. This includes upgrading librsvg to 2.60 and ImageMagick to 7, as well as resolving a number of long-standing thumbnailing bugs like rendering errors.
Latest comment: 1 month ago1 comment1 person in discussion
You instantly deleted my section in that article detailling how awful the school is from a student's perspective. Are you so absolutely dense that you think that writing something horrific about a schools action is vandalism or "not constructive?" Did you even bother to look at the edit reason in the first place or are you just forever waiting to be another cog in the machine to silence a victim's voice? ~2026-46794-35 (talk) 20:21, 27 August 2026 (UTC)Reply
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
A new format for the Community Wishlist is open for feedback. You can read the proposed ideas on Meta. This new process plans to improve how wishes are triaged, voted on, and prioritized in a way that is transparent and balanced across project families and language editions. This consultation is open for two weeks.
Updates for editors
The latest release of the Wikipedia Android app includes updates to the Saved feature, bringing the app’s saving experience closer to iOS and Web. The update redesigns the Saved tab with an “All articles” view, removes the default “Saved” reading list, renames reading lists to “Collections,” and modernizes the article-saving experience.
The Reading Lists feature was enabled for all logged-in users on Bengali, Chinese, Czech and Vietnamese Wikipedias on August 25, after several months as a beta feature. Reading Lists will be available to all logged-in users on Arabic, French and Indonesian Wikipedias on September 1, followed by English Wikipedia on September 14, and all other Wikipedia wikis on September 28.
At the end of the month, some logged-out readers on Bengali, Czech, Persian, English, and Polish Wikipedias using the Minerva skin on mobile will see an updated navigation bar in an A/B test. The test will compare the current navigation bar with a new version designed to make it easier to find information more quickly. The goal is to determine whether these changes encourage readers to return more often. This experiment will not change the experience for logged-in readers and/or editors.
Editors who maintain redirects, templates, and categories used on redirect pages now have improved ways for finding and curating redirects. Previously, redirects pages could not be searched. Two new search keywords, onlyredirects: and withredirects:, now allow redirects to be searched directly and can be combined with existing keywords such as incategory:, intitle:, and insource:.
The ISBN lookup tools for generating citations were recently not working because of external service problems. Developers are working on solutions.
View all 30 community-submitted tasks that were resolved last week. For example, an issue where searching for pages by category using deepcat could return no results or unrelated results has now been fixed.
Updates for technical contributors
The domain of URLs for thumbnails is changing from upload.wikimedia.org to thumb.wikimedia.org. The old URLs will continue to work for the foreseeable future but MediaWiki will advertise the new domain instead. URLs to other types of media such as original files, videos and transcodes will still be served from upload.wikimedia.org.
The Wikimedia Math API is now deprecated. These endpoints will be fully sunset by the end of September 2026. Developers who call these endpoints should transition to alternative math rendering solutions, such as the native MathML or MathJax. Third-party MediaWiki installations that utilize the Math extension for formula rendering are required to upgrade to v1.43+ to avoid disruption of service.
Hi Brokeshotmet3r! I'm not very familiar with the subject but I wouldn't be surprised if that change was challenged by others since it highlights those locations and omits other areas that are also covered in the article. Actually it looks like it was already reverted, I'm guessing for that reason. Regardless, the reason I reverted your earlier edit wasn't because of that detail but instead because of the unexplained (apparently accidental) blanking. --TonySt14:01, 2 September 2026 (UTC)Reply
Latest comment: 1 month ago13 comments4 people in discussion
hello. I have just tried to add. My information is based on my unpublished M.A. paper .
If you wish i can demonstrate my sourses to you via email. In private. My sourse is Ibn Asakir's Taarih Madinat Dimashq.
Thank you Yak5029 (talk) 13:56, 2 September 2026 (UTC)Reply
It looks like the article already contains some of the information you added -- there is a section all about the subject transmitting hadith. I'm going to restore part of your edit, but if there's other information (like about their teacher, for example) which is referenced in that source on page 295-296 then you can use an inline citation like this:
{{cite book |last1=Asakir |first1=Ibn |title=Taarih Madinat Dimashq |pages=295-296}}
I'm referring to the state of the article as of the date and time of this comment, so the description still stands. I'd be happy to help fixing up footnote once the article has been cleaned up. SuperFastSpellChecker (talk) 16:57, 3 September 2026 (UTC)Reply
@~2026-47580-01: SuperFastSpellChecker is correct that the edits you've made there appear to be commentary, and in some cases they directly contradict the existing sourced information. Historians having doubts about their reliability is definitely not "slander", and if it is slander then we need a source describing it that way. --TonySt17:00, 3 September 2026 (UTC)Reply
the later hadith critics accused Sayf b. ' Umar of beeing a heretic/ zindiq. And also claimed that he put his own words to otherwise reliable transmitters. That he was accused of zindaqe is considered a slander. ~2026-47580-01 (talk) 17:12, 3 September 2026 (UTC)Reply
@TonySt it was corrected by autocorrect, I meant spaces (and forgot to subscribe so I missed your response). A random question; can you stop showing the auto posts for the "be bold" tour and user's .js (because only 13 user's can edit those pages). Can you also have a "hide this user" button (maybe as an option in monitor this user), There are sometimes very experienced, good editors who show up. In solidarity, Dafootballguy (Want to talk?) 03:18, 9 September 2026 (UTC)Reply
These are great ideas:) The "hide user" thing is something AntiVandal does well and I'll try to incorporate it somehow. And yes, I've noticed more of those "be bold" things and I think I have a way to make those show up less in a near-future update:) TonySt02:05, 11 September 2026 (UTC)Reply
Latest comment: 1 month ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
Add a Link has been upgraded for English Wikipedia users with improved detection of links that have different capitalization. This will help reduce ambiguous suggestions caused by differences in capitalization in article titles, including articles about cultural goods. A second phase of improvements is planned, which will also prepare the feature for release in other languages.
The Article guidance feature will be enabled by default for junior editors on Simple English and Turkish Wikipedia starting 10 September 2026 following an experiment. Junior editors with 0 to 99 edits will automatically see the feature when they click a red link or use the "Madde oluşturto" option on Turkish Wikipedia to create a new article. The change is intended to help junior editors create higher-quality articles that meet each Wikipedia’s standards. Additional improvements will continue based on the experiment results and community feedback.
The Pageviews Analysis tool which allows users to compare pageviews across multiple pages, turns 10 years old this year and several new features have been added. They include WikiNav which provides insights into how readers of Wikipedia explore the content, editing stats in Siteviews, the ability to lookup articles belonging to a WikiProject, and support for dark mode.
A visually simplified Minerva navigation bar is being tested for logged-out readers using mobile web on the Bengali, Czech, English, Farsi, and Polish Wikipedias. The experiment aims to determine whether simplifying the navigation improves reader retention. The test will run from August 31 to September 28, and no action is required from users.
All wikis will be read-only for a few minutes on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks.
View all 25 community-submitted tasks that were resolved last week. For example, an issue where Parsoid could mishandle nested nowiki tags, causing content to be lost and displaying unwanted text has now been fixed.
Updates for technical contributors
Interface administrators can configure gadgets from MediaWiki:Gadgets-definition. The definition format has been updated and no longer requires the ResourceLoader option, as gadgets are always loaded through ResourceLoader. This simplifies gadget configuration by removing an option that is no longer necessary, making gadget definitions easier for administrators.
Hey there! Seen you around active on recent changes many times and recently received rollbacker so I've been using your tool Interceptor; it's very, very helpful and I'm very appreciative of it.
I was looking to create a topicon for Interceptor users to complement the current userboxes you have listed at WP:CVPI#Userboxes and couldn't find an image logo for CVPI. I've gone ahead and converted the red logo (I assume by page history, at least, that you are the author of) in two of the userboxes to its raw HTML and vectorised it (with very little modification and solely to comply with SVG and non-WP specific HTML formatting).
@.sh1eldo7 I don't have any problem with that -- thank you for doing it, actually -- and I appreciate you checking even though it's within that threshold:) Please also feel free to add it to the project page wherever you feel it would be helpful! TonySt20:54, 11 September 2026 (UTC)Reply
Latest comment: 24 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Future Audiences team has started a discussion on English Wikipedia about a proposed new experiment to show a temporary notice about the new Google Preferred Sources feature to Wikipedia readers coming from Google. The experiment is to test whether this notice makes visitors come back to Wikipedia more often. Preferred Sources feature lets users choose websites they trust so Google can highlight content from those sources more prominently in Search and AI experiences. We are interested in testing this on other languages that Google supports and would welcome assistance with starting conversations on other wikis. If interested, please reach out to Future Audiences on the talk page.
Updates for editors
The chat platform Discord is releasing a new self-service framework that websites can use to specify how their links should look when shared on Discord. The Future Audiences team is planning to start using this new framework to improve how Wikipedia links look when shared on Discord, giving better attribution and credit to contributors. The link appearance and behavior won't change in the first phase of this project as we want to first collect some baseline data to assess the impact of future changes. However, if community members who are active on Discord spot any issues, they can reach out on Phabricator or Metawiki.
The Reader Growth team will be running an experiment to test whether compacting article lead sections on mobiles with the addition of a "read more" button improves reader retention. The test will begin on September 17 on Arabic, Spanish, French, Indonesian, Italian, Japanese, Portuguese, Vietnamese, and Chinese Wikipedias and will run for four weeks.
All wikis will be read-only for a few minutes on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming week.
View all 28 community-submitted tasks that were resolved last week. For example, an issue where Wikistats for Wikipedias was returning an HTTP 500 error and could not be reached, has now been fixed.
Updates for technical contributors
Developers who maintain a tool that queries the Wikimedia Commons links tables need to update their code to connect to the new x4 database cluster. The links tables have been moved from the s4 cluster to x4, and will no longer receive updates on s4. The page and redirect tables remain available on both clusters. A wiki replica for the x4 cluster will be set up afterwards. The change is being made because the s4 cluster has grown too large to operate efficiently. You can read more.
Hello! On Wikipedia, details about people need to be supported by a reliable source. If published reliable sources do exist, we can add them as inline citations so readers can verify the info themselves. I reverted your edit because it added biographical information about their early life without any references. It looks like you were able to add other information with some references after you reached out to me. Just curious, how did you find that image of the subject? --TonySt02:21, 16 September 2026 (UTC)Reply
Hi TonySt, thanks for clarifying. The image was provided to me for use on Wikimedia Commons as a more current photograph of the subject. I understand the concern regarding the early-life information and will make sure any future additions are supported by reliable published sources. Thanks for your help. Ajd707 (talk) 02:40, 16 September 2026 (UTC)Reply
I’d prefer not to share personal identifying information here, but I understand the conflict of interest concern. I’m happy to follow Wikipedia’s guidelines and rely on independent reliable sources for any proposed changes. Ajd707 (talk) 02:48, 16 September 2026 (UTC)Reply
Latest comment: 21 days ago1 comment1 person in discussion
On 17 September 2026, Did you know was updated with a fact from the article The Maine Woods, which you recently created, substantially expanded, or brought to good article status. The fact was ... that Theodore Roosevelt was inspired by The Maine Woods to climb a mountain? The nomination discussion and review may be seen at Template:Did you know nominations/The Maine Woods. You are welcome to check how many pageviews the nominated article or articles got while on the front page (The Maine Woods), and the hook may be added to the statistics page after its run on the Main Page has completed. Finally, if you know of an interesting fact from another recently created article, then please feel free to nominate it.
Latest comment: 11 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
All wikis will be read-only for a few minutes on Wednesday, 23 September 2026 at 14:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Updates for editors
The Growth team tested a new post-edit notice designed to encourage Temporary Account holders to register for a permanent account. The new notice replaced multiple dialogs and a simultaneous welcome notification with a single message highlighting the benefits of creating an account. The experiment increased permanent account creation from 1.94% to 3.66%, an 87% relative increase. The change will now be released to all wikis.
For Wikipedia editors using the "Suggestion mode" Beta Feature, there is a new opt-in user preference for showing "experimental" edit checks and suggestions. These types are listed at Special:EditChecks, and are intended for early developer-testing and for gathering feedback from experienced users. Administrators can change the configuration details for each suggestion as usual. Administrators can also use this feature to help test their community's ideas for locally created checks and suggestions. Experimental types will have a more distinct visual style later this week. Feedback is welcome.
The CEE Technical Village Pump has been launched as a space for technical discussions and collaboration among Wikimedia communities in Central and Eastern Europe.
A new tool, Starter Kit, is now available for new and small language Wikipedia communities. It brings together guided tasks, tools, and resources to help communities get started, monitor their progress, and collaborate with the broader Wikimedia community. Starter Kit is hosted on Wikimedia Toolforge and is designed for Wikipedias with fewer than 50,000 articles. Learn more about how Starter Kit works and how communities have been using it in this Diff blog post.
The Reader Growth team is launching a retest of the image carousel experiment. The retest will use three new versions of the design, updated based on community feedback. The team will assess results and determine with communities whether or not to proceed with the feature. The experiment will begin the week of September 28 and will run on Arabic, Bengali, Chinese, Czech, English, Farsi, French, German, Indonesian, Japanese, Polish, Portuguese, Spanish, Swedish, and Vietnamese Wikipedias.
After successful rollouts to Arabic, Bengali, Chinese, Czech, English, French, Indonesian, and Vietnamese Wikipedias, the Reading Lists feature from the Reader Experience team will be available to all logged-in users on all Wikipedia wikis starting September 28.
View all 28 community-submitted tasks that were resolved last week. For example, an issue where the mentor status script repeatedly updated mentors’ status even when nothing had changed, creating unnecessary Recent Changes entries, has now been fixed.
Updates for technical contributors
The abusefilters list query API, used to retrieve specific details about active or historical abuse filters configured on a wiki, has been updated to support the formatversion=2 configuration parameter, thereby leading to breaking changes to the API response. All users who maintain user-scripts or other code need to check if they use the abusefilters list query API, and respond to any breaking changes.
Latest comment: 10 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
Users of default skins on desktop and mobile web (Vector 2022 and Minerva respectively) will now be informed if the search suggestions displayed as they type into Search come from page redirects. Previously, users could get confused when the top search suggestions did not match exactly what they had typed. The new redirect notice clarifies that these suggestions are not random, but related to the search. The suggested pages may be redirects to the most relevant destination articles being searched for.
Logged-out Wikipedia users on mobile web will begin to see a bookmark button for saving articles to their reading lists instead of the current Watchstar button. When clicked, the bookmark button prompts users to log in or create an account to save an article for later. An earlier experiment found that the bookmark icon was four times more likely than the Watchstar button to encourage logged-out users to create an account. This change is part of efforts to encourage more readers to become account holders and use features that help them save and return to content.
An experiment will begin on September 29 on Spanish, Arabic, English, and French Wikipedias to simplify the experience users encounter immediately after account creation. The test will explore whether removing friction from the current Welcome Survey helps new users understand what to do next more easily. The experiment will run through the end of October.
The Product and Technology Advisory Council has put out a call for the community to suggest topics that it should consider and discuss with the Wikimedia Foundation. Editors and technical contributors are invited to add topics to the council's talk page.
A bug in the Global Watchlist is causing the page to fail to load for users that have unseen changes on Wikimedia Commons. Developers are working on a fix. Until then, affected users can follow the workarounds described in the relevant help section.
New magic words {{CATEGORYSORT:TIMESTAMP}} and {{CATEGORYSORT:RTIMESTAMP}} are now available for use. They are able to change the default sorting of categories to be based on timestamp of categorization.
View all 20 community-submitted tasks that were resolved last week. For example, the issue where Wikistats for Wikipedias was not reachable has now been fixed.
Updates for technical contributors
The datacenter switchover, scheduled on September 23, has been postponed. The equinox exercise revealed capacity issues, preventing the switch of all services to the other datacenter. The process has been paused, prioritizing investigating that issue, to ensure that we continue to be able to serve our users reliably. A new exercise will be scheduled. Meanwhile, all traffic and edits continue to work as usual.
On September 23, a power loss briefly affected all wikis, creating intermittent issues on both reading and editing modes. This also affected Gerrit. This is unrelated to the datacenter switchover postponement.
Produnto has been deployed to mediawiki.org and some Indic language wikis. We want to hear your feedback on this experimental product. Produnto allows users to use Lua modules hosted in Wikimedia's GitLab. It simplifies the sharing of Lua code between wikis. Instead of copying each individual Lua module from one wiki to another, users will be able to easily share packages across all wikis.
A Cross-wiki code collaboration workshop will be held online on October 2 at 12:30 UTC, bringing together South Asian technical contributors to learn about Produnto and begin piloting it on Hindi, Punjabi, Odia, Telugu, and Malayalam Wikipedias. Produnto is a package manager for deploying Lua modules hosted on GitLab to Wikimedia wikis, and was recently deployed on some pilot wikis.
Latest comment: 9 days ago1 comment1 person in discussion
The administrator elections process has officially started! Qualified editors are encouraged to find at least one experienced nominator. Self-nominations are also allowed. Please review instructions at Wikipedia:Administrator elections/October 2026/Candidates.
Here is the schedule:
September 29–October 5: Nominations phase (we are here)
October 8–12: Discussion phase
October 13–19: SecurePoll voting phase
Please note the following:
The requirements to run are identical to RFA—a prospective candidate must be extended confirmed. However, in practice, few candidates succeed without ~10K edits, some content creation, no recent behavioral issues, and a nominator.
The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
Ask any questions about the process at the talk page. Later, a user talk message will be sent to official candidates with additional information about the process.
If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Latest comment: 2 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The process for this year’s Community Wishlist has been published, incorporating community feedback. The wish submission process will end on November 8. This year, a working group (open for volunteering) that includes community members familiar with the technical aspect of our wikis alongside Wikimedia Foundation staff, will take care of the triage process. The triage is expected to be completed by late November. Votes for wishes will start in January.
Updates for editors
Editors using the visual editor will now see a warning when they paste text that is likely to have initially been copied from one of five external generative AI chatbots into Wikipedia. This feature is known as LLM Paste Check. It is a type of Edit Check that is community configurable. The check looks for markers in the copied HTML and is not using content watermark detection. Edits will also be tagged so that patrollers can review them more closely. The feature helps newcomers add content that respects Wikipedia’s policies and makes it easier for experienced editors to identify problematic edits. Communities with local policies about LLM usage can adjust the wording and policy that is linked. The team apologizes that this was rolled out without a delay for translations.
Editors can now easily access the web visual editor directly from the iOS and Android apps. When opening the editor, users will be given a choice between visual editing and source editing. If they choose visual editing, they will be sent to a mobile web window in their phone's browser. After completing their edit, a banner will give them the option to return to the app. This enables readers to make quick contributions while casually reading.
Users of the Wikipedia Android and iOS apps will now see a one-time account creation prompt after they have used the app for two consecutive weeks. This prompt explains the benefits of having an account. It is intended to help more casual readers become logged-in users who return to the apps regularly.
Editors on group1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on Recent Changes and Watchlist when a link to another language version of a page is added, removed, or changed in its Wikidata item. This change will begin on October 5 at 07:00 UTC as a two-week trial to reduce high-volume, low-value notifications and make important changes easier to identify. Editors who rely on these notifications can read more on the project page and share feedback or concerns on the talk page.
View all 36 community-submitted tasks that were resolved last week. For example, an issue where mentors who removed themselves from the mentorship program could still have mentees assigned to them and receive questions, has now been fixed. Mentees will now be reassigned when a mentor leaves the program.
Updates for technical contributors
Wikimedia Brasil has published its Development Best Practices Framework (ABPD). It is a guide for staff, contractors and volunteers building technical tools and projects. It covers the project lifecycle, security, accessibility, personal data protection and responsible AI use, and explains how movement-wide guidelines were adapted to a local context. They encourage other affiliates to reuse it and adapt it. Read more in the Diff post.
A new, canonical base URL for Wikimedia APIs will soon be introduced. The new canonical route follows a {projectName}/api/ pattern and will act as an alternative path for current REST APIs (for example: {projectName}/w/rest.php/). Both versions will be callable for all existing APIs, but the new structure will be the preferred path for newly created API modules. This change will be non-breaking for most users. The existing pathways will remain available for all existing endpoint requests. However, some endpoints may return URLs following the new pattern in response bodies. Changes will be available on test wiki first, with the rollout expected to cover all wikis by the end of October.
Latest comment: 2 days ago1 comment1 person in discussion
Thank you for choosing to run in the October 2026 administrator elections. This bulletin contains some important information about the next stages of the election process.
As a reminder, the schedule of the election is:
October 6–7: Housekeeping phase (we are here)
October 8–12: Discussion phase
October 13–19: SecurePoll voting phase
Scrutineering phase
All times are in UTC. The first date in the range starts at 00:00, and the last date in the range ends at 23:59. So for example, the Discussion phase opens on 8 October 2026 at 00:00 UTC, and ends on 12 October 2026 at 23:59 UTC.
We are currently in the Housekeeping phase. Your candidate subpage will remain closed to questions and discussion. However, this is an excellent opportunity for you to recruit nominators (if you want them) and have them place their nomination statements, and a good time for you to answer the standard three questions, if you have not done so already. We recommend you spend this phase getting your candidate page polished and ready for the next phase.
The discussion phase will take place from October 8–12. Your candidate subpage will open to the public and they will be permitted to discuss you and ask you formal questions, in the same style as a request for adminship (RfA). You are strongly encouraged to be around on those dates to answer the formal questions in a timely manner.
On 13 Oct, 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. Anyone can see who has voted, but not who they voted for. You are permitted and encouraged to vote in the election, including voting for yourself. 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 your vote total during the election.
Once voting concludes, we will begin the scrutineering phase, which does not have an exact end date, but typically takes a few days to a week. Once everything is certified, the results will be posted on the results page (you may want to watchlist this page) and transcluded to the main election page. In order to be granted adminship, you must receive at least 70% support, calculated as support ÷ (support + oppose), and must also have received a minimum of 20 support votes. 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 as a candidate, and best of luck.
You're receiving this message because you are a candidate in the October 2026 administrator elections.
Thanks for the kind words @Dafootballguy:) Yes, I'm going to need to do something like that. I was hoping the "be bold" stuff would be tagged as The Wikipedia Adventure or similar but it turns out they're not tagged in that way. I've avoided whitelisting specific pages but I might need to start filtering those out if I can't find a better solution because I've been noticing them a lot as well. --TonySt14:53, 7 October 2026 (UTC)Reply
Cheers @Drmies. Maybe after the TPA stuff is implemented we can start a discussion about something similar to the "hide username" feature at meta:SRG, and ask the helperbot to respect it. Seems like that would make it a bit easier for everyone. --TonySt15:01, 7 October 2026 (UTC)Reply
On 13 Oct, 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.