User talk:Callanecc

Callanecc is busy and may not respond swiftly to queries.

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

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28: 32 days

If you wish to discuss or inform me of a sensitive or private matter please read User:Callanecc/Emailnotice before emailing me.

If I left you a message: please answer on your talk page, as I am watching it. If it was a warning or other notice please ping me so I know to look.
If you leave me a message: I will answer on this talk page, so please add it to your watchlist.

This user talk page might be watched by friendly talk page stalkers which means that someone other than me might reply to your query. Their input is welcome and their help with messages is appreciated.

Question about Contentious topics/India, Pakistan, and Afghanistan

I was hoping to make some factual edits on the weapon systems used in the recent India-Pakistan conflict. Is it just not possible for people with my permission levels to edit anything around India/Pakistan/and Afghanistan ? Sukosuko1 (talk) 07:47, 12 May 2025 (UTC)[reply]

Hi @Sukosuko1, you can make those sorts of edits as long as you cite reliable sources. I've left a message on your talk page with some information about Contentious Topics. Sometimes articles are protected from editing due to a history of disruption, you won't be able to edit these articles. Callanecc (talk • contribs • logs) 08:44, 12 May 2025 (UTC)[reply]

History of Vietnam

This article has a very long history of persistent vandalism by multiple accounts and IP addresses (sock puppets of Phạm Văn Rạng). It is currently temporarily semi-protected, but I would like to request permanent semi-protection as it is an important article. 2401:D800:2B2:353F:7358:BDF5:EF6B:8B56 (talk) 08:24, 12 May 2025 (UTC)[reply]

Hello, the article has been semi-protected until October this year. We tend to lean towards temporary protections due to sockpuppetry since the premise of Wikipedia is that everyone can edit and sockpuppetry is an isolated (to one person) form of disruption rather than being a long term history of lots of different people causing problems. Callanecc (talk • contribs • logs) 08:41, 12 May 2025 (UTC)[reply]

I fear that this important article will be vandalized as soon as the protection expires. At the very least I think we need to have edit moderation for accounts with less than 4 days and 10 edits as well as IP addresses, like in History of the United States article. 2402:800:BAA1:1E45:FEEA:EE89:E02D:62C8 (talk) 09:50, 12 May 2025 (UTC)[reply]

This is a very important article like the article about history of China, and there have been many vandalisms by many different people, Phạm Văn Rạng is just a recent prominent vandal. A proper protection is deserved. 2402:800:BAA1:1E45:FEEA:EE89:E02D:62C8 (talk) 10:00, 12 May 2025 (UTC)[reply]

You are probably right, but as I didn't add the protection I'll wait until the semi-protection has run out before doing anything further. Callanecc (talk • contribs • logs) 10:16, 12 May 2025 (UTC)[reply]

Thanks! 2401:D800:224:EB34:F1A8:4531:BCD7:6B9 (talk) 03:27, 14 May 2025 (UTC)[reply]

Phạm Văn Rạng came back, my requests make sense. 2401:D800:262:188A:F854:4FB2:F87B:55E2 (talk) 08:41, 17 May 2025 (UTC)[reply]

Operation Léa

An IP address of Pham Van Rang is vandalizing this article, I hope you will revert this IP's edits and install proper protection for this article. 2401:D800:267:CD60:7031:32B8:6B70:501F (talk) 11:32, 15 May 2025 (UTC)[reply]

Phạm Văn Rạng's edits were reverted👍. 2401:D800:2C:9B08:7564:DE9E:821D:F3EE (talk) 13:52, 15 May 2025 (UTC)[reply]

The rest was done by Sir Sputnik👍. The article has been semi-protected. 2402:800:5EDF:BEFF:25EC:BC71:E9F5:8C5C (talk) 18:15, 15 May 2025 (UTC)[reply]

Veilguard edit warring

Hello @Callanecc, I'm contacting you because you applied the most recent protection to the Veilguard article due to edit warring. The situation still hasn't improved, and there's one point where your input might help. An editor mentioned the WP:STABLE essay, which says that only an uninvolved administrator can decide to keep the stable version to help calm a dispute. Based on the history of the article, a clarification and action would be helpful to reduce the edit warring. Most of the reverts are just about this and probably won’t stop without some clarification.

Since you've protected the page twice, does that mean you're now considered involved, and that another admin would need to make that call? Vestigium Leonis (talk) 17:51, 18 May 2025 (UTC)[reply]

It seems that you are very concerned about having your preferred version in the short term, but this is a long running dispute so there isn't a clear stable version.[1] The solution is to work toward a consensus rather than asking an admin to pick your preferred version. BMWF (talk) 19:33, 18 May 2025 (UTC)[reply]

I am simply asking the last involved admin how to handle this situation. The dispute ended months ago, and the article remained stable until May 15. I am fine with whatever the admin answers or decides here; I just don't believe that this can be resolved at the editor level anymore. Vestigium Leonis (talk) 20:20, 18 May 2025 (UTC)[reply]

I've replied on the article talk page. Callanecc (talk • contribs • logs) 08:30, 19 May 2025 (UTC)[reply]

Thanks! I figured not everyone would be happy (it is a dispute, after all), but at least the focus is back on the talk page. Vestigium Leonis (talk) 09:29, 19 May 2025 (UTC)[reply]

Continued edit warring on an article you previously protected

You recently gave a 24 full protection to Sabu (wrestler) due to edit warring over his birth and death dates. Since the article opened back up, the edit warring has only intensified. Now they’re also arguing about whether his real name was Terrence or Terry and at least one established editor has ignored a 3RR warning and continued to do so. I did file another protection request but it seems to have been ignored for the last day or so. Would you mind looking into the situation again? Thanks. NJZombie (talk) 15:19, 19 May 2025 (UTC)[reply]

Thanks for the heads up @NJZombie. It looks like Ymblanter is dealing with it. Callanecc (talk • contribs • logs) 08:04, 21 May 2025 (UTC)[reply]

Unfortunately, they’re not. They blocked one editor but refused to block the main offender. I have a report up on wp:AN/3 now. NJZombie (talk) 10:17, 21 May 2025 (UTC)[reply]

Brunei

Hi Callanecc, it's been 11 years since you placed the Brunei article under semi-protection. Do you think, after all this time, the current protection level is still necessary, or do you think you could either unprotect it or downgrade the protection to pending changes to see how it goes? Brunei doesn't fall under any Contentious topics, and it's a country not many talk about (at least compare it to Singapore, for example). I also find it ironic how the English version of this article is protected, but not the Malay version of this article (Malay being the country's official language). BriDash9000 (talk) 03:40, 23 May 2025 (UTC)[reply]

Hi @BriDash9000, re your Singapore example, I note that the Singapore article is indefinitely semiprotected but I'm happy to give it a go. I've downgraded the protection of Brunei to pending changes to see how it goes. Callanecc (talk • contribs • logs) 07:06, 24 May 2025 (UTC)[reply]

History of Vietnam again

As I warned you above, this article is classified as an important article and it is also sensitive so it is very vulnerable to vandalism (history has proven). This article has recently continued to be heavily vandalized by not only a sockpuppet account of Phạm Văn Rạng (talk · contribs) but also a sockpuppet account of Sotavino (talk · contribs) (another banned account). I understand Wikipedia's policy is to prioritize ease and openness in editing, however ease and openness with this article only brings negativity and chaos to it rather than contribution. We need to be tough to defend this article. Currently the article is protected at 30/500 until 25 May 2026, however I think we should increase the protection to permanent like the article History of India. 2401:D800:DA1:59EE:2816:2286:31C0:E383 (talk) 00:42, 29 May 2025 (UTC)[reply]

Hi, we tend to be hesitant to idenfinitely protect articles at levels higher than semiprotection due to the number of people it effectively prevents from being able to edit it. History of India, for example, is only indefinitely semiprotected. This is especially the case when it's primarily due to sockpuppetry rather than being random but continuous vandalism. It's got a year of ECP on it so let's see what happens after that especially since it isn't technically possible to indefinitely semiprotect it now as that would remove the higher level of protection. Callanecc (talk • contribs • logs) 01:20, 29 May 2025 (UTC)[reply]

I see. Sorry, I was wrong about the protection level for the article History of India! In my opinion, when the protection term for the article History of Vietnam expires (although there is still nearly a year left), this article needs to be semi-protected indefinitely. Thanks for getting back to me! 2401:D800:7E06:A62:9C1E:D84:55D:8983 (talk) 13:05, 29 May 2025 (UTC)[reply]

Tech News: 2025-23

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

Weekly highlight

The Chart extension is now available on all Wikimedia wikis. Editors can use this new extension to create interactive data visualizations like bar, line, area, and pie charts. Charts are designed to replace many of the uses of the legacy Graph extension.

Updates for editors

It is now easier to configure automatic citations for your wiki within the visual editor's citation generator. Administrators can now set a default template by using the _default key in the local MediaWiki:Citoid-template-type-map.json page (example diff). Setting this default will also help to future-proof your existing configurations when new item types are added in the future. You can still set templates for individual item types as they will be preferred to the default template. [2]
View all 20 community-submitted tasks that were resolved last week.

Updates for technical contributors

Starting the week of June 2, bots logging in using action=login or action=clientlogin will fail more often. This is because of stronger protections against suspicious logins. Bots using bot passwords or using a loginless authentication method such as OAuth are not affected. If your bot is not using one of those, you should update it; using action=login without a bot password was deprecated in 2016. For most bots, this only requires changing what password the bot uses. [3]
From this week, Wikimedia wikis will allow ES2017 features in JavaScript code for official code, gadgets, and user scripts. The most visible feature of ES2017 is async/await syntax, allowing for easier-to-read code. Until this week, the platform only allowed up to ES2016, and a few months before that, up to ES2015. [4]
Detailed code updates later this week: MediaWiki

Meetings and events

Scholarship applications to participate in the GLAM Wiki Conference 2025 are now open. The conference will take place from 30 October to 1 November, in Lisbon, Portugal. GLAM contributors who lack the means to support their participation can apply here. Scholarship applications close on June 7th.

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

MediaWiki message delivery 23:52, 2 June 2025 (UTC)[reply]

Administrators' newsletter – June 2025

News and updates for administrators from the past month (May 2025).

Administrator changes

Interface administrator changes

0xDeadbeef

CheckUser changes

L235

Oversight changes

L235

Guideline and policy news

An RfC is open to determine whether the English Wikipedia community should adopt a position on AI development by the WMF and its affiliates.

Technical news

A new feature called Multiblocks will be deployed on English Wikipedia on the week of June 2. See the relevant announcement on the administrators' noticeboard.
History merges performed using the mergehistory special page are now logged at both the source and destination, rather than just the source as previously, after this RFC and the resolution of T118132.

Arbitration

An arbitration case named Indian military history has been opened. Evidence submissions for this case close on 8 June.

Miscellaneous

Voting for the Universal Code of Conduct Coordinating Committee (U4C) election is open until 17 June 2025. Read the voting page on Meta-Wiki and cast your vote here!
An Articles for Creation backlog drive is happening in June 2025, with over 1,600 drafts awaiting review from the past two months. In addition to AfC participants, all administrators and new page patrollers can help review using the Yet Another AFC Helper Script, which can be enabled in the Gadgets settings. Sign up here to participate!
The Unreferenced articles backlog drive is happening in June 2025 to reduce the backlog of articles tagged with {{Unreferenced}}. You can help reduce the backlog by adding citations to these articles. Sign up to participate!

Sent by MediaWiki message delivery (talk) 17:16, 6 June 2025 (UTC)[reply]