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.
I noticed your comment on the Gypsy Rose Blanchard talk page about the proposed 1q21.1 microdeletion context. I agree it’s important to be careful about medical details, but I thought it might be relevant since it has been publicly documented and discussed by reliable sources (e.g. People, 2025).
I wasn’t able to reply directly on the talk page since it’s currently semi-protected, but I wanted to reach out here instead to understand your perspective better. Would you be open to clarifying what kind of supporting context would make it appropriate for inclusion? I’m still learning the best way to structure this type of addition and would appreciate your insight.
If you’re open to it, I also have some additional context and source details I can share for review.
Hi @Mylittlepony333. The reason I wasn't sure if it was appropriate is because I'm ignorant of the subject and don't know why a mention of that medical diagnosis is relevant for the article. Per WP:BLPPRIVACY, The standard for inclusion of personal information of living persons is higher than mere existence of a reliable source that could be verified. In other words: the fact that we can verify that the information is true does not mean we need to have it in the article. If there are reasons to add it to the article, then it should be done in a way that indicates to the reader why we're including the information. I can see another editor has responded on the talk page with some context. The talk page will become non-semi-protected in about 17 hours, at which point you will be able to participate in the discussion there -- I'd encourage you to wait until that time before providing additional context, as it would probably be more appropriate on the article's talk page.
Also, welcome to Wikipedia! I do have a question though -- you appear to be pretty familiar with the idea of page protection types, how to cite references, and talk pages. After reading your comment here, I was surprised to see that your only two edits to the project have been the addition of that information and this comment here. Have you, by chance, had any other usernames here before? Regardless, thank you for your contributions, and I look forward to you participating in the discussion at Talk:Gypsy-Rose Blanchard when it becomes unprotected shortly! --tony17:30, 30 October 2025 (UTC)[reply]
Hi Tony, thank you so much for your kind and detailed reply, I really appreciate the clarity.
To answer your question, no, I haven’t edited under any other usernames. I’m new to actively contributing, but I’ve been researching this particular case for quite some time and spent a lot of time reading through Wikipedia’s sourcing and BLP guidelines before attempting any edits. I wanted to make sure that anything I suggest is handled correctly and neutrally.
I completely understand the privacy and relevance concerns you raised about context, and I agree that any addition needs to clearly show why the information is encyclopedically significant. I’ll make sure that’s addressed when I outline my proposal.
I’ve already drafted a properly sourced version that I’ll add to the article’s Talk page for review once it reopens, so everyone can weigh in on the tone, placement, and context before anything is changed.
Thanks again for your earlier reply and guidance. I just wanted to follow up briefly. I wasn’t aware that the talk page would remain under semi-protection for newer accounts, so I wasn’t able to reply there as planned.
I’ve since refined my proposed clarification with full sourcing and neutral context, ready to share once my account becomes autoconfirmed. However, if you’d prefer I share the draft here for review in the meantime, I’m happy to do that instead.
Given that I’m still a new user, I’m also perfectly happy to wait the few days and make the ten constructive edits needed to gain autoconfirmed status if that’s the better path for credibility and process.
Hello, TonySt. This message is being sent to remind you of significant upcoming changes regarding logged-out editing.
Starting 4 November, logged-out editors will no longer have their IP address publicly displayed. Instead, they will have a temporary account (TA) associated with their edits. Users with some extended rights like administrators and CheckUsers, as well as users with the temporary account IP viewer (TAIV) user right will still be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range.
How do temporary accounts work?
Editing from a temporary account
When a logged-out user completes an edit or a logged action for the first time, a cookie will be set in this user's browser and a temporary account tied with this cookie will be automatically created for them. This account's name will follow the pattern: ~2025-12345-67 (a tilde, year of creation, a number split into units of 5).
All subsequent actions by the temporary account user will be attributed to this username. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser.
A record of the IP address used at the time of each edit will be stored for 90 days after the edit. Users with the temporary account IP viewer (TAIV) user right will be able to see the underlying IP addresses.
As a measure against vandalism, there are two limitations on the creation of temporary accounts:
There has to be a minimum of 10 minutes between subsequent temporary account creations from the same IP (or /64 range in case of IPv6).
There can be a maximum of 6 temporary accounts created from an IP (or /64 range) within a period of 24 hours.
Temporary account IP viewer user right
How to enable IP Reveal
Administrators may grant the temporary account IP viewer (TAIV) user right to non-administrators who meet the criteria for granting. Importantly, an editor must make an explicit request for the permission (e.g. at WP:PERM/TAIV)—administrators are not permitted to assign the right without a request.
Administrators will automatically be able to see temporary account IP information once they have accepted the Access to Temporary Account IP Addresses Policy via Special:Preferences or via the onboarding dialog which comes up after temporary accounts are deployed.
Impact for administrators
It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects the autoblock option.
It will still be possible to block an IP address or IP range.
Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this (see a video about IPContributions in a gallery below).
Rules about IP information disclosure
Publicizing an IP address gained through TAIV access is generally not allowed (e.g. ~2025-12345-67 previously edited as 192.0.2.1 or ~2025-12345-67's IP address is 192.0.2.1).
Publicly linking a TA to another TA is allowed if "reasonably believed to be necessary". (e.g. ~2025-12345-67 and ~2025-12345-68 are likely the same person, so I am counting their reverts together toward 3RR, but not Hey ~2025-12345-68, you did some good editing as ~2025-12345-67)
Hi, i’m ravecrowny or Gear. I was here because I accidentally caused an edit conflict on the Battle For Dream Island article because I didn’t add a reliable source to my citation (correct me if I am wrong). I was just trying to edit the article even though I had no prior knowledge of the rules and other information for editing on Wikipedia. Just letting you know that I made the accident and I didn’t mean to cause it. I ain’t no troll or anything trying to buffer with the article, just trying to make some edits. Also was asking if there was any consequences to doing that? I did it only 1 time so can you let me know? 2603:6011:7A00:C5E0:21C9:ABD4:FA2F:F3A4 (talk) 02:47, 2 November 2025 (UTC)[reply]
Hello Tony, I hope this is where I can reach you in response to your removing the external link I posted. SH Acoustics is a bonafide contributor to this facility as part of the Ralph Appelbaum Exhibit team. If you don't allow external links, that's fine, but why did you have to remove the text listing for SH Acoustics as well? StevieJ67 (talk) 17:29, 3 November 2025 (UTC)[reply]
Hello @StevieJ67! Thank you for reaching out. If that information can be supported by one or more secondary and independent reliable sources, then we may be able to re-add the information along with an inline citation to the source. I did a cursory search to see if I could find anything that meets the reliable source criteria but I wasn't able to find anything to support the information you added. I'm going to leave some more information on your talk page with regards to potential conflits of interest on Wikipedia, including some links that you might find helpful. Take care! --tony17:57, 3 November 2025 (UTC)[reply]
OK, so in full disclosure, I am related to the company that I am trying to list on this page, but also understand that other colleagues have added their names to project pages like this only to state the fact that they are involved, not to be overly "promoting". Perhaps you can help me understand how to navigate this process better on Wikipedia, as we have a number of project (building/factility) pages that we would like to see our name receive proper credit just like all the other names here do. What sources do these other companies provide for Wikipedia, especially when the building like the Obama Center is not complete and therefore most companies involved should not be "promoting" their involvement in any heavy way on social media or elsewhere? I feel very strange asking our Client - the Obama Center - or our project partner - Ralph Appelbaum Associates - to provide the necessary proof for Wikipedia that we are indeed a key part of the Design Team . StevieJ67 (talk) 18:05, 3 November 2025 (UTC)[reply]
Hi @StevieJ67. I appreciate your transparency and I think you might have stumbled on a core misconception that a lot of businesses and organizations initially have about Wikipedia. Wikipedia is an encylopedia edited by those whose sole goal is to create and maintain an encyclopedia. If your goal is to improve the encyclopedia, that can be accomplished in a lot of different ways. If your goal is to add references to your company to different articles, that is generally considered promotion and can be seen as contrary to the purpose of the encyclopedia. If your company's association is notable enough to warrant inclusion in secondary, independent reliable sources, chances are that one of our volunteer editors will notice and add that information into the article with citations supporting the information. If they don't notice on their own and you feel it would benefit the encyclopedia to include the information, you're more than welcome to write and submit edit requests. I encourage you to check the links I left on your talk page for clear answers on how to request changes to articles that you're associated with (this guide here is great), including how to use the edit request wizard. --tony18:48, 3 November 2025 (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.
Updates for editors
Administrators will now find that Special:MergeHistory is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start). [1]
For users with "Automatically subscribe to topics" enabled in their preferences, starting a new topic or adding a reply to an existing topic will now subscribe them to replies to that topic. Previously, this would only happen if the DiscussionTools "Add topic" or "Reply" widgets were used. When DiscussionTools was originally launched existing accounts were not opted in to automatic topic subscriptions, so this change should primarily affect newer accounts and users who have deliberately changed their preferences since that time. [2]
Scribunto modules can now be used to generate SVG images. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files. [3]
Wikimedia sites now provide all anonymous users with the option to enable a dark mode color scheme, featuring light-colored text on a dark background. This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments. [4]
Users with large watchlists have long faced timeouts when editing Special:EditWatchlist. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100× slower than sorting by title. A community wish has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish! [5]
View all 31 community-submitted tasks that were resolved last week. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query. [6]
Updates for technical contributors
Since 2019 the Wikimedia URL Shortener at https://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means /s/ URLs will not be advertised under article titles via HTML class="title-shortlink". The /s/ URLs will keep working. [7]
On Thursday, October 30, the MediaWiki Interfaces and SRE Service Operations teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the Service Ops team board.
MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025. [8]
In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia in a Diff blog post.
The problem is, anybody can create a Reddit thread titled "Abraham Lincoln ate pickled ducklings for fun" and, if we were to treat it as any reliable source, then we would have to write something on Wikipedia that is obviously not true. While some articles from reliable sources have factual errors, those sources also bear the responsibility and have a reputation at stake, making them motivated to have accurate information. monkeysmashingkeyboards (talk) 21:25, 3 November 2025 (UTC)[reply]
To put it differently:
If I make a post to Reddit saying "George Washington has 15 illegitimate children," and someone calls me out, then I can just create a new account.
If the article doesn't exist anymore, then you can remove the "Play for free" statement. However, there are still rules against using forums and self-published sources. See WP:RELIABLE for the policy in question. (Exceptions do exist, but none apply here AFAIK) monkeysmashingkeyboards (talk) 21:59, 3 November 2025 (UTC)[reply]
Those promotional articles aren't considered reliable or independent sources, and the content they support can be removed if a better source can't be found. In my reply I was not commenting on Top Eleven's sources in particular, I was making a point on sources in general. Cheers! monkeysmashingkeyboards (talk) 23:01, 3 November 2025 (UTC)[reply]
You're right, they never got accepted(They weren't accepted at all!) There is no formal process to "accept" changes to an ordinary article, e.g. Top Eleven. I and @TonySt reverted your edits using Reddit as a source because we are trying to prevent addition of improper sources. No one was there to scrutinize when the previous sources were added, so they slipped under. Those sources are also illegitimate, but for sources that have already been added, a bad source is better than no source(with 1 exception, WP:BLP).
(talk page stalker) As mentioned above, a Reddit thread or Facebook post can say anything the poster wants them to say. Would you appreciate someone saying you did something illegal? Anybody on Reddit or Facebook (or other social media) can say just that. self-published sources are not bad sources, they are not sources at all, the sole exception being if a company's facebook account posts something, in which case it ccan be used as a primary source for simple statements of fact ("X is Y") but cannot be used for qualitive statements ("X is the best Y"). Also, regarding your statement If you care about truth? - we in fact do not care about truth, we care about verifiability. - The BushrangerOne ping only03:08, 4 November 2025 (UTC)[reply]
Thank you for reaching out! I replied on that talk page section. You're right and I'd like to readd the reference with an archive link (we can discuss at the article talk page) :) --tony03:32, 4 November 2025 (UTC)[reply]
Thank you for finding that archive. Yes, please re-add the reference with the archive to the page. It is a lot better than I expected from Fox News + the headline.
A quote or summary of what is said by Daryl Kimball and / or Olli Heinonen in that archive might be good to add as well if you have time.
Hello! As I mentioned on your talk page, please refrain from hijacking pages, as you did with Chris Vargas. Should you believe the subject you were writing about deserves an article, please use the Article Wizard, which has an option to create a draft version that you can then get feedback on. Please also see Wikipedia's disambiguation guideline which indicates how to handle separate subjects with similar names. Take care --tony01:55, 7 November 2025 (UTC)[reply]
Hi, you should re-instate my nice text no I think you are making a mistake I am a amateur journalist and writer for the albanian rap scene I just write the most precisely possible biography of this singer My writing was completely neutral going from the base that an artist with 40 millions views on a hiss songs without a major deal is quiet something and I was describing exactly what the singer does Sind (talk) 02:48, 8 November 2025 (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.
Updates for editors
Example of a talk page with the new design, in French.
MediaWiki can now display a page indicator automatically while a page is protected. This feature is disabled by default. It can be enabled by community request. [10]
Using the "Show preview" or "Show changes" buttons in the wikitext editor will now carry over certain URL parameters like 'useskin', 'uselang' and 'section'. This update also fixes an issue where, if the browser crashed while previewing an edit to a single section, saving this edit could overwrite the entire page with just that section’s content. [11][12][13]
Wikivoyage wikis can use colored map markers in the article text. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed. [14]
The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. [15]
The Reader Growth team is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, will go live on English Wikipedia in the week of November 17 and will run for four weeks, affecting 0.05% of users on English wiki. The test launched on November 3 on Arabic, Chinese, French, Indonesian, and Vietnamese wikis, affecting up to 10% of users on those wikis. [16]
View all 27 community-submitted tasks that were resolved last week. For example the inability to lock accounts on mobile sites has been fixed. [17]
The JWT subject field in OAuth 2 access tokens will soon change from <user id> to mw:<identity type>:<user id>, where <identity type> is typically CentralAuth: (for SUL wikis) or local:<wiki id> (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and the sessionJwt cookie more similar. Old access tokens will still work. [19]
A REL1_45 branch for MediaWiki core and each of the extensions and skins in Wikimedia git has been created. This is the first step in the release process for MediaWiki 1.45.0, scheduled for late November 2025. If you are working on a critical bug fix or working on a new feature, you may need to take note of this change. [21]
The process for generating CirrusSearch dumps has been updated due to slowing performance. If you encounter any issues migrating to the replacement dumps, please contact the Search Platform Team for support. [22][23]
Sorry. If you received a automatic notification of an revert of your edit to this article you can ignore it. I was backing out an edit from early October and I mistakenly undid from the current version. Same overall effect (no change to your edit), but I now realize you may have been notified. Meters (talk) 22:20, 10 November 2025 (UTC)[reply]
lists of people and fictional characters do not belong on the disambiguation page, they belong on either the given name page or a separate page entirely. ~2025-32590-82 (talk) 05:40, 11 November 2025 (UTC)[reply]
Hello! I saw you posted a note on the article talk page shortly after leaving this message here. Just a heads-up: unexplained content removal can be indistinguishable from vandalism, so it would be helpful if you used edit summaries in the future. Take care --tony15:38, 11 November 2025 (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.
Updates for editors
The Reader Experience team is experimenting with reading lists on mobile web, allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November.
Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of the Account Security initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. Learn more.
As part of the Parser Unification project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in the Extension:ParserMigration documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the "Report Visual Bug" link in the Tools sidebar or create a phab ticket and tag the Content Transform Team in Phabricator.
Unsupported Tools: Several issues with Video2Commons have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check the Phabricator board.
Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026. Scholarship applications are currently open, and will close on November 28, 2025. If you have any questions, please email hackathon@wikimedia.org.
Hello! Voting in the 2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
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
Last week, the Wikimedia Search Team recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching for cxfcnmt on Russian Wikipedia will now add suggestions for счастье ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week. [25]
Later this week, users of the "Improved Syntax Highlighting" beta feature will have syntax highlighting available in DiscussionTools. This requires that the "Enable editing tools in source mode" preference be set. [26]
Campaign events extension – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known as Collaborative contribution to help organizers and participants see the impact of activities has also been added. Join the upcoming learning session to see the new feature in action and share your feedback.
View all 24 community-submitted tasks that were resolved last week. For example, the bug which stopped CodeReviewBot from working, has now been fixed. [27]
Updates for technical contributors
Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill the recruitment survey. [28]
The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support for format=xml&xlst={stylesheet} will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026). [29]
The WDQS legacy endpoint (query-legacy-full.wikidata.org) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (https://query.wikidata.org/ - Main graph or https://query-scholarly.wikidata.org/ - Scholarly graph). For support with migrating use cases, please review the Data Access and Request a Query pages for details and assistance on alternative access methods.
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.
This might help fill in some gaps too. This is pre the Image release, where he was selling them elsewhere, as I mentioned, mainly on Whatnot, and his own website.
It was after this that the deal to release them via Image came about, and the first issue was released on November 5. The roster is as I noted, and as featured on the covers: Badrock, Diehard, Shaft, Vogue, and Chapel. Hence why I updated the current roster. I did make a mistake though. I didn't make Chapel into a link. Although this isn't that Chapel, this is his son, so I don't know how you want to deal with that. ~2025-36331-46 (talk) 18:27, 25 November 2025 (UTC)[reply]
I'll just update the roster and leave the rest incomplete. I just don't have the time to learn how to add in references and such. I've re-edited it adding in things that otherwise don't require a source. I doubt anyone else cares about this to update it completely, but maybe someone will. ~2025-36631-62 (talk) 17:09, 26 November 2025 (UTC)[reply]
Hey all, just learned about conflict of interest so I cannot edit my 1st Cousin Bessie Halls page. I dont know if anyone would think it is important but I would sure be grateful for someone to add some more pics. Also about my Grandmother Irma Beatrice who changed her name to Rosalie Sipp after marrying my grandfather Charles Walter Sipp in Kansas City Missouri. I can provide more sites for sources if anyone would be interested. Thank you. If not I understand and I do not want to create any conflicts of interest at all. Here is one source for reference. Bessie Hall Dempsey – Oz Wisdoms and LessonsGSIPP (talk) 03:58, 26 November 2025 (UTC)[reply]
Hi @GSIPP! It looks like you meant to add this onto the talk page for the article Bessie Hall Dempsey, but you instead may have accidentally added it to my personal talk page instead. If you'd like, I can copy your comment to Talk:Bessie Hall Dempsey so other interested editors can take a look. Just let me know :) --tony04:00, 26 November 2025 (UTC)[reply]
I'm sorry about that but idk how to source stuff on Wikipedia, after talking to a few people from there it seemed to have an big impact on the school so I figured it would be worth mentioning as of its influence of the school, i saw you took it down and I was wondering could you put it back up and cite it maybe? Im sorry if thats annoying I just dont know how to do anything ~2025-36996-62 (talk) 02:47, 29 November 2025 (UTC)[reply]
I'm not sure how many people are using interceptor yet, but it's great that I can now patrol recent changes on mobile without the extreme difficulty I would otherwise face. Thanks a lot; I genuinely really appreciate it.
A suggestion if you don't mind: it would be great to have an option to warn users for not using an edit summary (with {{uw-es}}). Given that it's mobile-oriented, I think a really good way of doing this would be to replace the blank space where an edit summary should go with a button saying something like "warn for edit summary". In my experience, the majority of "false positive" edits that get flagged by ORES are there because they don't have an edsum, and I believe that sending out warnings for this would significantly improve the project. lp0 on fire()18:28, 30 November 2025 (UTC)[reply]
Hey Lp0 on fire! Thanks for the kind words :) I'm glad you're finding it useful. I appreciate the suggestion, too, and it's something I'll seriously look at as I make additions. Something on the roadmap soon is another section within the revert menu for single-use notices, and it will probably find its way in that area first, but the layout is all very much in flux so it might make sense at some point to move it to the (blank) edit summary. Can I ask what device/browser you're using? I haven't been able to test with an iPhone yet as I don't have one :) --tony19:27, 30 November 2025 (UTC)[reply]
I'm using an (ancient) Android phone. I think it's a Galaxy S6 but whatever it is it's running LineageOS. Excited for the single-issue notices – they're something I find lacking in many recent changes patrol tools. Again, thanks so much for developing this; now I can procrastinate efficiently on any device! lp0 on fire()07:25, 1 December 2025 (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.
Updates for editors
The Wikipedia Year in Review 2025 will be available on December 2 for users of iOS and Android Wikipedia apps, featuring new personalized insights, updated reading highlights, and refreshed designs. Learn more on the review's project page.
The Growth team is working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful and informative. Some new text have been drafted for A/B testing and you can help by translating them. See Phabricator.
Add a link will now be deployed at Japanese, Urdu and Chinese Wikipedias on December 2. Add a link is based on a prediction model that suggests links to be added to articles. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time. If you would like to know more, please contact Trizek (WMF).
View all 34 community-submitted tasks that were resolved last week. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed. [30]
The Wikimedia Foundation is in the early stages of exploring approaches to Article guidance. The initiative aims to identify interventions that could help new editors easily understand and apply existing Wikipedia practices and policies when creating an article. The project is in the exploration and early experimental design phase. All community members are encouraged to learn more about the project, and share their thoughts on the talk page.
Hello Tony, I'm confused. I just spent hours learning how to use Wikipedia's edit function and to correctly editing my page. This is not promotion, its accuracy. There was information that was obsolete, outdated, incorrect, private, and unnecessary. It was profoundly out of date. I spent all day updating and correcting it. I do not understand how all of that work can just be deleted. I'm very new to this. I'm learning. Was that work I spent all day on today saved or is it all just gone? All of the information I added was linked to external sources, primarily academic and news media sites such as Rolling Stone, Harper's Magazine, CNN, etc. In only a few instances did I link to my site, but only because I saw that older posts that had been on Wikipedia for years were linked to my website, so I assumed that must be acceptable. I do not understand why links to prestigious and well-known media outlets, as well as links to academic sites where journalism Fellowships, Adjunct Faculty positions, etc. which I linked to should be unacceptable. I improved the wikipedia page for accuracy, timeliness, improved the links, and reflected how I am known in the popular culture. Existing entries which I deleted did not do the same. Can you please restore the work I spent all day on today? Thank you very much. MNYUHG (talk) 19:26, 2 December 2025 (UTC)[reply]
Hi MNYUHG! I see you left a similar message on your talk page, so I'll respond there to consolidate the discussion. tony20:16, 2 December 2025 (UTC)[reply]
Hi Tony, The passage added by @deepbajwareal which you have just added by reversion in the Border 2 (film) => Casting section is grammatically poorly written. The grammar needs to be corrected for that article. That is why I had removed it earlier. Robzz (talk) 16:15, 3 December 2025 (UTC)[reply]
Hey @Robzz, really sorry for the template! I noticed the invisible comment you added in this diff, which looks to be an attempt at using the article itself to communicate with another specific editor. In reverting that addition it also swept up the previous edit you made where you removed some bad grammar. I was about to offer to restore your change (sans invisible-comment) but it looks like you beat me to it :) --tony16:30, 3 December 2025 (UTC)[reply]
On December 9, 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. 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 totals during the election. You must be extended confirmed to vote.
Once voting concludes, we will begin the scrutineering phase, which typically lasts between a couple days and 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, a candidate who has not been recalled must have received at least 70.0% support, calculated as Support / (Support + Oppose), and must also have received a minimum of 20 support votes. A candidate that has been recalled must have at least 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.
Hey @TonySt. Your wiki edit anniversary was 1 day ago, marking 20 years of dedicated contributions to English Wikipedia. Your passion for sharing knowledge and your remarkable contributions have not only enriched the project, but also inspired countless others to contribute. Thank you for your amazing contributions. Wishing you many more wonderful years ahead in the Wiki journey. :) -❙❚❚❙❙ GnOeee ❚❙❚❙❙✉08:25, 5 December 2025 (UTC)[reply]
I'll bet you are a Tony Stark. I just noticed your invention on Interceptor. Looks really cool! And wish to try it out someday. You seem to be wikipedia's top gun leader when patrolling rc. Great work! B⠄Jayden(talk)15:34, 5 December 2025 (UTC)[reply]
Thank you for the kind words Jayden! I've seen your name often lately, and your help in recent changes patrolling is very much noticed and appreciated by many of us :) Take care! --tony15:53, 5 December 2025 (UTC)[reply]
"Hello,
I am writing to sincerely apologize for my recent edits to the Joseph Bruchec page a few weeks ago. I now understand that my changes were disruptive/incorrect, and I take full responsibility for "ruining" the article temporarily.
I have since reverted my changes to restore the correct version.
It was not my intention to cause harm to the encyclopedia, and I will be more careful in the future and review the core Wikipedia editing policies and manual of style to ensure my contributions are constructive.
Thank you for your understanding.
Tony that apology was made by ai.
Here is my real apology. I hope you can forgive me for my actions and I expect the fullest of consquences to my actions and I admit, I was wrong. I was very DISRUPTIVE and annoying so I hope you can forgive me and I will go to church to confess my sins.
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
Anybody who wishes to secure their user account can now use two-factor authentication (2FA). This is available to all registered users of all Wikimedia projects. This is part of the Account Security initiative. Later, 2FA will be required for all users who can take security- or privacy-sensitive actions.
Updates for editors
Following last week's deployments, the Add a link feature, which allows editors to add suggested links during editing, will be available to an additional 33 Wikipedias starting on 9 December. This expansion is possible thanks to the new prediction model that now supports all languages, including those that were previously not covered. While the feature has been available on most Wikipedias for some time, this rollout brings us closer to using the improved model everywhere. If you have any questions or would like more details please contact Trizek (WMF).
Last week, the Search Platform team added transliterated as-you-type search suggestions to Georgian wikis. If there are only a few regular search suggestions, then queries in Latin or Cyrillic script are now rewritten into Georgian script to look for more matches. For example, searching for either bedniereba or бедниереба will now suggest the existing article about ბედნიერება ("happiness"). You can recommend other languages where transliterated suggestions would be useful on Phabricator for future development.
Later this week, a controlled experiment will begin for editors on the 100 largest Wikipedias who are editing a section in the mobile web visual editor. 50% of these editors will notice a new "Edit full page" button that will enable them to expand their editing session to the whole page. This feature is intended to make it easier for people on mobile web to edit any article section, regardless of which section-edit icon they tapped to begin. The experiment will last ~4 weeks. You can find more details about the project.
Later this week, the Reader Growth team will launch a mobile web experiment to expand all article sections by default (currently they are collapsed by default) and pin the section header the user is currently reading to the top of the page. The experiment will affect 10% of users on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias. [33]
The Wikipedia Year in Review 2025, a feature in the Wikipedia mobile apps (iOS and Android) that provides users with a personalised summary of their engagement with Wikipedia over the year, is now available on the iOS and Android apps. This edition includes expanded personalised insights, improved reading highlights, new donor messaging, and updated designs. Open the app to view your Year in Review and explore your reading journey from 2025.
A recent software bug caused edits made with VisualEditor to make unintended changes to wikitext, including removing whitespace and replacing spaces with underscores in wikilinks inside citations. This was partially fixed last week, and further fixes are in progress. Editors who used VisualEditor between November 28 and December 2 should review their edits for unexpected modifications. [34]
View all 23 community-submitted tasks that were resolved last week. For example, the incorrect handling of URLs copied from the address bar of Microsoft Edge users, has been resolved. [35]
Updates for technical contributors
Starting this week, users of the "Improved Syntax Highlighting" beta feature will have CodeMirror as the editor for Lua, JavaScript, CSS, JSON and Vue content models, instead of CodeEditor. With this, the linters will be upgraded. This is part of a larger effort to eventually replace CodeEditor and provide a consistent code editing experience. [36]
Developers are encouraged to take the 2025 Developer Satisfaction Survey, which remains open until 5 January 2026. If you build software for the Wikimedia ecosystem and would like to share your experiences or feedback, your participation is greatly appreciated. [37]
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.
I’d appreciate your advice. Attempts to update certain biographies in accordance with the RFC appear to result in reversions or site blocks. Is it not reasonable to consult editors who are active in the topic area and have a deeper understanding of the platform? ~2025-39528-98 (talk) 01:53, 9 December 2025 (UTC)[reply]
Yes, edit requests are exempt from this, except that yours was disruptive and controversial, so it was procedurally denied. But despite this, you kept repeating your edit request despite warning, causing you to be sanctions. --pro-anti-air ––>(talk)<–– 02:58, 9 December 2025 (UTC)[reply]
@~2025-39528-98, your edit request was the opposite of uncontroversial and it was denied as such. The duplicate request was disruptive and the canvassing doubly so. Which named user account(s) have you previously used to edit on this project? I may be able to offer advice if I know who I'm talking with. tony02:19, 9 December 2025 (UTC)[reply]
Any edit on the page is seemingly controversial (including adding books to the bibliography?) and includies the current addition which was added without consensus, mind you. It was apporpriate notification given WP: Canvassing
On the user talk pages of concerned editors. Examples include:
Editors who have made substantial edits to the topic or article
Editors who have participated in previous discussions on the same topic (or closely related topics)
Editors known for expertise in the field
Editors who have asked to be kept informed
Given that, advice for updating the content to reflect recent news by editors who seem not interested in making even neutral edits, would be helpful. ~2025-39528-98 (talk) 02:50, 9 December 2025 (UTC)[reply]
Hey Elijah Wilder! I've used a few tools in the past, like AntiVandal and lately a script I wrote. Both of those tools require that you're in the "rollbackers" group, which is something you receive after requesting it at WP:RFP/R. But a lot of the time I'm just using Twinkle, which it looks like you're familiar with. Twinkle doesn't require rollback, but is still probably more useful in general than any of the semi-automated tools like AV or Huggle or Interceptor.
Most of recent changes patrolling is based on communication, calmness, denial, and accountability -- that is: being able to talk to people who are angry, being able to walk away from a situation, being able to ignore nasty insults, and being able to accept when you are wrong.
Most of "talking to people" is, in practice, done with escalating templates that are designed to let people know why you reverted them. Vandals usually receive four of these before being reported to AIV. Beyond templates, it's a lot of overly-nicely communicating with people who reach out to you via your talk page or theirs, especially when they're mad.
I also have a rule for myself, which is I never delete things from my own talk page unless they're obvious vandalism or block evasion. If someone is trolling I usually ignore them, but otherwise I always try to answer them, especially if it seems like I've done something wrong (and when that happens I try my best to fix it).
I don't have rollback rights and my previous history might make it harder to get them. I think after some time on here and proving myself I will be eligible again. Elijah Wilder (talk) 03:39, 13 December 2025 (UTC)[reply]
I want to say thanks on the edit you did on Ron McNeil (musician)'s page. I never knew that McNeil formed a Beatles tribute before The Fab Four. There isn't any proof or sources that McNeil had Imagine: A Tribute to the Beatles before the Fab Four. And that McNeil has never mentioned that band in any of his interviews regarding the Fab Four and his other tribute band the Monkee Men, even news articles. And I don't think there are any YouTube videos regarding it. So again, thank you. Dream7392 (talk) 05:56, 14 December 2025 (UTC)[reply]
Hi,
I see that you edited this page Ezhava recently kindly do refer to the recent addition to this page and the introduction of a political POV fork in the lead kindly recert the edit if needed. Miamiller777 (talk) 06:22, 14 December 2025 (UTC)[reply]
Hi Tony! I was going through some of the WP:GS authorizations to see if there are any that we don't need anymore. I noticed that you are a frequent alert-giver—of the ~13 alerts since 2021, you gave out 5 of them. I still lean towards removal: it seems like most of the disruption comes from new SPAs who probably should just be indef'd. The last user enforcement action was in 2022; the rest is just protection which could occur regardless of whether or not there was a GS. But given you are handing out a bunch of alerts, I wanted to check and see your thoughts on the matter :) Best, HouseBlaster (talk • he/they)23:22, 14 December 2025 (UTC)[reply]
Hey HouseBlaster! Thanks for reaching out. I'd support a repeal of that GS. As you mentioned the disruption in that topic tends to be the type that can be taken care of via normal protection or blocks. My use of the alerts is mostly to give a heads up to any user who might wiggle themselves into the tiny space of PW-topic disruption that could only be addressed via GS, but in practice that hasn't really happened (and in retrospect I'm not sure what I was doing with the TA and IP alert!). tony00:38, 15 December 2025 (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.
Updates for editors
View all 18 community-submitted tasks that were resolved last week. For example, one of the fixes addressed an issue for temporary accounts adding an external URL, which triggered an hCaptcha request in more cases than intended, and did not display the required popup on the first attempt to publish the edit. [38]
Updates for technical contributors
To improve database and site performance, external links to Wikimedia projects will no longer be stored in the database. This means they will not be searchable in Special:LinkSearch, will not be checked by the Spam Blacklist or AbuseFilter as new links, and will not be in the externallinks table on database replicas. In the future this may be extended to other highly-linked trusted websites on a per-wiki basis, such as Creative Commons links on Wikimedia Commons. [39]
Hi Tony, my edit was snarky - but information was drawn from a quality source, cited (The Spinoff). I've removed the snark, and the perhaps excessive reproduction of verbatim falsehoods. Not trying to vandalize. Thanks. IdiotSavant42 (talk) 04:54, 16 December 2025 (UTC)[reply]
Hey @IdiotSavant42! It wasn't reverted for vandalism -- the "snark" was the reason for the NPOV revert, and I appreciate you re-adding your contribution without it. Sorry for the template, and thank you for reaching out :) --tony05:05, 16 December 2025 (UTC)[reply]
As a request, it would be nice if rollbacks for things like "unsourced" or "NPOV" weren't marked as minor since minor edits are usually just for reverting vandalism and tests. There is technically an exemption for any tool that uses rollback but it would be nice not to need that.
That non-warning reversion is weird and concerning, I haven't run into that yet. Do you have any recollection of it showing you a notification (at the bottom, like the "editconflict" or "alreadyrolled" you sometimes see)? I'll do some troubleshooting to figure out what's going on, and I'll also make sure it throws a notification on any issues when writing to talk page.
Good catch with the "minor" thing. I'll adjust it to only mark "vandalism" reversions as minor, which seems more in line with the spirit of WP:MINOR, as you suggested.
I'm about to push a version that has some single-issue warnings in the revert menu -- it's still a work in progress as far as how those warnings are presented but hopefully they're useful. I'm planning on having that version out today, and then after that another small fix today for the minor edits and more verbose notifications. Thank you for letting me know about these, and definitely please keep letting me know if you see anything amiss or if there are any additional features you'd like to see. tony14:37, 16 December 2025 (UTC)[reply]
Thanks so much! This is really an amazing tool, and I'd guess it's probably just about the only thing I do on mobile now.
As far as I remember there was no notification for that edit. I was using rather patchy Wi-Fi though, so it's plausible that it reverted, couldn't warn because the connection died, and then forgot to do it when the Wi-Fi came back on.
I suppose I'll find out soon, but I wonder whether it would be possible to issue single-issue notices (e.g. edit summaries) without reverting the edit in question. lp0 on fire()15:52, 16 December 2025 (UTC)[reply]
You should now see those single-issue templates. I'm not super happy with how it's laid out just yet, but it's there now. I've also added in some additional notifications for errors, though I suspect your inkling is right in that it was probably a network error. Network errors will still prevent warnings at this point, but now it should at least give you a heads-up when that happens. I'm still investigating the "minor" edits thing -- the fix was easy for warnings but the rollbacks being marked as minor is proving to be more difficult. tony16:21, 16 December 2025 (UTC)[reply]
Here things seem to be working as intended. It threw http, so I redid it. The second time it threw alreadyrolled, but it seems that one of the two times did result in a warning. lp0 on fire()18:42, 16 December 2025 (UTC)[reply]
Hey @Lp0 on fire, following up on this: turns out rollback actions via API are automatically marked as "minor" by the MediaWiki software, and there's unfortunately nothing I can change to alter that :( --tony03:22, 24 December 2025 (UTC)[reply]
That's a shame. I think LunieZunie found a way of doing it for WikiShield (don't quote me on that) so perhaps you (or I) could ask how they did it? lp0 on fire()10:12, 24 December 2025 (UTC)[reply]
Not at all -- the original issue you were talking about was the warnings being issued as "minor", which is now fixed thanks to you mentioning it :) tony16:26, 24 December 2025 (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.
Updates for editors
From January, edit filters can be set to automatically suppress their details such as rules and list of attempted edits and actions. This will help oversighters use edit filters to prevent doxxing or other suppressible material. [40]
The next issue of Tech News will be sent out on 12 January 2026 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year.
View all 16 community-submitted tasks that were resolved last week. For example, the crash that occurred when tapping "First Steps" in the Wikipedia Android Year in Review has now been fixed, and the feature opens as expected. [41]
Updates for technical contributors
Interface elements such as diffs and categories generated by MediaWiki used to have the attribute data-mw="interface" to distinguish from wiki content. The attribute has been replaced with data-mw-interface="", to avoid potential conflicts with other data-mw attributes, which are generated by Parsoid. [42]
There is no new MediaWiki version this week or next week.
Meetings and events
The Wikimedia Hackathon Northwestern Europe 2026 will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications just opened mid-December and will close in mid-January or earlier if capacity is reached. With space for approximately 100 participants, early application is encouraged.
If you had thought I'd totally forgotten about trying to use CVPI, shame on you! I always keep my word : ) The moment to test out the tool has come. It looks awesome! I think I nailed in the first two edits with it. The rest of the time till now, I've just been skipping through a pile of edits to catch the rhythm (you know what I'm saying?). Sadly, a glitch happens to me whereby the feed completely stops updating and displays the message "Waiting for next change...", even after 20 minutes of waiting, which looks really awkward. I solved this by restarting the browser and re entering CVPI, but this solution doesn't seem right, because it keeps on happening again. I also disabled all browser extensions. You enter CVPI and enjoy the feed for about 5 minutes, then it stops updating. I suppose the tool was created to favor mobile smartphones? I'm using the latest version of Chrome, 143.0.7499.148, on Windows 11. Oh yeah and another teaser! I noticed the message you added to the loading page of CVPI, it ends with "...st computer, or are the world's fastest reader." LOL! To tell you the truth, it displayed for like 3 seconds on my screen. I only read from the middle to the last parts of the message as normally as I do before it disappeared, and I was like "What the heck man?? He actually planned this!!!!", Hah! Cool! Happy holiday! B⠄Jayden(talk)00:06, 23 December 2025 (UTC)[reply]
Hey @B.Jayden! Thank you for reaching out about this. That "Waiting..." thing is super weird behavior. I use the tool in Chrome with a Windows 11 machine and a MacOS machine, and I regularly use it for pretty long periods (usually more than 15 minutes and sometimes upwards of an hour). Can I ask what ORES setting you're using? I'd expect it to hang indefinitely if it's a very high setting (like 1.00), but if it's a lower setting (like the default 0.15) then it shouldn't hang unless there's significant network issues. Also, it sounds like you ARE a pretty fast reader :) --tony02:50, 23 December 2025 (UTC)[reply]
Oh heck yeah, my high school teacher also said the same thing about my reading skills. That was looong ago. Yeah! ORES! I haven't tripped that up yet, but still at the default 0.15 you've set, I still don't receive any feed updates after 5 to 10 minutes, so had to use twinkle to run today. I'll try to shift the ORES volume to 0.00 and see if I can live for at least more than 30 minutes, but will not revert. My network's always above 5 bars, so I doubt it could be the issue. Yeah, I'll check back with ya later. It's kinda sad things didn't work out the first time as expected. If it fails again, I'll try restarting Windows or just use a different browser and see. B⠄Jayden(talk)03:34, 23 December 2025 (UTC)[reply]
CVPI is awesome! I was going to make a new section, but since there's already one with this title, I'll ask here: what does CVPI stand for? lp0 on fire()21:43, 23 December 2025 (UTC)[reply]
Hi Tony. Update, I think I'll have to stop using CVPI for the moment, still no luck. The maximum alive time until the recent feed stopped updating was about 15 minutes (an improvement to when I first ran it at least) but then froze on the waiting notice again. Same thing happened with different browsers like Edge, Firefox, etc. Maybe I'll try again in a few months when you've patched some updates to it? And Chrome will be far more better than it is now. Thanks for all your work. B⠄Jayden(talk)22:09, 23 December 2025 (UTC)[reply]
Hey @B.Jayden, I just pushed an update a few minutes ago, if you could let me know if that fixes your issue I'd appreciate it. I just pushed a version that fixes a bug related to how the ORES scores are fetched, and I'm thinking it might help you. You may (or may not!) need to clear your cache for the script to update on your machine. Take care --tony23:14, 23 December 2025 (UTC)[reply]
Ah, unlucky! Sad news, there is a new faulty behavior with CVPI. This time when I click on "Next" to view the next edit. The new edit appears about 10-15 seconds after the waiting notice in the center. This also happens when there are current edits left available to see (by the visible number showing on "Next"). Also tested with other browsers and juggled the ORES volume back and forth. Even at 0.00 which is wicked fast!! Going to the next edit takes time to load up. I Even tried switching between 7 different MiFi connections to confirm this, and my PC speed is totally exceptional. It's a gaming setup. Don't stress yourself too much on this man, you did just fine. I obviously won't forget to try this out again soon. Thanks. B⠄Jayden(talk)02:59, 24 December 2025 (UTC)[reply]
It's not unusual to wait that long between edits being shown, but it's very strange that it still says there's edits waiting for you (with the number next to "next") even when it's waiting. If you see any notifications pop up or additional feedback from the tool that you find relevant, please let me know :) --tony03:18, 24 December 2025 (UTC)[reply]
You have been making Wikipedia way better by reverting vandalism. I really appreciate that you revert it and never stop. Thanks for your contributions to Wikipedia.
Hello Tonyst,
I suppose you are in control of what changes are allowed on the article you may have written. And in response to your response of the changes I made to the header Hebrew Bible in https://en.wikipedia.org/wiki/Fall_of_Babylon I now respond to your message here:
Hello, I'm TonySt. I noticed that you added or changed content in an article, Fall of Babylon, but you didn't provide a reliable source. On Wikipedia, it's important that article content be verifiable. If you'd like to resubmit your change with a citation, your edit is archived in the page history. If you have any questions, you can leave me a message on my talk page. Thank you. tony 05:25, 26 December 2025 (UTC)
I have supplied the Scriptures as reliable source, just as the header of the article presupposes the reader interprets it as. Which the original author or multiple authors of the article under the header have done as well, but I have corrected the errors. What do you mean with not having supplied a reliable source? Kind regards, Ruben ~2025-43059-40 (talk) 05:32, 26 December 2025 (UTC) ~2025-43059-40 (talk) 05:43, 26 December 2025 (UTC)[reply]
The battle is called Battle off Ulsan. There have been several battles on land at Ulsan. In particular, it was a notable time during the Imjin War, in the development of Korea. The Russ-Japanese War happened centuries later. Korean martial arts and Gakgung both refer to the Imjin War's Battle of Ulsan, not the Russo-Japanese War -- ~2025-41582-72 (talk) 04:23, 28 December 2025 (UTC)[reply]
Hey @~2025-41582-72, thank you for reaching out and for the information. Just a heads-up -- it's probably a good idea to use an edit summary with that information, since otherwise other editors might think it's an introduction of a typo instead of the correction you're describing. Thank you for your contributions :) --tony04:27, 28 December 2025 (UTC)[reply]
Thank you for reporting this! "http" error means it received an error code from the server (like a 404 or 503). I was seeing a bunch of these last night and yesterday, and when it happened I clicked a few diff links and one of them opened to a server error instead of the diff link. It looks like the Wikimedia servers have been having issues over the last day or so. I'll adjust that message so it isn't lying about the warning not being left. I also need to change how those errors are reported in general because when the servers start having issues it can sometimes spit out a TON of errors when it really only needs one. Again, thanks for letting me know, it's only possible to fix these issues because you report them :) tony16:47, 28 December 2025 (UTC)[reply]