Jump to content

User:FlyingKiwi/Dash

From Wikipedia, the free encyclopedia


CAVEAT: all the |show= parameters have been set to 7 days.


Immediate requests Entries
Candidates for speedy deletion as attack pages 0
Wikipedians looking for help 1
Requests for unblock 116
Wikipedia semi-protected edit requests 57
Wikipedia template-protected edit requests 15
Wikipedia fully protected edit requests 3
Wikipedia conflict of interest edit requests 190
Candidates for speedy deletion as copyright violations 0
Candidates for speedy deletion 42
Open sockpuppet investigations 307
Click here to locate other admin backlogs

AB = Administrative Backlogs

[edit]

Administrative backlog

[edit]

AIV= Administrator intervention against vandalism

Administrator intervention against vandalism


Reports

[edit]

User-reported

[edit]


CSD= Candidates for speedy deletion ; PROD= Proposed deletions

Candidates for speedy deletion Entries
User requested 10
Empty articles 0
Nonsense pages 1
Spam pages 12
Importance or significance not asserted 5
Other candidates 15

The following articles have been proposed for deletion for around 7 days:
( source / chronological order / expired )

UAA= Usernames for administrator attention ; RFPP= Requests for page protection

Usernames for administrator attention

User-reported

[edit]
  • Damudcock (talk · contribs · deleted · filter log · SUL · Google) (block · soft · promo · cause · bot · hard · spam · vandal) – Violation of the username policy as a disruptive username. Jdcomix (talk) 00:55, 3 August 2024 (UTC)
    @Jdcomix: Do not leave a username warning on a user's talk page and also immediately report them here. Do one or the other, and not both simultaneously. jlwoodwa (talk) 03:58, 3 August 2024 (UTC)
Requests for page protection


Current requests for increase in protection level

[edit]
Request protection of a page, or increasing the protection level

Place requests for new or upgrading pending changes, semi-protection, full protection, move protection, create protection, template editor protection, or upload protection at the BOTTOM of this section. Check the archive of fulfilled and denied requests or, failing that, the page history if you cannot find your request. Only recently answered requests are still listed here.


Reason: IP editors repeatedly adding spam link. Skyerise (talk) 09:21, 2 August 2024 (UTC)

Semi-protected for a period of one week, after which the page will be automatically unprotected. Daniel Case (talk) 04:55, 3 August 2024 (UTC)

Reason: Edit warring Trade (talk) 11:35, 2 August 2024 (UTC)

Declined – Not enough recent disruptive activity to justify protection. Daniel Case (talk) 04:11, 3 August 2024 (UTC)

Semi-protection: Persistent vandalism. — GhostInTheMachine talk to me 12:17, 2 August 2024 (UTC)

Semi-protected for a period of 10 days, after which the page will be automatically unprotected. Will leave CTOPS notice on talk page Daniel Case (talk) 04:18, 3 August 2024 (UTC)

Reason: Request indef EC protection of this ARBPIA article. Frequent unsatisfactory non-EC edits. Zerotalk 14:10, 2 August 2024 (UTC)

Extended confirmed protected indefinitely. Will log at CTOPS. Daniel Case (talk) 04:22, 3 August 2024 (UTC)

Reason: The subject of the article regularly makes edits (via IP address) which then have to be reverted by others due to being contrary to the results of earlier COI edit requests: e.g. recently [1], [2], [3]. See also, edits under a previous IP address here [4]. Some form of page protection would seem desirable to prevent IP addresses from editing the article directly. (Copying in Melcous who has had previous experience on this article.) Axad12 (talk) 14:30, 2 August 2024 (UTC)

Having had the chance to look further into this issue, there is a recurring problem that has been going on since 2020 where various IP addresses, claiming to be the subject, either (a) make an edit contrary to COI policy, (b) make an edit contrary to COI policy and directly afterwards make a (rather redundant) COI edit request on the article talk page, (c) make a COI edit request and then make the edit themselves within an hour or so of making the request, or (d) make a COI edit request and then after it has been declined (they are almost all declined) make the edit themselves. These sorts of edits have been frequently reverted and the user has often been asked not to edit the article themselves. So, as per my earlier request, page protection to prevent the subject from editing the page via IP addresses would be appreciated. Axad12 (talk) 19:59, 2 August 2024 (UTC)
Semi-protected indefinitely. Will also log at CTOPS. Daniel Case (talk) 04:28, 3 August 2024 (UTC)

Temporary semi-protection: Persistent Disruptive Editing. 98𝚃𝙸𝙶𝙴𝚁𝙸𝚄𝚂[𝚃𝙰𝙻𝙺] 15:27, 2 August 2024 (UTC)

Update: IP users keeps disrupting the page. 98𝚃𝙸𝙶𝙴𝚁𝙸𝚄𝚂[𝚃𝙰𝙻𝙺] 20:37, 2 August 2024 (UTC)

Temporary pending changes: Persistent addition of unsourced or poorly sourced content – There have been a number of IPs adding a specific date for part 3 of this season without providing a reliable source. Netflix has not disclosed a specific date of release for this part of the season as of this point in time. MPFitz1968 (talk) 15:51, 2 August 2024 (UTC)

Temporary pending changes: Persistent vandalism – Recent disruption by an IP editor. O.N.R. (talk) 17:13, 2 August 2024 (UTC)

Temporary semi-protection: Persistent sockpuppetry – Block evasion by User:Kuba20223radio using the Scottish IP range Special:Contributions/2A0A:EF40:602:8D01:0:0:0:0/64. Binksternet (talk) 18:10, 2 August 2024 (UTC)

Temporary semi-protection: Persistent vandalism – persistent vandalism by ip, adding controversial and unsourced materials in the article. Drat8sub (talk) 18:34, 2 August 2024 (UTC)

Semi-protected for a period of three days, after which the page will be automatically unprotected. Daniel Case (talk) 04:33, 3 August 2024 (UTC)

Reason: Repeated edits by users with unconfirmed accounts, often unfamilair with WP:NPOV and other guidelines, especially WP:RS Lajmmoore (talk) 18:39, 2 August 2024 (UTC)

Declined This happens with a lot of breaking news events. The editors seem able to handle it for now. Daniel Case (talk) 04:35, 3 August 2024 (UTC)

Semi-protection: Persistent vandalism – Page history edit summary seems to suggest vandalism from a handful of IP accounts. SSSB (talk) 18:48, 2 August 2024 (UTC)

Reason: Anon editor is repeatedly adding a redlink which is specifically discouraged in navigation elements, under WP:WTAF. Probably covered under WP:GS/PAGEANTS. ☆ Bri (talk) 18:56, 2 August 2024 (UTC)

Semi-protection: Persistent vandalism – Persistent IP vandalism. Unknown-Tree🌲? (talk) 21:11, 2 August 2024 (UTC)

Temporary semi-protection: Persistent vandalism – Death of subject being added to article despite no WP:RS proving as such. Ten Pound Hammer(What did I screw up now?) 21:33, 2 August 2024 (UTC)

Declined. Source added. Paul Erik (talk)(contribs) 02:54, 3 August 2024 (UTC)

Semi-protection: Persistent disruptive editing. — GhostInTheMachine talk to me 21:40, 2 August 2024 (UTC)

Reason: Dear Administrators,

I am requesting page protection for the "Doping in China" article due to ongoing biased edits that appear to be part of a coordinated effort to sanitize the page and portray the country in a more favorable light. These edits are consistently removing well-sourced information about doping incidents in China and replacing it with content that downplays or outright denies these issues.

These changes violate Wikipedia’s Neutral Point of View (NPOV) policy and seem intended to obscure the reality of doping incidents in China, thus misleading readers. Given the repeated nature of these edits and the clear agenda behind them, I believe that page protection is necessary to preserve the integrity of the article.

I suggest temporary or semi-permanent protection to prevent further biased modifications and to ensure that only well-sourced, neutral content remains on the page.

Thank you for your attention to this matter.

Johannesvdp (talk) 22:57, 2 August 2024 (UTC)
DeclinedWarn the user appropriately then report them to AIV or ANI if they continue. Actually the latter page would be a lot better. Daniel Case (talk) 04:51, 3 August 2024 (UTC)

Reason: Persistent disruptive editing by IPs TWM03 (talk) 23:26, 2 August 2024 (UTC)

Please also enforce WP:CT/AP. IanDBeacon (talk) 00:48, 3 August 2024 (UTC)
Declined – Not enough recent disruptive activity to justify protection. Daniel Case (talk) 04:49, 3 August 2024 (UTC)

Reason: Was previously semi-protected and is back to experiencing POV-pushing from IPs and removing of content from single issue editors. CNC (talk) 23:29, 2 August 2024 (UTC)

Declined – Not enough recent disruptive activity to justify protection. Also, the page has never been protected. Daniel Case (talk) 04:52, 3 August 2024 (UTC)

Indefinite extended confirmed protection: Arbitration enforcement – AP2. Jdcomix (talk) 00:23, 3 August 2024 (UTC)

Declined – Not enough recent disruptive activity to justify protection. Daniel Case (talk) 04:37, 3 August 2024 (UTC)

Reason: persistent disruption from IPs for a month Tehonk (talk) 00:48, 3 August 2024 (UTC)

Semi-protected for a period of three weeks, after which the page will be automatically unprotected. Daniel Case (talk) 04:39, 3 August 2024 (UTC)

Reason: Anonymous editors repeatedly adding unsourced/inaccurate information. UndergroundMan3000 (talk) 01:36, 3 August 2024 (UTC)

Semi-protected indefinitely. Will log at CTOPS. Daniel Case (talk) 04:42, 3 August 2024 (UTC)

Temporary semi-protection: Persistent disruptive editing – The all-time medal table should only be updated after the 2024 Summer Olympics are over, I think the article should be protected until then. Annh07 (talk) 02:49, 3 August 2024 (UTC)

Declined The point of Wikipedia is, among other things, to allow that sort of real-time updating. Daniel Case (talk) 04:48, 3 August 2024 (UTC)

Semi-protection: Persistent vandalism – LTA. NightWolf1223 <Howl at meMy hunts> 03:48, 3 August 2024 (UTC)

  • Automated comment: One or more pages in this request appear to already be protected. Please confirm.—cyberbot ITalk to my owner:Online 03:58, 3 August 2024 (UTC)
    Already protected by administrator Paul Erik. for three days. Daniel Case (talk) 04:46, 3 August 2024 (UTC)

Reason: Persistent sockpuppetry. See Wikipedia:Sockpuppet investigations/TyMega. HorrorLover555 (talk) 04:02, 3 August 2024 (UTC)

Already protected by administrator Materialscientist. for three months. Daniel Case (talk) 04:45, 3 August 2024 (UTC)

Current requests for reduction in protection level

[edit]
Request unprotection of a page, or reducing the protection level

Before posting, first discuss with the protecting admin at their talk page. Post below only if you receive no reply.

  • To find out the username of the admin who protected the page click on "history" at the top of the page, then click on "View logs for this page" which is under the title of the page. The protecting admin is the username in blue before the words "protected", "changed protection level" or "pending changes". If there are a number of entries on the log page, you might find it easier to select "Protection log" or "Pending changes log" from the dropdown menu in the blue box.
  • Requests to downgrade full protection to template protection on templates and modules can be directed straight here; you do not need to ask the protecting admin first.
  • Requests for removing create protection on redlinked articles are generally assisted by having a draft version of the intended article prepared beforehand.
  • If you want to make spelling corrections or add uncontroversial information to a protected page please add {{Edit fully-protected}} to the article's talk page, along with an explanation of what you want to add to the page. If the talk page is protected please use the section below.
Check the archives if you cannot find your request. Only recently answered requests are still listed here.

Current requests for edits to a protected page

[edit]
Request a specific edit to a protected page
Please request an edit directly on the protected page's talk page before posting here

Ideally, requests should be made on the article talk page rather than here.

  • Unless the talk page itself is protected, you may instead add the appropriate template among {{Edit protected}}, {{Edit template-protected}}, {{Edit extended-protected}}, or {{Edit semi-protected}} to the article's talk page if you would like to make a change rather than requesting it here. Doing so will automatically place the page in the appropriate category for the request to be reviewed.
  • Where requests are made due to the editor having a conflict of interest (COI; see Wikipedia:Suggestions for COI compliance), the {{Edit COI}} template should be used.
  • Requests to move move-protected pages should be made at Wikipedia:Requested moves, not here.
  • If the discussion page and the article are both protected preventing you from making an edit request, this page is the right place to make that request. Please see the top of this page for instructions on how to post requests.
  • This page is not for continuing or starting discussions regarding content should both an article and its discussion page be protected. Please make a request only if you have a specific edit you wish to make.


Handled requests

[edit]
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.
Protected edit requests

4 protected edit requests
v·h
Page Tagged since Protection level Last protection log entry
Template:Protected page text (request) 2024-07-24 18:26 Fully protected (log) Protected by Mr. Stradivarius on 2014-01-01: "used in MediaWiki:Protectedpagetext and MediaWiki:Cascadeprotected"
Template:Wikipedia languages/core (request) 2024-07-27 11:23 Cascade-protected from Wikipedia:Cascade-protected items/Main Page/5 (log) Protected by Mifter on 2017-03-25: "Considering the main page was unprotected by a compromised sysop semi recently, perhaps transcluding it to a cascade protected page will provide a small increase in protection"
Template:Wikipedia languages (request) 2024-07-30 19:50 Cascade-protected from Wikipedia:Cascade-protected items/Main Page/5 (log) Protected by Mifter on 2017-03-25: "Considering the main page was unprotected by a compromised sysop semi recently, perhaps transcluding it to a cascade protected page will provide a small increase in protection"
User:XLinkBot/RevertList header (request) 2024-08-01 18:09 Fully protected (log) Protected by Beetstra on 2008-02-08: "high-risk page"
Updated as needed. Last updated: 13:30, 2 August 2024 (UTC)
16 template-protected edit requests
v·h
Page Tagged since Protection level Last protection log entry
Template:Infobox Chinese (request) 2024-06-07 08:07 Template-protected (log) Modified by Primefac on 2018-02-23: "high-risk template with 4000+ transclusions"
Template:Infobox officeholder (request) 2024-06-20 06:11 Template-protected (log) Modified by Mark Arsten on 2013-10-18: "Allowing Protected Template editors"
Template:Rail-interchange (request) 2024-06-20 07:17 Template-protected (log) Modified by Primefac on 2018-02-23: "high-risk template with 4000+ transclusions"
Template:Infobox Christian leader (request) 2024-06-28 12:36 Template-protected (log) Modified by WOSlinker on 2013-10-19: "allow template editors to modify"
Template:Infobox language (request) 2024-06-30 06:30 Template-protected (log) Modified by MusikAnimal on 2021-08-16: "Highly visible template: transclusion count now over 9,000; most recent editors are still able to edit"
Template:Infobox islands/length (request) 2024-07-10 14:57 Template-protected (log) Modified by Yaris678 on 2017-03-13: "For consistency with Template:Infobox islands. An increase of edit protection and decrease of move protection."
Module:Sports color/baseball (request) 2024-07-10 18:29 Template-protected (log) Modified by MusikBot II on 2021-08-17: "High-risk template or module 30997 transclusions (more info)"
Template:Contentious topics/talk notice (request) 2024-07-15 08:15 Template-protected (log) Protected by Dreamy Jazz on 2023-01-16: "Highly visible template"
Template:Infobox person (request) 2024-07-19 00:30 Template-protected (log) Modified by WOSlinker on 2013-10-19: "allow template editors to modify"
Module:Navbox (request) 2024-07-19 19:53 Template-protected (log) Modified by Ged UK on 2014-05-07: "lowering to template protection"
Template:Copied (request) 2024-07-25 02:26 Template-protected (log) Modified by Callanecc on 2015-02-17: "Highly visible template: More than 7500 transclusions"
Template:Infobox road (request) 2024-07-26 06:18 Template-protected (log) Modified by WOSlinker on 2013-10-18: "allow template editors to modify"
Template:User sandbox (request) 2024-07-28 15:51 Template-protected (log) Modified by Mike V on 2014-02-17: "enabling template protection"
Template:Infobox islands (request) 2024-07-30 17:45 Template-protected (log) Modified by Yaris678 on 2017-03-13: "For consistency with Template:Infobox islands. No change to edit protection and decrease of move protection."
Template:Hidden archive top (request) 2024-07-31 20:26 Template-protected (log) Modified by Mike V on 2014-08-01: "Highly visible template: per WP:RFPP request"
Module:Icon/data (request) 2024-08-01 03:01 Template-protected (log) Protected by Mr. Stradivarius on 2015-01-23: "High-risk Lua module"
Updated as needed. Last updated: 03:06, 1 August 2024 (UTC)


RFA= Requests for adminship

RFP= Requests for permissions

Autopatrolled

[edit]

Has created roughly 30 articles by my count; only one stub, my spotchecks found nothing concerning. Diverging Diamond (is Queen of Hearts's alt; talk) 19:10, 1 August 2024 (UTC)

Is there any indication that the user wants autopatrolled? I don't want to throw rights at someone who would prefer that their creations be reviewed by NPP/AfC. — Red-tailed hawk (nest) 10:42, 2 August 2024 (UTC)
@Red-tailed hawk: Unlike other PERMs, third party nominations for autopatrolled are welcome (preferred even), because it's primarily a tool used by NPP to manage its workload rather than a tool used by the holder to edit. If someone really doesn't want it for some reason, they can of course ask for it to be removed. – Joe (talk) 11:59, 2 August 2024 (UTC)
@Red-tailed hawk I would be open to having it. Hypothetically I like the idea of someone else checking my articles or critiquing them, but no one who has patrolled my articles has ever really made a significant change or tagged anything, so it hasn't really helped there lol, so if it reduces the NPP workload and gets the page indexed faster I don't see why not. PARAKANYAA (talk) 13:04, 2 August 2024 (UTC)
In that case, I have no objection to granting the right. — Red-tailed sock (Red-tailed hawk's nest) 13:08, 2 August 2024 (UTC)

For a third time, I'm applying for autopatrolled rights; my first request was denied in April 2023, and my second request was denied in June 2024. The reason for the first decline was that my previous articles were tagged for "notability." After that decline, I worked on bringing articles over from the Russian Wikipedia and had relatively few problems when other editors were reviewing them (I don't bring over everything from those respective pages, so I added a tag for expanding from Russian to let others know that information is still there). The reason for the second decline was that I moved one of my BLP articles back into the mainspace without changing the sourcing, and it was eventually deleted (that was a mistake on my part). Now, roughly two months later, I have had little to no problems with the other articles I have brought over. I respectfully request that I be granted the autopatrolled permission this time around, as I believe it will help lighten the NPP workload to some extent. Thanks in advance for your consideration. Losipov (talk) 20:10, 2 August 2024 (UTC)

 Automated comment This user has had 1 request for autopatrolled declined in the past 90 days ([5]). MusikBot talk 20:20, 2 August 2024 (UTC)

Page mover

[edit]


I have been editing for over 7 years and I plan on using this permission in order to help with discussions on WP:RM and deal with cross-redirects for articles that should have more disambiguated titles. KingSkyLord (talk | contribs) 12:46, 2 July 2024 (UTC)

Reason for requesting page mover rights: I want to have my page mover rights extended, as I contribute to RM/TR. Was given 3mo trial and it will end on August 20. ToadetteEdit! 08:30, 29 July 2024 (UTC)

 Automated comment This user was granted temporary page mover rights by Robertsky (expires 00:00, 20 August 2024 (UTC)). MusikBot talk 08:40, 29 July 2024 (UTC)

I was granted pagemover rights nearly a month back, but due to mistakes on my part, the rights have been now revoked. So, I am requesting the rights again on Primefac's advice, explaining why I made the mistakes and how I shall avoid those mistakes going forward.

  • On 30 July, I moved British Indian Army to Indian Army (1895–1947) after which Celia Homeford informed me that the move had been unilateral, following which I immediately proceeded to check the talk page of the article for previous RMs, which I did find and had resulted in the move of Indian Army (1895–1947) to British Indian Army. I hadn't checked the talk page before swapping the page and thus had not been aware of this RM when I had swapped — a mistake on my part. I had checked the WP:COMMONNAME of the article and sought to make the article title WP:Consistent with other historical army related articles like German Army (1935–1945) for instance. I should've checked the talk page and it's archives for any previous RMs and discussions before making the swap. That is what I usually do before making a move or a swap, but this step had slipped my mind in this case. In future, I shall make sure to always check the talk page and the archives for RMs and discussions regarding the article title without fail before making a move or a swap.

I've learnt from my mistakes and hope not to repeat them. I also aim to minimise any chance of any other mistakes on my part. PadFoot (talk) 17:56, 30 July 2024 (UTC)

 Automated comment This user has had this permission revoked in the past 180 days ([6]). MusikBot talk 18:00, 30 July 2024 (UTC)


Pending changes reviewer

[edit]

I've been doing RCP for a little while now, and recently started NPP. I believe I could assist in patrolling recent changes to expand on my anti-vandalism work. Thanks, Lordseriouspig 06:20, 26 July 2024 (UTC)

 Done Elli (talk | contribs) 18:21, 31 July 2024 (UTC)

I've been doing patrolling for a little while now, and recently started seriously devoting time. I believe I will submit myself in patrolling recent changes in contributing to anti-vandalism work. Thanks Fsrvb (talk) 19:43, 1 August 2024 (UTC)

 Automated comment This user has had an account for 5 days and has 28 edits in the mainspace. MusikBot talk 00:00, 3 August 2024 (UTC)

I have been monitoring recent changes on pages for a while now AlexBobCharles (talk) 08:36, 2 August 2024 (UTC)


Rollback

[edit]

I've been patrolling recent changes for a while now, using Twinkle to warn members. I have over 200 mainspace edits, and I'm extended confirmed with over 700 edits total. I've also been doing NPP for a little too. I'd like to use rollback for more advanced tools such as Huggle and AntiVandal. Thanks, Lordseriouspig 06:14, 26 July 2024 (UTC)

I see that you are failing to consistently warn editors when you revert their edits. Why? It's important to leave a notification for every revert you make. Are you aware that we have tools such as Twinkle or Ultraviolet that make this extremely easy? -Fastily 10:34, 28 July 2024 (UTC)
I don’t believe I'm not, @Fastily:, I warn people using twinkle, here is my warn logs: https://wiki.riteme.site/w/index.php?title=Special%3AContributions&target=Lordseriouspig&namespace=3&tagfilter=twinkle&start=&end=&limit=50. Lordseriouspig 20:31, 28 July 2024 (UTC)
I reviewed your contributions from last month and found these within seconds: 1, 2, 3. I'll repeat what I said above: it's important to leave a notification for every revert you make. Are you aware that we have tools such as Twinkle or Ultraviolet that make this extremely easy? -Fastily 08:03, 1 August 2024 (UTC)
I’m unsure why I forgot to add a warning for those, @Fastily, considering Twinkle automatically opens the talk page, but I usually warn members, and tools like Anti-vandal or Huggle would probable negate me forgetting warns. Thanks, Lordseriouspig 10:00, 1 August 2024 (UTC)
No worries, thanks for your honesty. Please ensure that you are always leaving warnings. I can't stress enough the importance of not biting the newcomers; if you find yourself reverting good faith edits, then it's especially important to notify the editor. If you don't want to leave a template warning, that's completely fine, but you do need to leave a talk page message explaining why you reverted the edit. Moving forward, could you please make a promise to leave warnings/notifications for every revert? -Fastily 23:02, 1 August 2024 (UTC)
No problem, @Fastily I’ll definitely try to leave warnings for every revert I make. Thanks, Lordseriouspig 02:57, 2 August 2024 (UTC)

I've been recent changes patrolling on and off with Twinkle, and more recently Ultraviolet, for years now, and would like to try Huggle's more advanced tools. I have over 1.4k mainspace edits, no history of edit warring, and consistently and appropriately notify editors whose changes I revert. P1(she/her, talk/contribs) 04:18, 1 August 2024 (UTC)

 Not done I noticed you make a handful of edits, and then drop off for months at a time. While I appreciate your enthusiasm, I'd like to see you spend at least a month consistently patrolling RecentChanges (Twinkle & Ultraviolet can help with that) before reapplying. Also, please ensure that you are always warning editors when you revert their edits. Thanks, Fastily 08:03, 1 August 2024 (UTC)

I've been viewing recent changes for a while with Twinkle, and would like to keep using the Android app to prevent vandalism, which requires rollback permissions.

I am aware, after reading others' requests, that warning users after edits must be done every single time. While there are moments in which I have forgot to do this in the past, I will ensure to make it a consistency going forward. LR.127 (talk) 00:54, 3 August 2024 (UTC)

Template editor

[edit]

I am a frequent editor and creator of templates and modules, and I have encountered several instances where having the template editor permission would be helpful. Many of my requested edits on protected templates have been performing minor visual fixes or fixing small bugs with the template's logic. For these uncontroversial edits, having to submit a request and involve another editor feels unnecessary, considering the nature of the requested edits. In other cases with more significant changes, going through the edit request process works fine for the most part, but I like to be able to avoid the process because of the backlog the edit queue can have at times and the added potential confusion added by having to request technical changes. Because of this, I'd much rather be able to have a standard discussion on template talk pages, if necessary, followed by implementing the agreed upon changes myself rather than having to request someone else to implement the changes. In the near future, I plan on exploring adding support for the new dark mode to more templates and being able to implement these changes on protected templates myself would be of great help. In the future, I would also like to use my technical knowledge of wikitext and Lua to help with processing the template edit request queue.

Another issue that the template editor permission would resolve is that several templates I've created or rewrote are now template editor protected: Template:For-multi, Template:Country name, Template:Yearly archive list/display, Template:Visible anchor/styles.css, Template:Divbox/styles.css, and Module:Outdent. As a result, I am unable to edit them, which makes several of them difficult to maintain. Per the guidelines, three templates sandboxes I've worked on include Module:Jcon/sandbox, Template:Visible anchor/sandbox/styles.css, and Template:Infobox road/sandbox and at some requested template edits are [7] [8] [9] [10] [11] [12][13].

Also, I acknowledge that I performed what ended up being (unintentionally) disruptive templates several years ago. Since then, I have learned a lot about collaborating with others on Wikipedia and being mindful of the impact template edits can have on articles across the wiki. Since then, I have been much more careful with the edits I perform, as these past experiences have shown me the dangers of not doing so. With the template edit permission, I intend to take from these past mistakes, and I will follow the best practices to ensure the template edits I perform are well-tested, agreed upon, and non-disruptive. I find that now I am very cautious with my template edits, and I always create thorough test cases (e.g. Template:Jcon/testcases) before performing changes. BrandonXLF (talk) 19:08, 28 July 2024 (UTC)

After looking at your contributions I'm inclined to grant, but would like to know if Primefac, EdJohnston, or Galobtter (admins who were involved with the placing and then lifting of your sanctions) have thoughts. Elli (talk | contribs) 01:39, 30 July 2024 (UTC)
Brandon has definitely matured as an editor since their first go-round with this permission. I've been burned in the past but let's say I'm cautiously optimistic. Primefac (talk) 12:11, 30 July 2024 (UTC)
 Done for a three-month trial period. Feel free to request again in October and assuming there weren't any issues in the meantime, I'll be happy to grant the permission indefinitely. Elli (talk | contribs) 18:11, 31 July 2024 (UTC)

Footer

[edit]

Policies and links