Jump to content

Wikipedia:Village pump (policy)/Archive 181

Add links
From Wikipedia, the free encyclopedia
Village pump (policy) archive  

This page contains discussions that have been archived from Village pump (policy). Please do not edit the contents of this page. If you wish to revive any of these discussions, either start a new thread or use the talk page associated with that topic.

< Older discussions · Archives: A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, AA, AB, AC, AD, AE, AF, AG, AH, AI, AJ, AK, AL, AM, AN, AO, AP, AQ, AR, AS, AT, AU, AV, AW, AX, AY, AZ, BA, BB, BC, BD, BE, BF, BG, BH, BI, BJ, BK, BL, BM, BN, BO · 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, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197

WP:MASSCREATE and WP:MEATBOT

Both shortcuts are within the bot policy and suggest that they apply for permission for their edits here. I suggest that the top 20 of the article creators are included in the denomination of masscreating editors and they should apply for permission there. In a RFC of 2009, (also at the village pump (policy)), the article number that classifies for masscreation was not really defined, but 25-50 was not opposed. Yet also the ones who created more than 25-50 didn't apply for permission, with one of the prominent cases being Lugnuts, which in my opinion is a deplorable loss, because his investment of time to wikipedia was huge. If his and also of others energy could have been guided to a calmer area, they'd likely still edit (under their original accounts).

They could anyway have been requested to apply for permission per WP:MEATBOT (about bot-like editing), but that policy doesn't seem to have been observed or enforced when the several discussions on masscreation began. Many of the masscreating editors are lost to Wikipedia, and I'd say it is not only their fault, but in part also our fault because we were not able not guide them to a more cooperative way of editing.

In order to prevent further very long discussions, I believe it would be good to just enforce WP:MEATBOT and amend WP:MASSCREATE to the top 20 article creators of the month. If one enters the top 20, they must apply per MASSCREATE, if one edits bot-like and is able to create several articles within a few minutes or two hours they shall apply per MEATBOT.Paradise Chronicle (talk) 09:08, 21 March 2023 (UTC)

You are conflicting a few things here. WP:MEATBOT doesn't mean we treat all fast edits and lots of changes as being a bot. It talks of disruptive editing, and if it's done quickly, it makes no difference if done by a bot or by hand, and WP:MASSCREATE is talking about specifically using automated or semi-automated tools. If someone is making lots of articles with the use of tools, then they need to fill out at BRFA. If they are creating poor or disruptive articles, then they need to be raised at ANI or another noticeboard. We don't simply create policy to penalise good faith article creation, see WP:NOTBURO Lee Vilenski (talk • contribs) 09:29, 21 March 2023 (UTC)
What do @you think of amending MASSCREATE to top 20 article creators instead of only the ones who create 25 - 50 a day? Paradise Chronicle (talk) 10:40, 21 March 2023 (UTC)
What would be the point of that? Thryduulf (talk) 13:58, 21 March 2023 (UTC)
To prevent long discussions as we had with Carlossuarez and Lugnuts? Future examples might become Adamtt9 or Pvmoutside, both editors who are in the top 20. Adamtt9 creates articles contrary to
WP:NOTDATABASE, WP:NOSTATS or WP:NOTMIRROR, are poorly sourced with databases not independent to the subject. See here, sourced with that mirror/database, here sourced to that mirror/database, and here sourced to that mirror/database, all in the general references and not as inline citation. There is probably also no inline citation, I am not sure if a game between ATP number 180 with 150 is notable enough for any WP:RS. Pvmoutside creates technical micro stubs on species in danger, withholding the info that they are species in danger, see here, here and here. Nirmaljoshi is number 3 and created 19 stubs on dams in Japan within 2 and half hours after they were told to stop to create them here. Sakiv is another one, they create articles on football seasons usually full of tables contrary to WP:NOTDATABASE and WP:NOSTATS, see here, here and here. Why start an ANI discussion for each of them
?(talk) 19:12, 22 March 2023 (UTC)
? We could just formalize MASSCREATION and then there would be less discussions.16:21, 21 March 2023 (UTC) Paradise Chronicle (talk) 16:21, 21 March 2023 (UTC)
Courtesy pings to Adamtt9, Nirmaljoshi, Pvmoutside and Sakiv. Paradise Chronicle (talk) 16:26, 21 March 2023 (UTC)
Regarding the species in danger comment, I reviewed the three articles referenced. The first two are referenced properly and according to the IUCN are categorized as least concern, so I'm not sure what the editor is trying to say, the third article I did not create...Pvmoutside
You sure also created the third one, just check here. And least concern... ok and? they are still on the red list and the infobox should be a summary of the article in which you usually do not mention the red list as far as I have noticed.Paradise Chronicle (talk) 21:49, 22 March 2023 (UTC)
The reference point has been corrected...Pvmoutside (talk) 01:26, 23 March 2023 (UTC).
Uhhh, I want to correct myself. I didn't know that least concern means no concern as I figured that if they are included in the red list for threatened species they are in danger. Apparently it's not like that and I apologize. I still see those articles as taggable, let's say for too technical as they are full of latin names and acronyms and would support the removal of autopatrolled from Pvmoutside. Paradise Chronicle (talk) 07:47, 23 March 2023 (UTC)
No? Where do we state a figure for how much one can create? MASSCREATE talks about using tools. If someone wants to create hundreds of articles that are all well cited, there is no issue. Lee Vilenski (talk • contribs) 14:23, 21 March 2023 (UTC)
Tools for semi-automation would include things like boilerplate text - a necessity for anyone who is creating dozens of articles per day. WP:MEATBOT would also apply, which doesn't require any tools to have been used.
However, I agree that this proposal isn't the route forward; defining mass creation solely in terms of the most prolific editors is too inflexible and will likely exclude many mass creators, and may include a couple of editors who don't engage in mass creation. BilledMammal (talk) 15:35, 21 March 2023 (UTC)
At Masscreate it says any large-scale automated or semi-automated content page creation task must be approved by the BRFA. It is the first phrase. Since no-one seems to have been approved, no-one seems to have applied for the rights even though they surpassed the mentioned unopposed threshold and we are having very long discussions on stub creations, I thought it might help narrowing it down to the 20 most prolific ones. But if not even they can be included, who will, and then also what's the sense of having such a policy? To be included in the top 20, doesn't have to be seen as a punishment, and it is also not meant as a punishment, the amendment is meant to regulate the masscreation of articles, so the ones that are good at it, can be shown as the examples to follow to the ones who are not yet so good at it, and this before having created hundreds or even thousands of articles. Paradise Chronicle (talk) 20:10, 21 March 2023 (UTC)
What are the actual problems with the individual articles that these editors are creating (ignoring how, when and by whom they were created)? If you cannot identify any specific problems that apply to at least the majority of the articles created, and explain how classifying them as mass-created would address those problems, then all this is a waste of time.
Looking at a random recent creation (Charles Connor (actor)) by the editor at the head of that list (Lord Cornwallis) I can't see any issues. Thryduulf (talk) 22:03, 21 March 2023 (UTC)
It specifically says "automated". You are trying to make any user who creates a lot of articles need to fill out a BRFA, giving examples of people who create poor articles. All this policy is designed to do is make more work for someone actually making non-automated articles - and if they are making them badly, they'd hardly put in enough time to do a bot request form. Lee Vilenski (talk • contribs) 22:15, 21 March 2023 (UTC)
@Lee Vilenski. It says semi-automated and underneath comes
WP:MEATBOT which includes semi-automated bot-like editing. You are not fit for crat-ship if you can't properly cite policy. Paradise Chronicle (talk) 23:33, 21 March 2023 (UTC)
That simply isn't true. MEATBOT talks about disruptive bot like editing. It DOES NOT suggest that all edits that are done quickly are bot edits, nor that they are disruptive However, merely editing quickly, particularly for a short time, is not by itself disruptive. That is the bit where this falls down. This proposal suggests that all users who create lots of articles (regardless of quality) should in fact be treated like a bot, and made to fill in a form.
This is also something that is already easy to deal with with existing policy. Is the user using tools? Yes - get them to fill out the form. No? Well, are the articles disruptive, or of poor quality? Yes - report to ANI, other noticeboard, or their talk. They'll soon stop, or gain a block. No? Well, I don't really see the issue. If I wanted to create 30 articles tomorrow that were all well sourced? I don't really see what the issue is, nor would I expect someone to come along and tell me that I need to put in paperwork and become a bot.
Thank you for the personal attack, please refrain from doing these in future. Lee Vilenski (talk • contribs) 07:09, 22 March 2023 (UTC)
Yeah I am not sure if that was a personal attack or a personal point of view. I'd be glad to learn what was you see as a personal attack. You are an admin and like a politician public figure you should be receptive to criticism.
Anyway, while you are right that it is mentioned that for a short while it is not disruptive some of the Masscreators edit high speed on long term. Some like Pvmoutside are editing high speed since years. And if the short term is the one where my suggestion fails, the opposite which would be long term is where I should have your support.
Then I'll also copy paste this part of WP:MEATBOT and then all can decide for themselves.
Editors who choose to use semi-automated tools to assist their editing should be aware that processes which operate at higher speeds, with a higher volume of edits, or with less human involvement are more likely to be treated as bots. If there is any doubt, you should make a bot approval request. In such cases, the Bot Approvals Group will determine whether the full approval process and a separate bot account are necessary.
It doesn't say the edits have to be disruptive in order to apply, just that they have to be high speed enough and their edits can be treated as bot-like editing which applies to several of the top 20 article creators. The title of the shortcut MEATBOT is Bot-like editing and that it is mainly focused on disruptive editing can be a point of view, but one I do not share.
And I don't believe to start an ANI discussion for each masscreating editor I do not agree with is a good idea,Paradise Chronicle (talk) 22:42, 22 March 2023 (UTC)
You may want to peruse the recent WP:ACAS. Yes, our current rules don't address mass creation without problems and without the use of tools, and that's not ideal. A big problem seems to be some fundamental disagreements about what, exactly, the problems are when it comes to mass creation and how to define it... — Rhododendrites talk \\ 16:48, 21 March 2023 (UTC)
@Rhododendrites I took part in that WP:ACAS discussion, which was one of the many discussions on masscreation and no satisfying solution came out of it. Discussions go on.Paradise Chronicle (talk) 19:41, 21 March 2023 (UTC)
That was pointed out on my talk page, yes. I assumed you didn't see it because you referenced a 2009 RfC but not the one we just had on this topic (a long one that took a lot of time with, as you point out, no real solution). Not saying that should be the end of it -- it just seemed worth mentioning is all. NBD. — Rhododendrites talk \\ 22:16, 21 March 2023 (UTC)
@Rhododendrites Why does creation (mass or otherwise) without problems need addressing? Thryduulf (talk) 22:04, 21 March 2023 (UTC)
I don't know that it does, except insofar as there have been a lot of people who claim the existing guidance does apply, should apply in spirit, or otherwise operate as though we have rules that we do not have. My "not ideal" is just about clarity/common understanding. — Rhododendrites talk \\ 22:16, 21 March 2023 (UTC)
The number one editor on this list produced an average of just over four articles per day. Any of us could sit down and spend 15-20 minutes sketching out a reasonable rudimentary article on a missing notable figure, and thereby create four articles in a day, with nothing even close to resembling mass-editing. BD2412 T 22:53, 21 March 2023 (UTC)
Then if the two admins here stonewall my suggestions, how can we apply those policies? If it's not the top 20 or editors who perform semiautomated edits, then who? You are the admins, you should know. Or are you all hoping to block the next one instead of finding solution for them? Be a bit constructive here.Paradise Chronicle (talk) 23:54, 21 March 2023 (UTC)
I don't know if this adds to the discussion, but a few years ago the Tree of Life Project had a bot called Polbot which created many species pages, but was ended when many of those pages needed corrections....Pvmoutside (talk) 00:24, 22 March 2023 (UTC)
The following question was proposed previously, but a discussion on it was never opened due to the cancellation of the ArbCom mandated RfC. It might be worth revisiting?
Which proposed definition of mass creation should we adopt?
Please rank your choices by listing them in order of preference from most preferred to least preferred. Preferences, weighted by strength of argument, will be resolved through IRV.
A: A single editor creating a large number of articles based on boilerplate text and referenced to the same small group of sources.
B: A single editor creating more than 100 articles based on boilerplate text and referenced to the same small group of sources.
C: A single editor, creating more than 10 articles per day, 20 articles per week or 50 articles per month, based on boilerplate text and referenced only to the same small group of sources.
D: None of the above
BilledMammal (talk) 00:26, 22 March 2023 (UTC)
C.
The large number of A is too vague.
In B 100 articles are meant in total or per minute? If this is not clarified the ones who prefer not to apply will find any excuse. And I doubt if boiler plate should be mentioned as then a possible answer would be that they edit micro stubs manually for days and then publish all at once within a few minutes like I already read before. Paradise Chronicle (talk) 02:38, 22 March 2023 (UTC)
100 means in total; previous discussion has suggested that boilerplate is necessary, both because it can be determined by reviewing the articles, and because there is agreement that mass creation isn't simply due to the rate of creation but what is created. BilledMammal (talk) 02:43, 22 March 2023 (UTC)
Thank you for the explanation and also the constructive suggestion. Paradise Chronicle (talk) 15:52, 22 March 2023 (UTC)
@Paradise Chronicle you still haven't explained what problem you want to solve. Until you can do that everything else is pointless. What do you want to achieve by applying MASSCREATE? What benefit will doing so bring to the encyclopaedia? It's worth noting that as far as I can tell from a quick glance, none of the suggested definitions BilledMammal would apply to Lord Cornwallis' articles because they are not based on boilerplate text. Thryduulf (talk) 00:50, 22 March 2023 (UTC)
I have explained above, but you probably didn't read. The aim is to prevent long discussions in the future as we had in the past with Lugnuts and other editors. I believe if editors apply at BRFA, we can show examples to the ones who create deficient stubs. I'd say Lord Cornwallis and I believe also Moonswimmer and Esculenta for sure (articles are rather good) could serve as examples to show to editors who also want to masscreate articles. But since no-one is interested in that I thought it would be interesting to know how the policies on masscreate and meatbot can be applied. If no-one knows we can also just abolish them, then also no-one will have the idea to bring them up. Either show a way how to apply it or abolish it. Paradise Chronicle (talk) 02:16, 22 March 2023 (UTC)
@Thryduulf, I think the motivation is "drama prevention" rather than anything about the articles or the creation – like if we were to write down that "Mass creation applies to the creation of six or more articles per hour, except during a new moon, when the rate is lowered to one article per hour, unless you have reviewed five extra DYKs during the last 90 days, in which case the usual rate limits apply", and another rule that says "If someone claims mass creation when the creation rate is approved by this tool, then the first three editors who notice this are entitled to post 'Liar, liar, pants on fire' on the editor's talk page", then we won't have l-o-o-o-n-g discussions about whether creating two articles that I dislike is "mass creation" instead of "a violation of all that is right and decent".
However, given that I see editors who persist in claim "original research" for material that is both verifiable and cited, I am not convinced. Maybe if we give them another badname they'd switch to that eventually.
Paradise, the problem with "top 20" is that if editor #20 has created 1,000 articles ever, then:
  • I can do whatever I want for the first 999 articles, including flooding the review queues with 999 articles in the space of 999 minutes, but
  • if I create just one article per week, then after ~20 years, I'm going to have to get permission from the bot folks to do something that is obviously not bot-like editing.
You need to have a rate limit on it. WhatamIdoing (talk) 01:27, 23 March 2023 (UTC)
@WhatamIdoing, the Top 20 are only for 2022, not for the last 20 years. And also, Wikipedia can develop towards quality, as it happened in many areas of Wikipedia. I believe this development will also come to article creation but maybe I am just a bit ahead of time. Paradise Chronicle (talk) 07:01, 24 March 2023 (UTC)
Based on a rolling 12-month period or on the previous calendar year?
It doesn't make sense to tell someone that they were in the top 20 last time, so creating even one article now requires extra permission. And it might not make sense anyway, because what if I create hundreds or thousands of redirects, but someone expands those into real articles? Our tools detect that as being a real article (now), so it would count someone else's article creation "against" my limit, unless you did a manual review, which is not really helping.
And it doesn't address the practical problem with mass creation, which is flooding the review queues. It does not matter what the overall limit is, if you say I can do whatever I want for the first ____ articles, including flooding the review queues with ____ articles in the space of ____ minutes will always be a problem unless ____ is a sufficiently low number that the reviewers can handle the burst of activity (generally accepted as 25 to 50 per day). WhatamIdoing (talk) 18:34, 25 March 2023 (UTC)
Then let's turn it around. What kind of editor would have to apply at BRFA as suggested by MASSCREATE and MEATBOT? So far none seems to have applied for and none was given the rights even though they have created more than 25-50 articles per day or used semiautomated tools for their article creations. I have asked this already before but no answer so far. Paradise Chronicle (talk) 19:04, 25 March 2023 (UTC)
Paradise Chronicle, I think the rule should be that you apply at BRFA if your future plans will produce a level of articles that the community expects to cause problems for the Wikipedia:New pages patrol. That level has been set at 25 to 50 articles per day for many years. I would personally reduce it slightly, to say something like "25 to 50 articles per day day, or a total of more than 300 articles per month", but other editors would probably choose other numbers. WhatamIdoing (talk) 23:26, 28 March 2023 (UTC)
300 a month only one has created in 2022, so this would just raise the level instead of reducing it. I'd support a WP:MEATBOT approach that if articles are seemingly faster created than for example video link for the worlds fastest typists (ca. 200 words per minute) like creating several articles within a few minutes or 25 per day its considered semi-automated editing and worth of a review. It's not supposed to punish editors, but much more to regulate masscreation and show editors who like to masscreate articles what the community believes is good for wikipedia and what kind of editing raised concerns. Paradise Chronicle (talk) 21:56, 3 April 2023 (UTC)
The classification for Mass creation (in which 100 created articles in total are seen as a sign for masscreation) produced by BilledMammal is also interesting and has also not received much feedback either.Paradise Chronicle (talk) 22:05, 3 April 2023 (UTC)
In re this would just raise the level instead of reducing it: Does the number of articles that individuals are permitted to create actually need to be reduced? Are there still any editors who like to masscreate articles around? If not, why should we write down a rule to ban something that nobody is doing any more?
It's not sensible to say "More than a decade ago, Lugnuts created ~100,000 articles. I think his quality was poor, so I decree that editors who want to create one thousandth as many articles as him must get special written permission first." WhatamIdoing (talk) 18:08, 7 April 2023 (UTC)
Yes. I've been trying to compel them to request permission as required by WP:MASSCREATE, and in some cases I have been successful (with the result never being a consensus in favor of mass creation), but many ignore the requests. BilledMammal (talk) 18:11, 7 April 2023 (UTC)
MASSCREATE requires people to request permission for >50 articles per day. 100 per lifetime would be a substantial reduction from that.
@Paradise Chronicle, I see that you have created more than 300 articles. That is more than 100 in total. Are you a mass creator? Do you think that Wikipedia needs to be protected from you? Should you be getting special permission for every article you want to create in the future? WhatamIdoing (talk) 18:32, 7 April 2023 (UTC)
I wouldn't call me a mass creator in the current meaning. But I support the 100 article bar and would apply for permission if it came through. Paradise Chronicle (talk) 19:30, 7 April 2023 (UTC)
I want you to imagine yourself explaining Wikipedia's processes to someone in your real life, and saying something like this:
"I want to create one article this month. Now, if I were a new editor and didn't know what I was doing, I'd just click here and do it. But I'm experienced, so have to jump through bureaucratic hoops first. I'll have to write up a description, identify my planned sources, and get written permission. By the time you consider writing the request and all the people reading and replying, applying will take more time from the community than creating the article. Of course, a newcomer wouldn't like this; we only impose this on people who have experience with creating articles."
Do you think they would consider that to be sensible or silly? WhatamIdoing (talk) 04:41, 11 April 2023 (UTC)
Today, it only concerns editors who crossed the bar of 25-50 articles a day or used semi-automated tools for their article creation. The semi-automated is mainly mentioned since the 25-50 was ignored in the past. I do not believe the result of the Lugnuts and the Carlossuarez discussions is the one editors hoped for when they began editing. The Lugnuts articles were sourced well enough when they were created, but not anymore later. I believe the rules and guidelines will eventually get enforced, as it's not really informative to have heaps of unexplained, unsourced statistics and micro stubs of a few words or phrases. Paradise Chronicle (talk) 06:25, 11 April 2023 (UTC)
@Paradise Chronicle, I think you would hold a different view if you had been around back in the day. Please click this link and open, say, 10 tabs: nostalgia:Special:Random. That's what editors hoped for when they began editing. That's what they were doing. If you'd like to see some of the best, then try the equivalent of Featured Articles. Clicking through the first five, I see: one with ASCII art but no references; one with a general reference; two with suggested sources but no refs; and one with no sources mentioned at all.
If you're interested in learning more about the early days, then nostalgia:What Wikipedia is not might also be interesting. Also, if you see a page title that says /Talk at the end, that's what turned into talk pages. Before that (and even concurrently with it), editors just dumped their comments in the article page, at the bottom of the page. Namespaces weren't a thing back when Wikipedia was started. Talk pages were invented by Wikipedia.
And, more generally, when you think about saying I do not believe the result ... is the one editors hoped for when they began editing, you might want to pause and consider whether that statement should be re-written as I do not believe the result ... is the one I hoped for when I began editing. Since you started editing (your prior account) in 2018, you likely have a very different view of what's reasonable than the folks who were editing in 2003, or even in 2013. WhatamIdoing (talk) 20:21, 17 April 2023 (UTC)
Yeah, your reply sort of proves my point in a way that Wikipedia developed for the better. I do not believe you'll find consensus to go back to 2005 where "FAs" were able to be unsourced. In small wikis this is still possible but the English one is sort of a reference for the majority of the world which makes it one of the first hits on google and similar search engines all over the world. My suggestion is that Wikipedia develops further from quantity to quality but at the moment, consensus will not be found for that. And no, I meant what I wrote, and I believe you agree as well. Nor I, Lugnuts, Carlossuarez and the majority of other the editors partaking in the discussions were expecting that such a heap of poorly sourced content was able to exist and grow on Wikipedia when they began editing.Paradise Chronicle (talk) 18:16, 20 April 2023 (UTC)
It actually doesn't need to be reduced if the policies were enforced, but admins find any kind of excuses in order not to apply them. 25-50 a day most of the top 10 have created so far, very likely all use semiautomated processes. To apply for permission is not meant to ban masscreation, one can create 100 a day and for as long as they want, but please masscreate informative articles, not stubs with a few phrases or full of statistics.Paradise Chronicle (talk) 19:52, 7 April 2023 (UTC)
How frequently did the top 10 exceed 50 articles in one day?
(Note the NOTSTATS only bans "unexplained" stats.) WhatamIdoing (talk) 04:43, 11 April 2023 (UTC)
Why don't you ask for Semiautomated? I just believe that Wikipedia guidelines will develop towards quality instead of quantity as it did in the past. There would be also other policies that would apply, like WP:NOTMIRROR or WP:NOTPROMO for statistics mainly or only sourced to databases (not independent of the article subject). But I see the resistence of applying MASSCREATE and MEATBOT, so I guess its a matter of patience.Paradise Chronicle (talk) 07:37, 11 April 2023 (UTC)
Proving that someone exceeded 50 article creations on the same day is easy. Proving that they used an off-wiki tool requires either mind reading or intrusive surveillance, neither of which I'm good at. Consequently, I'm asking for the thing that really could be enforced (in software, if necessary). WhatamIdoing (talk) 20:23, 17 April 2023 (UTC)
Just came here to mention that a similar discussion was held here, where some standards were purposed for articles specific to the Dams. I think at the end, it boils down to the quality of article , not the quantity of article. Each project's articles should be discussed on the specific project group because you can find the concerned experts there and can decide on the quality, standards and overall assessment. After all one cannot be an expert in everything. Best regards!nirmal (talk) 02:11, 23 March 2023 (UTC)
My opinion is that the problem could be mitigated by banning the creation of stubs. If an article on a subject doesn't have at least, say, 250 words or an equivalent number of bytes then it doesn't belong in the encyclopedia. Maybe stubs should be relegated to the wiki dictionary or some other site. Smallchief (talk) 16:21, 24 March 2023 (UTC)
An encyclopaedic stub and a dictionary entry are not at all similar, and suggest you have a fundamental misunderstanding of the purposes of Wikipedia and/or Wiktionary. That does not lend favour to your proposal. Thryduulf (talk) 16:59, 24 March 2023 (UTC)
@Smallchief Great idea the one with the wiktionary. I have/had a similar idea. I thought that if one is not able to word out 10 phrases on a subject, it's not notable enough for wikipedia. As for me it's not enough to add a source, but also the information to the article that is in the source. Paradise Chronicle (talk) 17:43, 24 March 2023 (UTC)
Yes you are right. There @Nirmaljoshi was told not to create more stubs on dams but create Lists on dams in Japanese administrative divisions. Result? Nirmaljoshi created 19 stubs in 2 1/2 hours on the 1 March. That's the kind of discussions I'd like to prevent.Paradise Chronicle (talk) 17:54, 24 March 2023 (UTC)
No, there was not any clear outcome. Please read the discussion properly. Anyway, in the dam related article, one guy hijacked the process and I left on him to move forward.nirmal (talk) 01:28, 25 March 2023 (UTC)
I agree with you that there was no proper closure, but as to me the replies with the strongest arguments were the ones that supported List of Dams articles (comparable to the Lists of Dams in the USA). And your suggestion of a certain professional criteria per ICOLD is good as well, but not one of your dams created on the 1 of March I checked fulfills your own criteria of 1 Million Cubic capacity. Or maybe you can explain how lower numbers still fit in the ICOLD criteria?Paradise Chronicle (talk) 02:31, 25 March 2023 (UTC)

The top 20 article creators in that query generally have a volume of article creations (single digits of articles per day) that could easily be attained by someone hand-crafting and hand-typing individual articles rather than using any automation for these articles. That is not what MASSCREATE and MEATBOT are about. So this proposal seems to me to be missing the point. —David Eppstein (talk) 05:43, 11 April 2023 (UTC)

Little update, Esculenta was now blocked for one month for using AI for article creation per MEATBOT. I have actually asked them to apply for article creation at the BRFA in March but they didn't apply. They were blocked without my direct involvement in the discussions and I would have preferred for them to apply at the BRFA instead of being blocked. Paradise Chronicle (talk) 07:47, 23 April 2023 (UTC)
I’ve read the entire thread above a couple of times. My feeling is I’d rather wait till individual editors do something disruptive and then take action against them if it’s needed. I don’t think we need a policy to cover everything anyone might do, and I think long discussions about individuals’ editing, if they’re needed, are absolutely fine. Mccapra (talk) 08:23, 23 April 2023 (UTC)

Seems to me that the problem is best solved by demanding better quality from article creators. The solution is to have a policy that a newly created article must contain a minimum text of 200 words and be footnoted with at least one reliable source.Smallchief (talk) 11:16, 30 April 2023 (UTC)

I certainly would prefer a requirement for quality in new articles, and suggested one in the RfC on mass creation, but it was ignored. The community certainly seems to be focused on limiting quantity rather than requiring quality as an answer to dealing with mass creation of poorly sourced stubs. Donald Albury 13:06, 30 April 2023 (UTC)
Indeed, so many of these problems would be completely solved by requiring at least one piece of SIGCOV in SIRS for GNG-based articles to avoid draftification/userfication. Then we wouldn't even need the creator to actually write prose in the article. JoelleJay (talk) 16:57, 30 April 2023 (UTC)
Good idea. The main problem with these stubs is that they're hard to expand, and this would begin to address that — DFlhb (talk) 17:47, 30 April 2023 (UTC)

Proposed definition (MASSCREATE and MEATBOT)

As an initial draft I propose replacing the current text of WP:MASSCREATE with the following:

Any large-scale automated or semi-automated content page[a] creation must be approved at Wikipedia:Bots/Requests for approval.

For the purpose of this policy the use of any tools that replace, in part or in whole, the manual work required to create an article will be considered automated or semi-automated creation. These tools include, but are not limited to, the following: For the purpose of this policy use any of the following tools will be considered automated or semi-automated creation. This list is not exhaustive and it is possible to engage in mass creation without the use of any of these tools.

When determining whether creations are done at a large scale only the cumulative number should be considered; the rate of creation is not relevant. There is no set definition of "large scale", although anything more than 25 or 50 is likely to be so. Creating articles without the use of tools, regardless of the scale or rate, is not considered mass creation, although WP:MEATBOT still applies.

All mass-created articles (except those not required to meet WP:GNG) must cite at least one source which would plausibly contribute to GNG, that is, which constitutes significant coverage in an independent reliable secondary source.

As defined this won't affect the average editor who is manually creating articles. Further, clarifying and enforcing the definition will benefit the community in two ways.

  1. For mass creation that is constructive and that the community would approve of, it will provide an opportunity for the community to suggest modifications to produce better articles; it is easier to improve an entire set of mass created articles at the start of the process than it is to do so after the articles have been created.
  2. For mass creation that is not constructive, such as the mass creation of geostubs by Carlossuarez46, it will allow the community to intervene before the scale of the problem becomes a significant burden on the community.

We consider the cumulative number, not the rate, because the issues mass creation can cause are related solely to the number of articles created, not the rate they are created at. It is possible for mass creation done at a low rate to result in greater issues than mass creation done at a high rate because detecting low rates of mass creation is more difficult and thus can result in a greater number of pages that the community must deal with. BilledMammal (talk) 09:20, 23 April 2023 (UTC)

There are multiple problems with this. Firstly, the rate of creation is relevant. If I create 51 articles in 365 days using one of those methods that would not cause anybody any problems at all yet would be prohibited by your definition, yet creating 1000 articles in 10 days without using "tools" might or might not be covered (see below) despite being likely problematic.
I say "might or might not" because the proposal is contradictory :
  • Any large-scale automated or semi-automated content page creation must be approved and
  • it is possible to engage in mass creation without the use of any of these tools., yet
  • Creating articles without the use of tools, regardless of the scale or rate, is not considered mass creation.
The third bullet point contradicts the first two.
Finally, you seem to have ignored much of the discussion above regarding what is and isn't problematic. Thryduulf (talk) 09:37, 23 April 2023 (UTC)
The third bullet point doesn't contradict the first two. If you aren't using any tools then you aren't engaged in automated or semi-automated creation. However, I've reworded the second bullet point.
For manual large scale creation, like your example of 1000 articles in 10 days, I don't believe we can or should address it. I don't believe we should because the issues caused are different, and because we can address those issues under other policies - the community can easily handle an editor manually creating 1000 problematic articles in 10 days under WP:DE.
I don't believe we can because any attempt to do so will make it more likely that this policy will apply to editors who have the reasonable expectation that it won't because they are not using any tools in their editing; per the discussion above, which I haven't ignored, this is something that must be avoided.
If I create 51 articles in 365 days using one of those methods that would not cause anybody any problems at all yet would be prohibited by your definition It wouldn't be prohibited; it would just require you to go through BRFA, where approval should be quick if no issues exist. However, issues can exist for even smaller levels of mass creation. For example if you want to create 51 articles with ChatGPT I think community oversight would be a very good idea.
I also think that such an example would be extremely rare or even non-existent; how many editors engage in semi-automated or automated creation of articles but stop at 51 or a similarly small number? Do you have any examples? BilledMammal (talk) 10:12, 23 April 2023 (UTC)
Editors need to seek permission to upload files and create categories? I've seen some poorly thought out categorization schemes where I wish the editors creating the categories would have consulted somewhere about creating them. But requiring editors to seek permission to create more than 25 pages in their Wikipedia careers is ridiculous Are disambiguation pages and redirects included too? Plantdrew (talk) 16:31, 23 April 2023 (UTC)
That aspect is taken directly from the current WP:MASSCREATE policy. It also would only apply to automated or semi-automated activities; as most editors create categories and upload files manually it wouldn't apply to them. In line with the current policy, it wouldn't apply to redirects but it would apply to dab pages. BilledMammal (talk) 17:04, 23 April 2023 (UTC)

Notes (MASSCREATE and MEATBOT)

  1. ^ "Content page" means any page designed to be viewed by readers through the mainspace. These include articles, most visible categories, files hosted on Wikipedia, mainspace editnotices, and portals.

Alternative proposal: Move MASSCREATE out of BOTPOL

As I've looked at recent discussions around WP:MASSCREATE, I've become convinced that these are being hampered by that being a part of WP:Bot policy. It seems to me that the community wants to concern itself with mass creation in general, without regard for whether it's automated, semi-automated, or fully manual. WP:MEATBOT can help there, but that can only stretch so far—if you get to the point where "boilerplate text" might include Wikipedia:Manual of Style/Layout, you've probably gone too far.

Additionally, the bot policy can't legitimately say much about how non-bots should go about getting approval. MEATBOT is mainly about enforcement, not approval. In the recent RFC, a proposal to require BRFAs for mass-creation approval was rejected, and BAG does not seem to want it there either.

So how about it? Should the community move WP:MASSCREATE to some other policy, or to a policy page of its own? Mass creations by bot would still also be subject to WP:BOTPOL and WP:BRFA for the bot aspect, but the new policy would be freed from having to imply that all mass creations are somehow bot activity. Anomie⚔ 12:17, 23 April 2023 (UTC)

@Anomie Don't think it is big enough to be a stand alone policy, but it certainly doesn't need to be in BOTPOL (got somewhere else it could be merged?); botpol should reference wherever it ends up as a reminder to BAG/operators that bots that want to do that not only need to be approved as a bot, but ensure they have whatever community support is needed to exempt them from that policy. — xaosflux Talk 13:31, 23 April 2023 (UTC)
It might expand a bit once released from the constraint of being ostensibly about bots. But my main goal is to establish a consensus to move it out of BOTPOL since it really no longer fits there, where exactly it ends up I'm happy to leave to others to decide later. I agree that WP:Bot policy#Mass page creation should remain as a stub. Anomie⚔ 13:59, 23 April 2023 (UTC)
A layout guide can't be boilerplate text, but apart from that I think you make a good point - even if we decide to exclude fully manual mass creation from its scope it is better for MASSCREATE to be outside BOTPOL. We would need to replace the reference to BRFA; I think instructing editors to get community consensus at VPR would be a good replacement.
The best target I can see to merge it to would be Wikipedia:Editing policy, but I think it is better off as a standalone policy; it would be one of the shorter policies we have, but there are several of comparable or lesser length such as WP:IAR and WP:STRONGPASS. If it is made a standalone policy I think the best classification for it would be as a procedural policy; the same classification as BOTPOL. BilledMammal (talk) 13:50, 23 April 2023 (UTC)
  • Oppose for the record. Huge change to the policy needs a formal RfC, but also there's not enough of a proposal here to explain what it would say when moved out of the bot policy. — Rhododendrites talk \\ 14:15, 4 May 2023 (UTC)
    • 🙄 Do you actually oppose the idea of moving it at all? Or are you just "opposing" because you want a 100% fleshed-out proposal instead of a check for whether it's worth the time making one? Anomie⚔ 01:19, 5 May 2023 (UTC)
      • Moving it isn't really what's happening (or not the meaningful part). This is completely redefining what "mass creation" is to include some as-yet undefined kind of mass creation that applies to totally manual editing. Simply moving it doesn't actually change anything, but changing the way it just talks about automated or semi-automated editing is, and that needs a fully fleshed out proposal. — Rhododendrites talk \\ 22:30, 5 May 2023 (UTC)
        • As far as I'm concerned, this proposal would indeed be satisfied by moving the existing text with zero changes to some other location. And I agree with you that actually making changes to the policy would require specific discussion about those changes. I disagree with your assertion that simply moving it wouldn't change anything: it would change the context, and that's exactly the point. "It's in the bot policy so it can only apply to bots" is in the way of those discussions, causing them (like the sections above) to have to try to stretch WP:MEATBOT to cover clearly non-bot edits and to somehow involve BRFA in the approval process for these not-actually-automated creations. Anomie⚔ 12:57, 6 May 2023 (UTC)

So I took a look at all the policies that User:Anomie has noted, and it seems to me that there should be a small subsection in Wikipedia:Editing policy which explains some basics about bot editing and about semi-automated editing (meatbot), and even WP:FAITACCOMPLI. Automated editing wasn't that big of a deal in Wikipedia's early days, but now we even have semi-automated editing options integrated into Wikipedia. I think we're doing a diservice to our editors if we don't at least point to where to find more information on these things, without relying on a bottom-of-the-page navbox. - jc37 13:35, 6 May 2023 (UTC)

What is and isn't part of a country on Wikipedia?

I notice that Crimea is considered a Ukrainian territory on Wikipedia, as the United Nations voted to not recognize Russia's land grabs.

Yet at the same time, the first line on the Taiwan article is "Taiwan is a country", while Taiwan is not recognized as such by the UN.

Why is that? Synotia (moan) 16:56, 28 April 2023 (UTC)

The stance of the UN is one factor that might be considered, but it's not a deciding factor. We go by what the mainstream position is in WP:reliable sources. If you look at the footnote next to "is a country", it lists several reliable sources that describe Taiwan as a country. Thebiguglyalien (talk) 17:06, 28 April 2023 (UTC)
I suspect that if you looked for Chinese-language sources, the opposite would be the consensus. You might understand what I mean? Synotia (moan) 17:07, 28 April 2023 (UTC)
Not really a policy issue, this. Selfstudier (talk) 17:10, 28 April 2023 (UTC)
Because other stuff exists, and WP:CONSENSUS. Each situation is determined individually, and there have been discussions on both individually have led to the current texts on Wikipedia. If you wish for one to be consider as another for either one, it is best to open a discussion on talk page of the article of the one you want to change. – robertsky (talk) 17:11, 28 April 2023 (UTC)
I would also note that we have articles on both the Russian province of Crimea (Republic of Crimea) and the Ukrainian province of Crimea (Autonomous Republic of Crimea) in the same way we have articles on the province of Taiwan in the ROC (Taiwan Province) and the province of Taiwan in the PRC (Taiwan Province, People's Republic of China). There is also a fundamental difference between the two disputes you list, in that Taiwan claims itself to be an independent nation while Crimea does not. Curbon7 (talk) 17:28, 28 April 2023 (UTC)
Because you can't backdoor your way into overriding consensus by trying to invent a rule. If you think the wording of an article should be changed, get your evidence together, go to the article talk page, lay out your evidence, and let others do the same. If other people have stronger evidence than you do, there's no rule or policy that should change that. --Jayron32 18:35, 28 April 2023 (UTC)
As others have pointed out, this is a really complicated question, with no universally correct answer. I used to work for a network management company. Our product was the kind of thing that put up a big world map showing the status of all your data centers, communication links, etc. We had multiple versions of the base map, showing countries labeled in whatever way was not going to offend a particular customer. -- RoySmith (talk) 16:36, 30 April 2023 (UTC)
Toponymy is the politics of naming and often different state/actors have competing interests. Wikipedia doesn’t take a position but tries to summarise different non-fringe/authoritative sources. Happy editing! ~ 🦝 Shushugah (he/him • talk) 12:45, 1 May 2023 (UTC)
Without commenting on the specific geopolitical issues raised here, I'll point out that in general, although we aim for NPOV, we do not always achieve it. Our articles often reflect an American or Western European point of view, because of our systemic bias. —Mx. Granger (talk · contribs) 13:17, 4 May 2023 (UTC)
There has been a peaceful status quo in the dispute between the PRC and the ROC for over 70 years, and the Wikipedia article generally reflects that. There is a hot war in Ukraine, and the Wikipedia article reflects the status quo ante of the conflict. I don't see any contradiction here. Walt Yoder (talk) 19:41, 6 May 2023 (UTC)

Would like to understand how Criteria_for_speedy_deletion#G8 applies to Templates?

Hi I am an editor from Chinese Wiki and my major interest is to move the templates from English Wiki to Chinese Wiki, so the people can build pages with minimal effort.

Currently I face one problem while moving templates. In English wiki there are some templates looks like a subpage (e.g. Template:NYCS_Platform_Layout_BMT_Brighton_Line/embankment and there is no main page for this template (Template:NYCS_Platform_Layout_BMT_Brighton_Line in this example). While I move the template from English wiki to Chinese wiki the bot triggered a speedy deletion alarm and the subpage template was deleted zh:Template:NYCS_Platform_Layout_BMT_Brighton_Line/embankment due to the speedy deletion rule. While chatting with other editors they said the Speedy deletion rule was inherited from G8:Subpages with no parent pagerule.

So I would like to understand how English wiki interpret the speedy deletion policy and how speedy deletion wouldn't apply to Template:NYCS_Platform_Layout_BMT_Brighton_Line/embankment? Thank you very much Winston (talk) 00:13, 7 May 2023 (UTC)

My understanding is that the "Subpages with no parent page" provision in WP:G8 can apply to templates, e.g. to delete components, docs, testcases alongside the main template. One example is Template:CBB Seasons Cat Header/Name conv. But the whole WP:G8 "excludes any page that is useful to Wikipedia", so it should not be used to delete helpful templates that can work on their own and not actually a subpage in the sense of being a component of a non-existent parent template, even if they are (perhaps inappropriately) titled as a subpage formally. ——HTinC23 (talk) 02:05, 7 May 2023 (UTC)
G8 is almost always invoked in template space only when the parent template is deleted at WP:TFD. A G8 otherwise would be quite suspect.
That said, our rules don't decide how zh works. OP should discuss there about how and why actions should be taken. IznoPublic (talk) 01:38, 8 May 2023 (UTC)
@Izno I totally agree that the en rules doesn't decide how zh works. And thanks for your comment.
I am looking at WP:TFD#REASONS and it seems that the subpage rules doesn't apply to templates, from the general application point of view. Winston (talk) 02:45, 8 May 2023 (UTC)

RfC: Non-free licensed files

CLOSED
See Wikipedia:Perennial proposals § Allow non-commercial licensed content.
This is a WP:SNOW close, but initial response here should be enough indication alone that consensus is against this.
(non-admin closure) –MJL ‐Talk‐☖ 17:21, 10 May 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Should full-size Creative Commons NC, ND, or NCND, or compatible, licensed files be allowed?

Context

Some files are classified as non-free by Wikipedia standards but are available under a license that permits educational, personal, or otherwise non-commercial use and/or prohibits derivative works. These include certain Creative Commons licenses.

The policy, as currently written, has a number of criteria that must be met in order for a non-free file to be used. One of these is the minimal extent of use which is further specified as "including usage of low-resolution, rather than high-resolution/fidelity/bit rate (especially where the original could be used for deliberate copyright infringement)". Bots enforce this provision by automatically resizing any files deemed too large.

The wmf:Resolution:Licensing policy is the ultimate authority in copyright matters. It authorizes projects to develop and adopt an Exemption Doctrine Policy consistent with the resolution, permitting "the upload of copyrighted materials that can be legally used in the context of the project". The proposed change is fully compatible with the resolution.

This proposal was discussed before here.

Rationale

Low-resolution requirement is in the policy solely because fair use compliance so requires. It is intended to reduce the reusability of the file, and so any adverse commercial impact our use would cause to the copyright holder. However, under these licenses, no fair use considerations are required.

We should always use free files when available, and this change would in no way affect that requirement. However, when we are given the option to either use the file under a claim of fair use and reduce its quality, or use it under a non-free license, we should choose the less bad alternative. To do otherwise would be a disservice to both our readers and re-users.

It would also better respect the wishes of the copyright holders: they want (and in case of ND explicitly require) us (and the general public) to use their works in their original form, but we are in fact forcibly altering them to a worse quality. I don't think we can even claim our use to be fair if, given the option to use unaltered files, we choose to alter it anyway and misrepresent its quality.

Best, CandyScythe (talk) 10:25, 6 May 2023 (UTC)

  • No. The WMF Resolution on non-free images uses a definition of "free" that requires us to allow end users to redistribute and modify images regardless of their type (commercial or not). While we could use licenses like CC-ND or CC-NC at full size, end users cannot. So we have to treat these as non-free and offer low resolution versions that end users likely have a better chance to use under a fair use allowance on their end. --Masem (t) 13:52, 6 May 2023 (UTC)
    We really have to balance the interests of our readers, different types of re-users, and copyright holders. I think it's undisputed that readers come first, and that they would be better served with higher-quality files. Non-commercial re-users would also benefit. What is fair use for Wikipedia is most often not for a commercial re-user, so most of those would already be unable to use those files. In the rare case that someone would be unable to legally re-use files because of their high quality, re-sizing them like we already routinely do would be trivial for them. It would be strange to sacrifice all the potential benefits to protect a small subclass of our re-users from minor inconvenience. The WMF Resolution does in no way force us to do it, as it explicitly authorizes use of non-free files under an applicable rationale. Best, CandyScythe (talk) 14:37, 6 May 2023 (UTC)
    We have effectively "marching orders" from the WMF here. Unless you want to run your own servers and set the rules on what content we allow, we have to follow the resolution here and what counts as free or not. You're also effectively asking to create a third class of images outside free and non-free, and that would become a mess in creating all the necessarily policy and procedures for under the resolution. Masem (t) 15:18, 6 May 2023 (UTC)
    I think that you're confusing and diluting your your good explanation with the "Because WMF said so". If that were the only reason, then we'd need to tell WMF to change that. North8000 (talk) 17:18, 6 May 2023 (UTC)
    They own and pay for the servers. They get to make the rules here. Masem (t) 02:37, 7 May 2023 (UTC)
    Importantly, I believe it could not merely affect operation of servers, but interfere with contracts the WMF has with commercial partners (Google is paying the Wikimedia Foundation for better access to information – the Verge). — HTGS (talk) 05:59, 7 May 2023 (UTC)
  • No It is a disservice to our readers and downstream users to create content that is not available under a fully free license. We are not the somewhat-free-encyclopedia. This would undermine the very idea of the free culture movement and make our licensing situation considerably more restrictive rather than permissive. We already have north of 700 thousand non-free files on this project. We don't need another category of somewhat-free files that will very likely balloon to such a huge figure itself. Absolutely not. --Hammersoft (talk) 15:06, 6 May 2023 (UTC)
  • No Commercial uses are still uses, so non-commercial licences are a restriction on our users akin to fair use. – John M Wolfson (talk • contribs) 16:09, 6 May 2023 (UTC)
  • No Per reasons given by others. But thanks for the thought and bringing it up. North8000 (talk) 17:20, 6 May 2023 (UTC)
  • Yes NC images are a good resource for our purpose and we should not hinder or obstruct their use in any way. It's best to capture the entire image in case the original should go down and be lost. I was looking for the source of an image the other day and found it had gone offline. Andrew🐉(talk) 17:50, 6 May 2023 (UTC)
    Wikipedia is not archive.org, archive.is or other archiving service. Use one of those to preserve the original of non-free images if they have not already done so. Doing so matches directly their mission and they have the infrastructure, policies, etc. in place to deal with such tasks better than we do (because it's only a tangential part of our mission). Additionally you can use them to preserve far more images more reliably than you could on Wikipedia, because images can and do get deleted here for many reasons. Thryduulf (talk) 20:42, 6 May 2023 (UTC)
  • No per Masem's first comment. Files that have restrictions on commercial use and/or derivatives are not Free in the sense we use it on Wikipedia, and I see no benefit to creating a class of slightly less non-free images with all the added complexity, bureaucracy, policy and maintenance overhead that would entail. Thryduulf (talk) 20:38, 6 May 2023 (UTC)
    The only change required would be that if tagged with a "Non-free with NC and ND" template, it would also tell bots not to resize that file. I don't really see the bureaucracy argument. Best, CandyScythe (talk) 20:46, 6 May 2023 (UTC)
  • No per others above. NC and ND conditions are not considered sufficiently free under the WMF resolution and so they should be treated under the same non-free content policy as other non-free images for reasons outlined above. -- Whpq (talk) 21:21, 6 May 2023 (UTC)
  • No, per Masem et al. Boing! said Zebedee (talk) 06:11, 7 May 2023 (UTC)
  • No (or Oppose) mainly for the reasons given above, but also because this seems to be trying to carve a general exception to WP:JUSTONE for certain types of images when such a thing isn't really necessary. While it's true that WP:NFCC#3b (WP:IMAGERES) does require that non-free images, in principle, be "rescaled as small as possible", it does qualify that with "to still be useful as identified by their rationale, and no larger". This seems to allow for the possibility of a non-free image either not being fully rescaled or rescaled at all when doing so is deemed necessary to preserve it's encyclopedic value to readers. A file could be tagged with Template:Non-free no reduce if the uploader feels the any rescaling is not needed. The uploader could also rescale the image themselves to what they feel is the appropriate size before uploading it and then add the aforementioned template to prevent any further rescaling. There's also Template:Non-free manual reduce that can be used when excessive rescaling by bots is a concern. In any of these cases, there's no reason why disagreements over rescaling or appropriate image size can't be resolved through discussion at WP:FFD much in the same way that disagreements over the application of any of the other NFCCP are often resolved. For sure the burden would fall upon the uploader or whomever wants to image to remain at a certain size to establish a consensus in support of their position, but that's no different from how things currently are per WP:NFCCE. When it comes to free image licensing, Wikipedia for the most part seems to pretty much follow c:COM:L and c:COM:LJ, except it does so on a local level. Wikipedia and several other of the local Wikipedia's do allow some fair use content to be uploaded and user, but many others are like Commons and allow no fair use content at all. What this RFC is proposing (at least in my opinion) is to create a new category of image licensing that lies somewhere in between what would be considered free licenses and non-free licenses; in other words, a sort of hybrid-license that tries to apply parts of both WP:COPYOTHERS and WP:NFCC. That (at least in my mind) involves something much more that telling bots not to resize a file (which already can be done to some degree), and might even require running things pass the WMF to see whether it is OK with this new category of licensing. -- Marchjuly (talk) 11:41, 7 May 2023 (UTC)
  • No The point of disallowing these licenses is that Wikipedia should be as free as possible to any downstream reuse while still respecting the creators. CC-BY-SA attributes the creators and allows unlimited downstream reuse so long as attribution is maintained. Once you put restrictions on reuse like NC or ND, that has unintended knock-on effects. --Jayron32 13:37, 9 May 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Petition to remove appealing to Jimbo from the Arbitration Policy

Hi all, please see this petition to amend the arbitration policy to remove Jimbo Wales's ability to overturn ArbCom decisions, which needs a 100 signatures as per the formal amendment process. Galobtter (talk) 18:18, 9 May 2023 (UTC)

Thanks! Signed it! Chaotic Enby (talk) 22:04, 14 May 2023 (UTC)

Can we promote WP:Prodigy to a guideline?

This popped up because of a recent edit and I realized that this has been sitting as a draft for a very long time. There has been no substantive discussion of it in a while either, so I would like to propose that it be made a guideline as is. Mangoe (talk) 03:43, 28 April 2023 (UTC)

I have no strong opinion about this either way, but this thread reminded me of an old situation and encouraged me to put together this RFD. Graham87 08:57, 28 April 2023 (UTC)
This seems like a very specific circumstance to have its own guideline. If this is a recurring problem (which apparently it is), the best approach might just be to enforce existing policies like WP:BLP and WP:NBIO, which seem to cover this. Things like WP:PRODIGY work better as essays that interpret policy rather than becoming P&G in their own right. WP:NEXTBIGTHING comes to mind as a similar example. Thebiguglyalien (talk) 15:37, 28 April 2023 (UTC)
I would second this, with the thought that perhaps it could be linked to within the appropriate policy articles. Nerd1a4i (they/them) (talk) 03:44, 1 May 2023 (UTC)
Meh. I'm not sure it's particularly needed. Wikipedia covers articles on children who meet the same guidance as adults. There are dozens of articles about children Edward V of England, Tad Lincoln, Nandi Bushell, Gavin Warren, etc. and I'm not sure we need special rules for "child prodigies" vs. other children. Why does one need special protection because one was a prodigy? --Jayron32 16:17, 28 April 2023 (UTC)
Child prodigies need special protection because of the publicity hype about them often generated by the media and by ambitious and unscrupulous parents. There have been several examples in the last ten years. I should like to see this as a guideline or an essay. Xxanthippe (talk) 04:12, 1 May 2023 (UTC).
I mean, if you want to write an essay, write it. No one has to agree with an essay. --Jayron32 11:02, 1 May 2023 (UTC)
Discussion here appears to have died. I've tagged it as an essay, feel free to revert. casualdejekyll 20:50, 11 May 2023 (UTC)

Capitalization of hockey rounds and such

Following on discussion at WT:MOSCAPS#And_again, there's an RFC at WT:WikiProject Ice Hockey#RfC: NHL round names capitalization, essentially asking for a Hockey exception. Comments? 04:25, 12 May 2023 (UTC) Dicklyon (talk) 04:25, 12 May 2023 (UTC)

Handling and interpreting the globalize template

I apologize if I have placed this in the wrong area. I welcome anyone to move it, if they wish to do so.

I think that the Globalize template is of very little value to Wikipedia and is in some ways a negative influence. I am not trying to antagonize anyone who has placed Globalize templates. Unless other edits show otherwise, I believe that they all acted in good faith and that they were genuinely trying to help. I have never found anyone who was acting in bad faith in regard to this template, or any template that does not deal with article deletion. However, in all of my time on Wikipedia, I cannot remember a single time when the person who placed the globalize template actually did work on the article to help with globalizing the article. I can remember them doing some minor edits, sometimes (a couple of wording changes to the document that indicate that the article refers to how things are done in a specific country, not the world), but not anything else. It is possible that many of the "taggers" did substantial work on the article, and I have just missed it (taggers is not meant to be a derogatory term, here, it is just easier than "editor who placed a globalize template" and I use it to describe all templates, and I call them all "tags" for short). Although, I always check to see if they have done additional work, and I also check to see if they posted on the talk page to explain why the globalize template is there. From my experience (anecdotal evidence, the worst type of evidence because it is so prone to bias of the person, as well as sampling bias, and the huge problem of relying on human memory), I would say that over 90% of the tags were placed with no explanation on the talk page or the edit summary* about why it was placed and no change made to the article besides the tag, and I think that is a very conservative estimate (I do not count putting the word "globalize" or "globalization" in the edit summary to be an explanation). However, the articles I read and edit may be unrepresentative of the use of the tag as a whole. Again, in my personal experience, I would say that perhaps half of the users of the templates put "globalize", or something to that effect, in the edit summary, while the rest were blank. In my opinion, that is insufficient unless the state of the article and the subject matter is such that the need for globalization is essentially self-evident. I believe that globalization tags have been added to articles inappropriately in some cases. If one cannot voice how an article should be globalized on the talk page, I do not think that the tag should be placed.

In addition, true globalization in an article is a completely ridiculous standard, if one thinks about it. There are close to 200 countries in the world (the precise amount varies with what one is willing to call a country, personally I do not think Monaco, Andorra, The Vatican, and other micronations count, unless you have a separate micronations category, but that is another issue). It is completely impossible to come up with articles that cover even simple issues in every country, let alone complex ones. There are also regional variations within countries to consider for some topics. To write such an article would be a monumental task. It might be something that a college could do with all of its majors in one subject making a contribution, but that would be a single article. There are thousands of articles with the globalize tag. Even if one such article were written, it would be far too long. Then, even if it were not too long, it would be impossible to keep such an article up to date, with fast-moving topics being a dozen times more impossible.

Another problem is that some topics are not covered by developing nations, as they are currently having problems with things like extreme poverty, natural disasters, rampant corruption, murder squads, impoverished locals selling drugs to rich nations and drug cartels murdering anyone who gets in the way. Their nations do not have people documenting the use of braille by their citizens, and even when they do, they usually only publish the books and articles in their own languages.

In my opinion, Wikipedia should come up with a more reasonable standard for presenting an international view of topics. As an English language encyclopedia, I suggest that we try to get the situation in English speaking countries first (U.S., UK, IR, CA, NZ, AU, IN – I think those are the right codes for Ireland, Canada, Australia, and India) and to make some more sweeping generalizations for certain areas, like regional things – Latin America, North Africa, Sub-Saharan Africa, Middle East, Western Europe, Eastern Europe, Central Asia… and so on. I mean no offense to the non-English speaking world. I am just trying to be realistic. No one would like an article that actually covers a topic on a global scale more than I would, even if it is twenty pages long. My perfectionist heart is currently breaking, but this task is simply impossible. There are over 5,000 articles with the globalize template on them. It would require the effort of many times the number of editors that we currently have to handle such a project. You would have to assign a scholar to a couple of topics, and depending on the nature of each topic, have him or her be assisted by students, as I suggested. For some topics, you could go 10 to 40 years without needing to do it again. However, some would have to be done every three to five years. If something is on the three year side, it is essentially a never ending project.

I have not been able to express things as elegantly as I would have liked. However, I hope that my issues have been understood despite that. I will try to get back here in case anything needs clarification, but I pretty much said what I wanted to say. I warn you that it can be days before I am able to come back to Wikipedia, sometimes longer. If that is the case, I hope that you can be patient with me and I apologize for the delay in advance. -- Kjkolb (talk) 03:02, 26 April 2023 (UTC)

Globalize doesn't mean "cover every aspect of the topic in every country". It means "don't present the U.S. aspects as if they're universal or the only ones that matter". Thebiguglyalien (talk) 05:45, 26 April 2023 (UTC)
Although the US is the most common single country used, it is not the only one and globalisation can apply equally to articles that are United Kingdom-centric, Europe-centric, Hong Kong-centric, Anglosphere-centric, etc. Thryduulf (talk) 09:06, 26 April 2023 (UTC)
This issue is exactly the one we had with {{Expert needed}}, namely editors tagging articles without providing any context or reason, leaving it to others to work out what the problem is and to put in the effort to fix it. Following a 2021 TFD, it was agreed to formally deprecate {{Expert needed}} if the reason= parameter was not filled in. Something similar might help here, as it would make it clearer that unexplained Globalize tags either need to be expanded or can be removed without the removing editor needing to get into arguments about whether the (unstated) reason was 'evident'.
The meaning of the tag also needs clarification. Many editors think it means "please add information about other regions or countries", unsurprisingly given the tag name and the wording "this article may not represent a worldwide view of the subject". But that's not an easy thing to do, with the result that many such tags languish for years. Better might be to change (or clarify) the meaning to "this article includes information that is wrongly stated or implied to be universal or applicable over an excessively wide geographical area. Please either provide additional examples covering other countries or regions, or clarify the geographical area to which the text applies." That's much easier for later editors to deal with, very often by adding some sort of limiting text such as "In the United States, ...". MichaelMaggs (talk) 12:53, 26 April 2023 (UTC)
The globalize template can already be removed if no reason is provided. From Template:Globalize:
  • Please explain your concerns on the article's talk page and link to the section title of the discussion you initiate. Otherwise, other editors may remove this tag without further notice.
  • This [template]...assumes that you will promptly explain your concerns on that article's talk page in a new section titled "Globalize." (specifically referring to use of the syntax {{Globalize|date=April 2023}})
  • If you do not explain your concerns on the article's talk page, you may expect this tag to be promptly and justifiably removed as "unexplained" by the first editor who happens to not understand why you added this tag.
--Sunrise (talk) 03:14, 27 April 2023 (UTC)
I think the meaning of the template is pretty clear. It is as User:Thebiguglyalien says above. If an article only covers one or a few countries then that should simply be made clear. As with most templates that are put on articles the reason for placing it is simply that an editor has seen the issue but doesn't have the time or the ability or the inclination (we are all volunteers) to fix it. If the issue is not clear then people who remove templates should not be treated any worse than people who place them. Phil Bridger (talk) 17:29, 26 April 2023 (UTC)
Indeed, if it isn't clear to you why an article has a particular template then, unless it's clearly incorrect (e.g. [1]), the best thing to do in most circumstances is ask on the talk page and/or ask the editor who placed the template. If other editors can explain the issue then all is good, if they can't then that's very likely consensus to remove it. Of course in some situations some aspect of the topic does apply only to one part of the world (despite a non-expert's gut feeling that it is more widespread than that) and it can't be globalised. In that case the section should be reworded to make that clear that it's a local issue and/or spun off into it's own article. Thryduulf (talk) Thryduulf (talk) 19:11, 26 April 2023 (UTC)
Just to refocus this. Providing a "global perspective" doesn't mean "provide 200 different individual perspectives". It means provide a more general and universally applicable perspective rather than one focused on individual geographies. The main way should write is "Here's the basic idea (and here's a some representative places where some differences from the basic idea vary)." That's the correct way to write an article. It shouldn't be "Here's what happens in country 1. Here's what happens in country 2. Here's what happens in country 3." That's bad writing. --Jayron32 19:18, 26 April 2023 (UTC)
IR is Iran and IE is Ireland :p
Also, I concur with the replies above: globalization isn't providing one separate perspective for each country, to the contrary, it is providing a higher-level reporting of the situation free from national bias. Chaotic Enby (talk) 13:10, 13 May 2023 (UTC)

And besides there being no such thing as true globalization, often it should not be expected (such as on inherently local topics) I think that the good use of the template is when the article has a particularly narrow (e.g. single country) perspective and is on a topic where such should not be the case. Maybe the template could be tweaked along those lines. North8000 (talk) 20:26, 26 April 2023 (UTC)

I've suggested some wording above. Is the tweaking you suggest the same, or something different? Trying to find an actionable suggestion here. MichaelMaggs (talk) 21:21, 26 April 2023 (UTC)
Assuming your suggestion is the green text, that doesn't cover all the uses of the template. See for example Bus stop#Regulation where the geographical scope of the content we have couldn't be clearer, but it relates to only part of one country while the topic (regulation of bus stops) is much wider. Thryduulf (talk) 00:18, 27 April 2023 (UTC)
If the topic has no global perspective, perhaps it should be broken up into separate topics per geography. --Jayron32 11:43, 27 April 2023 (UTC)
I can give an example from the world of cars (where this comes up a lot). Sales of the Toyota FJ Cruiser was discontinued in the US at the end of their 2014 model year but it continued being sold in other markets. Their local news sources almost universally reported it as "discontinued", not "discontinued in the US". Therefore, for years yanks would come along and change the article text and its infobox to say that production finished in 2014 - with no qualification. And this was in spite of hidden comments in the article explicitly warning that it was still being sold in other countries. This was a prime example of Americans writing what was true for them but not realising that it was not true for many other countries.  Stepho  talk  01:15, 28 April 2023 (UTC)
Well, then you fix the problem. People who don't read policies also don't read policies when you change them. You can't do anything to stop this from happening, you can only clean up when it does. Sorry for the bad news, but "being diligent and fixing mistakes other people make yourself" is the only reasonable solution. Everything else is meaningless and will have no effect on the problem. --Jayron32 12:25, 2 May 2023 (UTC)
@Kjkolb, do you remember seeing various versions of this tag?
The tags may be appropriate, and it's even possible that they might occasionally result in improvements to the articles (although AFAICT that's never been proven). But it's probably not realistic to expect the editors who tag the articles to contribute to improving the articles. WhatamIdoing (talk) 01:58, 13 May 2023 (UTC)

Examples

Whether one is dealing with a country by country situation or whether you need to take a wider look would seem to depend on the topic. For example, how would you handle topics like the following. Just come up with what your very basic plan for the article would be in a few words. Also, no need to do them all, just pick a couple:

  • Appellate court
  • Borough
  • Bioterrorism (getting sources from many countries will be impossible and many countries do not do research on bioterrorism, which is the part of the article tagged)
  • Cable television
  • Divinity
  • Door (standard door size subdivision is tagged. do standard door sizes outside of North America and Europe even exist and where do you get references?)
  • Dominatrix (good luck getting reliable sources for Latin America, Africa, Middle East, China)
  • Flirting
  • History of science and technology (unless you say that it is the United States or the Western World in the title, this one is asking for problems)

For "appellate court" and similar articles, like Supreme Court, it seems like the only solution is a country by country article, with some grouping by type, like common and civil law, just as the article does.

The following is not sarcastic, despite how it might seem. I suggest that examples of previous success stories of the globalize tag could be given to prove that it is more useful than a regular, general tag. They would also give guidance on how to properly address the issues in the articles that have yet to be fixed. The globalize template has been around in some form since 2004, which is more than enough time for it to have some successes. We could see which articles that it has been removed from and exclude the articles that should not have been tagged in the first place. At least a few of the rest should be success stories. If there are slim to no success stories, then perhaps the tag should not be added to more articles until we decide what we are going to do with the ones that are currently tagged.

Note: Removed list of "why" tags. --Kjkolb (talk) 21:55, 29 April 2023 (UTC)

If a global view exists, describe the global view. If multitudes of highly different individual views exist, the main article should be a DAB page (or nearly so) and the bulk of the information should be in their own articles. Borough could be done a lot better with a simple dictionary definition, then it could be broken out into separate articles on each type of Borough, for example. --Jayron32 12:23, 2 May 2023 (UTC)
Here's a reference for standard door sizes in a bunch of countries (especially non-Western ones): here!
And here's another one!
I don't have the names of the specific regulations establishing each of these, but they should be feasible to find too. In any case, yes, standard door sizes exist outside of NA and Europe.
For articles like Divinity, it's obvious that adding context from other religions and beliefs systems than Christianity (with their own relationships with the divine) would be what's needed. Chaotic Enby (talk) 13:18, 13 May 2023 (UTC)

Evolution/Creation

WP:SNOWBALL applies. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:54, 14 May 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

I've come from the 'horse' page. In the 1st paragraph it's redirecting to the page of a fossil and stating an evolution link. I am a creationist however I am interested in species adaptation. I have my own thoughts on macro vs micro evolution. In this situation, I wasn't expecting speculation, just living facts about horses. This is likely to be across many pages. It's a bad look. And honestly... it's a crap fossil, whatever that was it's unlikely it functioned like the horses of today. Suggestion: instead of 'the horse evolved from' - 'Some speculate that the horse(insert other animal)...' Because imagine yourself on the other side of things reading 'God made the horse on day 1 but it was still a bit dark so he had to adjust it later, which is thought to be this fossil...' 120.22.128.217 (talk) 11:15, 12 May 2023 (UTC)

Presumably you are talking about The horse has evolved over the past 45 to 55 million years from a small multi-toed creature, Eohippus, into the large, single-toed animal of today at horse. The body gives a series of reliable sources that suggest this is true. Are there any WP:RS by Wikipedia's definition that state otherwise?
You are welcome to your own WP:FRINGE theories, but this isn't where we promote them. This is also a content dispute, and shouldn't be at this location, rather at Talk:Horse as this isn't a policy change proposal. Lee Vilenski (talk • contribs) 12:13, 12 May 2023 (UTC)
Wikipedia has no interest in what you believe, or changing it for that matter. However, Wikipedia will continue to report things that are verifiably true and not merely to conform to what you wish were true. --Jayron32 12:49, 12 May 2023 (UTC)
If someone were to add "God made the horse on day 1", we'd have problems within existing policy. Even if we accept the Biblical account of creation and used that as a reference, land animals weren't created until the sixth day. Perhaps the modern horse is evolved from some sort of pegasus, but even that would only move it back to the fifth day. Whichever of those days it was, however, it came before Genesis 1:26 and the creation of man. That means that the only observer capable of recording events was the almighty himself, and it is His word, or Word inspired by Him, that this is what happened. So we're dealing with a WP:SELFSOURCE issue, and surely saying that one created the horse is a boastful claim (certainly if I invented the horse, it'd go right to the top of my resumé!) For matters of evolution, however, we have plenty of policies and guidelines on how to deal with science topics, relying on peer-reviewed literature and such. -- Nat Gertler (talk) 13:56, 12 May 2023 (UTC)
I think Eohippus would be pretty saddened to learn you called it "crap" if it was still alive. Of course it didn't function like the horses of today, there's a full Cenozoic of evolution between the two. Give it time, please! It filled more of a niche of small ungulate, like the dik-diks of today. Adorable little creature.
More seriously, there is definitely a debate to be had as to whether Eohippus should be mentioned in the first paragraph of Horse rather than of Equidae — it's just as much the (near) ancestor of horses as of other modern equids, although this line is often presented (misleadingly) as "horse evolution" even though it is just as much "zebra evolution". More of a question of how WP:RS discuss this topic, really (the facts stay the same — Eohippus or its close relative evolved into the modern Equidae species).
In terms of the evolution/creation matter, it isn't really a "one side vs the other side": verifiable scientific research overwhelmingly support evolution, and placing both on the level of personal beliefs is creating a WP:False balance that doesn't represent what the sources actually say.
Also, as the previous replies mention: this is a content dispute, not a policy change, so this conversation would be better located at Talk:Horse. Chaotic Enby (talk) 14:18, 12 May 2023 (UTC)
It is a 'content dispute' only in as much as the OP is arguing in favour of violating core Wikipedia policy regarding specific content. People who don't want to read about the evolutionary history of species are free to not look at Wikipedia articles on such species, but if they chose to read them, they can expect such articles to concur with the overwhelming scientific consensus on the subject. This clearly isn't open to negotiation on the talk page of the article concerned. There isn't any 'conversation' to be had. AndyTheGrump (talk) 02:16, 13 May 2023 (UTC)
I'd agree with that - I was mostly being polite, insofar as even if there weren't such policies or consensus, this should be at Talk:Horse rather than Wikipedia:Village pump (policy) of all things! But yeah, the conversation about hiding evolutionary history to not displease creationists shouldn't really be had to begin with. The only part of this discussion that is reasonable is whether Eohippus should be mentioned at Horse or at Equidae (or both!), but I don't think adding it to the Equidae lead even requires a conversation (interestingly, the first equid isn't even mentioned on that page!) I'll go and do it. Chaotic Enby (talk) 12:52, 13 May 2023 (UTC)
Added Eohippus to the Equidae lead. The body should probably get a rewrite, considering it mentions Hyracotherium instead which isn't considered an equid anymore (and isn't very up-to-date), but that's getting completely out of the scope of this... argument? I think we can call it closed, if anyone with a closing ability comes here. Chaotic Enby (talk) 13:03, 13 May 2023 (UTC)
There aren't "two sides" to this. There's facts and there's fairy tales. Encyclopedias deal in facts. --User:Khajidha (talk) (contributions) 16:12, 13 May 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
These entire two discussions are closed as being started by a blocked user evading a block --Jayron32 17:13, 16 May 2023 (UTC)
The following discussion has been closed. Please do not modify it.

Add public on‑chain activity to WP:RS

Consensus seems entirely clear that we aren't going to permit the use of primary blockchain data in the manner proposed, since it fundamentally violates core policies. The refusal of the OP to comply with requests to stop posting while logged out in regard to a subject where they have a clear CoI demonstrates a further unwillingness to actually listen. To be blunt, if the media doesn't report on this, neither will we. AndyTheGrump (talk) 14:18, 14 May 2023 (UTC)
The following discussion has been closed. Please do not modify it.


Hello,

I wanted to bring updates to a cryptocurrency software article using sources from on‑chain data since no newspaper talks about it. And they were reverted in the name that blockchain activity isn’t part of WP:RS.
This seems odd, because at justice on trials, blockchain data can be used as legitimate trusted proofs to tell what happened but not on Wikipedia. The only difference is the technical nature which requires some knowledge to read but in the end, there’s no error possible so it might even be more trustworthy.

Ideally though, I recognize we shouldn’t be using random third party blockchain explorer websites, but that blockchain data should have it’s own Template like ɪꜱʙɴ in order to cite logged events ; transactions ; and/or addresses. In the case of Ethereum like blockchains, the recommended trusted way to access the p2p data is through a full archival node. 2A01:E0A:401:A7C0:8474:A152:73C7:23E (talk) 22:16, 12 May 2023 (UTC)

I can think of very few circumstances where it would be appropriate to discuss "logged events ; transactions ; and/or addresses" in an article at all. Certainly not without the specific data also being discussed in secondary published reliable sources. Using blockchain data in the manner you propose would appear to violate WP:OR and could have serious WP:BLP implications. AndyTheGrump (talk) 22:32, 12 May 2023 (UTC)
This would probably be a WP:PRIMARY source in all cases, and therefore super rarely appropriate to mention at all. "No newspaper talks about it" is a big shiny red flag saying that it probably shouldn't be on Wikipedia. casualdejekyll 22:45, 12 May 2023 (UTC)
In the example we tried to edit, the global assumption of the press is that the software stopped working since the original developer team who created it disbanded and the original website and forums were sized (the fact they all left and the original off‑chain assets ceased to exists and that most almost all the userbase stopped using it is all true). This Point of vue is completely understandable since journalists tend to not be persons with a strong technical background, but that’s ignoring hosting shifted to the blockchain itself as a backup a few months before those events using alternative systems like the Ethereum Name System instead of the ᴅɴꜱ : I used the registration records as a source to prove the link to the official website.
It’s also ignoring what is truly a ᴅᴀᴏ so that in the end it’s the userbase who decide which updates are applied and which persons are paid to maintain the project much like shareholders on the stock exchange. I used the logged events to show that updates were still pushed contrary to the article which states the latest version dates from 2021 (that 2021 claim itself in addition to being wrong is unsourced but it was reverted anyway despite the obvious fact that they are not always newspapers when a new version of a software is published) as well as transactions to details the voting process which took place and the address of the ᴅᴀᴏ.
Think as falling from a cliff and not being found for 2 months : for this reason, your Wikipedia article is updated to declare you passed away in August 2022 using the news that states you fell from a cliff and that your property was even auctioned off. But while a major failure, you’re in reality still alive : you try to alert the press, but your relatives now refuse to talk about you in public and nobody has an interest in someone who is considered dead. In addition to your reputation (News article from peoples that declare they successed you in your work unaware you’re alive), that article is harmful to you because the providers who still work with you constantly require you to prove you are still alive when reading it (that part is true for us). So you end up editing your own Wikipedia article despite WP:COI by adding historical references from your own blockchain activity. But your own actions are declared to not be part of WP:RS and to be WO:OR. After 2 reverts, you can witness your own article being protected from vandalism in the state that declares you dead despite the WP:BLP#Legal persons and groups. With the latest news talking about you dating from your accident, at that point, you would quite frankly prefer to have that article that says rubbish about being deleted than corrected.
sounds like a Monthy Python sketch ? But that’s exactly what is happening to ᴜꜱ. 2A01:E0A:401:A7C0:8474:A152:73C7:23E (talk) 07:39, 13 May 2023 (UTC)
As a PRIMARY source that's almost always going to fail WP:WEIGHT. Unless you can find a reliable independant seconadary source supporting such material it's probably going to be excluded.
If you believe a new template is needed you may request its creation at WP:RT 74.73.224.126 (talk) 22:55, 12 May 2023 (UTC)
I tend to disagree with this in the case of computer science : an article that says something can’t happen (hence scientifically wrong) should be able to be corrected by a source that demonstrates it can happen (for example proving a cipher system can be deciphered and was multiple time deciphered). 2A01:E0A:401:A7C0:8474:A152:73C7:23E (talk) 08:25, 13 May 2023 (UTC)
Your analogy is flawed, but even so, if reliable, secondary sources say that you are dead, Wikipedia doesnt have a choice but to accept that.
To modify your analogy, what if you did die, and someone stole your identity and began to use that to drain your bank accounts. Bank transactions would show you as alive, and so long as the impostor didn't need to directly meet anyone, the impostor could pretend to be you. News sources may report you as alive, and even though someone had a photo of your smashed corpse at the foot of the cliff, that probably wouldn't convince anyone, since everyone would think that you are alive, and say that it was faked. You could try to stop them, but since you're dead, you can't exactly do anything about it.
How about saying that you actually want to modify WP:NOR, WP:PRIMARY and WP:RS to make a special case for using blockchain data? That is what you would really need, but I can assure you that it has a snowball's chance in hell of succeeding. Mako001 (C)  (T)  🇺🇦 09:11, 13 May 2023 (UTC)
Wrong and absurd!
In the case of blockchain there s can be no impersonation. There are many peoples who claim to be Satoshi Nakamoto, and Wikipedia has even individual articles about such persons who proved to be Satoshi Nakamoto in court, but none of them control his funds. Here it is the reverse and there can be no key theft since the ᴅᴀᴏ is an immutable computer program acting on its own.
If the Bitcoins of Satoshi Nakamoto are moved from their 11 years old addresses and sold on Bitcoin, then those transactions records should be used as a proof he is alive Argument from silence.
About modifying WP:NOR, WP:PRIMARY and WP:RS, that s more efforts than just changing the status of the software and modifying the website domain to its original backup on Ethereum, hence why I prefer to request it here. 2A01:E0A:401:A7C0:C5CB:DD1:D5D9:D583 (talk) 10:21, 13 May 2023 (UTC)
Please stop editing while logged out - doing so to avoid scrutiny while having a clear conflict of interest is a violation of Wikipedia policy. [2][3] AndyTheGrump (talk) 14:24, 13 May 2023 (UTC)
Not the scrunity of Wikipedia but scrunity from the peoples looking at the article I m talking about. This section is watched by more than 1000 users.
And otherwise we are aware of WP:COI. Thus we don t try to edit what is said about us like the fact the illegal activity was a minor part of the use. The aim is just to correct the fact we ceased to exists. 15:49, 13 May 2023 (UTC) — Preceding unsigned comment added by 37.174.43.101 (talk)
Please stop saying "we". Wikipedia articles and discussions are supposed to be edited by individual people who are responsible for what is said, not "we"s. Phil Bridger (talk) 16:35, 13 May 2023 (UTC)
Simply because I’m not the only person at the same who tried to fix we stopped existing. 2A01:E0A:401:A7C0:8474:A152:73C7:23E (talk) 07:34, 14 May 2023 (UTC)
If the Bitcoins of Satoshi Nakamoto are moved ... then those transactions records should be used as a proof he is alive — or evidence that someone else has the password / private key to those Bitcoins, which is a plausible scenario. Digital inheritance is a thing. Passwords can be held in escrow. Mitch Ames (talk) 04:00, 14 May 2023 (UTC)
If that was the case, it would had been done long before. More seriously, almost all courts can sentence you for using your blockchain activity as the only source of real proof. See the courts documents of https://www.reuters.com/article/usa-silkroad-agent-idUSL1N1162JJ20150831 for an example. Also, I don’t see why an official registration document can be used as a WP:RS source but not an official equivalent log on the blockchain. 2A01:E0A:401:A7C0:6CB7:4A51:17D:B464 (talk) 07:06, 14 May 2023 (UTC)
I don't think that requesting for the creation of the template is a good thing before this is established or not as a WP:RS, it would be a bit premature to create a template just for the consensus to end up being that it shouldn't be used as a source. Chaotic Enby (talk) 05:18, 14 May 2023 (UTC)
There is very little chance that a record on Blockchain would ever be considered an RS. There's so incredibly small chances that something coming from this, that isn't mentioned elsewhere in other RS would be suitable for inclusion in an encyclopedia, and would likely fall foul of RS. I'd recommend closing this discussion as it's clear that it's just starting an argument. I would also recommend logging into any accounts you have, and if this is multiple people talking (the use of the word "we") to not edit Wikipedia at all, accounts and IPs should only ever be edited by one person. (I get that IP addresses work different, but I get the feeling I'm talking to someone who is representing a series of people). Lee Vilenski (talk • contribs) 11:33, 14 May 2023 (UTC)
You’re indeed talking to an ɪᴘ address using a fixed ɪᴘᴠ6 prefix representing a group of people but the edits that were reverted were made by a group of people. I now recognize the only time the press talked about us is when all off chain assets were sized which is why there’s no Wikipedia article before and our notoriety remains small. Though such arguments here come against the generally admitted reasoning in the blockchain field : so I invited a few more people not linked to the software who will be able to explain better than me. Meanwhile, please leave this question open for the following 3 days.
Otherwise, an example website registration using a web proxy (everything is verifiable independently on the command‑line using your own full Ethereum archival node). According to the registration, the manager is 0x5efda50f22d34F262c29268506C5Fa42cB56A1Ce which is linked by Etherscan as the ᴅᴀᴏ and also included in the ᴏꜰᴀᴄ’s blockchain list under that purpose. But it’s not only someone who transferred control as the program stored at 0x5efda50f22d34F262c29268506C5Fa42cB56A1Ce indeed used it’s manager role to update it in https://etherscan.io/tx/0x07194973cfc042c452eb7370ded8e953533a202ffa842ddfa24e41cc15f81862/advanced#eventlog (use eth_getTransactionReceipt on your full node on 0x07194973cfc042c452eb7370ded8e953533a202ffa842ddfa24e41cc15f81862 for an independent confirmation). Thus https://app.ens.domains/tornadocash.eth?tab=more is indeed the live website of 0x5efda50f22d34F262c29268506C5Fa42cB56A1Ce. And using such on‑chain proof as a sole source, this is the reason 0x5efda50f22d34F262c29268506C5Fa42cB56A1Ce was added later by the OFAC in the list whereas it wasn’t included initially (and is also why https://etherscan.io/accounts/label/ofac-sanctions-lists by being not up to date contains addresses in the same category but not 0x5efda50f22d34F262c29268506C5Fa42cB56A1Ce). 2A01:E0A:401:A7C0:8474:A152:73C7:23E (talk) 14:03, 14 May 2023 (UTC)

How to source the preview release date when using Template:Infobox software?

The problem is it s rare for a news article from third party sources to be published for beta or Alpha releases. Some large software like Windows do receive media coverage but other ones like Mozilla Thunderbird or Firefox have their release date self sourced using links to downloadable versions for the simple reason it happens every day. And indeed, a quick look to Special:WhatLinksHere/Template:Infobox software give many examples not sourced at all.

In my case, I edited an article using the backup link to the official newer release (WP:SELFSOURCE as reference) and it was reverted 2 times (by 2 differents users) to the itself previous completely unsourced release date in the name of WP:OR and WP:RS. That I can use them only as WP:SECONDARY and I need to find reliable third party WP:PRIMARY.

What s the proper way to achieve this? Or if using reliable secondary third party sources is really needed even in that case, is a large cleanup across thousands pages needed? 37.170.88.2 (talk) 11:26, 16 May 2023 (UTC)

WP:ABOUTSELF seems to me to say that it is valid to source a release date to the company itself; "Self-published and questionable sources may be used as sources of information about themselves, usually in articles about themselves or their activities...so long as:the material is neither unduly self-serving nor an exceptional claim; it does not involve claims about third parties; it does not involve claims about events not directly related to the source; there is no reasonable doubt as to its authenticity; and the article is not based primarily on such sources." All of that applies to a company's own claims about their own release dates; it is not exceptional, does not involve claims about third parties, it is directly about the source, there is no doubt as to the authenticity, and it's only used for a single date; thus the article isn't really relying solely on such sources. You should be fine using the company who published the game as a source there, and anyone who says you can't isn't aware of Wikipedia's guidance on this. --Jayron32 11:37, 16 May 2023 (UTC)
can such thing also apply to the official address of the website? For example, can the old unused official Twitter account which is referred by reliable third party sources be used to reflect a longtime non updated change on the article? Given the newer Twitter account that referred the same newer address was deleted by the fired angry community manager.
I would understand it should be left as is if updating the website to the backup address is not possible. 37.170.88.2 (talk) 12:46, 16 May 2023 (UTC)
If the Twitter account is verified as official, and it makes a statement which covers something banal and uncontroversial and simple, it's probably okay, though of course the devil is in the details. The "deleted by the fired angry community manager." does not, however, sound to me like a likely positive sign for usability, however. Given that this is apparently some source of controversy, I would find some source that was not so ephemeral that a disgruntled employee could screw it up. --Jayron32 15:24, 16 May 2023 (UTC)
@Jayron32 This IP is Ytrezq evading their block, see Wikipedia talk:Sockpuppet investigations/Ytrezq. 192.76.8.85 (talk) 17:00, 16 May 2023 (UTC)
  • I’m sure you are aware of this, but… one potential problem with ABOUTSELF announcements of pending release dates is that they are notorious for being inaccurate estimates. This is especially true when the expected release is scheduled for several months from the initial announcement (delays often occur). Blueboar (talk) 15:45, 16 May 2023 (UTC)
I m mainly talking about using links to past published releases. Not necessarily announcements. 37.170.88.2 (talk) 16:47, 16 May 2023 (UTC)

Deleting to make way for accepting a draft?

Didn't really need a policy change, and once the editor offered a little more detail on what they wanted, a history merge was identified as a suitable solution. It was duly implemented, and everyone seems happy with the outcome. (non-admin closure) Mako001 (C)  (T)  🇺🇦 08:44, 13 May 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Hi there. I created a draft article, and a few other editors and I worked on it before submitting it for review. While our draft was undergoing review, someone created the article in mainspace. The reviewer procedurally declined our draft for that reason, but said our version was more detailed. The reviewer would like to know, admittedly at my request, whether it would be permissible to delete the mainspace article to make way for accepting the draft? This would be on the grounds that the article shouldn't have been created when the draft was already submitted. I know it's a small issue, but I'd greatly appreciate it. Thanks! Davey2116 (talk) 15:34, 12 May 2023 (UTC)

For reference, the article is Kenvue, and the draft is at Draft:Kenvue. Davey2116 (talk) 15:34, 12 May 2023 (UTC)
If an article already exists, you can simply edit/rewrite it to include the information from your draft. No need for deletion and then recreation. Blueboar (talk) 15:42, 12 May 2023 (UTC)
I understand I can do that, but would the deletion/recreation by the reviewer be against some policy? I would prefer to keep the version history of our draft. Davey2116 (talk) 16:19, 12 May 2023 (UTC)
@Davey2116, an admin would need to do it, and they'd need a valid reason under our deletion policy. What rationale are you offering? "Our draft was first and it's better" is probably not going to work. 199.208.172.35 (talk) 16:44, 12 May 2023 (UTC)
I have done a histmerge. -- King of ♥ ♦ ♣ ♠ 16:51, 12 May 2023 (UTC)
Thank you! I was unaware this was called a histmerge, this is exactly the solution I was looking for. Davey2116 (talk) 16:59, 12 May 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Make Wikipedia:Verifiable but not false a guideline

There is no guideline that states that incorrect information should be removed. Wikipedia:Verifiable but not false is an explanatory essay. Some of us have been treating it (explicitly or implicitly) as if it were a guideline and removing or correcting incorrect information but in the absence of an actual policy or guideline it is merely an exercise of editorial judgment. (Although WP:BLP talks about "contentious" information, which is defined as "challenged or likely to be challenged", which is generally considered to include erroneous material.) This is not an RfC; as a preliminary I am surveying opinions on whether a proposal to elevate it to guideline status would receive support. Hawkeye7 (discuss) 00:04, 13 April 2023 (UTC)

The essay feels too redundant to be a guideline. I had not read it before now, and most of the principles feel like those that would naturally stem from existing guidelines and policies. For example, it is already uncool to make claims like those given in the essay (e.g. "All Americans think Hitler was evil") because those claims cannot be reliably sourced. The other principles are little more than restatements of WP:DUE, WP:NPOV, or WP:RSAGE. Orange Suede Sofa (talk) 00:30, 13 April 2023 (UTC)
While they may seem to stem naturally, the whole point is that we have no commitment to accuracy or correctness. WP:RSAGE is a case in point; we ignore it at MILHIST in favour of WP:FALSE. That is because of the problem of errors being propagated from one (otherwise) reliable source to the next. Hawkeye7 (discuss) 03:24, 13 April 2023 (UTC)
If this is elevated to a guideline, then what will change at MILHIST? If the problem is how an editor (or project) chooses to handle widely accepted guidelines, then address that directly. If it is not a problem, then we're all good here. If an existing guideline is a problem, then address that. BTW, with your note about no commitment to accuracy or correctness, I think you're getting at a much deeper philosophical problem that the existing policies and guidelines address: can we ever know what is accurate or correct? If not, we need a way to leverage the world's existing body of information to arrive at a largely consensual representation of a given subject, and I continue to believe that the existing policies and guidelines do that to the best of our ability. Orange Suede Sofa (talk) 22:45, 13 April 2023 (UTC)
What would change is that instead of edits being removed on the grounds that they are unsourced, undue or some other excuse, it will be explicitly stated that they are being removed because they are factually incorrect. Hawkeye7 (discuss) 02:02, 14 April 2023 (UTC)
How would an uninvolved editor be able to verify that the statement is factually incorrect? If there are sources that indicate that, why couldn't normal editorial judgment be followed? Orange Suede Sofa (talk) 02:14, 14 April 2023 (UTC)
This essay is not very well written. It's far too confusing as it stands to be elevated to be a guideline. I'd focus on improving the essay first. Jahaza (talk) 00:36, 13 April 2023 (UTC)
Let me know what you find confusing and what you think could be clarified on the talk page and I'll have a go at it. Hawkeye7 (discuss) 03:24, 13 April 2023 (UTC)
I do not think it provides anything not already in policies and guidelines. Certainly claims in sources can be removed if later sources contradict them or if we have information they are false. For example, that reliable sources show that some Americans adore Hitler disproves the claim that all Americans consider him to be evil. We could also counter with a source that said most Americans held this view.
This only becomes an issue in my experience when tendentious editors wiki-lawyer to include information they know to be false. For example, a secondary source may misstate what was said in a primary source. The solution is for editors to discuss in good faith. But if someone is determined to push their POV, more rules won't stop them. In fact, it can give them ammunition for wiki-lawyering.
TFD (talk) 00:56, 13 April 2023 (UTC)
The argument in these cases tends to be that while it is false, it meets our criteria for inclusion based upon widespread use in reliable sources. Hawkeye7 (discuss) 03:24, 13 April 2023 (UTC)
It would help to see a good example of an article that has information known to be false (not merely controversial) yet editors permit the information to stand. I am familiar with some BLP cases where someone claiming to be the subject says "my age is wrong" (or whatever) contrary to all available sources, but even those cases have an established path for resolution. Orange Suede Sofa (talk) 23:01, 13 April 2023 (UTC)
Yes, I have handled a case just like this. An athlete approached me and asked me to fix the incorrect date of birth on her article. To her, this was a big issue, because it was tantamount to an accusation of cheating. She showed me her passport and driver's licence as proof. Unfortunately, this ran afoul of WP:BLP, particularly WP:BLPPRIMARY, which says you are not allowed to use such sources. The origin of the error was easy enough to find: it was a simple typo, but one that had been spread widely by otherwise reliable sources that relied on the original erroneous but usually authoritative one. So what I did was invoke WP:IAR and elevate WP:FALSE over WP:BLP on the grounds that the latter does not improve the encyclopedia. I simply located a site that had the correct birth date and used that as the reference instead. Hawkeye7 (discuss) 01:18, 14 April 2023 (UTC)
This is super frustrating, yeah. Recent example I ran into was The Comfortable Chair -- pretty interesting band. (What's there in the article is a start, needs someone to go digging for the print sources.) Rob Fitzpatrick of The Guardian says Jim Morrison discovered them; he's a respected journalist and seems to be citing from aforementioned print sources. However, User:Midnight12 on the talk page, who says they are a member of the band, says this isn't true. Their contribs suggest that, at the very least, they're not a random drive-by poster. But obviously I have no way of actually verifying that they are who they say they are, or that they just weren't aware at the time. The best I could do was throw a "reportedly" into the copy since, if nothing else, it was reported. But obviously that's kind of a copout. Gnomingstuff (talk) 18:46, 14 April 2023 (UTC)
As to an article with false information that has been allowed to stand, consider Albert Kesselring, footnote 1. His birth date. Somewhere along the line, a typo crept into a source, and this erroneous information was repeated by several otherwise reliable sources. (The joke among military historians is that history doesn't repeat itself nearly as often as historians do.) A long debate followed with other editors who felt strongly that the article should acknowledge both the correct and the incorrect dates since WP:FALSE is only an essay and we should adopt a neutral point of view on matters of fact. I did not believe that having two birth dates, one which we knew to be incorrect, would benefit the readers in any way. The footnote represents the resulting compromise. "Albrecht" as a first name derives from Kenneth Macksey, who erroneously believed that it was the German form of "Albert". Again, the error has been propagated to other sources. Kirsten von Lingen wrote that this was "plain wrong", but another editor felt that saying so was non-neutral, so that comment was removed. Hawkeye7 (discuss) 01:18, 14 April 2023 (UTC)
I had a related experience in a death discussion about about Marilyn Monroe's sister Berniece Baker Miracle. As an aside, the Monroe page itself is a remarkable and featured work; related pages get special scrutiny, and rightly so. Based on less-than-reliable sources the BLP subject had died, but the only source we could present was Find-a-grave (with several photographs of her gravestone). This went on for some months and put Wikipedia in the awkward but never unique situation of hosting outdated, incorrect and potentially damaging information about a BLP. BusterD (talk) 08:57, 18 April 2023 (UTC)
Editorial discretion along current guidelines seems better for such cases. Any guideline about truth is bait for RGW-style arguments, and we say verifiability not truth precisely to avoid those pointless quagmires. We can use editorial discretion to value more recent sources over older ones because they are more likely to be in line with what is currently accepted as correct knowledge, but that doesn't mean what we have is definitely true. CMD (talk) 03:44, 13 April 2023 (UTC)
"That statement has been viewed as claiming Wikipedia is, somehow, not concerned with truth." -- Is there really a critical mass of people saying this in good faith? If not, what's the issue? Gnomingstuff (talk) 07:46, 13 April 2023 (UTC)
A very, very, very good essay. Minor grips over wording, but it's vital. For example, recently, I found one book that said Steve Wozniak used 45 chips on a circuit board; another book said 42 (a magazine said 44...) Then I found a Woz interview where he says: I got it down to 42, but it went back to 45 before it ran well. I could have just flipped a coin and picked a number, but now the discrepancy has been resolved.
Secondary sources routinely publish errors; citogenesis proves that. We've run into peer-reviewed papers and scholarly books that saw uncited crap on Wikipedia, and repeated it as fact! The whole point of WP:NOTTRUTH was to dumb-down WP:OR so even fringe-pushers can understand it. But we have a huge audience, and it would be irresponsible to punt the accuracy question to our sources, without exercising nuanced editorial judgment. Bad-faith editors can misuse WP:FALSE, but they can misuse anything. Tracking down and reconciling potential factual mistakes in source is what any responsible, thoughtful editor "should" do, and "should's" are what guidelines are for. DFlhb (talk) 01:07, 14 April 2023 (UTC)
Right now we basically have three categories of this type of thing. Policies and guidelines (which in shorthand are sort of "rules") and then thousands of essays which anybody can get lost in and usually remain obscure unless they have a short catchy name to link to within sentences. We need another category of highly exclusive highly vetted pages. Some will be guiding principles, too general to be specifically invoked in disputes (as guidelines and policies are) . I think that this would contain things like 5 Pillars and this proposal. The other group would be highly vetted explanatory essays that describe how Wikipedia is and operates. North8000 (talk) 19:33, 14 April 2023 (UTC)
I agree there needs to be a level between "guideline" and "essay", because "essay" at this point can either mean "this is so frequently referenced it's effectively a guideline" (e.g. WP:BLUESKY) or it can mean "this is one editor's opinion" (e.g. Wikipedia:Avoid negative claims) or it can mean anything in between (e.g. WP:POSA, which by the very fact it can find so many examples clearly has not achieved wiki-wide consensus). Loki (talk) 23:51, 14 April 2023 (UTC)
Good points, but they point to more fundamental changes needed. Your essay is a good start in some of those areas. In cases where objective accuracy exists, we need to modify folklore to say that wp:ver is a means to that end, not the end. The other folklore that we need to get rid of is that editorial judgement (within the guardrails) (e.g. to resolve dilemmas like you describe) is illegitimate or banned in Wikipedia. Finally we need to establish that source reliability is context-specific, that it relates to objectivity and expertise with respect to the text which cited it. Sincerely, North8000 (talk) 13:52, 14 April 2023 (UTC)
Someone asked above for examples of articles where information was verifiable but false; I can provide a couple:
  • A source says Fallon Fox had surgery at "Bangkok National Hospital", but if you look for more information about that hospital, most of what you'll find is about Fox (parroting that initial source) or else unreliable miscellany, because AFAICT Bangkok National Hospital doesn't exist: the original source apparently made a mistaken assumption about what the full name of the national hospital in Bangkok that's called "BNH" is — the hospital is actually named Bangkok Nursing Home hospital. In that case, after another editor raised the issue on talk, I changed the article to just say "a hospital in Bangkok" since this is verifiable and the exact hospital name is unimportant trivia, but no reliable sources have the correct name. (Possibly even the detail that Fox had surgery in Thailand is removable trivia, but that's a separate issue.)
  • Qasem Soleimani's article faced at least two such issues: some reliable sources said he was the first person in Iran honored with a multi-city funeral (but this is false, since other notable people were previously honored with multi-city funerals as discussed in other RS, but these other RS predate and weren't about Soleimani, so technically might be WP:SYNTH), so editorial discretion was used to drop that claim. And one US intelligence source said he was born in Qoms province, but other RS say he was born in Kerman province; he lived his early life in Kerman, and when he was buried in his birthplace, that was Kerman province, so I downgraded "Qoms" to a footnote, but the idea that he might've been born in Qoms still made its way citogenetically into some later news articles, so it might be better to just drop the wrong information.
I sympathize with the idea that it would be useful to have a note somewhere explicitly stating that Wikipedia strives to be accurate. But I share the concern expressed above that making an explicit guideline or policy besides WP:V would encourage edit wars ("sure, RS all say Trump / Xi / Kim Jong Un / Qanon / etc did X, but I know it's not true so I'm removing it per NOTFALSE!!"). -sche (talk) 22:22, 15 April 2023 (UTC)
I understand this concern, but the point is that in removing information simply because it is false, you are indeed removing it per WP:NOTFALSE! This is acting although WP:NOTFALSE already has guideline status. Hawkeye7 (discuss) 19:32, 16 April 2023 (UTC)
It's permissible to remove information simply because it's false, and if we have a rule that says otherwise, then that rule needs fixing.
About a dozen years ago I fought tooth and nail to get "verifiability, not truth" removed from policy because it's important that we try to tell the truth. I also think that we block and ban people who lie. Oh sure, we have all these fig leaves about consensus and pretexts involving disruptive behaviour and advocacy and POV-pushing, but actually, underneath it all, there's a real distinction between people who're here to educate and inform on the one hand, and people who're here to propagandise, advertise and misinform on the other.—S Marshall T/C 08:10, 17 April 2023 (UTC)
The problem is that one person's "truth" may be another person's "lie". How then are we to determine that content that someone wants to remove because they say it is false is indeed false? If there is no citation to a reliable source, such content can be removed. But, if we allow someone to remove content that is supported by a citation to a reliable source because they say it is false, how do we know that it is indeed false, and not just a mistaken opinion of the editor who wants the content removed? That is why I supported "verifiability, not truth", because, all too often, "truth" is in the eye of the beholder. Donald Albury 13:18, 17 April 2023 (UTC)
Oppose doing so. It's a fine essay. I see no reason it needs to be a guideline. --Jayron32 14:18, 17 April 2023 (UTC)
Oppose. "Verifiability, not truth" is a powerful statement. It's the secret to avoiding a constant high-temperature flame war and has the not inconsiderable benefit of actually being better for favoring true content over false content, and honestly should be placed back on WP:V in big bold letters. Anyway, given that Wikipedia:Verifiability, not truth is technically only an essay at the moment, it only seems reasonable that this kind of essay have the same status. Obviously, the truth is important, but the kind of stance suggested by NOTFALSE just gives a big bludgeon to the worst cranks & POV-peddlers who want to argue about whether their fringe theory is true or not. VNT refocuses the debate onto "fine, whatever, let's say it's true, who's actually published it in the mainstream. Nobody? I guess we can't have that on Wikipedia yet." The actually good faith editors interested in truth can work fine under both a VNT and a NOTFALSE system, but the fringe theorists tend to be deterred better by VNT and encouraged by something like NOTFALSE. SnowFire (talk) 05:49, 18 April 2023 (UTC)
VNT was deliberately removed from wp:ver after a gigantic RFC. Actually two gigantic RFC's with the same result. North8000 (talk) 19:23, 18 April 2023 (UTC)
I'm familiar, yes. It was a mistake. SnowFire (talk) 04:04, 19 April 2023 (UTC)
Oppose. SnowFire says it better than I could. "True" and "False" are both loaded and subjective terms that get in the way of writing a verifiable encyclopaedia. Thryduulf (talk) 10:42, 18 April 2023 (UTC)
Oppose. Don't try to ground rationales in underlying "truth". It's a problem. Truthwarriors often know full well that the article matches the sources, they want to push their POV in articles by ranting that the sources are biased or wrong. I have successfully brought peace to some of these hellholes by firmly explaining Wikipedia policy requires our content to be an accurate summary of what Reliable Sources say, explaining that they need to find sources to back up their claims, explaining that their truth-arguments simply do not work here, explaining that under policy we are required to ignore their truth-arguments.
We have abundant methods for keeping bad content out. One often noted method is simple editorial discretion to leave out anything we consider not useful to the reader. An often overlooked point is that a "generally reliable" source does not imply reliability for every individual claim in that source. Even the best sources apply a lower standard of care to minor incidental details, and available evidence can be considered when evaluating the care applied on that specific point. Something that appears to be a typo or simple mistake fails our Reliability standard, regardless of whether it's "true". Alsee (talk) 07:28, 21 April 2023 (UTC)
blocked user evading block--Jayron32 17:14, 16 May 2023 (UTC)
The following discussion has been closed. Please do not modify it.
See also WP:Village pump (policy)#Add_public_on‑chain_activity_to_WP:RS with code is law for an example, where self mathematical verifibility when linked to WP:OR means articles should remain provably wrong (some statements made by the article can be quicly proved wrong but use of the source fall in WP:OR because being published on the ledger doesn t equal what is published in a book or on the web) . 37.170.88.2 (talk) 13:15, 16 May 2023 (UTC)
This makes no more sense than when you wrote similar gibberish in that now closed discussion. --Jayron32 16:43, 16 May 2023 (UTC)
  • This is where “Verifiability does not guarantee inclusion” is so useful. It may take some discussion to achieve consensus, but we absolutely CAN omit verifiable information that we agree is false. What we can NOT do is replace that false information with unverifiable information we think is true. Blueboar (talk) 14:31, 16 May 2023 (UTC)

Discussion

There is no Nutshell summary. Without that, I'd oppose as well. A quick reading gave me the impression, the whole essay was a bit vague and vague policies are not what we want.Paradise Chronicle (talk) 18:04, 4 May 2023 (UTC)

Maintenance templates

The process for creating a maintenance template is too easy. It creates situations where people can say that information is unreliable, when it is reliable without proof. That is especially problematic with pages that have less visitors that will edit.

I therefore propose that any editor that wants to create a template has to write out a justification that explains why he or she is right. That means provability, they for example would have to point out exactly where the articles are not citing correctly and why they are not cited correctly. That may mean having to read a source to judge if what the article says is provable.

Then after that editor is finished, he or she would have to show their work to an administrator who would have to approve and thoroughly explain why they approve. The same process should be done for the removal of a maintenance request. Orlando Davis (talk) 23:39, 11 May 2023 (UTC)

You would do well to learn a little more about how Wikipedia works before proposing changes in policy. Admins have no authority to make rulings regarding content. AndyTheGrump (talk) 23:44, 11 May 2023 (UTC)
If editors are putting Template:Advert on the article you contributed to, it's probably because you're adding content that sounds promotional or celebratory. The article should just tell us about the person's life. It shouldn't tell us how talented or successful they are. In the future, I suggest using the articles for creation process so someone else can review it before it becomes an article. Also, don't forgot that you don't own any article on Wikipedia. Anyone can add anything to it as long as they follow Wikipedia policies. Thebiguglyalien (talk) 23:59, 11 May 2023 (UTC)
I didn't create this one:
Sergio Oliva Orlando Davis (talk) 00:17, 12 May 2023 (UTC)
Or this one:
Clone trooper
There are many more. I think it's bringing down the quality of Wikipedia, the lack of checks to make sure content is verifiable. Orlando Davis (talk) 00:20, 12 May 2023 (UTC)
It's also not aesthetically pleasing. You wouldn't see that in the Encyclopedia Britannica. Orlando Davis (talk) 00:22, 12 May 2023 (UTC)
This is an old article, but it highlights some problems that I think have gotten worse.
http://edition.cnn.com/2007/TECH/11/02/perils.wikipedia/ Orlando Davis (talk) 00:24, 12 May 2023 (UTC)
And Sergio Oliva looks like it has problems in need of maintenance. I checked just one sentence and its reference: As a teenager, after only a year of training, Sergio was able to perform clean & jerks in excess of 400 pounds. Well, there's a boastful statement, and the source given, https://wikiz.com/wiki/Sergio_Oliva , is a mirror of Wikipedia, so its a circular reference. So yes, it has reference failure. Does it have enyclopedic tone failures? 'He then ran at top speed until he was safely inside the American consulate. Arriving breathlessly, he demanded and received political asylum. – so, yes. It is indeed an article that editors should be encouraged to improve. Britannica does not seek such improvement; we do. -- Nat Gertler (talk) 01:23, 12 May 2023 (UTC)
Hello Nat,
I do love your work. What about this article? It is one I am creating. I was told by 2 editors that it is not neutral, encyclopedic, and that it sounds like an advertisement. Do you agree?
Draft:Guillermo Rojas Bazan
I appreciate your feedback. Orlando Davis (talk) 01:54, 12 May 2023 (UTC)
Here is another one I created that I was told sounds like an advertisement:
Cherry Hill (model engineer)
What do you think. I appreciate your feedback. I read the peanuts comic as a kid. It is really great! I got a lot of laughs. Orlando Davis (talk) 02:20, 12 May 2023 (UTC)
Cherry Hill: "She is recognized worldwide among model engineers for the quality of her work." "During her 60-year career, Hill built nearly 20 super-detailed scale models of steam vehicles, including intricate Victorian models, which each took her approximately 7,000 hours to make. These models are remarkable because of their perfectionism and because the engines are completely operational."
Yep, that's "advert" speak, or more in WP-terms, WP:PROMO and WP:FLOWERY. Gråbergs Gråa Sång (talk) 07:16, 12 May 2023 (UTC)
Well, maybe it should change. If someone is stating facts and those facts are verifiable. Then that should be good enough. Even if verifying takes some effort like going to a library, or making phone calls. The neutral tone is stuff nobody cares about. You read an encyclopedia because you want to learn facts. Verifiability is the only thing that should matter.
There has been chat on Wikipedia that women engineers are not included due to misogyny. I think this article should have people trying to build it instead of tear it down. Orlando Davis (talk) 10:53, 12 May 2023 (UTC)
You can pretty much be an obstacle to the truth by setting up bureaucracy that makes it difficult to tell it. Orlando Davis (talk) 10:58, 12 May 2023 (UTC)
@Orlando Davis:, you focus on verifiability, so you should easily be able to prove The neutral tone is stuff nobody cares about. that received less comment than such as drastic statement really should. Given the vast number of sources talking about the neutrality, comparative neutrality, and lack of neutrality of Wikipedia I'm interest in seeing the rebuttal. Nosebagbear (talk) 01:21, 14 May 2023 (UTC)
The issues quoted are of neutrality. not advertising. As is often the case, it is wrong to describe them as "advertising". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:59, 14 May 2023 (UTC)
Presumably you are referring to addition and removal of maintenance templates not their creation, or at least that's what I infer.
Bluntly this proposal is a nonstarter, if you want to try and workshop something from your ideas at WP:VPI you are welcome to, but I don't see that as likely to produce anything actionable either.
Sysops have never had any special power over content and that's not going to change. Nor would the bureaucracy of sysop approval be workable in any case. If you believe a maintenance template was inappropriately added or notice that an issue a template refers to has been resolved you or any other editor in good standing can remove it. If the issue hasn't been resolved then maybe you should try to resolve the issue.
The templates do not bring down the quality of Wikipedia rather their purpose is to call attention to existing issues. The fact that we are tracking unsourced articles is a good thing, and believe it or not there are quite a few people who still work the backlog.
De gustibus non est disputandum, so I won't get too much into aesthetics. Some people don't like the size or prominence but part of what we are attempting to do is get people involved in improving articles and calling attention to issues in a prominent way increases the odds of that happening. 74.73.224.126 (talk) 01:14, 12 May 2023 (UTC)
What evidence do you have that the maintenance templates increase quality?  Has that been studied? Orlando Davis (talk) 01:31, 12 May 2023 (UTC)
I'm not sure what statement you're referring to. Regardless, the very fact that there are active projects dedicated to working certain areas of the backlog belies the idea that maintenance tagging serves no purpose. If instead you're asking if the WMF or anyone else has done any research on this question the answer is I don't know; Whatamidoing (WMF) would be in a better position to respond to such an inquiry.
Of course if you believe that e.g. {{BLP unreferenced}} is a net negative you can always start a deletion discussion, though I would strongly recommend against doing so. 74.73.224.126 (talk) 02:01, 12 May 2023 (UTC)
Thank you for that information. What is the link for submitting a request for deletion of may not reflect an encyclopedic tone, sounds like an advertisement, and does not sound neutral.? Where are the links for all the different maintenance requests? I appreciate it. Orlando Davis (talk) 02:40, 12 May 2023 (UTC)
@Orlando Davis, Wikipedia:Templates for discussion is the place. A full list of clean-up templates is here. I also strongly recommend against this - I think you're heading into disruptive editing territory, thus risking a block - but it's up to you. 199.208.172.35 (talk) 13:52, 12 May 2023 (UTC)
Hello,
I apologize if you believe that I am a disruptive editor. Could you show me where I have done that? You know, I have edited many articles for small errors, and have done my best to remove subjectivity in my editing. Everything is double checked to make sure it's right. and I don't impose subjective judgement on quality. Rather, I have focused on things that are generally accepted, for example spelling. Again, it is not my intention to be disruptive. I appreciate your help. Orlando Davis (talk) 14:19, 12 May 2023 (UTC)
@Orlando Davis, I think you've been edging into disruptive territory, and I wanted to give you a heads-up before you proceeded any further. IDHT-ing and BATTLEGROUND-ing is a bad idea even as a veteran editor; you are still quite new and unfamiliar with Wikipedia's policies and procedures. It's up to you where to go from here. I'd recommend standing back a bit, continuing to gain experience and ask questions, and revisiting your ideas about this issue when you have a few more months and several hundred more edits under your belt. 199.208.172.35 (talk) 14:44, 12 May 2023 (UTC)
I'll second everything 199 just said. Please spend some time editing and getting to know your way around before diving into the deep end. 74.73.224.126 (talk) 21:00, 12 May 2023 (UTC)
Even checking something as seemingly straightforward as spelling, grammar and style can involve subjective judgment to a degree when it comes to Wikipedia because of things like WP:ENGVAR, WP:CITEVAR, WP:DATEVAR, etc. For example, Wikipedia doesn't have one house-style of English, and it allows articles to be written in different varieties of national English. So, deference is often given to the style (spelling, grammar, formatting, etc.) established by the original creator of an article or the first major contributor to an article. In-article consistency is important per things per WP:ARTCON and WP:DATEUNIFY, but simply changing a previously established style just because it's not the one you (from hereon "you" in this context is the generic you) might prefer or regularly use yourself can be seen as disruptive, particularly if you're making a point of doing so across lots of articles within a relatively sort period of time without giving the matter much thought and when it's perhaps not really warranted. -- Marchjuly (talk) 22:40, 12 May 2023 (UTC)
74.73, I prefer to have volunteer-me answer that question. To the best of my knowledge, nobody has ever properly studied the effect that maintenance tags have on articles.
In my own experience, certain kinds of simple tags (e.g., {{Uncategorized}}) that are added to new articles probably do result in those discrete issues being addressed. Tags on heavily edited articles tend not to linger, so they are either effective or just removed.
However, for the most typical types of tags and the most typical types of articles, I strongly suspect that many of the more generic or whole-article tags (e.g., {{ref improve}}, {{third-party}} [which I created]) do not have a significant effect for typical articles.
Other tags may have a mixed effect. For example, {{fact}} may sometimes cause the loss of uncited but verifiable and accurate content (e.g., through edits such as this one), but might result in the addition of sources (e.g., through tools such as Wikipedia:Citation Hunt). WhatamIdoing (talk) 02:30, 13 May 2023 (UTC)
Often someone will add a maintenance template, and the article will get fixed, but no one will remove the maintenance template. If you come accross an article with a maintenance template that you feel is no longer applicable, check the article history to see when it was added and what changes have been made since then, and check the talk page to see if there is relevant discussion. If the issues have been fixed and/or there is no discussion, feel free to remove it, as I have to one of the examples you gave above, see this diff - and pay attention to my edit summary. ~ ONUnicorn(Talk|Contribs)problem solving 14:34, 12 May 2023 (UTC)
Got it! Thank you! Orlando Davis (talk) 14:47, 12 May 2023 (UTC)
If one is less sure, one can talk about it first: Talk:Johnathon Schaech/Archive 1#The major contributor banner. It can be productive to ask the adding editor "Hey, I think I fixed this issue, do you agree?" Gråbergs Gråa Sång (talk) 16:07, 12 May 2023 (UTC)

I will agree that adding maintenance tags is too easy a process. I have come across articles with one of those tags slapped on top, & silently wondered if said editor's goal was simply to bloat their edit numbers -- which can be done quickly by adding a tag & moving to the next article to tag -- instead of taking the time to actually do the work improving the article. (I've had occasions where it took me weeks to find a proper citation.) After all, if you know enough about a subject to know the article needs expanding, you know enough to improve it -- or at least leave a note on the Talk page to explain what needs doing. I don't know how we can fix those cases, & while I remove any tag I feel is inappropriate or silly, I doubt any changes to policy will fix this problem.But I appreciate the opportunity to vent about it. -- llywrch (talk) 18:32, 16 May 2023 (UTC)

In general, any such template added without an explanation can be removed without one. So feel free to do so. You can't prevent people from doing the wrong thing, you can only clean up after them. --Jayron32 18:40, 16 May 2023 (UTC)

ARBPOL amendment referendum live

As the petition for an ARBPOL amendment to remove the right for Jimbo Wales to act as an appeal route for arbcom decisions has received 100 signatures a referendum on the proposal has been opened.

Proposed amendment referendum

It requires a majority in favour with at least 100 supporting editors.

CENT, WLN, WP:AN, and VPP will all be notified. Please feel free to provide neutral notices to other relevant fora. Nosebagbear (talk) 11:06, 17 May 2023 (UTC)

Forgive former vandals

I was wondering if, say User:Example vandalizes Example, but then, after being warned, becomes a constructive contributor. Do we just...forgive and forget? If so (or not so), there should be policy that supports it. Just want to get consensus. Sincerely, --AugustusAudax (talk|contribs) P.S: Aliens exist 12:15, 10 May 2023 (UTC)

well if they are constructive after one warning, that is great. As long as they are not blocked permanently they can attempt to do good with their edits. No one has to forget or forgive though. But WP:AGF means we give them a chance if they look good. Graeme Bartlett (talk) 12:24, 10 May 2023 (UTC)
I'm not sure what there is to forgive though. Wikipedia doesn't maintain a formal set of demerit points or any other way to quantify bad behavior. Memory of bad behavior tends to fade over time based on the severity of the offense and the time since the last offense, but that's just general human nature. Since Wikipedia has no formal means of tracking such things, there's nothing to "forgive". Either you are being useful, or you aren't. That's really all Wikipedia as a system cares about. --Jayron32 13:12, 11 May 2023 (UTC)
Unless you are blocked (or banned), every user is free to contribute constructively. If you have a history of vandalism, it might take a lot longer for your record to be seen as cleaner (say if you were to ask for advanced perms, say), but you aren't blackballed for it. If you are blocked, such a "forgive and forget" mentality can be seen with WP:FRESHSTART. It's difficult to have a policy around this, as users will have different standards of history if a user was to say, run at RfA. Some users might ignore things happening over two years ago, some might not care about minor stuff, and some might really care about that time in 2007 you accidentally mistyped "shift" into an article on a BLP. To each their own. Lee Vilenski (talk • contribs) 14:40, 11 May 2023 (UTC)
Forgive and forget is a good idea in general; some former vandals have actually become sysops. Of course we can't compel people to forget, but from a procedural standpoint everyone is welcome to contribute as long as they remain in good standing. 74.73.224.126 (talk) 01:31, 12 May 2023 (UTC)
Also probably depends on how long it's been. A lot of vandals are teenagers and grow out of it. Gnomingstuff (talk) 02:00, 12 May 2023 (UTC)
I have wondered at various points whether vandalism might even be a point-of-entry for some users. “Anyone can edit” etc.
I feel no need to enshrine anything into policy though. We have, as a community, many guidelines (and policies?) that can collectively be read as saying, “hey, if you’re doing good work I won’t chase you for old crimes.” — HTGS&.nbsp;(talk) 04:44, 12 May 2023 (UTC)
@HTGS: Such as what? Sincerely, --AugustusAudax (talk|contribs) P.S: Aliens exist 11:16, 12 May 2023 (UTC)
IP vandalism is usually one-off unless it is a shared account (a school, usually) so probably impossible to say. Gnomingstuff (talk) 15:44, 12 May 2023 (UTC)
@HTGS and Gnomingstuff: Well, here's one data point. A number of my earliest edits (although not the very first) were vandalism, and I do think those experiences contributed to me becoming a productive editor. There was something cool about being able to just change the site like that and, when not trying to come up with silly jokes with my friends, that turned into a desire to make the wiki better. -- Tamzin[cetacean needed] (she|they|xe) 08:15, 19 May 2023 (UTC)

RfC on a procedural community desysop

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Shortcut

Although rare, there are situations where the community has consensus that an administrator should be blocked indefinitely, or at least for a significant period. In those circumstances, this proposal suggests that administrators who have been blocked for more than 28 days do not hold the trust of the community and therefore the sysop userright should be removed procedurally alongside inactivity desysops. WormTT(talk) 14:05, 17 April 2023 (UTC)

Proposal: Procedural community desysop

NO CONSENSUS
Numerically, opinions were about evenly split with about 60 in support and 67 in opposition. The main arguments in support were that any administrator blocked for such a lengthy period, and assuming their appeals were unsuccessful and no other admin would unblock, has clearly lost the trust of the community and should not retain the +sysop bit. Arguments in opposition tended towards two main points: (1) blocks are a technical restriction to prevent imminent disruption, so adding a new consideration when blocking could disincentivize their use, (2) the situation the proposal would address is so rare that the benefits do not outweigh the potential harms of tying blocking and block appeals with desysopping especially compared to existing procedure (ArbCom). There was substantial support early on, but over the course of the RfC the opposition arguments were weighed more favorably by participants. Not enough that there would be consensus against, but enough to prevent the formation of a consensus. — Wug·a·po·des 20:44, 18 May 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

The following section should be added to WP:Administrators

Procedural removal

On the first day of the month, any administrator who is blocked and has been blocked for more than 28 days will have their administrator user-right procedurally removed (alongside inactivity removals). Administrators who have their sysop user right removed in this manner are not eligible to simply request return at the bureaucrats' noticeboard, but may appeal the removal to the Arbitration Committee. The administrator may regain their administrative permissions through a successful request for adminship.

Survey (Proposal: Procedural community desysop)

  • Support as proposer. Recent events have brought home to me that we are still lacking in ways to handle poor behaviour by administrators. I believe that as a community, we have consensus that an indefinitely / long term blocked administrator does not hold the trust of the community. However, in those situations, the only place to remove the toolkit is Arbcom (or waiting 12 months). I see no reason why such a removal shouldn't happen more quickly, and no reason that Arbcom needs to be involved if it does.
    Instead, I'm suggesting that we have a 1 month period, which allows for cooling off, then removal as part of the next automatic removals, no request necessary, no fuss, no mess. WormTT(talk) 14:05, 17 April 2023 (UTC)
  • Support I'm speaking as an admin here. If my conduct as an editor warranted any sort of long term block of a month or so, I should not be trusted with the admin tools any longer. RickinBaltimore (talk) 14:15, 17 April 2023 (UTC)
    The reasoning here sounds straightforward to me. It seems rather easy to become an Admin these days, based on some of the pro/con discussion I have seen this year regarding length and depth of candidate editing experience. So, I can certainly understand some people getting carried away and behaving "poorly". Martindo (talk) 06:48, 26 April 2023 (UTC)
  • Oppose Pointless. A blocked admin can't (since 2018) unblock themselves, and if they're blocked indefinitely, they'll just be auto-de-adminned when the time comes around. I find it difficult to think of a situation where this process would be useful. --Jayron32 14:17, 17 April 2023 (UTC)
    Actually, editing their own talk page would be enough to forestall the annual edit requirement. Courcelles (talk) 13:33, 18 April 2023 (UTC)
  • Support with revisions to clarify "blocked". In exceptional circumstances we might pblock a sysop from a small number of pages but still want them to continue as a sysop -- I feel that "blocked" in this case should mean "blocked from the entire mainspace".—S Marshall T/C 14:20, 17 April 2023 (UTC)
    I'm having a hard time picturing under what circumstances we might want to pblock somebody yet still trust them enough to hold a mop. -- RoySmith (talk) 14:33, 17 April 2023 (UTC)
    People could want to have a pblock? —Kusma (talk) 17:06, 17 April 2023 (UTC)
    The community has rejected the idea of an admin being desysoped due to a partial ban. Don't see why a single page block should be any stronger in this context. Animal lover |666| 20:05, 17 April 2023 (UTC)
    Only sitewide block should be considered for the removal of administrators. Thingofme (talk) 14:09, 18 April 2023 (UTC)
  • Weak support. The choice to only desysop on the first of the month concerns me as it could lead to some controversial situations; an admin blocked for 50 days on the 5th of March will remain an admin, while an admin blocked for 30 days on the 2nd of March will not. I find it hard to justify this, as for blocks of under two months whether an admin remains an admin becomes random chance. However, this isn't enough for me to oppose this proposal as I believe it is important to have a process to address situations where admins have so clearly lost the trust of the community. BilledMammal (talk) 14:21, 17 April 2023 (UTC)
    It appears to me from Worm That Turned's vote that it would happen during the normal automatic removals, I'm assuming that means the others happen on the first of the month, so no need to create extra work. But you have a good sentiment Happy Editing--IAmChaos 16:44, 17 April 2023 (UTC)
    That was my guess. Can someone confirm it would actually work the same way via software? Martindo (talk) 06:44, 26 April 2023 (UTC)
  • Support in principle but Oppose in its current form. I don't get why this needs to be tied to a specific day on the calendar. But more than that, it allows for stealth desysops. Let's say I block bradv. He's been inactive for 9 months, so he's not going to notice. If nobody else happens to notice, come June 1st, he'll get desysopped. I assume that's not your intent, but as written, it's what would happen. This could be fixed by adding a requirement that in addition to blocking brad, I would have to post a notice to WP:AN to start the clock ticking. Then it essentially becomes WP:PROD for admins. -- RoySmith (talk) 14:32, 17 April 2023 (UTC)
    OK, it's been demonstrated to me that blocks do show up on watchlists, and I'm sure every admin's talk page is watchlisted by lots of people, so that satisfies my concern about stealth blocks. I still don't get why this needs to be tied to a specific day on the calendar (and if it must be, at least make it the ides) but that's not enough to me to oppose. -- RoySmith (talk) 15:07, 17 April 2023 (UTC)
    Interestingly, I did consider putting together a proposal about blocking administrators as part of this, which included a notice to AN. But I didn't feel it was necessary. That said, I really don't like the idea that administrators get an automatic AN review if blocked, creating a "class structure" - we already have supermario issues, which is something I'm trying to address.
    If you are concerned about blocking inactive admins, well, yes, it's possible, but most admins userpage's are watchlisted by multiple people - a stealth block would be noticed. Even if it wasn't, this is something that the appeals process would be quick to fix. WormTT(talk) 14:46, 17 April 2023 (UTC)
    Does watching somebody's user page generate a watchlist notice? Normally, a block is accompanied by a talk page notice, but it doesn't have to be. Could you please block User:RoySmith-testing without any explicit notice? I'm watching their user page. Let's see if I get a notice. -- RoySmith (talk) 14:53, 17 April 2023 (UTC)
    It does show up on watchlists. To show this, I have just pblocked your test account for 3 hours. Best, Barkeep49 (talk) 14:57, 17 April 2023 (UTC)
    Yeah, I got:
    × Block log 14:57:29 Barkeep49 talk contribs block changed block settings for RoySmith-testing talk contribs blocking the page User:RoySmith/Three best sources with an expiration time of 2023-04-17T17:56:33 (autoblock disabled) ‎(requested for testing purposes by User:RoySmith) (unblock | change block)
    I'm actually kind of surprised about that, but, OK. -- RoySmith (talk) 15:02, 17 April 2023 (UTC)
  • Oppose in this form. (a) it isn't clear that 28 days is enough for a good-faith unblock request in complicated cases and we shouldn't let stalling an unblock turn into a desysop (b) why not just escalate to ArbCom after the 28 days? (c) would any block trigger this? —Kusma (talk) 14:38, 17 April 2023 (UTC)
    I also note that no discussion is required, meaning that the mechanism is - in theory - not implementing a "community desysop" but a "single admin PROD-like desysop". I know that this will likely play out differently in practice, but there should be safeguards against the proposed mechanism. —Kusma (talk) 15:09, 17 April 2023 (UTC)
  • Support If editor has been blocked for more than a month, especially if that block gets confirmed by the community which I suspect it would in a majority of these cases, they shouldn't be an admin anymore. This is true even if the block is for less than an indef or a year, to address Jayron's question about why not wait for the current inactivity to desysop. I see this as an important way for the community to take some control over the deysop practice, something I have long favored. The presence of this in policy would be an important way of combatting the super mario effect as there is now some incentive for an admin to block, as they would anyone else, an admin who has breached policy rather than just go "well it's for arbcom to sort out". As to the idea that it takes someone longer than 28 days to formulate an appeal, they can still appeal the decision: by re-running for RfA. If the community wants to be able to handle some desysops on its own, and it's my fervernt hope that it does, then we need to stop letting the perfect be the enemy of the good and support reasonable proposals like this as first steps towards building community capacity around merit based desysops and showing concerned editors that the community can handle these issues, not just arbcom. Best, Barkeep49 (talk) 14:55, 17 April 2023 (UTC)
  • Support - I'm not quite sure why it's necessary to wait for 28 days. If we're going to go in this direction, then it seems to me that a CBAN of an admin should carry with it an automatic immediate desysop, which, after all, can always be undone if necessary - but, that being said, this proposal is certainly better than the situation we have now, where there's absolutely no way for the community to desysop an admin (despite the fact that it's the community which creates the admin in the first place, via RfA). Beyond My Ken (talk) 15:06, 17 April 2023 (UTC)
  • In the proposal, admins can desysop other admins. There is no community element. —Kusma (talk) 15:18, 17 April 2023 (UTC)
    I don't agree. A block of an admin would be reviewed by the community. It wouldn't happen based on a single admin's view - or rather, it wouldn't stick for over a month based on a single admins view. WormTT(talk) 15:20, 17 April 2023 (UTC)
    Only admins can initiate the desysop review by blocking. The community can't initiate this. —Kusma (talk) 15:53, 17 April 2023 (UTC)
    Admins are part of the community - what's more, if you have a consensus of non-admins at say, WP:AN, we can be confident that an admin would implement it. The only way this works is with consensus, and with our current practises. WormTT(talk) 15:56, 17 April 2023 (UTC)
    I am rather uncomfortable with how many implicit assumptions about the functioning of the community and the current practises are part of this proposal. —Kusma (talk) 16:42, 17 April 2023 (UTC)
    +1 - it seems unclear to me why a community desysop process does not actually require the community to weigh in, and only assumes that it will. Galobtter (talk) 19:03, 17 April 2023 (UTC)
  • Oppose If we wish to devise a procedure for community-instituted de-sysop, we should devise a procedure for community-instituted de-sysop (with appropriate safeguards). The proposed process will only mean that editors will be encouraged to !vote at for a month or longer block at WP:AN when they believe that the admin should be de-sysoped (irrespective of whether they believe that a block itself is necessary) since that is the only procedural loophole they have been granted to achieve the desired end. Why introduce such a de-sysoping through wink-and-a-nod process? Abecedare (talk) 15:08, 17 April 2023 (UTC)
    All editors have safeguards if they are wrongly blocked or they wrongly lose a permission. I do not believe administrators should get extra safeguards and I do not believe that someone who has had conduct worth a 28+ day block fulfills the administrator conduct policy and thus should not be an admin. Best, Barkeep49 (talk) 15:12, 17 April 2023 (UTC)
    Sorry, if I was not clear enough. My argument is not that admins with long blocks should not be desysoped (frankly, I can't imagine a scenario, except for self-requested blocks, when they shouldn't be) or that admins need extra-safeguards from being blocked (they don't!). My objection is that a >28-day block should not be a necessary intermediate step for a community-instituted desysop. If the community wishes to desyspo an admin they should !vote for it explicitly rather than be forced/encouraged to !vote for a > 28-day block with the understanding that such a block would eventually lead to the desired end, i.e., a desysop. (I think I may be repeating myself, so if you or anyone wishes to discuss this separately we can do so at my talk-page w/o taking too much space here.) Abecedare (talk) 15:31, 17 April 2023 (UTC)
    @Abecedare I would absolutely support a direct community desysop proposal, but as yet, we have not found one that can gain consensus (even though mor than one have had majority support). I am not sure that opposing something you agree with because you see a potential something tangentially better is a good idea though. Is that not the definition of perfection getting in the way of good? WormTT(talk) 15:52, 17 April 2023 (UTC)
  • Support I'm an admin. I got blocked. A lot of people asked me to appeal, so I did, apologising for bad conduct (I was going through a horrible time in my personal life, leading me to lash out completely unnecessarily in complete violation of WP:ADMINCOND) and I was unblocked, easily within a week. If you can't successfully file an appeal within 28 days, you probably shouldn't be an admin. Ritchie333 (talk) (cont) 15:23, 17 April 2023 (UTC)
  • Support I had a completely different comment, but Ritchie333 edit conflicted me and changed my mind. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 15:28, 17 April 2023 (UTC)
    I did also misunderstand on first reading, thinking that having a block imposed of 28 days or more triggered the desysop, rather than still being blocked after 28 days. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 15:32, 17 April 2023 (UTC)
  • Support. Although I think this proposal does not go far enough. In practice this sounds similar to a community admin de-sysop process in two steps (Admins getting blocked - 28 day period for the procedural desysop) and I would like more discussion on a robust system based around considering it as a single process (but presumably higher thresholds to implement). That discussion does not have to be now or on this survey, but I think more community power to desysop admins is a good thing. Soni (talk) 15:31, 17 April 2023 (UTC)
  • Oppose. If a desysop is needed, do it via ArbCom. That's what it's there for. Seraphimblade Talk to me 15:34, 17 April 2023 (UTC)
  • Comment Also @Worm That Turned: maybe this should be listed on WP:CENT or similar. Soni (talk) 15:33, 17 April 2023 (UTC)
    It's already been on CENT :). Best, Barkeep49 (talk) 15:44, 17 April 2023 (UTC)
    Ah, I see how I missed it. I forgot links are marked as "read" on my browser if I follow it from anywhere, not just from CENT specifically. Thanks for clarifying. Soni (talk) 15:50, 17 April 2023 (UTC)
  • Support per Ritchie333. I agree that it's a fair assumption that if an admin stays blocked for 4 weeks then they don't have the community's trust. —pythoncoder (talk | contribs) 15:57, 17 April 2023 (UTC)
  • Oppose. This proposal reminds me of the one linking desysops with community restrictions, which resulted in a clear consensus against.
    Despite the supporters' best intentions, this worsens the "unblockable" and "Super Mario" effects, given that the proposed policy increases the consequences of blocking an administrator and further discourages it. If the proposal prevents even one administrator from being blocked when they should be, then it is not worth it: administrators must be held accountable for their actions. We elect the Arbitration Committee so that it can handle requests for removal of administrative tools. That grave responsibility should not be borne by a single editor.
    When Special:Block is opened, one needs to be convinced that imminent or continuing damage and disruption to Wikipedia will be prevented. That is the main concern. That decision-making process, which is already clouded by the fact that a user with social capital is being blocked, should not be impaired by secondary questions over whether an administrator is fit to continue holding that access.
    Administrators must be held accountable. But this is not the answer. Sdrqaz (talk) 16:18, 17 April 2023 (UTC)
Not sure I agree with you on the top line but I really appreciate your well reasoned and concise argument. I think its so important that people look beyond just the question in front of us and try to fit the current proposal into the big picture. Horse Eye's Back (talk) 16:43, 17 April 2023 (UTC)
  • (edit conflict) Oppose This proposal allows admins to near-unilaterally desysop another one, unless a review of the block is brought up at AN/I which won't always happen even if a block is controversial. It also makes blocks of an admin greater than 28 days unnecessarily more contentious. I am willing to support a method for the community to desysop an admin, but it should unconditionally require community discussion. Snowmanonahoe (talk) 16:21, 17 April 2023 (UTC)
    Any admin who is blocked is able to make an unblock request and ask for a community review. I think 28 days is plenty long enough for them to do that. Boing! said Zebedee (talk) 16:31, 17 April 2023 (UTC)
    Currently, a blocked admin would be subject to a standard block review. With this proposal, they will be subject to a community desysop review, a very different beast for which there is no precedent. It is quite a new ability for any single admin to initiate a community desysop review. —Kusma (talk) 16:47, 17 April 2023 (UTC)
  • Question - Does anyone have a number for how many times an admin has been blocked >28 days and arbcom hasn't quickly and easily stepped in to remove permissions? Seems like a reasonable proposal, but has it ever been needed? — Rhododendrites talk \\ 16:23, 17 April 2023 (UTC)
    This feels a bit like a chicken and the egg. Recently, for instance, Athaenara could have been desysopped under this proposal rather than the arbcom motion which happened. One virtue of this proposal, which I didn't mention above, is that I think it would save some time and community drama - even an ArbCom case request is high on both. Barkeep49 (talk) 16:44, 17 April 2023 (UTC)
    I reviewed the list of current admins; the only one who this would have affected would be Smartse, who was blocked for 78 days per their own request to enforce a wikibreak. BilledMammal (talk) 18:23, 17 April 2023 (UTC)
    @BilledMammal: Not true. Per my research using a PHP script making API queries, Randykitty self-blocked in 2018 for 85.3 days (relevant contribution history). That's the longest block tor a current administrator, assuming my algorithm is correct. – wbm1058 (talk) 20:12, 7 May 2023 (UTC)
    ...and Spartaz was blocked for 79 days in 2018 as well, per their request. – wbm1058 (talk) 21:22, 7 May 2023 (UTC)
    That was before my RfA. SmartSE (talk) 18:31, 17 April 2023 (UTC)
    But raises the question of whether it's sensible to de-sysop for requesting a wikibreak. Imagine someone on a military deployment: "Thank you for requesting that your account be blocked while you know you won't be able to use it. By the way, we're going to de-sysop you." Thank you for your service, indeed. WhatamIdoing (talk) 21:06, 17 April 2023 (UTC)
    I'm unsure as to whether to support the proposal as a whole, but it would need an exemption for an admin in good standing who requested to be blocked. Certes (talk) 10:01, 25 April 2023 (UTC)
    ...especially as an adept wikilawyer would sidestep this measure by resigning their adminship before requesting a block, then re-request sysop when they return. Certes (talk) 10:07, 25 April 2023 (UTC)
    Part of me wants to support this as a sorta-kinda community desysop process. Rather than "should this person be desysopped" it's "should this person be blocked for exactly 29 days? wink wink what I mean?" My concerns are (a) that the illusion of a community desysop process will lead arbcom to defer to the community for some cases, when it seems like arbcom is doing alright with the extreme cases already (such as those requiring a long block); (b) I'm not sure why it would reduce drama. Anytime someone with a lot of experience gets blocked for one day (nevermind a month or more), it leads to a ton of drama. It's the block more than the desysop, right?; (c) Isn't this easy enough to handle on a case-by-case basis? A desysop can be carried out by arbcom motion, and that should be relatively straightforward in the case of someone blocked for a month. On the other hand, requiring an action by arbcom means there's room for judgment to handle exceptional cases like a requested block. Not sure. — Rhododendrites talk \\ 12:51, 19 April 2023 (UTC)
  • Support. If an admin is indef/long-term blocked and has been so for more than 28 days, I don't think it could be read in any other way than they've lost the trust of the community. An ArbCom request in such a case would be little more than a rubber stamp (as I can't see ArbCom reversing such a strong community action), so this would really just save time and effort for the same ultimate result. Boing! said Zebedee (talk) 16:26, 17 April 2023 (UTC)
    @Boing! said Zebedee Or maybe they just needed a break or they rage quit? I'm not meaning to call you out on those (nor do I need to know the details), but we should consider if those events should have resulted in the loss of your mop. -- RoySmith (talk) 14:53, 19 April 2023 (UTC)
    Voluntary relinquishment due to taking a break or leaving Wikipedia would still allow for requesting privileges to be re-granted without a request for administrative privileges, within the bounds of the activity requirements. isaacl (talk) 15:39, 19 April 2023 (UTC)
  • Support. The community appoints admins. If it can be trusted to do that, it can be trusted to remove them. The proposed conditions under which this would occur seem entirely reasonable. AndyTheGrump (talk) 16:50, 17 April 2023 (UTC)
    The community has been doing an absolutely terrible job at appointing admins (extremely conservative and unforgiving of small mistakes). —Kusma (talk) 16:58, 17 April 2023 (UTC)
    I think that's true, yes. But I wonder if it's another side of the same thing - if theres no community way to get rid of an admin, does it make people at RfA a lot more cautious and demanding? (I really don't know, just pondering out loud.) Boing! said Zebedee (talk) 18:20, 17 April 2023 (UTC)
    We've had years of people clamouring against "admins for life" and we have recently made it harder to retain admin status, offending a few low-activity oldtimer admins. It doesn't seem to have made people less cautious. I don't think admin-PROD is going to make any difference to RfA either. —Kusma (talk) 20:34, 17 April 2023 (UTC)
    Hmm, yes, I think you're probably right - maybe the creeping intolerance at RfA simply goes hand in hand with general rule creep across the project. Boing! said Zebedee (talk) 07:09, 18 April 2023 (UTC)
  • Support If an admin needs to b e blocked, and the block sticks, they are obviously unfit to be an admin. We don't need a month-long committee case to make decisions this obvious. Beeblebrox (talk) 17:00, 17 April 2023 (UTC)
  • Support - this accounts for appeals happening and so on, so is fine. For the sake of clarity, this can be taken to oppose any alternate standard that might be picked out from this discussion (obviously I'll amend if I see a good one, just to avoid missing a discussion). Nosebagbear (talk) 17:01, 17 April 2023 (UTC) Since we have broken out new ideas as they arise, !vote adjusted to just this one. Nosebagbear (talk) 14:58, 24 April 2023 (UTC)
  • Hesitant support. I have several concerns here. First, that this will raise the stakes for blocking an admin, which is already hard enough: but we don't do it very often, so perhaps it's not a concern. Second, per Abecedare above, that we're not going far enough; but I don't want to let the perfect be the enemy of the good either. Finally I'm concerned that the ARBCOM appeal clause defangs this proposal. If the intention is that a full ARBCOM case should not be necessary step to a desysop, we're making it to easy for this to end up in ARBCOM's lap anyway. I suppose the burden is shifted from the community to the admin, so perhaps it's a shift for the better; but I'm unconvinced this is going to be a big change in that respect. Ultimately, though, yes, an admin blocked for more than 28 days should likely be desysopped. So I land here. Vanamonde (Talk) 17:35, 17 April 2023 (UTC)
  • Support - (another admin here). I think Wugapodes and Beeblebrox have explained why. - Donald Albury 17:46, 17 April 2023 (UTC)
  • Support. I'm a bit worried that this will incentivize admins/the community to make blocks that wouldn't otherwise need to be made, but I also strongly agree with what Ritchie333 is implying below: that holding out for the perfect proposal means we end up stuck with an even less desirable status quo. I believe this proposal will remove admins who need to be removed and will not remove admins who don't need to be removed, all while furthering admin accountability to the community, which is important to me. That means it's likely to be on net an improvement, and I support things that are improvements even if my ideal desysop proposal might read differently. And if this system doesn't work, I have no doubt that the community will be capable of revising or repealing it. Extraordinary Writ (talk) 17:52, 17 April 2023 (UTC)
  • Support per nom. This doesn't seem likely to solve much since I can't imagine very many admins are blocked for a month, return to editing, and don't resign the tools. But as a few of the supporters have alluded to, even a miniscule tightening of the rules for administrators who have clearly lost community trust (and anyone remotely high-profile here who is blocked for a month has very clearly lost the community's trust) is a net-positive. Even if its only real effect is to show that we can agree on something. Ajpolino (talk) 18:14, 17 April 2023 (UTC)
  • Oppose Is this really a "community" desysop process? That is, if most of the power is with admins, can it even really be called a community process? The proposal ostensibly starts with a case where "the community has consensus that an administrator should be blocked indefinitely, or at least for a significant period". But the actual proposal doesn't require any sort of community consensus that the admin be blocked. Yes, any block that's in anyway not obvious will almost certainly go to the community within 28 days, but it still gives the power to admins to start the desysop process. I also note that WP:CTOP blocks can be unilaterally imposed and require a "clear consensus" to lift, so we could have a situation where 60% of the community disagrees with a block but that still results in a desysop. Imagine also being the closer of such a discussion and having the almost unilateral power to decide if someone gets desysopped. Yes, there's the safeguard of "may appeal the removal to the Arbitration Committee" but in a proposal meant to save time I only see more drama and time being wasted in any controversial case.
    I also think this makes blocking admins worse, both in them not being blocked and in them being unnecessarily blocked. As Sdrqaz eloquently explains, this makes blocking admins more troublesome. But I also think this could result in admins being unnecessarily blocked just so they can be desysopped. Someone brought up Wikipedia:Arbitration/Requests/Case/Neelix as one case where this could be useful. But I note that Neelix was never blocked for more than a few days until well after the case, and I don't think a block should have been imposed just to cause a desysop - often times, a community restriction is all that is actually needed. I think there's a case of Goodhart's law here - I'm not and I don't think anyone is disputing that an admin blocked for more than 28 days is unfit to be an admin, but I think using that as a the only measure will cause more problems than it will solve.
    To be honest, I'm not convinced there's any particular need this is addressing. ArbCom has only seemed more and more willing to de-sysop over the past few years (and I've generally seen this as a good thing). The main argument seems to be that this will save a full case in obvious cases, but ArbCom literally just de-sysopped by motion without requiring a case (after a lot of hemming and hawing to be fair). And that was in a case where the community even rejected an indefinite block, so less obvious than any case this proposal addresses. I honestly think all we need is ArbCom being more willing to desysop by motion in obvious cases and the community supporting that. Galobtter (talk) 19:00, 17 April 2023 (UTC)
  • Support because it's something. Moneytrees🏝️(Talk) 19:46, 17 April 2023 (UTC)
  • WeakSupportOppose "Support" reasons are those given by the nom and because it's something. "Weak" Oppose because this we need stronger more routine community reviews rather than focusing on desysop, and this one is for even rarer cases when they blew it as an editor rather than aqs an admin. We need to strengthen WP:Administrative action review and take the "poison pills" out of it. And add to it more admin conduct issues. And the most common results would be mere findings and guidance and maybe a few trouts. North8000 (talk) 20:18, 17 April 2023 (UTC)
"Safe" but so specialized/ unlikely to get used that it's not worth the diversion and complexity of creating. North8000 (talk) 20:41, 18 April 2023 (UTC)
  • Oppose Why can't we just keep it simple and have a community desysop process based on an up-and-down majority vote like Commons? -- King of ♥ ♦ ♣ ♠ 20:36, 17 April 2023 (UTC)
    Because people keep opposing to the specific proposal rather than the general concept, so it never gets consensus. Ritchie333 (talk) (cont) 20:59, 17 April 2023 (UTC)
    The next admin block/unblock will be a de facto desysop discussion, and we have no rules at all how to deal with these, so we'll just make the rules up as we go along on ANI. That is a terrible way to make sound policies. —Kusma (talk) 21:08, 17 April 2023 (UTC)
  • Support. I disagree with Sdrqaz that this will make the WP:SUPERMARIO effect worse. To the contrary, I believe it will help by linking the "normal" way of dealing with conduct issues (blocks) with the loss of tools. Otherwise, this is a sensible, if imperfect, proposal. I think Tamzin's concern can and should be easily solved by specifying the block must be non-voluntary. And I would rather have a clause delaying the removal of the bit if there is an appeal ongoing: there shouldn't be a race-against-the-clock to form consensus within the next 24 hours at AN before a new RfA is required to regain the mop. I also think it would be cleaner to simply specify that losing the tools in this way counts as losing them under a cloud, instead of separately explaining how one can regain the tools after losing them in this way. But perfect cannot be the enemy of progress. HouseBlastertalk 21:45, 17 April 2023 (UTC)
    Just after I hit publish, I realized the significance of something WTT said above: "(or waiting 12 months)". One off-the-rails admin can already issue a block that will eventually result in the removal of the bit. Heck, anyone can hop over to ANI and seek consensus for an indef ban, which would result in them losing the tools after a year. All this proposal does is lower the amount of time it takes before the tools are removed. Do you think someone who is blocked for more than 28 days but less than a year deserves access to the tools? I don't think so. HouseBlastertalk 21:54, 17 April 2023 (UTC)
  • Support Without reservations. This has been desperately needed for 20 years. The process itself can be amended later if needed but we need SOMETHING here. The idea the community can elect admins but never remove them without appealing to ArbCom is backwards and always has been. - Who is John Galt? ✉ 21:47, 17 April 2023 (UTC)
  • Oppose - I support the idea of a process for community desysop. But this isn't it. First, 28 days is way too short a time period. This should be a year at least, and only in the case of a ban. Second, as we have shown through adding things like partial blocks, what an editor does in one place may not disqualify them from being able to positively help out in other ways. And so, just being blocked for reason A, should necessarily mean that the admin tools should be removed. Due to the idea of escalation blocks, should someone who receives a 30-day block suddenly lost the tools? Also, there's a difference between a block and a ban - and this is intentional. So no, we should not be removing tools merely due to an arbitrary time period of a block. To be clear, I think I might have supported this if the time period was "a year and a day", and if it was a "community ban", not merely a block. - jc37 22:42, 17 April 2023 (UTC)
    @Jc37 If an admin doesn't edit for a year, say, because they're blocked - they already have their admin rights removed. But I can guarantee, that there would be community uproar and an arbcom case before that happened. This simply gives a procedural option, shortening the time period, meaning that Arbcom need not be involved. WormTT(talk) 07:35, 18 April 2023 (UTC)
    @WTT - 28 days is way too short. It needs to be at least longer than the 6 months of the Wikipedia:Standard offer. To do otherwise is just inherently wrong. And, in practice (based upon actual requests I've seen), longer than a year is what's more likely, if the community is willing. Hence my "a year and a day". If you think there would be an uproar and this needs encoding, then let's please have that discussion. And what everone's been saying here about a single admin essentially making this happen - that really just sounds like a bad idea. And setting aside the act itself, I think adding this to the mix will rachet up the drama. That's a time sink that we can avoid, I think, by making this a community ban rather than merely a block. - jc37 07:48, 18 April 2023 (UTC)
    @Jc37, I understand where you're coming from, as I say, we already remove for inactivity after a year, block or ban. So, in my eyes, your suggestion is moving further away from the goal of a community desysop without Arbcom. Why is (at least) 28 days too short? It allows for absence, cooling off, negotiation, self imposed / community imposed sanctions or any other dispute resolution. A month is considered a reasonable period for discussion at almost every venue I can think of. WormTT(talk) 07:59, 18 April 2023 (UTC)
    If that's all true, why then do we wait 6 months for the Standard offer? I think that community has already set the absolute minimum length of time there, and really, even there, it suggests longer. What does it say about us if we say: "It's been 30 days - you've done your time and now are unblocked, but we don't trust you any more." ? Useight (below) was very right that this just screams punitive. Where's the fire? - jc37 08:11, 18 April 2023 (UTC)
  • Support per Ritchie333 and Beeblebrox. I have nothing to add to their words. LEPRICAVARK (talk) 22:48, 17 April 2023 (UTC)
  • Support per Ritchie333 and Beeblebrox. In the extremely unlikely event that someone was blocked for >28 days, and was not unblocked before that period elapsed, but did still have the trust of the community then they could demonstrate this trust to arbcom who would grant the appeal and/or they would easily pass a new RFA. Thryduulf (talk) 23:05, 17 April 2023 (UTC)
    I think that's a bit of circular reasoning. That could be said of anyone for any reason. For example: "If they have the community's trust then they would easily pass a new RFA, so we should have daily RfAs for admins."... - jc37 23:20, 17 April 2023 (UTC)
    Well daily is hyperbole, but I fully support having reconfirmation RFAs when someone figures out how to get community consensus for a scalable process. Thryduulf (talk) 00:01, 18 April 2023 (UTC)
  • Support with caveats. An admin who has been blocked in good faith for more than 28 days should just not be an admin. If they haven't been able to appeal their block in that time, then they don't have the support of the community, and they should be demopped until they can demonstrate support in a reconfirmation RFA. What we're proposing here is a desysop related to clear misconduct; WP:CLOUD should apply. These shouldn't be procedural with the right to regain the tools upon request, like inactivity desysops are. If I block someone and take away their pagemover userright for out-of-process moves, they don't just get it back when the block expires, they have to make a new WP:PERM request and demonstrate suitability all over again. There's no way admins should be held to a lesser standard than that. Ivanvector (Talk/Edits) 23:30, 17 April 2023 (UTC)
  • Oppose just because I think this is going to end in wheel wars. I would support automatic removal of sysop on a successful community ban that was widely participated in, however. It should also be made clear that ArbCom is still an option to result in a desysop. --Rschen7754 00:49, 18 April 2023 (UTC)
    I'm not surprised to see an editor, like yourself, who was around for the wild west days bring this up but it strikes me as not part of our current culture. The last time we had a true wheel war was Fred Bauder, no? I feel WHEEL is properly understood to be a brightline desysop offense these days and so admins just don't do it. In this situation the third mover would be someone reinstating a block so losing your admin bits to try to make sure someone else loses theirs would be a choice. Best, Barkeep49 (talk) 02:49, 18 April 2023 (UTC)
    I don't remember if WP:FRAM came before or after Fred Bauder but there were minimal penalties for that scenario. Rschen7754 03:02, 18 April 2023 (UTC)
    We have strong procedures for wheel wars and actually, we haven't seen them in years. Maybe the odd Wheel skirmish, but nothing of the like from Wikipedia's early days. Yes, this proposal risks pushing those procedures, but I think that's worth it. WormTT(talk) 07:32, 18 April 2023 (UTC)
  • Oppose While it might seem intuitive to say that an admin blocked for a month shouldn't be an admin, a block can be instituted by any admin or cabal of admins and I don't agree their decision should overturn the results of an RfA. I don't have that much faith in the sort of admins we have on this website. Chris Troutman (talk) 03:13, 18 April 2023 (UTC)
  • Oppose. The purpose of a block is to prevent damage or disruption to Wikipedia. Assuming the block was done properly, then the block is performing that function (that is to say, the user is blocked and therefore cannot damage/disrupt Wikipedia). Having the block do something more is not within the intended scope of a block. I would go so far as to say that this proposal would make 28-day blocks punitive instead of (or in addition to) being preventative. It's unclear to me how removing the bit prevents something that the block doesn't. Useight (talk) 03:46, 18 April 2023 (UTC)
    "Preventative, not punitive" is a very, very good point. - jc37 06:10, 18 April 2023 (UTC)
  • Support per Ritchie333 and Beeblebrox.Pharaoh of the Wizards (talk) 05:41, 18 April 2023 (UTC)
  • Oppose I support a community-based desysop procedure, but only one that has a clearly defined and equally community-based resysop procedure. The proposal as written tries to address potential objections around resysop by splitting the baby and having ArbCom oversee an undefined appeals procedure.
    Ultimately it comes down to this: if this is procedural and linked to inactivity desysops as the proposal is hinting at, then an individual should be able to request it back at BN. If it is actually a community-based disciplinary procedure, +sysop should only be able to be restored via RfA, not by ArbCom.
    Worm, I'm assuming you wrote this proposal as something that would address potential objections and could pass (i.e. the objection that there's no procedural protection, so leaving the option of an appeal on one hand, and then the objection that if it is procedural it can just be re-requested on the other.) The problem is that the resysop provisions try to have it both ways, and the real crux of any desysop proposal is the resysop provisions (removing the flags are easy; the question is who can get them back.)
    I would support some version of this with resysop provisions that are clearly defined and aren't ambiguous and subject to a relatively opaque ArbCom appeal process - whether that be requiring RfA, or allowing restoration at BN. But the current language will cause drama when someone is desysoped after 28 days, is unblocked on day 29, and then goes to ARCA or even emails the mailing list. If this is going to be community based, resysop must be community based too. TonyBallioni (talk) 06:00, 18 April 2023 (UTC)
    I accept that the Arbcom appeal process is opaque, and you are right, I put it in to address potential concerns. The point of the committee is to deliberate, and I'm sure the group could make a decision on whether the procedural removal should have happened - which will go back to whether the block was valid in the first place. I'd also welcome expansion of that clause to whatever the community wished (from ability to raise a full case to only appeal in absolute obvious circumstances, eg bad block that somehow stuck) - or indeed the complete removal of the clause. I am against allowing restoration at BN, but RfA being the only option here would be fine by me. WormTT(talk) 07:30, 18 April 2023 (UTC)
  • Oppose. Blocks are a technical measure to prevent imminent or likely damage to Wikipedia. This proposal would turn them into a proxy for a high-stakes disciplinary process. That is not the purpose of the block feature. It is ArbCom's job to desysop users, and in the rare cases in which the community keeps an admin blocked for more than a month I find it difficult to imagine that ArbCom would not take up an appropriate motion, as they recently did in the Dbachmann case. Sandstein 11:32, 18 April 2023 (UTC)
  • Support per Worm That Turned and Ritchie333. ✠ SunDawn ✠ (contact) 11:39, 18 April 2023 (UTC)
  • Support I originally thought I would oppose this, but ultimately an action serious enough to warrant a 4 week block is one that would have led me to oppose at an RFA, and by extension should be enough to indicate that the user shouldn't be an admin. I understand that mistakes happen, but at this length it isn't a minor infraction or one-off issue, and there's been time for appeals and considerations. So yes, I'm ok with this, and oddly enough I'm more ok with this than some of the issues that I've seen result in a desysop via Arbcom. That said, if it is easier to remove admin rights I wish it was also easier to grant them, but perhaps one needs to be modified to fix the other. - Bilby (talk) 11:45, 18 April 2023 (UTC)
  • Support. Seems uncontroversial and logical, per "an admin blocked for that long should not be an admin". --Piotr Konieczny aka Prokonsul Piotrus| reply here 12:10, 18 April 2023 (UTC)
  • Support with perhaps an exception that a self-imposed block should not trigger the desysop. But if an admin is blocked for cause and can't find an unblock from any other admin in a month, that's prima facie evidence of having lost the community's trust. Courcelles (talk) 13:37, 18 April 2023 (UTC)
  • Support - First choice as compared to the alternate proposal below. There's nothing I can really add that hasn't already been said. Other than Fnord. --⛵ WaltClipper -(talk) 15:49, 18 April 2023 (UTC)
  • Weak Oppose per Jayron32. This seems more like a solution in search of a problem than an actual need. If someone can show me a need, i.e. where an admin really needed to be de-sysopped and existing procedure failed to do it, I could be convinced to support. Dave (talk) 16:38, 18 April 2023 (UTC)
  • Support This proposal won't really solve the problem of unaccountable admins or the need for a community desysop procedure, and will in practice probably never be used. But it's something, and really, it should work this way regardless. Writ Keeper ⚇♔ 17:34, 18 April 2023 (UTC)
  • Support per above. If an editor with admin rights gets blocked for a month, they're clearly not fit to be an admin -FASTILY 19:55, 18 April 2023 (UTC)
  • Oppose This is prescribing punishment without due process, and would incentivize wheel warring. We need to come up with more than just the outcome. We need a set, agreed upon way of removing adminship in the first place. Just because someone has been in jail for a month does not make them guilty. CaptainEek Edits Ho Cap'n!⚓ 20:30, 18 April 2023 (UTC)
  • Oppose mainly per Sandstein. This proposal is outside the traditional use of the block tools. It seems like a method for reducing Arb's workload, which isn't really that high anyway. I think if you are going to desysop someone, some kind of process needs to take place. Since desysopping via Arb really isn't that difficult, it needs to stay there. Arb has virtually unlimited tools, from full cases, suspend and desysop, hear and keep the bit, admonish, or sanction. Arb has shown they can do it in less than 28 days. Pushing it off onto the blocking admin and a calendar seems to be a cheap substitute for fair process, and frankly, seems a bit lazy. Dennis Brown - 2¢ 20:35, 18 April 2023 (UTC)
  • Oppose. Upon reading the proposal my inital reaction was to support, but then I read the opposes here and changed my mind. The main argument that convinced me was Useight's point about WP:BLOCKNOTPUNITIVE. This seems like it would expand the block function into something punitive. I do think admins should be held to a higher standard than the average user, but I don't think an expansion of the block is the proper way to bring that about. Patr2016 (talk) 21:23, 18 April 2023 (UTC)
  • Support. An admin who is successfully blocked for an extended period almost certainly does not have the trust of the community that is supposed to be the basis for adminship. Contra the "blocks should not be punitive" argument, as User:HouseBlaster points out above, a long enough block could already result in a desysop for inactivity. This is exposing the same result in a shorter timeframe, which is justified for the reason I stated initially. --RL0919 (talk) 06:03, 19 April 2023 (UTC)
    The words "could" and "same" are doing a lot of heavy lifting in that sentence. I have quickly sketched out this process and the inactivity process (apologies if I missed some details) here. There is a scenario in which the result is the same (defined as an administrator being desysopped and requiring a new RFA to get the bit back), but not necessarily (hence the "could"), but it would essentially have to be a two-year block with talkpage access revoked in order to force the same result as this 28-day proposal could do. To be clear, I'm not arguing the merits of this proposal here (as I already have done above), nor the merits of the inactivity policy, as that is not relevant here. I'm asserting that insinuating that this proposal is more or less the same as the inactivity policy applying to a blocked admin, only shorter, is a disingenuous argument. Useight (talk) 15:41, 19 April 2023 (UTC)
  • Oppose as unnecessary and potentially harmful as a strict policy. Long-term or indefinite blocks of admins are fortunately very rare. The situations where they do happen, and the proposed policy would apply, are already drama-filled, and it is precisely for that reason that it is helpful to have someone like Arbcom reflect on whether continued admin permissions are warranted. I see lots of potential for additional drama from a policy like this one (e.g. keeping a user blocked past the time a block is needed to prevent disruption so that deadminning is triggered). I would support the community validating to Arbcom that admins engaging in behaviour that gets and keeps them blocked long-term is conduct unbecoming and grounds for desysopping, but given this is a rare occurrence I think the additional step of Arbcom weighing the desysop is beneficial and hardly a horrible additional workload. Bottom line: the *behaviour* that leads to a long-term block of an admin is likely grounds for desysopping, but that should be through normal channels for a conduct-related desysop (Arbcom) rather than "procedural". Martinp (talk) 17:41, 19 April 2023 (UTC)
    Added an alternative proposal relying on WP:LEVEL2 below. Martinp (talk) 18:12, 19 April 2023 (UTC)
  • Oppose in it's current form. This seems overly bureaucratic, and makes no mention of specifically being blocked for misconduct as opposed to something like a self-block to enforce a wikibreak or a circumstance where an appeal is ongoing (controversial ones can last longer than 28 days). I'll review the alternates below, but in general I'm opposed to this sort of "automatic" process for anything but housekeeping. The WordsmithTalk to me 18:26, 19 April 2023 (UTC)
  • Support - if blocked for that amount of time, indeed a desysopping is in order. Atsme 💬 📧 02:44, 20 April 2023 (UTC)
  • Oppose this specific policy implementation but not the general idea of such a process. Andre🚐 02:47, 20 April 2023 (UTC)
  • Support per Barkeep, Beeblebrox, et al. firefly ( t · c ) 08:27, 20 April 2023 (UTC)
  • Support - Recent months have highlighted again the need for some kind of community desysop procedure; while this proposal would not work for all situations, it is an improvement on the current situation. Fundamentally, an admin who has been and remains blocked for 28+ days is not a suitable person to be an admin. The worries about rogue blocks leading to desysops without community input do not worry me - I cannot imagine that one admin blocking another, especially for 28 days, would not makes its way to ANI almost immediately. I would be very happy to add a condition that if the community later overturns the block (as a bad block, rather than a "you've apologised and learned your lesson"), then admin rights can be restored. Equally, I would be happy to put in a hold condition that would pause the process if there is an active, ongoing review of the block. And waiving the procedure for non-bad behaviour blocks (self-requested, for example) would be fine too. WJ94 (talk) 09:19, 20 April 2023 (UTC)
  • Oppose as a solution looking for a problem. Stifle (talk) 10:14, 20 April 2023 (UTC)
  • Oppose a rare occurrence like this can be handle by ArbCom. Such a rule would encourage gaming the system (get a long block on an admin you don’t like to end them for good). Jehochman Talk 12:19, 20 April 2023 (UTC)
  • Oppose this is an overly baroque procedure. I'm supporting the alternate proposal instead. Jahaza (talk) 16:54, 20 April 2023 (UTC)
  • Support in cases where someone is blocked for that long they should almost certainly be desysopped. Any block like this would be subject to lots of community review anyway and I highly doubt it would be used just to desysop someone. Hut 8.5 18:20, 20 April 2023 (UTC)
  • Oppose as needless bureaucratic bullsnot to control the flow of power. Rules, restrictions, and more rules on top of more restrictions... This whole site creeps me the bleep out! Huggums537 (talk) 05:32, 21 April 2023 (UTC)
  • Oppose as pointless - blocking an admin for this period of time happens very rarely, and the one time it did happen (Athaenara) it wouldn't have helped as Arbcom was already pursuing a desysop long before it would have triggered. * Pppery * it has begun... 21:20, 21 April 2023 (UTC)
  • Weak oppose as I really like the sentiment of the proposal, but I think it would have the opposite of the intended effect. I'm really not worried about wheel warring or covert blocking, since any block of an admin is inevitably going to garner a lot of scrutiny. What I do worry about though is the impact this has on blocking admins. Either the potential desysop consequence is a factor in blocking a sysop, in which case the wonderfully uncontroversial question "have they done something desysoppable" would be introduced to the decision making process behind the block (and you can imagine how many admins want to make unilateral decisions on that). Or, the desysop sanction is not a factor, in which case a) said sanction is punitive, not preventative, and b) any admin that feels compelled to block another admin is opened up to immense drama and inevitable speculation over their motives. The drama that would likely come with a blocked sysop today is already big, and I don't think raising the stakes and adding a timer and an ultimatum on whether to unblock would be an improvement. Giraffer (talk·contribs) 14:30, 22 April 2023 (UTC)
  • Oppose There's too many potential negatives to this, and the reality is the number of cases it could possibly address are vanishingly small, if they exist at all. I don't see a need for more instruction creep to deal with a non-existent problem. --Hammersoft (talk) 17:01, 23 April 2023 (UTC)
  • Weak support My first thought was 'oh, what if it was a bad block?' and some protection needs to exist for that. Also, my second thought was 'let's just block someone for 28 days and there they go, desysopped!' with the intention being the secondary and not the primary...'oh look, 28 days? Desysop!!'. Nonetheless, I hope common sense will be applied to this proposal, as it will make desysopping quicker in some cases when it needs to be. Obviously, an indef block of an admin means goodbye admin rights. That's pretty clear cut. talk to !dave 12:54, 24 April 2023 (UTC)
  • Weak Oppose - kill the "On the first day of the month" part, if this is going to happen it shouldn't be pegged to a specific day of the month, should just be rolling like everything else in the admin policy. (Now, if it in practice happens a bit late sometimes - no big deal, but if the processor is late and the block has already lapsed then it shouldn't be done either....). In short, this sets up yet another pile of bad timing issues that like to find their way in to the admin policy, cause headaches, and need to eventually be repaired. Try again, — xaosflux Talk 22:54, 24 April 2023 (UTC)
  • Oppose mainly per TonyBallioni's lengthy oppose and Stifle's pithy one.--Bbb23 (talk) 23:12, 24 April 2023 (UTC)
  • Support this with reasonable exceptions as needed, and also support TonyBallioni's proposal. – John M Wolfson (talk • contribs) 23:30, 24 April 2023 (UTC)
  • Oppose - Can't see how this is needed or useful. Paul August ☎ 23:34, 24 April 2023 (UTC)
  • Support - very reasonable.--Dl.thinker (talk) 23:47, 24 April 2023 (UTC)
  • Oppose per Stifle who beat me to it. This is a solution in search of a problem. I have confidence that if an admin has been blocked for good cause that the matter will be handled by ARBCOM where they would also have at least an opportunity to present their side rather than being automatically punished in contravention of the community's blocking policy. See also WP:CREEP. -Ad Orientem (talk) 00:58, 25 April 2023 (UTC)
  • Oppose grave punishment done mechanically without deliberation. Lokys dar Vienas (talk) 04:06, 25 April 2023 (UTC)
  • Oppose Per Seraphimblade. A month gives plenty of time for Arbcom to sort things out, and if they can't handle desyops in that time, why do we have an Arbcom again? Jclemens (talk) 04:14, 25 April 2023 (UTC)
  • Oppose both per WP:BLOCKNOTPUNITIVE and per CaptainEek's "just because someone's been in jail for a month doesn't mean they're guilty" argument. I'd support a separate community desysop procedure, but would not support automatically tying it to a block. Loki (talk) 23:53, 24 April 2023 (UTC)
  • Oppose Classic solution in search of a problem. What problem are we trying to solve here? How many times has an administrator been legitimately blocked for 1+ months and didn't subsequently lose the tools? More needs to be done to better define the problem to be solved by this proposed policy change, so that we can gauge whether this is the best solution to that problem. As it stands, the proposed solution is somewhat bizarre, e.g. having it tied to the first day of the month. —⁠ScottyWong⁠— 04:50, 25 April 2023 (UTC)
  • Oppose; the ArbCom exists to deal with these matters. The proposal as written fails to exclude no-cause self-blocks and self-requested blocks. The proposed process could easily be gamed. Sending desysop proposals though the ArbCom avoids gaming and less-than-desirable behavior like pile-ons and partisan !votes at dramah boards. See also WP:CREEP. Baffle☿gab 05:46, 25 April 2023 (UTC)
  • Oppose; sounds good on paper, but it just means that admins are able to desysop each other, and given ArbCom exists to deal with these sorts of matters, why don’t we just leave desysops to them. Zippybonzo | Talk (he|him) 06:16, 25 April 2023 (UTC)
  • Oppose: I've worked at CAT:RFU and introduced a category for idle unblock requests because of the overwhelming amount of unblock requests in the queue that needed some kind of sorting. Even with these, currently 31, idle unblock requests taken out of the main category, there remain 96 open unblock requests as of now. A noticeable amount of these won't reach a decision within the next 28 days, so I'm not sure which allegedly reasonable source that number of days comes from. I'm unhappy with the assumption that an admin's unblock request will surely be handled quicker than the others, skipping the queue as an implicit necessity codified into the desysop procedure. ~ ToBeFree (talk) 06:51, 25 April 2023 (UTC)
  • Oppose we already elect Arbcom to desysop admins when necessary. Re this specific proposal, the only admin who would have been caught by this in recent years was someone requesting a block to enforce a wikibreak. I don't think that we should discourage such wikibreaks in this way, or more likely create huge ANI debates about the blocking of admins who could be more quickly, fairly and less dramatically reviewed and if necessarily desysoped by Arbcom. I'm also concerned that this raises the stakes when blocking admins, especially thirty day blocks in the last couple of days of the month. I think that if anything we should try to reduce the stakes re the blocking of admins, an admin should be blocked in a situation where a non admin would be blocked. ϢereSpielChequers 06:57, 25 April 2023 (UTC)
  • Oppose. A solution in search of a problem. There is absolutely no evidence that we have a significant number of admins who get blocked for an extended period of time without being desysopped by Arbcom. Moreover, as noted above, this proposal, if implemented, would significantly raise the stakes for blocking an admin. That would increase the amount of drama and gamesmanship surrounding such blocks and likely make such blocks more difficult to impose in practice. Nsk92 (talk) 08:23, 25 April 2023 (UTC)
  • Oppose Reading through all the arguements above, Sandstein's was the most persusaive. The Squirrel Conspiracy (talk) 09:56, 25 April 2023 (UTC)
  • Support We say that being an administrator is "no big deal," but as soon as a proposal comes up to remove administrators, it suddenly is a very big deal and administrators circle the wagons. This is a very reasonable idea. Figureofnine (talk • contribs) 12:11, 25 April 2023 (UTC)
  • Oppose per Sdrqaz and The Wordsmith. OhanaUnitedTalk page 13:19, 25 April 2023 (UTC)
  • Oppose, at least in current form. I think there's an unacceptable level of arbitrariness in this design. First, based on the votes, I now understand that "has been blocked for 28 days" refers to the the number of days the admin has been blocked as of the first of the month, not the total length of the block, as the buffer is meant to ensure an appeal is possible. But—and I concede it's possible I'm missing something big about how block timing works—doesn't that create chaos? Consider a user blocked for 1 month (or, hey, 30 days) at any point between April 3–29. By the first of the month, that user will not have been blocked for 28 days. Even if the user is blocked for 5 weeks on April 10th, they will not be subject to this sanction. But a user blocked for 1 month on, say October 2nd will have privileges stripped, because, by November 1, the user will have been blocked for 28 days.--Jerome Frank Disciple (talk) 13:55, 25 April 2023 (UTC)
  • Support per Ritchie333. Inevitably, this procedure will have growing pains and problems. However, refinement requires testing and this is a very reasonable proposal. ~ Pbritti (talk) 17:49, 25 April 2023 (UTC)
  • Oppose. This is a solution looking for a problem. If an administrator truly needs to be blocked longer than a couple days, I would expect an WP:ARC request to be filed well before the 28-day period is up. Recent examples have demonstrated that ArbCom is perfectly capable of expeditiously desysopping administrators in less than 28 days where necessary. For example, see
    1. Special:PermanentLink/1149026678#Dbachmann, in which ArbCom summarily desysopped an administrator (who was not blocked) after only 8 days of discussion, and
    2. Special:PermanentLink/1116499056#Athaenara, in which ArbCom summarily desysopped a blocked administrator after only 34 hours (see [4] for the desysop motion)
  • Essentially, with the threshold set at 28 days, this will result in no tangible change to the current process, which is already quite efficient. Mz7 (talk) 21:22, 25 April 2023 (UTC)
  • Support Though i don't care for the bureaucratic portion of it ~ on the first, twentyeight days... ~ which seem somewhat open to misinterpretation or abuse, it is a positive step towards a proper community de-admin process, and very clearly any admin who's been blocked for that long has lost the trust of enough of us that they shouldn't be adminning any longer. Happy days, ~ LindsayHello 21:43, 25 April 2023 (UTC)
  • Support- if an admin is blocked for that long, it means they must have done something very wrong. Admins who get such a long block should not be admins after all as they have broken Wikipedia policies to a serious extent. 747pilot (talk) 01:39, 26 April 2023 (UTC)
  • Support This seems like a reasonable policy. Martindo (talk) 06:59, 26 April 2023 (UTC)
  • Oppose Is there a problem with the current desysop procedure? Arbcom seems to desysop problematic administrators just fine. Lightoil (talk) 08:34, 26 April 2023 (UTC)
  • Conditionally support if this can only occur where there are no ongoing appeal actions. Peacemaker67 (click to talk to me) 09:07, 26 April 2023 (UTC)
  • Support as a stopgap between leaving problematic admins with the tools and having to wait months for ArbCom to handle the matter. Anarchyte (talk) 12:40, 26 April 2023 (UTC)
  • Oppose The fact that an editor is blocked, does not automatically mean that he is not fit to be an admin. Sometimes it does, sometimes it doesn't. Therefore, this must be decided on a case-to-case basis, without any fixed procedures. Debresser (talk) 12:58, 26 April 2023 (UTC)
  • Support Perhaps it's pointless, but I have a really hard time seeing how it could be a net negative. ᴢxᴄᴠʙɴᴍ (ᴛ) 13:45, 26 April 2023 (UTC)
  • Oppose as written. Firstly, per Jayron32, there seems to be no actual problem that this would address. Secondly, the block tool is preventative and used to prevent ongoing disruption. This is mostly unrelated to reasons why an admin should be deadminned, and would muddy the waters — Martin (MSGJ · talk) 13:47, 26 April 2023 (UTC)
  • Support – I note that some opposing arguments state that blocking doesn't automatically mean that removing the bit is necessary. I concede that point, but I also note the length of block required for this to become relevant. ANYONE who has been blocked for 28 consecutive days has shown to this community that their trustworthiness is questionable at best. While beyond the scope of this RfC, I would also support that, in addition to Administrators, all extended permissions – viz. CheckUser, Oversight, Bureaucrat, and anything granted at WP:PERM – should be automatically rescinded if that user has been blocked for 28 consecutive days. I've seen rather egregious conduct be met with blocks of only a few days, so for a 28-day block to be levied then someone really WP:DONTGETIT. — Jkudlick ⚓ (talk) 20:52, 26 April 2023 (UTC)
  • Oppose I appreciate the intention in the proposal but I'm concerned with the aspect for creating higher level drama among individuals rather than solving an apparent, existing structural problem. Regards, --Goldsztajn (talk) 23:32, 26 April 2023 (UTC)
  • Oppose. The intent is good, but the procedure is poor. It creates unnecessary tensions among administrators and we have a regular procedure for desysopping via Arbcom which should be respected. In addition, 28 days may just be too short a period to appeal. --TadejM my talk 16:10, 27 April 2023 (UTC)
  • Support. Just about any proposal that makes it easier to get admin tools out of the hands of those who abuse them gets my support. The scenarios suggested in the oppose !votes where this causes problems are largely implausible. —swpbT • beyond • mutual 17:47, 27 April 2023 (UTC)
  • Weak support. I am not sure how often administrators block each other. If an administrator gets blocked, it should be serious enough to not only warrant a block but to warrant removal of administrator privileges. Samuel R Jenkins (talk) 04:32, 28 April 2023 (UTC) Blocked sock. NmWTfs85lXusaybq (talk) 03:43, 1 May 2023 (UTC)
  • Oppose I agree that the community needs a de-sysop procedure, but this is not it. This could make block of less than 50 days become somewhat of a Russian Roulette for whether they stay an admin. Furthermore, this is hardly a "community procedure" since only other admins can block admins. We need a system, but not this one. QuicoleJR (talk) 16:19, 28 April 2023 (UTC)
  • Support per Beeblebrox and Ritchie. Admins must have the confidence of the community, so it makes sense for their bit to be subject to community consensus, rather than needing to rely on ArbCom. Also agree with others that the risk of stealth desysops is very low; and anyway, that would itself be an ADMINCOND issue. DFlhb (talk) 19:24, 28 April 2023 (UTC)
  • Support if nothing else. I think this is a poor solution, but any form of community desysop is better than nothing... CLYDE TALK TO ME/STUFF DONE 21:17, 28 April 2023 (UTC)
  • Oppose per QuicoleJR. And WP:CREEP. This adds more procedural layers, while lacking clarity for implementation E.g., the faulty 1st of the month element. Something much simpler might find consensus. Pechmerle (talk) 05:53, 29 April 2023 (UTC)
  • Weak support I have concerns around mobbing but also if someone has that kind of ban they shouldn't be an admin UNLESS there is some sort of reasonable reason. Dr vulpes (💬 • 📝) 06:03, 29 April 2023 (UTC)
  • Weak oppose. It just seems like a lot of clean up when they should've had their admin rights removed as part of the block. I do agree with the proposal but not the process. Any admin who's worthy of a block should be desysopped automatically, and if they want their rights back, a community review should be conducted. Callmemirela 🍁 talk 14:48, 29 April 2023 (UTC)
  • Oppose Too many weird edge cases in this proposal, as already well described by others. Anomie⚔ 14:56, 29 April 2023 (UTC)
  • Oppose too much of a catch all such as admins blocked for a wiki break. Also desysops should not be automatic in my view, each one needs proper consideration, Atlantic306 (talk) 20:03, 29 April 2023 (UTC)
  • Support – This is a "Like, duh!" proposal, so of course it's opposed. Welcome to Wikipedia. --IJBall (contribs • talk) 00:16, 30 April 2023 (UTC)
  • Support. It seems like a waste of ArbCom's time when there is a snowball's chance in hell that a blocked editor deserves to be an administrator.  — Freoh 12:11, 30 April 2023 (UTC)
  • Weak Oppose In theory this could be good (say, someone gets radicalized into being a QAnoner or Anti Vaxxer on YouTube and that becomes their new activist cause for the site). However, I worry ArbCom in the end will value civility over all else and this will heighten demographic disparities in administrators. People of color, women, and queer people are more likely to be seen as incivil and I can easily conceptualize perma-bans from administration resulting in an even higher proportion of straight white men determining who is write or wrong at ArbCom, which already has documented troubles with arbitrating contentious topics related to race, gender, and sexuality.Computer-ergonomics (he/him; talk; please ping me in replies ) 12:56, 30 April 2023 (UTC)
  • Oppose Needlessly bureaucratic and WP:CREEPy. Some1 (talk) 14:03, 30 April 2023 (UTC)
  • Support, but what is who is blocked and has been blocked for more than 28 days? What happens if your block lasted more than 28 days but expired on say 5th of the month? Then you escape removal in the current cycle because it is not yet 28+ days, but in the next cycle, you won't fulfil is blocked requirement and won't be removed despite being blocked for 28+ days. I think is blocked is unnecessary. If you were blocked for 28+ between previous and current cycle, you should be desysoped. AhmadLX-(Wikiposta) 16:38, 30 April 2023 (UTC)
  • Oppose. The proposal is plausible enough on its face. But having read through all of the arguments above, nobody seems able to articulate an actually-existing problem that this would solve. Further, quite a few people have noted problems that this proposal would be likely to create. This is a narrow enough circumstance that the impacts would be limited, but given the risk of harm to the project and the lack of any clear benefit, it seems best to leave this sort of rare edge case to be handled on a case-by-case basis. -- Visviva (talk) 23:57, 2 May 2023 (UTC)
  • Oppose for basically the same reasons as Visviva.-- Aervanath (talk) 10:05, 3 May 2023 (UTC)
  • Support: Not the first time Tony's comments have been the pivot upon which consensus might swing, but while I don't really disagree with his statements (and also note Galobtter's fair points about "not community"), I still basically take the Moneytrees approach here: it's barely anything so at least it's something. If it were to go, I'd prefer clarity that it's considering full blocks not partial blocks. ~ Amory (u • t • c) 12:26, 3 May 2023 (UTC)
  • Oppose - This seems to create more problems than it solves. If the problem is untrustworthy admins, then giving admins the power to effectively de-sysop each other by imposing 28 day blocks seems to exacerbate the problem. Admittedly there could be a review, but I am not sure how well that would work. Rlendog (talk) 14:20, 3 May 2023 (UTC)
  • Support but enforcement should consist of removing admin rights on day 28. Aasim - Herrscher of Wikis ❄️ 15:08, 3 May 2023 (UTC)
  • How often does this happen? Guy (help! - typo?) 17:11, 3 May 2023 (UTC)
  • Weak oppose. Add me into the column of respondents who think we are long overdue to establish some sort of broad community based desysop process, but who view this particular proposed solution to be far too awkward, unnesesarily indirect, and likely to prove prone to numerous problematic knock-on effects, several (but probably not all) of which have been identified above. Personally, I would advocate that we simply create a process for a discussion and direct community !vote (presumably to be typically conducted at ANI like msot CBANS), with an atypical requirement that there be a certain advisory threshold for minimum number of participants and minimum proportion of support perspectives, so that any communty desysop has some degree of rough parity with the volume of community will expressed through RfA itself. I don't really see the need for a more complicated process or more involved criteria than that: so long as there is a relatively high burden of required support baked into the policy language that describes this process, the community should be able to handle these exceptional cases through the same open-discourse and proposed sanctions methodologies with which it handles any other claims of serious misconduct. SnowRise let's rap 02:04, 4 May 2023 (UTC)
  • Oppose. Solution in search of a problem that also has the potential to create new problems. The minimal benefit does not outweigh the risks. T. Canens (talk) 03:50, 4 May 2023 (UTC)
  • Weak support - I'm fine with the principle but share the concerns of User:BilledMammal and User:Xaosflux about limiting implementation to the first day of the month. My preference would be not to specify that in the policy. Procedurally that could mean automatic implementation on the first day of each month, but that bureaucrats could also desysop blocked admins meeting the criteria manually at any time. The scenario User:BilledMammal outlined indicates why limiting implementation to one day a month is a bad idea. WaggersTALK 07:29, 4 May 2023 (UTC)
  • Support – in general I support making it easier to revoke adminship. That brings us closer to the ideal of adminship being WP:NOBIGDEAL, which will hopefully make it easier to increase the number of new admins. —Mx. Granger (talk · contribs) 13:18, 4 May 2023 (UTC)
  • Support, although I don't really see this as a community desysop procedure in the sense of "something done by the community", I don't see how an admin subject to a long block, not overturned, for a month can be considered to hold the confidence of the community. In any case, as the proposal currently stands, there are sufficent avenues of appeal. Alpha3031 (t • c) 11:13, 6 May 2023 (UTC)
  • Oppose Needs to be after any length block (subject to any appeals over the block). Only in death does duty end (talk) 11:37, 10 May 2023 (UTC)
  • Support – any admin blocked for that long should not be an admin. Ritchie's point an appealing is also particularly convincing. Aza24 (talk) 05:37, 11 May 2023 (UTC)
  • Oppose per Tony. "Community desysop" should−explicitly and without exception−require community consensus. —Rutebega (talk) 19:44, 11 May 2023 (UTC)
  • Support, though not an admin, my beliefs are the same as RickinBaltimore. InvadingInvader (userpage, talk) 04:15, 12 May 2023 (UTC)
  • Weak oppose – no need for a procedural desysop here, in my opinion. Editing your own talk page while blocked should not count as an edit for postponing the year-long desysop, however. Skarmory (talk • contribs) 23:56, 12 May 2023 (UTC)
  • Weak oppose mostly because this feels like instruction creep. It sounds like this might unintentially apply to self-blocked admins taking a break and would only truly apply to a few people (per BilledMammal conversation). Darkfrog24 (talk) 01:17, 13 May 2023 (UTC)

Discussion (Proposal: Procedural community desysop)

The concern I have with Arbcom is that it is such a long-drawn out process, that it burns out the people who are participants in a admin conduct related case, that they'd rather quit Wikipedia than stick it out. So we not only lose an admin, we lose an editor. Kudpung and RexxS are the most obvious cases I could think of, and it's just possible, perhaps, that a 48 hour civility block on either could have stopped them from quitting, addressed the complainants' concerns somewhat (for example, it's not a WP:SUPERMARIO if they get blocked, and a block removes immediate disruption and defuses situations in a way a long Arbcom case can't) and allowed them to hold on to their admin bit. Ritchie333 (talk) (cont) 15:52, 17 April 2023 (UTC)

"Administrators must be held accountable. But this is not the answer." This is pretty much why we don't have enough accountability, because too many people oppose the specific proposal over supporting the general concept. So nothing ever happens. Ritchie333 (talk) (cont) 16:31, 17 April 2023 (UTC)

(Since I'm being quoted) Ritchie, this isn't an enemy-of-the-good situation for me. If I thought the proposal would have a neutral effect, or a tiny positive one, or maybe even a negligible negative one, I wouldn't have opposed. My issue with the proposal is that it makes things worse, and that we are choosing to do something because it is something rather than because it's a positive change. As I explain above, I believe that it worsens accountability. Sdrqaz (talk) 02:02, 18 April 2023 (UTC)

I somewhat like this idea, but don't think I can support without a distinction between "for-cause" blocks and other ones. While it's rare for an admin to be blocked at length as a not-for-cause matter, I recall someone self-blocking a few years ago due to a family emergency, although I can't recall who at the moment. I would suggest adding for misconduct after the words who is blocked; I think it will be pretty straightforward for the bureaucrats to sort out the difference between "admin X is indeffed for repeated copyright violations" and "admin Y is indeffed with summary 'requested some time away from Wikipedia'". I also would rather this say something to the effect of and has no pending on-wiki appeals, although I tend to agree with Ritchie that after 28 to 59 days, things have probably shaken out. -- Tamzin[cetacean needed] (she|they|xe) 16:32, 17 April 2023 (UTC)

For self-requested blocks, I think it would reasonable to relinquish administrative privileges at the same time. As a voluntary removal of permissions, the editor would be able to request to have them returned without having to go through a request for administrative privileges discussion. isaacl (talk) 18:26, 17 April 2023 (UTC)

One general issue is that our desysopping methods are already working better than our sysopping methods, so making additional desysopping methods (with no evidence that the current ones are insufficient) looks to me like working on the wrong problem. —Kusma (talk) 16:56, 17 April 2023 (UTC)

I choose to take that remark as a compliment. However, I don't think it is as much a matter of being insufficient as it is being unnecessary. Again and again when wayward admins are brought before the committee, they simply shut down and refuse to present a defense. So, the committee has been doing things like opening cases but suspending them for a few months, with the admin in question being temporarily desysopped unless and until they indicate a desire to open the case. To date, no admin has chosen the option of a full case when presented with such a choice. So, those admins do get removed, after 3-6 months, providing somebody remembers to actually close the case when it is supposed to close, which failed to happen at least twice in the last few years. This is simpler, faster, and presents pretty much the same choice to the admin: show up and present a cogent defense, or don't and let your admin tools go. Beeblebrox (talk) 17:08, 17 April 2023 (UTC)
I would note that as of this edit, among current or past arbs 5 support and 1 opposes. It's possible that "our desysopping methods are already working better than our sysopping methods" can be true but more because our sysopping methods are so broke that the desysopping looks good by comparison. Best, Barkeep49 (talk) 18:14, 17 April 2023 (UTC)
Recent for-cause desysops were handled quickly and with a comparably low amount of noise. I expect that there will be more noise under the proposed system, just less paperwork for ArbCom. —Kusma (talk) 18:52, 17 April 2023 (UTC)
I don't know. I feel like all of the recent admin arb cases, minus Jimmy's, had lots of community noise before and after it reached the case request stage. Best, Barkeep49 (talk) 20:02, 17 April 2023 (UTC)
In the Athaenara case, probably the desysop under this proposal would have gone through, but the block/unblock chaos might have been worse with blocks automatically meaning desysops. In the Geschichte case, if the community had had the tool of desysop-via-60-day block, it is anyone's guess how the epic ANI discussion would have played out, but I do think we'd have had more noise. —Kusma (talk) 21:21, 17 April 2023 (UTC)

"A blocked admin can't (since 2018) unblock themselves, and if they're blocked indefinitely, they'll just be auto-de-adminned when the time comes around." They are still able to edit their talk page and file an unblock request. This'll probably result in an ANI thread like this: "Hi, I just blocked admin X for edit warring and personal attacks, they're not admitting fault and threatening to block the other party in the dispute, can we review the block?" Or even, "Hi, I've indeffed Jimbo Wales as they've just blocked 3 arbs indefinitely; it clearly looks like their account is compromised". It'll get a response. If they're not prepared to file an unblock request, either they've got ANI flu and given up, or they think blocking is for the "little people" and not them, in which case they shouldn't be an admin. Ritchie333 (talk) (cont) 17:45, 17 April 2023 (UTC)

  • Question: So, I have been doing some thinking on this beyond my initial oppose vote. What I want to know is what existing ongoing problem is this supposed to solve? Which is to say, what are some examples of blocked admins who got to keep their tools after being unblocked, and for which this process would have taken the tools away? It feels like a solution in search of a problem, at this point. I mean, unless someone can actually point to this being a problem (and I don't mean "one isolated case", I mean "an ongoing issue that keeps biting us in the ass"), then I really fail to see why we're going through the trouble to create a new policy. Can anyone in support of the policy provide evidence that this is a problem that needs new policy to fix? Examples, evidence, etc? --Jayron32 17:40, 17 April 2023 (UTC)
    The principal problem, as Beeblebrox said, it is it stops putting an unnecessary workload on Arbcom. It's a bit of an old example, but Wikipedia:Arbitration/Requests/Case/Neelix comes to mind. After the mass-creation of puerile redirects were discovered, he could have been blocked (to prevent any more being created) until the community could work out what to do. The community could have decided to site ban Neelix. But he was an admin, so Arbcom had to get involved, wasting everyone's time as I think there was near unanimity that Neelix should have been sanctioned. Ritchie333 (talk) (cont) 17:49, 17 April 2023 (UTC)
    You've asserted that it is "unnecessary workload". If your only example is a singular 8-year-old arbcom case, that's pretty flimsy in terms of necessitating a new policy. I think ArbCom can handle one such case every decade or so. Doesn't seem to me like "unnecessary workload". I ask again, what is the evidence this is needed? --Jayron32 17:53, 17 April 2023 (UTC)
    Also, I note that your best example was an ArbCom case that was resolved in 3 days. Replacing a process that takes 3 days with one that takes 28 days is somehow more efficient? --Jayron32 17:55, 17 April 2023 (UTC)
    It was the first example I could think of, and one of the most memorable, but by no means the only one. For example, Carlossuarez46 could have been blocked for personal attacks, or Athaenara could have just been indeffed for hate speech and left as is. Also, it might be worth comparing the 3 days with the amount of text that was generated, and from how many users - also, it's worth remembering that it only took 3 days because Neelix resigned his tools with a pledge he would not get them back with a new RfA. Ritchie333 (talk) (cont) 17:59, 17 April 2023 (UTC)
    Again, hardly a major issue. The memorable cases are memorable because they are so rare. We don't need to write new policy for cases spaced out over several years. You claim to be saving ArbCom work; have they asked the community for this help? Also, people are free to contribute to discussions as they see fit. I could equally claim that the amount of text this discussion has generated is out-of-proportion for the magnitude of the problem it proports to solve, which makes it worse than the problem it is trying to solve. I'm just saying that if you want more support for a proposed overhaul of policy, you've not shown how it is needed. A few isolated, weird cases have been shown. We don't have an epidemic of blocked-but-still-can-use-their-tools admins now, do we? If this were happening 3 times every 8 weeks or even 8 months, I'd think we have a problem. 3 times in 8 years seems hardly worth creating a policy over. --Jayron32 18:14, 17 April 2023 (UTC)
    If in practice the community has considered being blocked incompatible with having administrative privileges, then codifying this shifts discussion from the majority of cases where this view is held to those where exceptional circumstances may alter the community's opinion. This should be a net reduction in discussion (of course provided the initial inference on the community's view on blocked admins is true, which this RfC seeks to establish). isaacl (talk) 18:07, 17 April 2023 (UTC)
    How often are admins blocked? There's no need to create a policy to deal with a rare event. --Jayron32 18:14, 17 April 2023 (UTC)
    Sure, I often agree with that view. We'll see if the community thinks it's a net positive to explicitly state the incompatibility versus handling it each time it comes up. isaacl (talk) 18:41, 17 April 2023 (UTC)
    It's rather hard to query, because the database doesn't give an easy way to check whether user X was an admin at time Y, but for a mostly-complete set, combine quarry:history/65830/669690/650357 for current admins who've been blocked (mostly accidents/testing, with false positives for users like me who were blocked pre-adminship), the "Blocked or locked" sections of WP:FORCAUSE, Wikipedia:Former administrators/reason/resigned for past admins who are currently blocked (with false positives for post-desysop blocks), and Wikipedia:Former administrators/reason/compromised and "compromise" entries in WP:RESYSOPS (where I think everyone is or was once blocked); these miss most cases of blocked-then-deysopped-then-unblocked (but there's only one of those every few years) and blocked-then-unblocked-then-desysopped (but those are likewise mostly accidents/testing, with unrelated desysops). To my knowledge, prior to Athaenara, the last admin to be indeffed for cause as a regular admin action (i.e. not CUblock/ArbComBlock) and then get desysopped was Craigy144 in 2010—copyvio block, desysopped as unresponsive to ArbCom. There's several more recent blocks-then-desysops for compromise, with or without later unblock and/or resysop. -- Tamzin[cetacean needed] (she|they|xe) 19:01, 17 April 2023 (UTC)
    @Tamzin: Fred Bauder was indeffed as a normal admin action by FPAS in 2018 for edit-warring and subsequent wheel warring. Maxim then removed the sysop flag as a unilateral emergency 'crat action (for violating WP:NEVERUNBLOCK/WP:WHEEL) shortly thereafter.
    There's a couple other indeffs done as normal admin actions that post date that of Craigy144 though none of them ended up lasting all that long, and thus were not the proximal cause of ARBCOM action, although in some of those cases they were part of the pattern that resulted in a later ARC and subsequent desysop. 74.73.224.126 (talk) 00:59, 9 May 2023 (UTC)
    @Jayron32:, you are right. This would probably apply about once every 5 years and won't affect Arbcom workload. But it's safe. Sort of like saying that if it it's found that somebody can't do basic addition (2 + 2 = ?) that we take away their math teaching position. North8000 (talk) 20:27, 17 April 2023 (UTC)
    @Jayron32, @North8000: The question is whether blocks of admins will remain rare if they have the option of turning into "community" desysops. —Kusma (talk) 10:33, 18 April 2023 (UTC)
    @Kusma: Good question. My guess is that that wouldn't happen. Basically a complex effort of a group of people mis-using the system to "get" an admin. But maybe a reason to avoid enacting something like this that really isn't going to serve a purpose. North8000 (talk) 13:39, 18 April 2023 (UTC)
    The Neelix case took four days. Guy (help! - typo?) 17:17, 3 May 2023 (UTC)

Regarding the concern that the proposal allows a single admin to block another, triggering a community discussion that may lead to the removal of administrative privileges: note unilateral blocks can only be enacted for edits related to contentious topics, enforcing specific arbitration remedies that authorize blocks, or for flagrant policy violations. An appeal of a block not meeting these conditions should be upheld, and the community can then decide if any further discussion of the situation is warranted. In essence, the same discussions that would occur today would still occur under the proposed change, with an added implication that being blocked is incompatible with holding administrative privileges. isaacl (talk) 17:50, 17 April 2023 (UTC)

It might be a good idea to have someone set up a bot to notify WP:AN whenever an administrator is blocked. Obviously it's pretty unlikely that such a block would slip under the radar for 28+ days, but if that notification would help reässure anyone that this proposal wouldn't be desysopping people under cover of darkness, it'd be a positive. Extraordinary Writ (talk) 18:08, 17 April 2023 (UTC)

Note the actual removal of privileges would not happen in the dark, and any unwarranted stealth blocks is going to be noticed when the list of blocked admins is prepared. So while it may be a good idea to have a bot update a page with a query of the list of blocked admins that can be transcluded elsewhere (or some other implementation), I don't think it's critical for this proposal. isaacl (talk) 18:38, 17 April 2023 (UTC)

This proposal does not require the community to weigh in in any way - it does not require the block to be reviewed or upheld. This is for obvious reasons: blocking an admin should in theory not be any different than a non-admin. But it at the same time relies implicitly on, and quoting the proposer himself, the assumption that "A block of an admin would be reviewed by the community". So I think it threads the needle of not explicitly making blocking admins different but in practice requiring community review of every long block of an admin (with the caveat that this will probably happen regardless of this proposal). In short, I'm not sure a proposal that explicitly required community review of the block would pass, but this proposal is functionally that. Galobtter (talk) 19:42, 17 April 2023 (UTC)

If blocking an admin results in de-adminship, then we will stop even pretending to treat blocks of admins the same as blocks of non-admins. WhatamIdoing (talk) 21:09, 17 April 2023 (UTC)
@WhatamIdoing FWIW, from a technical standpoint it effectively does.
While blocked the only logged action a blocked admin can perform is to block the admin that blocked them. SQLQuery Me! 23:10, 17 April 2023 (UTC)
Adding: Apparently you can't see deleted revs but can still see private abusefilter hits while blocked. SQLQuery Me! 23:18, 17 April 2023 (UTC)
But that "de-adminship" is automatically temporary. If you were blocked, you would still be an admin when the block expired. This is not what's proposed here. This proposal says: If you can get an admin blocked on January 3rd, for any reason, and it's not lifted before February 1st, then that admin will be permanently de-sysopped, even if the block is set to expire on February 2nd. WhatamIdoing (talk) 00:46, 18 April 2023 (UTC)
I am not sure if this has been considered. But since I found a discussion on desysopping, I bring it on. In the past I have observed two desysops not so much related with their sysop activity but with their views. I'd support a process where a sysop can be desysopped for their actions not so much for their views (they expressed some years ago). To desysop one for a few phrases in a little venue, when they had a tenure for several years...Have you considered to bring the desysop process before the community like the RfA?Paradise Chronicle (talk) 10:22, 25 April 2023 (UTC)

Clarification sought, in three scenarios:

  • Admin A is blocked for 50 days on 10 July. On 1 August they haven't been blocked for 30 days yet so retain the mop. On 1 September they're no longer blocked, so retain the mop. Correct? That would seem to go against the proponents who argue that a 30-day block is a bad enough sign that the comunity no longer trusts A.
  • Admin B is blocked for 40 days on 2 October. Drama ensues and a friendly (to B, anyway) Admin C unblocks Admin B in good faith, as C feels the block was inappropriate. A scant 23 minutes later after some testy posts at AN/I, Admin D reinstates the block, which holds. On 1 November, the review shows that B was not blocked 30 days and so retains the mop.
  • Admin F is blocked for 30 days on 1 May. On 1 June, F is no longer blocked and so retains the mop. (The obvious "lucky timing" case.)

Is this the correct understanding of the proposal as written? — JohnFromPinckney (talk / edits) 21:24, 19 April 2023 (UTC)

Tweak based on comments made: "On the first day of the month, any administrator who is blocked and has been blocked [for cause] for more than 28 days [in the preceding two months] will have their administrator user-right procedurally removed (alongside inactivity removals)." SilkTork (talk) 08:39, 25 April 2023 (UTC)

SilkTork, do you mean to propose (as I think you might) ...for a total of more than 28 days...? That is, it could have been three separate blocks, yes? — JohnFromPinckney (talk / edits) 09:21, 25 April 2023 (UTC)
The convenience of routine software "housekeeping" functions does make this proposal seem awkward to implement. I suggest a shorter time limit, say 17 days of *consecutive* block, regardless of what happens between day 17 and the start of the subsequent month. I recommend 17 because it includes 3 full weekends, allowing for variations in time zone. Martindo (talk) 07:03, 26 April 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Alternate proposal (Procedural community desysop)

SUCCESSFUL
There is a clear consensus to overturn Wikipedia:Requests for comment/User rights of (site) banned users and remove the userrights (including +sysop) of any editor banned by community consensus. — Wug·a·po·des 20:44, 18 May 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Let's simplify this, and align it with current policy and process.

If an editor is banned by the community (not merely blocked), their granted permissions - including but not limited to admin tools - are removed. And even if the editor successfully appeals the ban and returns to editing, they will need to re-apply through the typical processes (such as WP:RFA) to regain any removed granted permissions.

(This is for an indefinite, full ban only, not a limited, topical, or partial one.)

In the rare instance where the ban is reversed due to a mistake by the community (but not merely due to a successful appeal of the ban), then said removals are reversed as well. - jc37 08:28, 18 April 2023 (UTC)

Survey (alternate community desysop proposal)

  • Support I see no reason that this is mutually exclusive from the other proposal, but I do support this. If a site ban passes on an admin, they should no longer be an admin. WormTT(talk) 08:40, 18 April 2023 (UTC)
  • Support I support this. It is reasonable and a step even further in the right direction, with respect to having community say in desysops without forcing Arbcom involvement. I would like to also see non-ban related proposals for desysops, but those can wait for a more future time Soni (talk) 08:43, 18 April 2023 (UTC)
  • Support, that is fine (assuming ban means "site ban" and doesn't include any interaction bans). This would have worked in the Athaenara situation and would not have been discussed in the Geschichte case. —Kusma (talk) 09:28, 18 April 2023 (UTC)
  • Support as above Ritchie333 (talk) (cont) 10:21, 18 April 2023 (UTC)
  • Support per WTT. Thryduulf (talk) 10:35, 18 April 2023 (UTC)
  • Support Seems much more reasonable than the first proposal. If someone has lost the community trust to the point where a community discussion has led to a community ban, that should implicitly imply that such a person has lost enough trust to lose the tools. The first proposal leaves too much on a single, possibly time-limited block, it puts too much in the hands of a single individual. --Jayron32 11:42, 18 April 2023 (UTC)
  • Support - this is probably the only community decision which is so extreme that it would never occur unless the community has lost trust completely. Users may demand a temporary block or a partial ban to an admin who ruled against them on some issue, but not a permanent site ban; a small number of highly vindictive users may demand that, but the community won't support it. Animal lover |666| 12:48, 18 April 2023 (UTC)
  • "Their granted permissions - including but not limited to admin tools" - this will overturn the consensus determined in Wikipedia:Requests for comment/User rights of (site) banned users. Also, for the proposal itself: (1) I am personally against it citing WP:CREEP and current ArbCom is sufficient to handle such cases; (2) I suggest we should explicit mention that such actions may still be appealed to ArbCom.--GZWDer (talk) 13:43, 18 April 2023 (UTC)
    My understanding is that ultimately (after community paths have been trod) any community action may be appealed to arbcom. So that would presumably include this. - jc37 14:08, 18 April 2023 (UTC)
    I never really agreed with that in the first place anyway. --Rschen7754 23:25, 18 April 2023 (UTC)
    Consensus can change; no state of consensus is permanent, and no discussion can bind any future state of the community at Wikipedia from discussing an idea and reaching a new consensus. It is a good data point to know what the existing consensus is on a topic when discussing it, but that existing consensus only lasts until it isn't consensus anymore. This very discussion is the way we are change that consensus. --Jayron32 14:42, 19 April 2023 (UTC)
  • Weak support - I think the wording here will still favor de-sysop requests being taken to ArbCom rather than a community de-sysop process, for the reason that a site ban would be considered an action with greater scope and severity than a de-sysop. I don't think this is a sufficient remedy, but it's better than nothing. --⛵ WaltClipper -(talk) 14:07, 18 April 2023 (UTC)
  • Support introducing this consensus-oriented method of removing bits. As worded, this proposal would allow for the community to de-crat, de-CU, and de-OS; I believe that these are features of this proposal, not bugs. I would also suggest that whenever a unban discussion takes place, people should be advised to make it clear if they are supporting an unban as "User:Example should not have been banned in the first place" (in which case the tools should be restored) or as "no longer required to prevent disruption" (in which case they should not). I would also like it if we specified that any CBAN discussion that results in the bit being removed should be closed by a 'crat. That is, it should function like RfA closure does: anyone can WP:SNOW/WP:NOTNOW close, but only a 'crat can close as successful. (For the avoidance of doubt, I am not advocating that we institute 'crat chats or a "discretionary range" for CBAN discussions.) HouseBlastertalk 15:08, 18 April 2023 (UTC)
  • Support as duh. If an admin is site banned by the community, then obviously they lose their rights. Sending it to ArbCom would be, in my opinion, a waste of time as ArbCom would pretty much rubberstamp the desysop. RickinBaltimore (talk) 16:01, 18 April 2023 (UTC)
  • Support. I don't see this as mutually exclusive with the above, and I don't see it being used often, but I agree with the principle. Vanamonde (Talk) 16:10, 18 April 2023 (UTC)
  • Support, in addition to the original proposal above. Boing! said Zebedee (talk) 16:27, 18 April 2023 (UTC)
  • Support I opposed the original proposal but this is of course very reasonable and something I think we can all get behind. I think the amount of instances covered by the original proposal but not by this proposal is vanishingly few. (As a minor and moot point, I'm not sure if we can technically de-CU or de-OS a user, since WP:ARBPOL gives those duties to ARBCOM, but of course ArbCom will remove the permissions from a site-banned user.) Galobtter (talk) 17:33, 18 April 2023 (UTC)
  • Support This proposal won't really solve the problem of unaccountable admins or the need for a community desysop procedure, and will in practice probably never be used. But it's something, and really, it should work this way regardless.— Preceding unsigned comment added by Writ Keeper (talk • contribs) 17:35, 18 April 2023 (UTC)
  • Support, noting that in the Athaenara case several arbs implied they would do this anyways if it came to it. It's a little odd how this interacts with non-admin-tier rights, but at the same time not really an issue, since most of those can all be restored at any admin's discretion; the exceptions are EFM and EFH, but that's probably a good thing. I know I'd have no problem giving rollback back to a recently-unbanned user if the ban didn't involve rollback abuse or edit-warring, for instance. As to desysopping and decratting, I agree with HouseBlaster that this should follow the default rule that a discussion should only be closed by someone with the tools to enact it (or in the case of decratting, the authority to request a steward enact it). With de-CU and de-OS, a 'crat could close as "banned and referred to ArbCom regarding CU and OS" and start a pro forma case request. Like Galobtter, I very much doubt any committee will hesitate to remove rights in that situation. -- Tamzin[cetacean needed] (she|they|xe) 18:05, 18 April 2023 (UTC)
  • Support regardless of whether the original proposal passes. Of course, 99% of admins who do something even remotely sitebannable are going to be desysopped by the Committee (whether by level 1, level 2, or motion) well before the ban discussion is closed, and I hope arbitrators continue doing that without feeling that they need to defer to the community: the last thing I want to do is slow down the desysop process in straightforward and/or urgent cases. But in general I think the proposal does move us (very marginally) in the right direction toward additional admin accountability to the community, so I'm happy to support. Extraordinary Writ (talk) 18:33, 18 April 2023 (UTC)
  • Support regardless of whether the original proposal passes; makes sense. Editors holding rights are expected to hold the trust of the community; if the editor is banned it is very clear that they have lost that trust. BilledMammal (talk) 19:58, 18 April 2023 (UTC)
  • Support Not much more to add. Admins and 'Crats must retain the community's trust --Enos733 (talk) 20:06, 18 April 2023 (UTC)
  • Oppose per my above oppose. I don't see what problem this fixes. What terrible thing happened that this will prevent? Lowering the workload for Arb? I don't see the workload as a problem. Dennis Brown - 2¢ 20:37, 18 April 2023 (UTC)
    What terrible result will come from this passing? As far as I can tell, this should have nearly 0 effect in a century of Wikipedia but that nil effect would be good. Animal lover |666| 12:10, 19 April 2023 (UTC)
  • Support. It hopefully won't be needed often, but this does look like a process that the community can handle without needing an Arbcom case. - Donald Albury 20:40, 18 April 2023 (UTC)
  • Support It takes an awful lot of misbehavior to earn a site ban, & most admins are very visible folk. Further, some of admins gained the bit back when standards weren't as high, & even if this never implemented, it'll serve as a sword of Damocles to check admins from being too enthusiastic with the bit. -- llywrch (talk) 21:10, 18 April 2023 (UTC)
  • Weak oppose It's like saying that a person who can't do basic addition isn't allowed to teach math in a university. No argument with that, but it's something that will never get used and so not worth messing with. North8000 (talk) 21:17, 18 April 2023 (UTC)
    And, BTW this is a better proposal than the initial one. North8000 (talk) 17:29, 19 April 2023 (UTC)
  • Support even if seldom used, this will be a start for community based decisions. Graeme Bartlett (talk) 23:19, 18 April 2023 (UTC)
  • Support contains the spirit of the original proposal without the drama-adding elements. --Rschen7754 23:24, 18 April 2023 (UTC)
  • Support as a minimum. AndyTheGrump (talk) 23:56, 18 April 2023 (UTC)
  • Support for the same reasons I !voted support above. -FASTILY 02:09, 19 April 2023 (UTC)
  • Support simple and straightforward. Legoktm (talk) 03:57, 19 April 2023 (UTC)
  • Support in addition to supporting the original proposal above. An admin who draws a CBAN is even more obviously not trusted by the community. --RL0919 (talk) 06:08, 19 April 2023 (UTC)
  • Support, as a CBAN is a clear indication of the loss of the community's trust. ScottishFinnishRadish (talk) 13:57, 19 April 2023 (UTC)
  • Support per WTT. Ajpolino (talk) 14:59, 19 April 2023 (UTC)
  • Oppose - this isn't a logical extension of the original proposal, which was to procedurally remove the tools from admins blocked for a significant term, considering that blocks are to prevent editing disruption. There's generally no consensus that blocks can be used to respond to administrative misconduct, that's why we have WP:LEVEL1. Any admin who blocks another admin because of an administrative action is likely to be the first mover in a wheel war, and we should not introduce ambiguity to that policy. An administrator who is banned by the community is likely to be blocked anyway, and would have their permissions removed after 28 days if the above proposal passes or after a year under current policy; I don't see why this is necessary. However, the extension is a backdoor to create a community desysop process by which the only way for the community to remove admin rights is to ban the admin, even if their edit history is spotless. That's too heavy-handed, and it's absolutely going to be abused by bad actors to intimidate or eliminate administrators that get in the way of their tendentious agendas. It's a step too far, especially considering it's a first step. Ivanvector (Talk/Edits) 16:14, 19 April 2023 (UTC)
    In what circumstances do you envision a community consensus to ban an admin "if their edit history is spotless"? --RL0919 (talk) 20:10, 19 April 2023 (UTC)
  • Support as a start. If you mess us enough to get yourself community banned, then you're clearly not suitable to hold advanced user rights. SkyWarrior 17:50, 19 April 2023 (UTC)
  • Weak oppose based on the current wording. I think this is a solid idea, but I'd like to see it clarified that if an appeal finds that the original close was improper (incorrect reading of consensus, involved admin, wheel warring, things of that nature) rather than an appeal determining that the ban was valid but should now be lifted, then permissions should be restored. The WordsmithTalk to me 18:25, 19 April 2023 (UTC) Switching to Support as I had missed part of the proposal. It seems like a good idea and a fairly obvious change to be made. The WordsmithTalk to me 20:38, 19 April 2023 (UTC)
    That should be inherent in the last line of the proposal. Reversal due to "Community mistake". There are many ways in which mistakes could be made in a discussion. From the proposing, through to the closure. I don't think we could list them all. But should it be determined that the ban was done in error, then the granted tools should be restored. Essentially undoing a "miscarriage of justice". - jc37 19:28, 19 April 2023 (UTC)
    Somehow my eyes managed to skip over that entire line, I do see now that my issue is already addressed. I'll update my statement accordingly. The WordsmithTalk to me 20:37, 19 April 2023 (UTC)
  • Support other have already said everything I could say. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 21:30, 19 April 2023 (UTC)
  • Support this is better than nothing, but it is vastly inferior to the original proposal. The bar for admin accountability on this site is still way too high. LEPRICAVARK (talk) 01:56, 20 April 2023 (UTC)
  • Support per my comments above. TonyBallioni (talk) 02:05, 20 April 2023 (UTC)
  • Support Andre🚐 02:49, 20 April 2023 (UTC)
  • Oppose. I do not see the practical need for this instruction creep (WP:CREEP). Community bans of admins are hopefully very rare (has there ever been a case?), and there is no reason to believe that ArbCom would not promptly desysop an admin who has been properly banned by the community (if only because they can no longer legitimately use their tools). The problem with this proposal is that it would incentivize people to use ban discussions as a proxy for a desysop by community consensus, which so far the community has declined to institute for what I think are good reasons. Sandstein 07:20, 20 April 2023 (UTC)
  • Support I think usage othis will be incredibly rare but it's conceptually sound. Best, Barkeep49 (talk) 07:52, 20 April 2023 (UTC)
  • Suppport noting that this doesn't conflict with the primary proposal here so, despite the title, it's not in any meaningful sense an "alternative". I'm supporting it as a complementary idea.—S Marshall T/C 08:01, 20 April 2023 (UTC)
  • Support in parallel to the primary proposal. As WTT said, If a site ban passes on an admin, they should no longer be an admin. firefly ( t · c ) 08:25, 20 April 2023 (UTC)
  • Support in addition to the proposal below. Beyond My Ken (talk) 09:11, 20 April 2023 (UTC)
  • Support - Seems straightforward that if a user does not have the trust of the community to edit Wikipedia, they don't have the requisite trust to be an admin. Compatible with WTT's proposal above. WJ94 (talk) 09:21, 20 April 2023 (UTC)
  • Oppose, solution looking for a problem. Stifle (talk) 10:12, 20 April 2023 (UTC)
    • To add to this comment, this solution would be a witch-hunters' paradise. It takes a week, and a massive stressful process, to grant adminship. Removing adminship based on a pile-on on ANI is a desperately bad idea. There's a reason WP:QKP was killed off. Stifle (talk) 08:36, 12 May 2023 (UTC)
  • Oppose a rare occurrence like this can be handle by ArbCom. Such a rule would encourage even more gaming of the system (campaign for a long block on an admin you don’t like to end them for good). Jehochman Talk 12:18, 20 April 2023 (UTC)
    Hi Jehochman. The survey about long blocks is before this one. This one concerns site bans. - jc37 13:07, 20 April 2023 (UTC)
    Same logic, different terminology. (I did copy and paste.) This proposal is even more unnecessary because it addresses an extremely rare situation. If an administrator gets sitebanned, ArbCom should definitely be looking into it to understand what happened (compromised account, etc.). Jehochman Talk 19:22, 20 April 2023 (UTC)
  • Support per WTT Pharaoh of the Wizards (talk) 16:35, 20 April 2023 (UTC)
  • Support a bit narrow but I don't see any problems with this —pythoncoder (talk | contribs) 18:09, 20 April 2023 (UTC)
  • Support This sounds good too. - Who is John Galt? ✉ 21:33, 20 April 2023 (UTC)
  • Support, but I can't believe this is even a question. You mean to tell me that a banning doesn't mean you lose your privileges? Ok, so if I get banned you are telling me I still get to keep my autoconfirmed, rollbacker, and pending changes reviewer status rights, or is it only admins that get to keep tools? That is ridiculous. Huggums537 (talk) 05:46, 21 April 2023 (UTC)
  • Weak oppose as pointless instruction creep, per Dennis Brown, Jehochman, Sandstein. If an admin gets cbanned, I would imagine they would be pretty uncontroversially and with minimum additional drama be de-adminned by Arbcom using their Level II procedures. This situation is fortunately sufficiently rare that we don't need additional policy to sidestap that existing solution. I'm opposing this variant only weakly, as opposed to original proposal, since by applying simply to cbans and not imposing arbitrary timelines, the instruction creep is more manageable. But it's still unnecessary. Martinp (talk) 15:05, 21 April 2023 (UTC)
  • Oppose as pointless - it appears this situation has never happened in recent history. * Pppery * it has begun... 21:18, 21 April 2023 (UTC)
  • Support as codifying what should be common sense. Giraffer (talk·contribs) 14:34, 22 April 2023 (UTC)
  • Support, provided that an amendment is made to indicate that it must be an indefinite site ban, so that we don't see silly things like a five-minute site ban being proposed as a "backdoor desysop". Seraphimblade Talk to me 15:44, 22 April 2023 (UTC)
    Done - I already noted it did not include limited bans, but added the clarification anyway. - jc37 16:29, 22 April 2023 (UTC)
    Although of course tomorrow the community could invent a fixed-duration site ban, with the historical concept of a site ban, it's always indefinite. Editors are site banned when they are no longer welcome to be participate at all in the English Wikipedia community. It's not a situation that times out without an appeal. isaacl (talk) 04:03, 23 April 2023 (UTC)
  • Support While I acknowledge that the cases where this could apply are likely small which gives me reason to oppose, I think this is the best possible way to handle community based desysop proposals. We've been trying to untie this gordian knot for almost 20 years without success. It's been clear for a long time now that we need such a process. I can see how this process could have problems; a single administrator closing the discussion to CBAN? Hmm. Gang mentality polluting the results? Hmm. Sockpuppeters coming out of the woodwork after their favorite target? Hmm. I think the process can weather that. I would like to see one caveat applied though; CBAN "discussion must be kept open for 72 hours except in cases where there is limited opposition and the outcome is obvious after 24 hours". The 24 hour statement shouldn't apply in this case, instead requiring 72 hours. --Hammersoft (talk) 17:23, 23 April 2023 (UTC)
  • Weak support I don't think this is needed, as it is rare and there are existing venues to deal with this situation, but it may avoid needless redundant paperwork. — xaosflux Talk 23:00, 24 April 2023 (UTC)
  • Support - a natural, I'd say merely technical extension of ban. Lokys dar Vienas (talk) 03:56, 25 April 2023 (UTC)
  • Support in that it's 1) a higher threshold, 2) consistent across permissions, such that, if I remember correctly, it would have been useful--even if just as a principle--in some of the old bot operator/automated editing conduct issues. Jclemens (talk) 04:25, 25 April 2023 (UTC)
  • Support, as reaching a consensus for an indefinite siteban is a clear, existing way for the community to express a complete loss of trust. ~ ToBeFree (talk) 07:22, 25 April 2023 (UTC)
  • Oppose. Unnecessary, a solution in search of a problem. Nsk92 (talk) 11:47, 25 April 2023 (UTC)
  • Support This formalises what should be obvious. talk to !dave 12:15, 25 April 2023 (UTC)
  • Support.--Jerome Frank Disciple (talk) 13:57, 25 April 2023 (UTC)
  • Oppose as an absurd weakening of the original proposal. Figureofnine (talk • contribs) 14:49, 25 April 2023 (UTC)
    These proposal are not exclusive. — xaosflux Talk 12:45, 27 April 2023 (UTC)
  • Support: a plainly fine proposal; far better than nothing. ~ Pbritti (talk) 19:39, 25 April 2023 (UTC)
  • Neutral. I'm not substantively opposed to this proposal as I believe it reflects common sense: obviously a site-banned administrator has lost the confidence of the community and should be desysopped. However, like the original proposal, I see this as a bit of a solution looking for a problem, and I do not foresee that it will produce any tangible improvement to current process. We site-ban administrators exceedingly rarely—the threshold for a desysop is much lower than the threshold for a site-ban. If an administrator is under discussion for a site-ban, I would expect that a request at WP:ARC will have already been filed in parallel, and as I mentioned earlier, recent examples have shown that ArbCom is perfectly capable of expeditiously desysopping administrators where necessary. Mz7 (talk) 21:44, 25 April 2023 (UTC)
    Just wanted to add a bit to this to explain why I am "neutral" on this alternative proposal and "oppose" on the main proposal. I am more sympathetic to this alternative proposal because a site ban is a higher bar to clear than a block. A site ban requires clear community consensus at an administrative noticeboard, whereas a block can be imposed unilaterally. The consensus for a site ban can become clear pretty efficiently: I've seen cases at WP:AN where we've site-banned editors within a day or two (although because of the invention of WP:3X, site ban discussions are quite rare nowadays). This is in contrast to the required 28-day window from the main proposal.
    If we pass this alternative proposal, I can see cases where if an administrator does something so egregious that they need to be blocked indefinitely, the community would then have two avenues to desysop the admin: (1) start a site-ban discussion, or (2) request a desysop at WP:ARC. The reason I am "neutral" and not "support" is because I believe the existing process of requesting the desysop at WP:ARC already works as efficiently as a site-ban discussion (and may even be preferable because ArbCom is generally more evidence-focused and deliberative than the free-for-all style of WP:AN). Also, I am worried that this will lead to situations where we go for a site-ban on a blocked administrator where a simple indefinite block would have sufficed, just so that we can desysop them (a block can be overturned unilaterally whereas a ban requires community consensus to overturn). Mz7 (talk) 21:12, 27 April 2023 (UTC)
  • Oppose as unnecessary any C-banned admin would almost certainly be desysoped by Arbcom. Lightoil (talk) 08:39, 26 April 2023 (UTC)
  • Support Seems like a great idea to me. -- Grapefanatic (talk) 14:45, 26 April 2023 (UTC)
  • Oppose at the moment any admin who was community banned would likely be desysopped by motion from arbcom. So if this went through there would either be no meaningful change, or we'd have a bunch of attempts to ban particular admins, with some people supporting the ban as the most effective way to desysop that admin, and others saying that they hope arbcom does a desysop but they don't think a ban is merited. If there is any scope for a community desysop it is to deal with people who arbcom would not desysop, but where the people who elect arbcom want to be harsher than arbcom. That group won't overlap with the people who merit a ban. ϢereSpielChequers 14:58, 26 April 2023 (UTC)
  • Oppose; redundant proposal as the ArbCom can order an emergency desysop if needed. I agree site-banned users should not hold advanced rights but this proposal could be gamed, would create much dramah and become unworkable. Baffle☿gab 21:01, 26 April 2023 (UTC)
  • Oppose per WP:CREEP. Still a solution in search of a problem. Passing more rules just for the sake of passing more rules is something I typically associate with politicians and (some) civil servants who need to justify their paycheck. -Ad Orientem (talk) 21:04, 26 April 2023 (UTC)
  • Support in combination with the primary proposal. Long blocks and bans should mean de-sysoping, and a successful ban appeal should not mean an automatic restoration of the bit. Way too much abuse of the tools goes on, and anything that curbs that would have to have some pretty enormous downsides to lose my support. —swpbT • beyond • mutual 17:50, 27 April 2023 (UTC)
  • Support per Worm. ~ 🦝 Shushugah (he/him • talk) 22:57, 27 April 2023 (UTC)
  • Support a reasonable thing that sould happen. I don't see the need for arbcom to pro forma vote to desysop someone here. --In actu (Guerillero) Parlez Moi 07:51, 28 April 2023 (UTC)
  • Support as better than nothing, even if it's only used rarely. Hard to think of any case where an admin is banned, yet still trusted enough to keep the tools. DFlhb (talk) 16:47, 28 April 2023 (UTC)
  • Strong support. I don't see a world where a user who is so distrusted to be banned is trusted to be an admin... CLYDE TALK TO ME/STUFF DONE 21:22, 28 April 2023 (UTC)
  • Support Being allowed to resume editing is a different kettle of fish to having one's advanced privileges restored. MrsSnoozyTurtle 05:01, 29 April 2023 (UTC)
  • Neutral Makes sense, but it seems unlikely that existing processes (i.e. an ArbCom motion) wouldn't already handle this. Anomie⚔ 14:56, 29 April 2023 (UTC)
  • Strong support per my comment in the original proposal. Removing admin rights should be done automatically when such user is blocked or banned. RFA is the venue to regain their rights. Callmemirela 🍁 18:03, 29 April 2023 (UTC)
  • Support as superior to the original proposal. If an admin is site-banned by the community, then their privileges should be immediately revoked, full stop. I don't see a reason why this should need to be sent to ArbCom.-- Aervanath (talk) 10:09, 3 May 2023 (UTC)
  • Basically in agreement with the above supports: sure, not mutually exclusive. I'd go much, much farther, but as above, at least it's something. ~ Amory (u • t • c) 12:27, 3 May 2023 (UTC)
  • Support – seems like common sense, and in general I support making it easier to revoke adminship, as I explained above. —Mx. Granger (talk · contribs) 13:20, 4 May 2023 (UTC)
  • Support at the same level as the original proposal. Aasim - Herrscher of Wikis ❄️ 16:16, 4 May 2023 (UTC)
  • Support Thought this was done as a matter of course already; ArbCom shouldn't be in charge of literally everything. – John M Wolfson (talk • contribs) 01:37, 6 May 2023 (UTC)
  • Support. Side note, while I do think both of these proposals essentially codify something that would almost certainly happen anyway through existing processes (Level II), and if we could only have one procedure I would probably prefer one that's separate from any blocks or bans, but we can have more than one and I doubt we'd get to the point of it becoming CREEP unless we somehow decided to start adding new "things that gets admins' bits removed by the community" to the list every week or two. Alpha3031 (t • c) 11:13, 6 May 2023 (UTC)
  • Oppose Needs to be any ban (including topic). Only in death does duty end (talk) 11:38, 10 May 2023 (UTC)
  • Support it's somewhat incredible this wasn't adopted in some form about 15 years ago. —Rutebega (talk) 19:56, 11 May 2023 (UTC)

Discussion (alternate community desysop proposal)

There's a couple suggestions above that the discussion should be closed by a crat. Since the desysopping would be a consequence of the ban by policy but not explicitly part of it, I don't think this needs to be the case. I feel like this is a case where the admin closing could simply leave a note at WP:BN, as is done with ArbCom desysops. Galobtter (talk) 18:21, 18 April 2023 (UTC)

I agree. Closure by an uninvolved admin is fine. Thryduulf (talk) 11:56, 19 April 2023 (UTC)
If this were likely to be relevant soon for a specific admin, it may have required a bureaucrat; however, since this is clearly not the case, admin closure should sefice. Animal lover |666| 13:54, 19 April 2023 (UTC)
I am somewhat concerned that this might end up (to a greater degree than the slow 28 day process) be used in some cases to force a desysop through banning someone, when their actions would not otherwise have led to a CBAN. I'm not sure whether mitigation with stressed clarity that a !vote seemingly acting to ban only as a means to desysop. Nosebagbear (talk) 20:43, 19 April 2023 (UTC)
I hope the community isn't so cruel as to site ban just to cause a desysop, but I agree there is a perverse incentive here - but I feel like that equally applies to the original proposal. Galobtter (talk) 02:52, 20 April 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Alternate proposal (Arbcom Level II desysop of long-term blocked admins)

FAILED
Insufficient participation at best, consensus against at worst. — Wug·a·po·des 20:44, 18 May 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Let's address the issue without gameable instruction creep and with minimum changes to existing policies for what are very rare cases. Arbcom can already desysop an admin under WP:LEVEL2 if "(a) the account's behavior is inconsistent with the level of trust required for its associated advanced permissions, and (b) no satisfactory explanation is forthcoming." Doing so doesn't take the weeks or months of an active or suspended arbcom case, just a vote by Arbcom. Therefore, if there is any ambiguity, let's just resolve the situation by affirming the statement in the next paragraph. Then in the rare cases an admin ends up in this situation, sua sponte or on request any arbitrator can propose a Level II desysopping and the Committee can effect it by voting. They will presumably do this with a minimum of fuss, but with a bit of consideration/deliberation as to whether there are any exceptional circumstances, and whether sufficient time has passed for it to become clear that the user in question will remain blocked for some time.

Statement: The community affirms that engaging in behaviour that leads to an admin becoming and remaining long-term blocked (or banned), for cause, is generally inconsistent with the level of trust required for retaining administrator permissions. Arbcom is empowered (alternative: directed?) to act per its existing policies (currently WP:LEVEL2) to deal with such situations.

Editing since forgot to sign: Martinp (talk) 18:10, 19 April 2023 (UTC)

Survey (alternate proposal for Arbcom Level II desysop of long-term blocked admins)

  • Oppose For pure WP:BURO reasons. I do not see anything this proposal does that Arbcom does not already do, via their string of measures. A "please do this" from the community to Arbcom isn't enough. And the biggest draw of the other proposals for me was simply "Having more community measures to desysop" instead of putting even more things strictly at Arbcom alone.
In fact, I cannot imagine a single scenario where Arbcom would block or ban someone without de-adminning, making this even more of a rules creep. At least the others were explicitly "community decision" instead Soni (talk) 02:42, 20 April 2023 (UTC)

Discussion (alternate proposal Arbcom Level II desysop of long-term blocked admins)

Since my proposal is garnering quite a lot of opposition, let me explain my thinking. In my view, yes this changes very little. I view it as uncontroversial that in many (most?) circumstances, being blocked long-term for cause is clearly incompatible with the level of trust needed to continue holding adminship. So I would like to think that if some admin ends up in that circumstance, Arbcom could just de-admin them for conduct unbecoming. However, there is significant functionary (including Arb) support for the present "community procedural de-admin" proposal, with specific bright line criteria. This support presents as the alternative being avoided a "long, drawn out arbitration case". So I'm proposing to explicitly just say, "yeah, Arbcom, go ahead and pull the bit using L2 without too much fuss where warranted" as a less bureaucratic solution to a rare problem then a convoluted "community procedural" process, one where we're needing to wordsmith ahead of time exactly what the block age and duration should be, what kind of block counts, etc. Basically, I feel we actually don't need more rules to solve a rare problem. However, since Arbcom members seem (implicitly) unsure if they have the authority to desysop someone just because the community has decided to block them for a long time, reassure them that they already do. Martinp (talk) 19:38, 20 April 2023 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Alternate proposal: the community supports development of a de-sysop process

FAILED
Disagreement largely centered on the second sentence of the proposal rather than the first. Participants were concerned that the proposed RfC would not be a good use of itme in light of the proposals already being considered in this RfC. There was some sentiment that this might find consensus in the future, but at the moment there is no consensus to hold another, binding RfC to develop a community base desysop procedure as proposed. — Wug·a·po·des 20:44, 18 May 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Let's stop beating around the bush and just propose this:

The community supports the development of a community based process for removing administrator rights for cause outside of the current arbitration committee procedures. If this proposal closes with consensus, the community directs that a binding RfC be opened within 30 days where community members may submit proposals to determine the process.

Survey (Alternate proposal: the community supports development of a de-sysop process)

  • Support determines the actual consensus on the principle of the matter, and establishes a procedure to determine how to implement the consensus on the principle if it exists. Much better than picking around the edges. If there is a community consensus on the principle, let us establish that and then determine what the method of implementing it should be. TonyBallioni (talk) 02:10, 20 April 2023 (UTC)
  • Support I've long assumed this first part describes the community's desire (though I suppose we'll see here). It's the second part, actually finding details of such a process, that folks seem to struggle with. But another RfC is certainly worth a try. Ajpolino (talk) 02:27, 20 April 2023 (UTC)
  • Support This is most in line with what I would like to see. I worry that this structure guarantees another no consensus (being too similar to the last N failed RFA reforms, and apparently the other DESYSOP proposals). But I would like community desysop to happen, and supporting this is more preferable than standing in the way. Soni (talk) 02:46, 20 April 2023 (UTC)
  • Support. I think where the earlier proposals fail is in trying to make this work within the existing block framework, when what is actually required is a concrete mechanism by which sysops who have lost the confidence and trust of the community can be de-sysoped. Patr2016 (talk) 02:57, 20 April 2023 (UTC)
  • Support I guess, but I am not very optimistic that it will end in a real process. --Rschen7754 03:11, 20 April 2023 (UTC)
  • Support. I agree with the principle, and while I reserve the right to say "I told you so" when the RfC ends up with too many proposals, too few participants, and no consensus, I agree with Soni that supporting this is more preferable than standing in the way. An oppose !vote certainly wouldn't make community desysop more likely to happen. Extraordinary Writ (talk) 06:23, 20 April 2023 (UTC)
  • Support. I don't expect this to work but it is worth trying. BilledMammal (talk) 06:57, 20 April 2023 (UTC)
  • Oppose. I frankly don't see the practical need for yet another drama-laden process. From what I can tell, the ArbCom process works rather well, as in the recent Dbachmann case. If and when we have a specific case where ArbCom declines to desysop a person who's obviously unfit for the job, then we can and should have this discussion. Sandstein 07:24, 20 April 2023 (UTC)
  • Theoretical support, actual oppose. I support community desysop but for the reasons I mention here I find this proposal to get there not to be fully thought out or practical. Barkeep49 (talk) 07:42, 20 April 2023 (UTC)
  • Oppose. This seeks to replace the practical, workable ideas already on the table with no tangible offer at all.—S Marshall T/C 07:57, 20 April 2023 (UTC)
  • Oppose Per Barkeep and S Marshall. I support in theory, but not in practise. We have a couple of small step solutions here that are thought out. Scrapping the work above and hoping that a binding RfC which has failed twice in recent years is not a solution. WormTT(talk) 08:09, 20 April 2023 (UTC)
  • Oppose per Barkeep et al. This is a fine idea in theory, but I fear it won't actually result in any real change. IMHO - best to take iterative steps toward a solution than start a(nother) large discussion. firefly ( t · c ) 08:22, 20 April 2023 (UTC)
  • Weak support, this is much better than the original proposal where we would just make up the rules as we go along the next time an admin is blocked. I do think we can usually leave things to ArbCom, though; a slow and deliberative process is likely better than things like Wikipedia:Requests for comment/Kelly Martin/original. —Kusma (talk) 08:42, 20 April 2023 (UTC)
  • Support - OMG, this is so freaking overdue, yes, yes, yes. Beyond My Ken (talk) 09:02, 20 April 2023 (UTC)
  • Oppose at the moment. If either of the first two proposals on this page get consensus this will be redundant to them, if they don't then I can't see the point in spending more time developing a more complicated and drama-laden version of the same thing. Also per WTT et al. Thryduulf (talk) 09:16, 20 April 2023 (UTC)
    I mostly support because I hope the new process will be less drama-laden than turning every discussion about the block of an admin into a desysop discussion happening in an undefined location (the user's talk page? ANI?) under undefined rules. —Kusma (talk) 09:33, 20 April 2023 (UTC)
  • Oppose, essentially per Barkeep49, S Marshall, Worm That Turned, though support in principle for a future time and place. Every proposal for a fully worked-out community desysop has failed. Part of the problem is that all sorts of alternative proposals come up, and we get lots of partial support for them. But with everyone tugging in a different way, nothing gets done. Every single time - absolutely nothing. So, while we have a couple of clear and simple proposals going here, please let's not derail things yet again. I say let's see how the simple proposals here work out, and then revisit a full community desysop proposal at a future time. Ideally, I'd like us to have a full community desysop. But if we try it here and now, I think it's almost certain that the only achievement will, yet again, be nothing at all. We've tried running too many times. We need to walk first, one step at a time. Boing! said Zebedee (talk) 10:07, 20 April 2023 (UTC)
  • Oppose - it's not like it's been eons since the last time we went through this. So oppose per Worm et al. Also, functionally all RfCs are intended to be binding, so not sure what that was intended to add. Nosebagbear (talk) 10:13, 20 April 2023 (UTC)
  • Support, though I am not sure we will end up with anything, like the last trillion times. Stifle (talk) 10:16, 20 April 2023 (UTC)
  • Support, but I will not be volunteering to run it. :D Valereee (talk) 11:05, 20 April 2023 (UTC)
  • Oppose, am swayed by Barkeep49, S Marshall, Worm That Turned and Boing! said Zebedee. Hiding T 11:23, 20 April 2023 (UTC)
  • Support - a simple statement with the backing of consensus, affirming at a high level that the community desires a community desysop process. We always start with a proposal, then figure out what problems it solves, then ask if we actually want to solve those problems. Of course they fail, we're doing it entirely backwards. We need a discussion or process to flesh out what the problems are that the community wants to solve, and really only then can we constructively discuss how to solve them. But the first step of all is to determine whether or not the community actually wants such a process at all. I mean, I think it's pretty clear from the years and years of discussions and proposals, but I don't think we've ever really formally asked. Ivanvector (Talk/Edits) 11:53, 20 April 2023 (UTC)
  • Oppose perversely because it's to easy to oppose. Making a swiping change that gets a majority agreement is extremely hard, because different groups will oppose different parts. Maybe if the community was split into two simple groups (as some editors appear to beleive it is) then it would be possible to get a 51% majority victory. But realistically getting a majority of editors to agree on such a big change is like herding cats. Incremental changes like those already suggested are much more likely to succeed. The recent inactivity requirements are a good example. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 11:58, 20 April 2023 (UTC)
  • Oppose as pointless. The community has the power already to start such an RFC. No need to re-affirm what we could already do. If an editor or group of editors wishes to workshop an idea that might have a chance of gaining widespread consensus, they can just do so. They don't need a special RFC to empower them to do so. The barrier is not that proposals aren't made; the barrier is that no such proposal has gained consensus. --Jayron32 12:05, 20 April 2023 (UTC)
  • Support I sympathize with those who object that this will preempt the proposals above, but realistically the only proposal above likely to pass is the one about desysopping a sitebanned admin, and that's honestly a pretty redundant proposal since a desysop in that case would be inevitable anyway. LEPRICAVARK (talk) 13:50, 20 April 2023 (UTC)
  • Oppose in this context, where it is presented an alternative to the more specific process changes that are already under discussion. --RL0919 (talk) 15:40, 20 April 2023 (UTC)
  • Hesitant conditional support. Contra several respected colleagues above, I don't see why this would derail the above proposals, which I also support: but for the sake of clarity, my support is conditional to this proposal not overturning consensus on the previous two. As to the rest, I'm hesitant about the "binding" bit; I don't want us to end up stuck with a bad proposal because nothing better reached consensus in a binding RfC; but I suppose I trust that our general opposition to change that is not fully thought through will handle that. Vanamonde (Talk) 16:26, 20 April 2023 (UTC)
  • Oppose this is somewhat pointless, since there is nothing stopping anybody from starting an RfC or making a proposal on the subject anyway. Unless it's supposed to mean that we have to establish a community desysop process and the RfC is just to establish what it will look like, but I don't think that's a good idea. While community desysop is a good idea in theory a lot of the proposals end up being rather susceptible to lynch mobs and will probably make things worse. Hut 8.5 18:35, 20 April 2023 (UTC)
  • Support Yes, this would also work. - Who is John Galt? ✉ 21:35, 20 April 2023 (UTC)
  • Oppose. The lack of consensus in previous discussions about this, combined with flare-ups in drama in some high profile admin misconduct cases, lead me to believe it is best to leave desysopping for cause to Arbcom. That's a process that we've shown works reasonably well in cases of egregious misconduct. I would be much more inclined to support term limits on all admins in some way (e.g. reconfirmations after x years), with some sort of protection against grudge-bearing etc., since that would work better against the (perceived) issue of out-of-touch admins throwing their weight around on the boundaries of what they can get away with. Martinp (talk) 12:17, 21 April 2023 (UTC)
  • Oppose per Sandstein and Boing!. I'm not sure what problem we are really solving and it seems unlikely that another RfC would actually lead to anything useful. Galobtter (talk) 21:53, 24 April 2023 (UTC)
  • Support Fuck it, I think such a process is inevitable, and "something is better than nothing" here (even with the risk of action bias). – John M Wolfson (talk • contribs) 23:28, 24 April 2023 (UTC)
  • Oppose: I'm fine with "the development of a community based process for removing administrator rights for cause outside of the current arbitration committee procedures", but the RfC the proposal asks for is happening here already. I'd especially not want one to be held if one of the above proposals already passes. ~ ToBeFree (talk) 07:31, 25 April 2023 (UTC)
  • Support in principle, pending enough detail to make a more informed comment. Certes (talk) 10:16, 25 April 2023 (UTC)
  • Oppose That's right, I would like this process to open another process to gain another process. Process? talk to !dave 12:17, 25 April 2023 (UTC)
  • Weak support It would be better to focus the effort on giving more routine review and feedback such as tuning up and taking the poison pills out of WP:Administrative action review. Arbcom can handle the rarer severe desysop cases. But I 'spose it would be good to have some community route in place. And also to methodically decide on and float optimum proposal in order to resolve this question. North8000 (talk) 12:43, 25 April 2023 (UTC)
  • Support I don't see why this has to be an alternative, but yes it is a good idea. I can't think of a reasonable reason to oppose this, as clearly there needs to be an easier way to put the brakes on misbehaving and unfit administrators. Figureofnine (talk • contribs) 15:55, 25 April 2023 (UTC)
  • Oppose. My view is that the current process works sufficiently well. In other words, there is no need to develop "a community based process for removing administrator rights for cause outside of the current arbitration committee procedures". The proposal is not clear in describing what ways the current process is deficient, other than merely saying we want an alternative. Mz7 (talk) 21:33, 25 April 2023 (UTC)
  • Oppose. As others have noted, it's not clear that there is any actual pressing problem (or any consensus that there is a problem) that we need to find a solution to. People should certainly continue to feel free to propose any bright new ideas that they have, but if there isn't a consensus for any of these proposals it's hard to see the point of an additional binding RfC. We'd just be progressing from one round of policy churn to another. -- Visviva (talk) 22:13, 25 April 2023 (UTC)
  • Oppose. Please god no, no more RfC-trainwrecks. – Joe (talk) 04:19, 26 April 2023 (UTC)
  • Oppose Our current process of removal of administrative tools works just fine. Lightoil (talk) 08:42, 26 April 2023 (UTC)
  • Oppose per most of the above and WP:CREEP. Still a solution in search of a problem. -Ad Orientem (talk) 21:11, 26 April 2023 (UTC)
  • Oppose, as unnecessary, a solution in search of a problem. There is precisely zero evidence that the current arbcom desysop for cause process is insufficient and somehow fails to remove admins who should be removed because of abuse/misuse of admin tools. I would support some version of term limits for admins, requiring a reconfirmation RfA to retain the tools, but that's very different from a community desysop for cause. Nsk92 (talk) 23:02, 26 April 2023 (UTC)
  • Support, iff it includes Extraordinary Writ's option. Make it binding that the most supported option gets a six-month trial. Otherwise, this proposal is just the status quo, per Jayron32. DFlhb (talk) 16:41, 28 April 2023 (UTC)
  • Strong support. Desysops should need not be taken all the way up to ArbCom. Even if the 2nd RfC doesn't develop consensus, change should still hopefully come per WP:BARTENDER. I support EW's option, but that should be discussed in the 2nd RfC. CLYDE TALK TO ME/STUFF DONE 21:56, 28 April 2023 (UTC)
  • Oppose You don't need an RFC about having an RFC. If you have a proposal that you think might actually get support, just propose it. If you want to workshop it first with like-minded people (good idea), go ahead and do it. The problem in the past is that no one has been able to come up with something that actually gets consensus, not lack of will to talk about it. Anomie⚔ 14:56, 29 April 2023 (UTC)
  • Weak oppose as it's unclear as to what process the proposal is referring. Does it involve the community as a whole or established users? Furthermore, what "cause" would require for the community's input to desysop an admin? I feel desysop as part of a block then reaching to RFA to restore rights is the right process. I find this proposal unclear and vague, so I oppose for now as per Anomie above. Callmemirela 🍁 18:11, 29 April 2023 (UTC)
  • Strong support - This is a proposal I can get around. I'm an advocate for a community-based desysop process without the explicit need for arbcom and this is a great start to initiate such a policy. The community should absolutely have a say and an opinion on site administrators who get to stay or go. — That Coptic Guyping me! (talk) (contribs) 20:44, 29 April 2023 (UTC)
  • Oppose I have limited confidence, that an abstract RfC will actually lead to a clear outcome. I would rather ratify specific/limited recall processes, regardless of whether they're a step in the right direction or not, and shift the goal post to improving those policies instead of...inevitably...waiting for another perfect RfC proposal to come along. This is our chance and we should seize it. ~ 🦝 Shushugah (he/him • talk) 22:53, 27 April 2023 (UTC)
  • Support failing the other two proposals above, this sounds like a good idea. Aasim - Herrscher of Wikis ❄️ 16:17, 4 May 2023 (UTC)
  • Very strong support. I don't mean to sound hyperbolic, but I'm genuinely a little mystified by the number of "solution in search of a problem" takes on this rather non-specific proposal. Without question, the occasional need to take the mop back from a community member entrusted with it is an unfortunate but unavoidable concern, so the "problem" is very much concrete, and the specifics of how this process is handled have significant impacts. The only question, therefore, is whether we want this task to be the exclusive purview of ArbCom, and whether such an arrangement is the most rational and efficient state of affairs.
    As to the first part of that question, I've always gotten the impression that the community was widely supportive of a parallel process, but the more principle point is that I think it just makes good sense. I see no inherent problem with ArbCom continuing to do much of the heavy lifting in this regard, but I see no compelling reason why the community at large, with it's broader and more generalized mandate, should not have a detailed and agreed-upon process for quickly arresting problematic actors who managed to squeek their way into advanced tools, or were simply granted them in a more anarchic phase of the project's history.
    These may be relatively rare scenarios, but the damage that can be done to community cohesion and morale when the wrong personality is capable of abusing advanced permissions is significant, and in brightline cases, a laborious ArbCom brouhaha should not be the only option. Being entrusted with the bit should make a community member more inherently open to scrutiny, not for some reason suddenly unanswerable to the mere plebs who are also the sole source of that status (and the only ones who, as an institutional matter, can invest them with those tools in the first place). For a project based so fundamentally on the collective will of the community, in certain areas we sure have built up some fairly oligarchical twists to our systems, and this "the people we vote into advanced tools can only be stripped of them by the general agreement of just twelve community members" rule is one the most perplexing and irrational, in my opinion.
    So, as I see it, we're well past time to agree to a way forward for what is clearly something that is within the broader community's remit, and I think the real issue is figuring out a process which requires a robust community support for such CBAN-adjacent desysops, such that they don't take place unless there is support on a similar scale to that required by RfA itself. That is to say, so there is parity between community will for removing tools and the consensus needed to grant them in the first place (or something at least in the same ballpark). That can and should be an exhaustive and carefully-considered debate, but the question of whether the community should be able to exercise its prerogative on who can retain tools in the first place is, in a word, silly: with few caveats, every a priori principle of process on this project arises from community consensus--by quite conscious design and as a fundamental principle of the project. And even in this specific area, it's clearly that same broad community mandate which has the sole prescriptive function for investing these tools. So how can the broader community possibly lack the stature to remove those same tools in cases of abuse? SnowRise let's rap 09:52, 10 May 2023 (UTC)
Consensus for some sort of community desysop process has existed since 2019. The problem is that no one has been able to come up with a specific process that was able to gain consensus. Anomie⚔ 11:53, 10 May 2023 (UTC)
Sure, and to be honest, it's not surprising that there has been difficulty in nailing down the details of a specific procedure for that purpose. On the one hand, nobody wants a slapdash process for such an exceptional measure as desysop, and on the other, when it comes to community sanctions, there's reasons why the general community doesn't quite care for more structured and formulaic processes like those employed by ArbCom and AE. Finding a solution that both threads that needle and gets broad community support is unsurprisingly not the easiest thing in the world.
Still, I don't see how throwing our hands up in resignation can be considered a solution, and any oppose !vote here based on past difficulties is really missing the point, and abdicating our responsibilities for no concrete gain beyond a declaration of frustration, imo. Of course, no strawvote would be required in order for anyone to make a more concrete proposal for such a process at any time. But, realistically, because there were already proposals above at this moment in time, any additional proposal made in the near future would likely face calls for a procedural close because "we just talked about this".
So if I interpret the purpose of this alternative proposal correctly, it is to keep that door open by creating a clear community mandate to hash this issue out once and for all. Because it will be a real pity if the other proposals above lead to a procedural block on discussing the more general notion of a community desysop process in the near future. Because as you say, this general notion does have broad community support, even if we haven't been able to come to an agreement as to the particulars. So opposing just because of the past failures of particular groups of editors is not a particularly well reasoned-stance as regards whether the matter still warrants attention. SnowRise let's rap 05:56, 11 May 2023 (UTC)
  • Support Actually for the same reason Jayron opposes, the only difference being I think editors do need to be reminded. I also find it hilarious to see opposes (to something that would potentially result in a genuine solution to the core issue) from admins who supported the complete non-solutions above (that are no solution to anything). Its almost as if Admins dont want their tools removed by the people who gave them. Who would have guessed at the conflict of interest there... Only in death does duty end (talk) 11:45, 10 May 2023 (UTC)

Discussion (Alternate proposal: the community supports development of a de-sysop process)

Isn't this just restarting WP:DESYSOP2019 and WP:DESYSOP2021? Galobtter (talk) 02:25, 20 April 2023 (UTC)

Yep, I thought we already reached this "consensus in principle" in DESYSOP2019. Personally I think the only way to break the logjam would be to add "if there is no consensus in the binding RfC for any one proposal, the proposal closest to gaining consensus will be implemented for a six-month trial" to the end of Tony's proposal above, but I'm well aware that there'd be plenty of resistance to that. Extraordinary Writ (talk) 02:36, 20 April 2023 (UTC)
Not really - a 4 year old consensus doesn't establish ground for acting now. I see this more in line with WP:RESYSOP 2019 and the initial principles RfC that established it. The method I proposed for DESYSOP2021 was me one person (me) coming up with a proposal. This would establish the principle, and then direct a RESYSOP2019 style RfC be held to implement. Re-establishing the consensus as a whole is useful, and then directing that a multi-proposal RfC is to be held paves the way. The multi-proposal/statement method tends to work better in these type of cases. TonyBallioni (talk) 02:41, 20 April 2023 (UTC)
I think WP:RFA2021 shows why that doesn't work, though: everyone puts forward their pet proposals, the discussion gets so long that nobody but the diehard policy wonks will take the time to wade through it, and we end up with no consensus. I don't really know what the solution is (maybe it's a brainstorming RfC followed by two or three well-thought-out proposals?), but I just find it hard to see a large multi-proposal discussion getting us any closer to consensus. Extraordinary Writ (talk) 02:59, 20 April 2023 (UTC)
Yeah, but the craziest proposals tend to not get enough support to have consensus, and are usually the later ones proposed. RFA2021 also had the problem (imo) of being about too many principles rather than a single one, and of being an RfC where some people (myself included) didn't participate because no one thought that substantive changes to things that were not RfA would be proposed there.
The differing statements method works well when you have a clearly defined controversial issue that there's agreement something should be done about but no one proposal has received consensus in the past. Things surrounding removal and return of permission is one of them where its worked in the past, imo. TonyBallioni (talk) 05:45, 20 April 2023 (UTC)
Resysop 2019 worked because once the first consensus was found, that it should be tightened, there was a somewhat limited number of ways so consensus could be found. I absolutely agree with EW that this is far more likely to turn into RFA21 where people opposed to community desysop will find flaws with every proposal, not in bad faith but because they genuinely have issues with the concept, as will people who are actually concerned about some specific of that proposal. Best, Barkeep49 (talk) 07:37, 20 April 2023 (UTC)
And there'll be people who don't participate in this RfC, who will then turn out to obstruct anything that by some miracle passes. If WP:RFA2021 didn't teach us that this format doesn't work, WP:ACAS should have. – Joe (talk) 04:39, 26 April 2023 (UTC)
Yeah that's a second reason Resysop 2019 worked: It didn't require on consensus to implement. Rather it empowered (required) a specific group of people to act so people who were unhappy with the result couldn't create a WP:LOCALCONSENSUS during implementation. Best, Barkeep49 (talk) 14:52, 1 May 2023 (UTC)
Yeah, let's not fall into the politician's fallacy, requiring that "something" be done just because it's something. Anomie⚔ 14:56, 29 April 2023 (UTC)
  • I wrote up WP:RRA awhile back. It's a process for the community to review an admin's actions and potentially remove the tools. It was designed to reflect and work with all the current policies/processes. If there's interest, I'm happy to start an RfC on it. - jc37 04:49, 20 April 2023 (UTC)
  • If finding a good process were as easy as telling the community to come up with a process, we would already have come up with a process.... Dekimasuよ! 13:18, 25 April 2023 (UTC)
  • What is this meant to actually achieve? Say there is consensus for this proposal: what then? I don't see how this gets us any closer to coming up with an actual workable implementation of community-based desysop which can in fact gain consensus. Caeciliusinhorto-public (talk) 15:28, 25 April 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Admin block history

I was curious how often admins get blocked, so I did a little data mining. I parsed all the per-year subpages of WP:Successful requests for adminship for account names and pulled all their blocks from the logs. I'm sure there's edge cases I didn't handle correctly; any admin who was renamed won't be handled correctly, for example. And I made no attempt to figure out of the blocks happened while the user held the sysop flag. But it should give you some idea of how often it happens. See User:RoySmith/admin-blocks. -- RoySmith (talk) 18:09, 20 April 2023 (UTC)

@RoySmith Your list currently makes no distinction of blocks vs unblocks, just if it was in the log. Is there a way to check that? Or at least, note the change properly instead of marking unblocks as "indef" Soni (talk) 18:14, 20 April 2023 (UTC)
Good point. I uploaded a new set of results, with the unblocks filtered out. -- RoySmith (talk) 18:38, 20 April 2023 (UTC)
Thank you for this great data. I know it took time, and I appreciate it. How many of these are mistakes? Many admins have accidentally blocked themselves. In the admin interface a block link appears next to every username, including one's own. What about mistaken blocks like this bonehead move which I reversed? Clicked wrong link. What about admin accounts that get blocked after the account no longer has admin rights (the unfortunate downward spiral some have experienced). I think the number of long blocks on current admins is so small that it can be handled bespoke by ArbCom. Jehochman Talk 19:27, 20 April 2023 (UTC)
@RoySmith thanks for that, but would it be possible to get it in a table format so it can be sorted by other things than just username? Maybe also filter out blocks with a duration of less than 1 day (most likely tests) or which were reversed after less than a day (more likely errors)? Thryduulf (talk) 19:36, 20 April 2023 (UTC)
No good deed goes unpunished :-) I'll see what I can do, but I was hoping not to turn this into a major project. The script that does this is 24 lines of python that calls the pywikibot library. If there's any pyhonistas who want to hack on it, it's at https://github.com/roysmith/rfa-stats/blob/main/go.py -- RoySmith (talk) 20:01, 20 April 2023 (UTC)
RoySmith As Thryduulf says, you'll want to ignore admins blocking themselves. It's unlikely to happen these days as Special:Block is far more user-friendly, but it used to be embarrassingly easy to make that mistake, as I have ... twice. Black Kite (talk) 20:32, 20 April 2023 (UTC)
I was "this close" to writing the perfect Quarry Query for this, except my query both started sputtering in the middle bad, as well as having no clear way to handle short term blocks (like 30d etc).
Otherwise I would have just done some form of "Sum of unblock timestamp - Sum of block timestamp" to figure out how long people stayed blocked for. (probably like Now - Unblock timestamp or something using DATEDIFF).
Anyway, I pasted the query link, just in case someone optimises the final bits enough to make it consistently work below 10 mins. Then we can get a CSV of everything we need + summaries (block/unblock times for each admin etc). Soni (talk) 21:39, 20 April 2023 (UTC)
Ha! I was literally blocked one time, for one minute, in 2009, just to get my attention when I was on an AWB run. I imagine this was in the days before AWB would automatically stop when you got a talk page message. BD2412 T 21:49, 20 April 2023 (UTC)
I was blocked for WP:NOTHERE. -- RoySmith (talk) 22:20, 20 April 2023 (UTC)
From the timing I'd have to think this was an April Fools joke. BD2412 T 22:53, 20 April 2023 (UTC)
Worth pointing out, I know admins used to block each other to test how it worked and also for fun way back when. Hiding T 22:42, 20 April 2023 (UTC)
Gathering the data was a good idea, but unfortunately not filtering for whether the user was an admin at the time is an issue also. There are users with multiple blocks after they were desysopped. --RL0919 (talk) 23:16, 20 April 2023 (UTC)
1,882 admin blocks? Wow, way more than I thought. For some reason I had the idea that admins blocking admins was rare. –Novem Linguae (talk) 04:34, 21 April 2023 (UTC)
That's not really an accurate figure. Circa 277 are explicitly tests (include the word "test"), another circa 35 are for wikibreaks and the data also includes errors and blocks from before and after the blockee was an admin. Even then as the data goes back to December 2004, and almost all of them were over a decade ago:
Year Blocks
2004 10
2005 324
2006 376
2007 299
2008 195
2009 122
2010 112
2011 76
2012 37
2013 38
2014 27
2015 51
2016 31
2017 32
2018 47
2019 33
2020 18
2021 27
2022 26
2023 1
Figures found using find and replace, so may not be completely accurate. The one block this year was Barkeep49 partially blocking Geometry guy from WP:BN for 31 hours, after they were desysopped for inactivity. There is no easy way to see how many others were partial blocks. Thryduulf (talk) 09:49, 21 April 2023 (UTC)
I've now looked at all the entries on that list from 2022:
  • 9 were of former administrators (7 different blocks)
  • 6 were testing (3 editors)
  • 5 were mistakes (3 editors, Materialscientist managed to accidentally block themselves 3 times)
  • 1 was a compromised account, subsequently resolved
  • 5 entries relate to Athaenara who was subsequently desysopped (see Arbitration case)
details of blocks of (former) administrators made in 2022
  • Former administrators:
    • 1 72-hour partial block for edit warring (William M. Connolley, desysopped by arbcom in 2009)
    • 1 self-requested block after resigning as an admin (AustralianRupert)
    • 1 block (2 entries) indef ("WP:BLOCKNAZIS"), followed by community ban (Bedford desysopped by Jimbo in 2008)
    • 1 block (2 entries) for 12 hours for violating a community sanction, talk page access subsequently revoked (BrownHairedGirl, Desysopped by arbcom in 2020)
    • 1 indef partial block from 1 page, overturned at ANI after ~3 hours (Fram, desysopped in 2019)
    • 1 indef partial blcok from article and draft namespaces for copyvios (Gryffindor, resigned adminship in 2018)
    • 1 24-hour block for edit warring (Kwamikagami, desysopped by arbcom in 2012)
  • Testing blocks:
    • 3 1-minute self-blocks for testing purposes by Cryptic
    • 2 blocks of own alt-account (that was the former main account) for testing purposes (1 indef unblocked after 2 minutes, 1 24-hours unblocked after ~90 minutes), AmandaNP/DeltaQuad
    • 1 self-block for testing by Samwalton9
  • Mistakes:
    • 1 mistake fixed after 7 minutes (Izno blocked L235 when attempting to block a vandal on L235's talk page.)
    • 3 mistaken self-blocks by Materialscientist, all reversed after 0-1 minutes.
    • 1 mistake fixed after 2 minutes (Gadfium blocked RoySmith when attempting to block someone else)
  • Other:
Thryduulf (talk) 10:43, 21 April 2023 (UTC)
@Thryduulf: I'm not sure what of my actions is being questioned or talked about here. If you need some sort of response from me, please ping again with some additional clarity. Thanks, -- Amanda (she/her) 22:48, 21 April 2023 (UTC)
@AmandaNP: none of your actions are being questioned. This is just a factual list of all the times an account that has or had the admin bit was blocked in 2022 (I've improved the formatting to hopefully make that clearer). Your testing blocks (like the other testing blocks) were completely unproblematic. Thryduulf (talk) 23:00, 21 April 2023 (UTC)
Next time you might use the "noping" template as it links to the username without actually pinging them, since a ping could indeed be considered equivalent to "explain yourself." ⛵ WaltClipper -(talk) 17:46, 23 April 2023 (UTC)
If you do get the information to exclude test, self, and AFD blocks, it would be interested to see which admins placed the most such blocks. Jclemens (talk) 04:33, 25 April 2023 (UTC)
I've looked through the list above and the following is a summary of all the blocks of then-current administrators since 2019 (I've run out of time to look further now, I may do more later if there is interest). Reason is a breif summary, the block log usually contains more detail.
The list excludes: partial blocks, errors, testing, and self-requested blocks.
It includes: blocks that occurred at approximately the same time as a desysop, and blocks that were subsequently reversed (for any reason).
Date Performer Target Reason
2019-03-02 GeneralizationsAreBad Bogdangiusca Compromised account
2019-03-24 Fuzheado Necrothesp Compromised account
2019-05-14 KrakatoaKatie Jerzy {{ArbComBlock}}
2019-06-05 (vanished user) Od Mishehu Sockpuppetry
2019-06-10 WMFOffice Fram Office Action
2019-06-12 WMFOffice Fram Reinstating Office Action
2019-08-09 Huon Ritchie333 Violation of IBAN
2019-10-16 Premeditated Chaos Ritchie333 Violation of IBAN
2019-11-17 Diannaa BrownHairedGirl Personal attacks
2019-12-05 KrakatoaKatie Edgar181 {{ArbComBlock}}
2021-09-28 Ymblanter JGHowes Deceased editor
2021-11-20 Drmies Epbr123 Compromised account
2022-09-10 Paul Erik Staxringold Compromised account
2022-10-11 Floquenbeam Athaenara Hate speech or compromised account
2022-10-12 TheresNoTime Athaenara Reinstate block
In that time period the only editors to have placed two intentional, non-self-requested blocks on administrators for purposes other than testing are KrakatoaKatie (both were in their capacity as an arbitrator) and WMFOffice (both blocks part of WP:FRAMGATE). Thryduulf (talk) 17:40, 25 April 2023 (UTC)

Maybe I have missed something, in which case feel free to deliver the trout of your choice, while pointing me to the thing I missed, but for what reasons would an admin reasonably be blocked for a month? Would any of thesese potential reasons not involve a breach of trust? I have not read everything here: TL,DR would be an understatement, and my head started to hurt about halfway down, but it seems an important thing to consider. Cheers, · · · Peter Southwood (talk): 14:16, 3 May 2023 (UTC)

@Pbsouthwood: an admin may be blocked for a month for (pretty much) any of the reasons a non-admin might be. In at least most cases I would say that a situation rising to that level and the block not being lifted before the end of the month does demonstrate a lack of trust. The only contrary example I can think of would be where the block was very controversial and was still being discussed but there was no neither consensus to unblock nor anyone willing to unilaterally unblock; however if that situation has lasted a month without resolution then it's almost certainly something that's going involve arbcom sooner or later - and they are likely to (partially) unblock them to allow them to participate in a case. Thryduulf (talk) 21:32, 6 May 2023 (UTC)
@Pbsouthwood: I don't think you've missed anything. This discussion has been a waste of community resources and time. Looking at the block logs of current administrators, the three longest blocks (85.3, 79, and 78 days) were self- or self-requested blocks. I don't think we want to desysop for taking a wiki-break unless it extends into our established inactivity criteria. The next two longest blocks (17.2 and 16.2 days) were for compromised accounts. While these were resolved well within 28 days, I don't think we really want to desysop someone whose account is compromised when they're on a wiki-break. Here's your edge case: SarekOfVulcan was blocked by Courcelles for 13.9 days in December 2011 for edit warring: Per e-mail communication. Sarek was initially blocked for 21 days, but was unblocked for time served. So if we want to give this teeth, the 28-day limit would need to be at least cut in half. – wbm1058 (talk) 14:58, 9 May 2023 (UTC)
Actually, if memory serves, I initially blocked for a week and only extended it upon Sarek's request. (I also believe I unblocked based on another request from him, well after the initial week I had felt justified had passed). Going off memory here, as there's nothing important enough here to spend the time sorting through 12 year old emails! Suffice to say, I agree this proposal would have had absolutely zero historical impact. Courcelles (talk) 15:49, 9 May 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Blocking is not punishment?

In another one of those coincidences called ironic twists, the OP complaining about the blocking policy was blocked as a sock. Cheers, ⛵ WaltClipper -(talk) 17:55, 30 May 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

I'm rather confused on the wording on Wikipedia's blocking policy. It says that blocking is supposed to protect the encyclopedia, not to punish an editor for their actions. But that doesn't make sense. Suppose that User:Example is vandalizing and then gets blocked for it. Clearly that means its punishment. Yes, it's protecting Wikipedia, but it is punishment as well. Am I misunderstanding something? I want clarification on this. Svenard (talk) 23:47, 29 May 2023 (UTC)

The purpose of the block is to prevent further damage, not to punish. If, incidentally, it also happens to punish the vandal, that seems better than the alternative of allowing them to continue wrecking Wikipedia. Certes (talk) 00:10, 30 May 2023 (UTC)
So the point of blocking is not to punish, but it does so anyway? I still don't understand how it's not punishment though. Svenard (talk) 00:16, 30 May 2023 (UTC)
@Svenard recently we had a case where a User blatantly evaded their block for over a decade and admitted it. However their edits were constructive, so admins agreed to unblock them, since while they explicitly broke rules, they were not actively harming the Wikipedia project. If we were punitive, we’d have made them wait longer for the sake of it. ~ 🦝 Shushugah (he/him • talk) 00:42, 30 May 2023 (UTC)
@Shushugah I'm not saying that blocks are purely punitive, I'm saying that blocks are preventative and punitive, not just one or the other. Perhaps the policy should be edited, but that's just my opinion. Svenard (talk) 02:00, 30 May 2023 (UTC)
You can have sany opinion you want. It's wrong, clearly, but the thing about opinions is you can keep your wrong opinions and ignore all attempts to correct them. Nothing bad happens to you, unless you consider walking around believing wrong things about the world to be bad. --Jayron32 14:45, 30 May 2023 (UTC)
If a user has continued to make damaging edits after several warnings, they may be blocked. However, if it has been a day or two since the last edit, we normally will not block them unless they start making damaging edits again. The longer it has been since the last damaging edit from a user, the less need there is to block them. Block durations can also be progressive. A first block is often set for a short time (say, 31 hours), which is more of an attempt to get the editor's attention, than to punish them. Progressively longer blocks are intended to persuade the editor to stop making damaging edits. It is only when we have lost hope of the editor making constructive edits that we should improse indefinite blocks. Donald Albury 02:28, 30 May 2023 (UTC)
@Shushugah: Got a link re the decade-long block evasion? Graham87 04:25, 30 May 2023 (UTC)
@Graham87 truthfully struggling to find it in ANI since it's so long, but more critically...I do not believe it is entirely proportionate to link to names, just to provide an example here. ~ 🦝 Shushugah (he/him • talk) 08:41, 30 May 2023 (UTC)
Svenard, I think in part you may be confusing goal or intended effect with side effects. The purpose of chemotherapy for cancer patients is to protect the patient’s life. The fact that it causes your hair to fall out is a side effect, but was not the intent. For one person, having all their hair fall out may be distressing or feel punitive. For the guy who regularly shaves his head, it’s just a money-saving fringe benefit. Mathglot (talk) 09:31, 30 May 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Status of Snow Closes

A contentious Deletion Review was just closed. Well, it was really a contentious one-against-many Deletion Review. One form of the question for the community is whether the Snow clause is a valid basis for an early close of an AFD. The Snow clause is an essay, not a guideline. The most recent effort to raise it to the status of a guideline was not successful. The DRV in question was Wikipedia:Deletion_review/Log/2023_April_29, concerning Wikipedia:Articles for deletion/Christopher W. Shaw.

The appellant and at least one other editor disagreed with early or snow closes in general. However, the large majority of participating editors endorsed the closure, and the DRV was closed as endorsing the closure.

So my first question is whether the community wants to change the status of snow closures, either to deprecate them, or to formalize them as a guideline. My second question is, if it is desired to continue to recognize early or snow closes, why is the provision for them kept at the status of only an essay? Robert McClenon (talk) 02:11, 10 May 2023 (UTC)

WP:SNOW is an invocation of WP:IAR for when there's a snowball's chance in hell of a certain proposal passing. For example, if I were to nominate Earth for deletion, that has a snowball's chance in hell and there's no need to go through the full process. If there is any reasonable disagreement whatsoever, WP:SNOW should not be invoked. When reasonable people disagree and one group wins out, we just call that WP:CONSENSUS, and we have processes for determining consensus. Thebiguglyalien (talk) 04:45, 10 May 2023 (UTC)
A case I recall was Wikipedia:Articles for deletion/Peter Blake (artist). At the time, and now, I didn't think it did Wikipedia's credibility any good for that article to be carrying an AfD template for a week and was relieved when it was snow-closed after 2 days. In cases such as these, I would like to think a nominator would be actively considering others' comments, would "read the room" and withdraw their nomination, but where that level of engagement is absent, I see snow-closure (whether by an admin or not) as a sustainable fallback, so would oppose deprecation. I am inclined to think its current status as an unusual but understandable outcome is about right. AllyD (talk) 05:53, 10 May 2023 (UTC)
It seems clear from the discussion around your recent proposal and the February RfC that there is no appetite in the community to either deprecate them or to promote them as a guideline. The reasons that people support keeping WP:SNOW as an explanatory essay seem to be fairly clear from those discussions – primarily that the status quo works perfectly fine. Why are you bringing this up again only a week after your last proposal to upgrade the essay was closed? Caeciliusinhorto-public (talk) 11:17, 10 May 2023 (UTC)
Per Caecilius, the community (at least the part of it sitting behind this keyboard and typing) understands that explanatory essays are useful as is even if they aren't policy or guidelines. An explanatory essay is a time-saving measure for frequently used explanations. That doesn't make them policy or guidelines, which serve different purposes. Citing WP:SNOW doesn't mean "Wikipedia has a policy we expect you to follow, and here it is", citing WP:SNOW means "Look, it's too much to type this frequently-used explanation out over and over again. Just read this if you want to understand why I am doing what I am doing". Like Caecilius, I am perplexed why you continuously ignore this easy-to-understand idea. --Jayron32 13:17, 11 May 2023 (UTC)
Literally what's been said above, essays can be used as shorthand links to what can be more complex methods. Wikipedia:Don't template the regulars is an essay, but we shouldn't HAVE to make this a policy for people to understand it's meaning when someone removes a series of ill fitting templates from their userpage. WP:STICK is an essay. We don't need to be typing out a long winded explaination as to why people shouldn't continuously state the same information over and over to get the same result. Things being essays are just fine. Please can we snow close this? :P Lee Vilenski (talk • contribs) 14:34, 11 May 2023 (UTC)
Unlike everyone else (apparently), I do think we should elevate WP:SNOW to a guideline if we're going to be closing major discussions based on it. There are some really big-deal essays out there, but there aren't many that are as procedurally important as WP:SNOW. Loki (talk) 14:41, 11 May 2023 (UTC)
SNOW explains a type of WP:IAR, using "per WP:SNOW" is a way of avoiding typing "I am invoking WP:IAR in this case because there's no way this discussion needs to be left open anymore; everyone should be well aware of how it is going to be closed, so leaving it open any more is just silly at this point". It shouldn't be elevated to policy or guideline because it is not a type of policy or guideline, it is a common explanation. Policies are not explanations. Guidelines are not explanations. A good, well-used explanation doesn't magically become a WP:PAG merely because it is well-used. Policies, guidelines, and explanations aren't in a hierarchy, all three serve different purposes, and you don't make one into another by simply declaring it so. WP:SNOW is fine as an explanation because that's its purpose. It is not supposed to guide, it is supposed to explain. --Jayron32 15:55, 11 May 2023 (UTC)
  • My general take on SNOW closures of AfDs is that they should be used with caution. Wikipedia:Articles for deletion/Christopher W. Shaw was a good example of what can go wrong. It's not that there was any doubt about the outcome, but that the risk:reward ratio wasn't convincing. The reward was that we saved 8 hours, but there wasn't any cost to waiting, so there wasn't actually any potential reward at all. The risk was that somebody might object to process not being followed correctly. That's exactly what happened, and it cost us another full week of acrimonious debate. There's a place for SNOW closes, but I'd be looking for a much stronger consensus. I don't do a lot of AfD work these days, but when I was an active closer, I would be looking for unanimous (except for the nom) consensus with 10 or maybe 12 opinions. I would have never SNOW closed that AfD. At the same time, Jay was indulging in pointless wiki-lawyering by opening the DRV. We need some kind of double-headed trout award on this one. -- RoySmith (talk) 14:59, 11 May 2023 (UTC)
    I'm here because of the ping. I think I was right in opening the DRV, and actually did that with the expectation that the AfD close be reverted. I also said that Unless DRV is about outcome all the time, in which case I'm open to be educated, and not visit DRV again except for change of outcome.. There are unanswered questions, including why was the AfD closed 8 hours early. I respect the DRV close, so if this is an attempt to "review" what happened at the DRV, I won't be analyzing anyone's votes or comments. You may have your opinion about the DRV, and trouting is your prerogative! Jay 💬 15:18, 11 May 2023 (UTC)
    Nothing would have gone wrong in that case, except for one person who insists on playing the rules game. You shouldn't hold up that absolute farce of an example of "what can go wrong". We don't write or amend policy to deal with singular examples of silliness like that. People sometimes do unpredictably silly things. I've only been an active editor at Wikipedia since 2006, so maybe I'm still too new around here to know if this is a widespread problem, but I've never seen anything like that before. --Jayron32 15:32, 11 May 2023 (UTC)
In my opinion, SNOW is properly tagged as what it is: a supplement to IAR. casualdejekyll 22:03, 11 May 2023 (UTC)

I think that snow decisions are an example of the not-explicitly-acknowledged method of how Wikipedia operates Which involves weighing multiple considerations. In this case they include:

  • How overwhelming is the sentiment expressed?
  • How controversial/non controversial is the topic?
  • How high or low of an impact is the topic on Wikipedia as a whole?
  • Has it been open long enough to get what is likely to be a representative sampling (including taking number of eyes/visibility into consideration)?
  • Have any sincere objections to the early close process been expressed?

Unless any guidelines acknowledged this, I think it would do more harm than good. Sincerely, North8000 (talk) 15:34, 11 May 2023 (UTC)

Wikipedia is not a bureaucracy. "Although some rules may be enforced, the written rules themselves do not set accepted practice. Rather, they document already-existing community consensus..." Wikipedia:Snowball clause is a prime example of documenting community practice. It is not intended to be written down as a rule (or five hundred legalists will show up asking for exact numbers on when it can and can't be used), but rather as an explanation: "just why was this discussion closed early"? Others like this include Wikipedia:Deny recognition, Wikipedia:Competence is required; all powerful, and often cited, but not rules in the sense of "what we should do", rather explanations of "why did we just do that?" --GRuban (talk) 21:29, 11 May 2023 (UTC)

I feel that if anything is supposed to be closed (or someone even blocked, ban, IP block/ban,RfCs) all of that the exact policy needs to be stated as the reason for closure and not some essay. The essay can be used in an explanation for using the policy and the closure and keep/delete. I also agree that if one person goes against the norm as stated above you have 45 keeps and 3 deletes it should not be closed using WP:SNOW and should be ran it’s normal 7 days instead of rushing things. No essay should ever be used as a criteria for an admins actions. I remember a few years ago I think someone wrote an essay and it became a quoted reason for blocking named users/ips without an RfC for making it a policy. It appears when I look through various essays and other items of interest there is a lot of overlap between them all. Like they were cherry picked to form a policy that encompasses various authors ""views"" that do not reflect the consensus of or viewpoints of others. I also notice a lot of people who vote on these things are almost always admins. We should have a policy that there has to be a certain amount of editors (below admin level) have to also participate and vote or it fails. So if it is 65-30 then 65 of the votes has to be 32 regular editors or as close to 50/50 as possible to ensure it’s a consensus and not an admin group setting up the RfC to pass because they want it to. Just my 3¢ worth. — Preceding unsigned comment added by 2600:8801:CA05:EF00:4405:B060:E0C7:DB35 (talk) 07:15, 19 May 2023 (UTC)
It sounds like you believe that nobody should be blocked, no page should be deleted, etc. unless an "exact policy" is named as a justification.
We have a policy called Wikipedia:Ignore all rules. We have another policy that says not to worry too much about the exact policy, because the written wording isn't the key point.
It is literally impossible to follow our written policies and to also require an exact policy to be named as a justification for every admin action. WhatamIdoing (talk) 22:31, 19 May 2023 (UTC)
@WhatamIdoing Sorry if my statement was misleading to you or others. I agree that it is literally impossible to know all the rules and is a reason I think all editors choose an area they like to write about and with the various function, resolutions, etc admins are usually picky on what they want to focus on as well. Some will do vandalism and block others just want to do other things perhaps just behind the scenes (ie the technically adept who work a lot on bots and other projects for Wikipedia). I do think if a discussion is going to be shut down before the time it is due to it is not hard to say “CLOSED PER WP:IAR using WP:SNOW as reason” I have seen admins write longer closing statements then that on a majority of these. With the blocking I’m ok with it as I stated above. It should be a valid reason though and not using an essay as if it’s the policy they are using to enforce their actions. I hope that helps you. I’ll be happy to explain/clarify anything you or others need. 2600:8801:CA05:EF00:4405:B060:E0C7:DB35 (talk) 10:55, 20 May 2023 (UTC)
I don't think I was clear. The English Wikipedia does not operate according to some set of written rules. What you said about "the policy they are using to enforce their actions" is ... just not how it works, at least if you understand "policy" to be a written document.
When we say that admins need to follow policy, we mean that admins need to follow "A principle of behaviour, conduct etc. thought to be desirable or necessary" (from Wiktionary). We do not mean that admins need to follow "the exact words on a particular page on wiki, at the top of which you will find the {{policy}} template".
This may be more challenging for my fellow Americans to grasp (compare the Constitution of the United Kingdom, which is quite different in style from ours), but if the principle in question is "Don't deliberately harm the articles", then the policy is any accurate explanation of that principle at all. Someone addressing problematic behavior could choose to link to Wikipedia:Vandalism, which is labeled a policy, but they could equally choose to link to Wikipedia:Do not disrupt Wikipedia to illustrate a point, which is labeled a guideline, or Wikipedia:Revert, block, ignore, which is labeled an explanatory essay, or Wikipedia:Don't demolish the house while it's still being built, which is labeled an essay, or Wikipedia:Don't lie, which is labeled an essay, or nothing at all, and just say something like "Dude, stop deliberately harming the articles already. It's not funny." So long as those accurately support the principle, then any of them are acceptable explanations for an admin action. WhatamIdoing (talk) 01:13, 21 May 2023 (UTC)
You might want to read Wikipedia:The difference between policies, guidelines and essays. WhatamIdoing (talk) 01:15, 21 May 2023 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(policy)/Archive_181&oldid=1168798775"