|
1, 2, 3, 4, 5, 6, 7, 8, 9, 10 |
|
This page has archives. Sections older than 60 days may be automatically archived by Lowercase sigmabot III. |
 | I am busy due to real world activities. I may be absent for days at a time, and may not respond swiftly to queries. |
 | 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 that I cannot reply to quickly is appreciated. |
Suspicious IP edit
An IP address "117.193.205.235" keeps editing Virudhunagar Lok Sabha constituency again and again by using "winning candidate" template for a specific candidate instead of normal "candidate" template (election results due in 4 June 2024). Action required. Thank you. SamsonM2 (talk) 10:17, 27 March 2024 (UTC)
- I was just the one time, so I'm hesitant to take drastic actions unless it is a pattern, but I will keep an eye out. Dennis Brown - 2¢ 23:48, 27 March 2024 (UTC)
- @Dennis Brown: please check the page again. The same user (IP slightly different) doing disruptive edit. SamsonM2 (talk) 06:09, 28 March 2024 (UTC)
- Blocking isn't an option, given the range, but I've protected it for a week. It's a bit of a borderline case, but the different IPs are getting reverted for various valid reasons, enough to protect it. After the protection expires, if the problem comes back, go to WP:RFPP and request protection be extended, but only after several edits that are problematic. Dennis Brown - 2¢ 06:18, 28 March 2024 (UTC)
Administrators' newsletter – April 2024 edit
News and updates for administrators from the past month (March 2024).
Administrator changes
Guideline and policy news
- An RfC is open to convert all current and future community discretionary sanctions to (community designated) contentious topics procedure.
Technical news
- The Toolforge Grid Engine services have been shut down after the final migration process from Grid Engine to Kubernetes. (T313405)
Arbitration
- An arbitration case has been opened to look into "the intersection of managing conflict of interest editing with the harassment (outing) policy".
Miscellaneous
- Editors are invited to sign up for The Core Contest, an initiative running from April 15 to May 31, which aims to improve vital and other core articles on Wikipedia.
Notice of noticeboard discussion edit
There is currently a discussion at Wikipedia:Administrators' noticeboard regarding an issue with which you may have been involved. The thread is Conflict of interest editing by Dennis Brown. Thank you. – Joe (talk) 13:21, 23 April 2024 (UTC)
Forgive me as I might not be the most familiar with requests for decrease in protection. But from what seems logical to me based on the WP:Protection Policy, Wikipedia is an encyclopedia than anyone can edit. I, nor anyone, should be hindered by full protection (as its been in the past), for a redirect where protection was never really warranted in the first place. Instead of "why should full protection be removed", it seems more appropriate to ask "why should full protection be kept" and there's absolutely nothing I can think to say for it, besides the fact that an administrator felt like protecting it and then washing their hands of the matter (based on the DRV).
Multiple edit requests have already been made since 2017, which could have been avoided through reduced protection. Personally, I would like to add an "R from different spelling" rcat to the title, yet there's zero reason why I shouldn't be able to just uncontroversially do it myself instead of forcing an admin to oversee it, which the multiple past edit requests at this title have already been multiple too many. "Not visible" doesn't really apply to this redirect when it's tagged with the most relevant rcats (with slogans itself being highly visible due to being discussed as a well-condensed-yet-unnecessarily-bloated set of redirects, in the process of being cleaned out), and would be instantly viewable via the New Page Feed if something ever comes up. If a change ever affects the redirect, it will be the only page in the queue with a 2006 creation date, so that's not as much of an issue as it might have used to be, as a lot of people (myself included) monitor redirect changes. Needlessly protecting redirects just because one admin 7 years ago thinks they'll never have to be touched or edited with rcats ever again, is not a good practice, especially in cases where the future for the redirect is not obvious and rcats themselves change. This is not an alternate spelling of "Big Mac", but instead targets a section on a page that can easily be renamed or moved, forcing this redirect to be updated accordingly every time it happens. This is also not like "Obama" where the outcome has been talked to death about and needed to be protected to prevent vandalism. This is just a page, of dubious usefulness, that has teetered the line of being kept and being deleted on multiple occasions. While I would like to make a change and add an rcat, there seems to be no justification for keeping the protection; in my mind that's plenty enough explanation to reduce, as "no protection" is the default / status quo outcome according to the protection policy, for when there is no reason to have a page keep its protection. Utopes (talk / cont) 00:28, 24 April 2024 (UTC)
- Specifically, per WP:UNPROTPOL, "administrators may unprotect a page if the reason for its protection no longer applies, a reasonable period has elapsed, and there is no consensus that continued protection is necessary". The original protection was strange at best and seems to have arisen from the previous 2017 undeletion, where it's since been discussed at RfD and DRV on multiple counts. No longer applies, reasonable period elapsed, and no reason to suggest that protection is still necessary.
- Also from UNPROTPOL, "[Full protection is appropriate for] pages with persistent disruption from extended confirmed accounts." This rationale never applied as there was no disruption, much less from extended confirmed accounts. The only evidence of redirect removal was from the otherwise valid CSD G4 tag (as it was recreated following an AfD that closed as delete). Utopes (talk / cont) 00:37, 24 April 2024 (UTC)
- When I consider unprotecting an article, I look at a few things: How many people are likely to watch it? (fewer watchers means higher possibility of vandalism going unnoticed). How likely is it going to be edited? What is the likelihood that any edit would be vandalism rather than constructive? How difficult is it for editors requesting edits to get those edits considered? What is the risk vs. reward? Then I try to apply what I think is the community consensus, the expectation, for the protection. After all, it isn't about my opinion, it is my best guess of what the greater community would choose if it were to be put to a vote. In this case, I felt like the community would say "It isn't likely to be edited, since that is a trademarked slogan from a long time ago, so the value of making it so anyone could edit it is less than the value of preventing vandalism in an environment of increasing numbers of articles and decreasing numbers of admins and patrolling editors." Now, that isn't a guarantee that this would be the result, but it is my best judgement, so that is the basis for my decline. At the end of the day, the real policies aren't the words written down, they are the consensus of what the community (as a whole) would prefer to do, and the written words are just there for convenience. I still maintain that articles, templates and such that are very unlikely to ever be edited but pose a ripe target for vandalism, and are already protected, probably should stay protected because there is virtually no benefit in unprotecting them compared to the risk, and that most editors in the community would support that. Dennis Brown - 2¢ 01:09, 24 April 2024 (UTC)
- To address the hypotheticals in the order they were raised, this page is already in the top ~0.1% echelon of attention given to redirects, due to people having eyes on titles that recur in-and-out of multiple deletion venues. Most redirects have zero incoming links, while this specific title has been featured in a half dozen focused-discussions in WP space. I have already given an example of a change that I was planning on making, i.e. adjusting the rcats after an RfD closure, which I'd very well imagine to be uncontroversial to do and otherwise a net positive. This page has never been vandalized over the decade this existed pre-deletion, from 2006 to 2016, so there is zero basis to suggest that vandalism is a fear over any other title. There has never been a disruptive edit to this page, so I'm unsure why so much weight is given to that perspective. There is no evidence of any "risk" at this title, and the reward is that the third pillar isn't purposely obstructed after the existence of a no-longer-necessary full protection was brought to light at RfPP. Wikipedia is a work in progress; even the smallest of pages can and should be "mercilessly edited" by anyone, to inch closer towards a better encyclopedia.
- Redirects in general are less likely to be edited, sure, as it's an area that not everyone will see. But keeping an article protected longer than it needs to be is a disservice to the core tenents of Wikipedia being a place where anyone can edit, across pages big and small. Especially if the reason is "it's already protected, and because there probably won't be more than one edit a year, it shall be upon admins alone to maintain this title forever; they can handle the edit requests whenever they happen". It being protected already does not matter if the reasons do not hold up today, much less hold up 6 years ago. There was no policy basis for the initial protection. Years has passed, and the non-existent reasons for the initial protection have expired, surely. I really fail to see the reason for preventing people from editing the encyclopedia that anyone can edit, at an otherwise innocent title, all to prevent the tiny chance of vandalism on a page that has never been vandalized prior. (If someone really wanted to vandalize, this protection wouldn't prevent them from going for any of the other pages they could hide disruption on among several others, that are totally unprotected and never have been, nor has there been disruption from what I could find.) Utopes (talk / cont) 03:03, 24 April 2024 (UTC)
- I understand what you are saying, and I will admit that FULL protection is probably overkill, but I still feel some kind of protection makes sense, so I have reduced it to semi-protection. Dennis Brown - 2¢ 03:23, 24 April 2024 (UTC)
New sock edit
Hi, you sockblocked User:NonRevert this morning. Immediately afterwards, User:Sukshy was created and continued editing the same new article Rangiya Municipal Board. Clear WP:DUCK, can you block them too? Fram (talk) 12:35, 26 April 2024 (UTC)
- Fram, I was actually roaming around enwp when that happened and was about to block them myself, but another admin beat me to the punch by a couple of minutes. Dennis Brown - 2¢ 00:37, 28 April 2024 (UTC)
Ford–GM 10-speed automatic transmission Citation edit
Hello, I saw you reverted my source edit for #12 on the Ford-GM 10-speed page and wanted ask would the first edit of the web.archive of the png be the same as the link to the Camaro6 forum? The table from the web.archive links to that site and the phot is on the post. I only ask as I recently found out someone linked that table and I made it on the source. I am new so would love to learn, cheers! Bumbleboy92 (talk) 06:06, 27 April 2024 (UTC)
- Bumbleboy92: The problem is the website, Camaro6, which is a blog. If you check out WP:RS (our policy on what is a "reliable source", you find we really try to avoid blogs and forums except in exceptional circumstances. Mags like Hot Rod, Car and Driver, etc are perfectly fine. The difference is that the mags have an editorial staff and vet their articles more carefully. Blogs tend to be "one man shows" and so the reliability of the information is dubious, and often, incorrect. This is because there is no fact checking. Not a big deal, this is how you learn, so take no offense to the revert. The only time we are lenient about blogs and forums is if it is a from the company itself and the account is verified to be them, and even then, we would qualify the statement in the text of the article. ie: "CEO Bob Smith said on Twitter that they expect to increase horsepower by 10hp next year", instead of just saying "they are increasing horsepower next year". One of the principle ideas behind Wikipedia is that it is better to have LESS information that is WP:Verifiable than to have more that is not sources or poorly sourced. So the end result is that articles are often missing some information, but you can rely on the information that is there, being factual. So reverts happen. The best thing to do when you are reverted... is exactly what you did, start a discussion if you have questions. Try to not unrevert a revert, unless you know the revert was a mistake. Revering multiple times typically gets you blocked for edit warring here. So you are on the right path to learning and helping by coming here and just asking, although using the talk page of the article is where you would normally bring up the issue. Dennis Brown - 2¢ 00:36, 28 April 2024 (UTC)