Wikipedia:Village pump (policy)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Jc37 (talk | contribs) at 08:57, 19 May 2023 (response). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

 Policy Technical Proposals Idea lab WMF Miscellaneous 
The policy section of the village pump is used to discuss already proposed policies and guidelines and to discuss changes to existing policies and guidelines.

Please see this FAQ page for a list of frequently rejected or ignored proposals. Discussions are automatically archived after remaining inactive for two weeks.

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)Reply[reply]

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 (talkcontribs) 09:29, 21 March 2023 (UTC)Reply[reply]
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)Reply[reply]
What would be the point of that? Thryduulf (talk) 13:58, 21 March 2023 (UTC)Reply[reply]
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)Reply[reply]
? 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)Reply[reply]
Courtesy pings to Adamtt9, Nirmaljoshi, Pvmoutside and Sakiv. Paradise Chronicle (talk) 16:26, 21 March 2023 (UTC)Reply[reply]
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)Reply[reply]
The reference point has been corrected...Pvmoutside (talk) 01:26, 23 March 2023 (UTC).Reply[reply]
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)Reply[reply]
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 (talkcontribs) 14:23, 21 March 2023 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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 (talkcontribs) 22:15, 21 March 2023 (UTC)Reply[reply]
@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)Reply[reply]
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 (talkcontribs) 07:09, 22 March 2023 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
@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)Reply[reply]
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)Reply[reply]
@Rhododendrites Why does creation (mass or otherwise) without problems need addressing? Thryduulf (talk) 22:04, 21 March 2023 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
Thank you for the explanation and also the constructive suggestion. Paradise Chronicle (talk) 15:52, 22 March 2023 (UTC)Reply[reply]
@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)Reply[reply]
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)Reply[reply]
@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)Reply[reply]
@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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
@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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
@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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
  • Oppose due to the "rate doesn't matter" and inclusion of boilerplate text. — Rhododendrites talk \\ 14:15, 4 May 2023 (UTC)Reply[reply]
  • Oppose Boilerplate text is standard in most articles as they tend to have a common structure and phrasing. Templates are commonly created for the purpose and are used extensively. Andrew🐉(talk) 12:33, 6 May 2023 (UTC)Reply[reply]


  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)Reply[reply]

@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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
  • 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)Reply[reply]
    • 🙄 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)Reply[reply]
      • 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)Reply[reply]
        • 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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
"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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
I'm familiar, yes. It was a mistake. SnowFire (talk) 04:04, 19 April 2023 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
blocked user evading block--Jayron32 17:14, 16 May 2023 (UTC)Reply[reply]
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) . (talk) 13:15, 16 May 2023 (UTC)Reply[reply]
This makes no more sense than when you wrote similar gibberish in that now closed discussion. --Jayron32 16:43, 16 May 2023 (UTC)Reply[reply]
  • 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)Reply[reply]


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)Reply[reply]

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.

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)Reply[reply]

Proposal: 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.

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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    Actually, editing their own talk page would be enough to forestall the annual edit requirement. Courcelles (talk) 13:33, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    People could want to have a pblock? —Kusma (talk) 17:06, 17 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
    Only sitewide block should be considered for the removal of administrators. Thingofme (talk) 14:09, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    That was my guess. Can someone confirm it would actually work the same way via software? Martindo (talk) 06:44, 26 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • In the proposal, admins can desysop other admins. There is no community element. —Kusma (talk) 15:18, 17 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
    Only admins can initiate the desysop review by blocking. The community can't initiate this. —Kusma (talk) 15:53, 17 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    +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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    @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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Comment Also @Worm That Turned: maybe this should be listed on WP:CENT or similar. Soni (talk) 15:33, 17 April 2023 (UTC)Reply[reply]
    It's already been on CENT :). Best, Barkeep49 (talk) 15:44, 17 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
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)Reply[reply]
  • (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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    @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)Reply[reply]
    ...and Spartaz was blocked for 79 days in 2018 as well, per their request. – wbm1058 (talk) 21:22, 7 May 2023 (UTC)Reply[reply]
    That was before my RfA. SmartSE (talk) 18:31, 17 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    ...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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    @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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support - (another admin here). I think Wugapodes and Beeblebrox have explained why. - Donald Albury 17:46, 17 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support because it's something. Moneytrees🏝️(Talk) 19:46, 17 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
"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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
    @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)Reply[reply]
    @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)Reply[reply]
    @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)Reply[reply]
    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)Reply[reply]
  • Support per Ritchie333 and Beeblebrox. I have nothing to add to their words. LEPRICAVARK (talk) 22:48, 17 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    • Ivanvector, the proposal already covers this with Administrators who have their sysop user-right removed in this manner are not eligible to simply request return at bureaucrat's noticeboard, right? Or is there something else you'd prefer? Extraordinary Writ (talk) 23:35, 17 April 2023 (UTC)Reply[reply]
      Thank you, I misread. Comment revised. Ivanvector (Talk/Edits) 15:24, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
    "Preventative, not punitive" is a very, very good point. - jc37 06:10, 18 April 2023 (UTC)Reply[reply]
  • Support per Ritchie333 and Beeblebrox.Pharaoh of the Wizards (talk) 05:41, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • Support per Worm That Turned and Ritchie333. ✠ SunDawn ✠ (contact) 11:39, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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 - 20:35, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    Added an alternative proposal relying on WP:LEVEL2 below. Martinp (talk) 18:12, 19 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Support - if blocked for that amount of time, indeed a desysopping is in order. Atsme 💬 📧 02:44, 20 April 2023 (UTC)Reply[reply]
  • Oppose this specific policy implementation but not the general idea of such a process. Andre🚐 02:47, 20 April 2023 (UTC)Reply[reply]
  • Support per Barkeep, Beeblebrox, et al. firefly ( t · c ) 08:27, 20 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Oppose as a solution looking for a problem. Stifle (talk) 10:14, 20 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Oppose this is an overly baroque procedure. I'm supporting the alternate proposal instead. Jahaza (talk) 16:54, 20 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose mainly per TonyBallioni's lengthy oppose and Stifle's pithy one.--Bbb23 (talk) 23:12, 24 April 2023 (UTC)Reply[reply]
  • Support this with reasonable exceptions as needed, and also support TonyBallioni's proposal. – John M Wolfson (talk • contribs) 23:30, 24 April 2023 (UTC)Reply[reply]
  • Oppose - Can't see how this is needed or useful. Paul August 23:34, 24 April 2023 (UTC)Reply[reply]
  • Support - very reasonable.--Dl.thinker (talk) 23:47, 24 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Oppose grave punishment done mechanically without deliberation. Lokys dar Vienas (talk) 04:06, 25 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose Reading through all the arguements above, Sandstein's was the most persusaive. The Squirrel Conspiracy (talk) 09:56, 25 April 2023 (UTC)Reply[reply]
  • 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 (talkcontribs) 12:11, 25 April 2023 (UTC)Reply[reply]
  • Oppose per Sdrqaz and The Wordsmith. OhanaUnitedTalk page 13:19, 25 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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 [1] 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support This seems like a reasonable policy. Martindo (talk) 06:59, 26 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose Too many weird edge cases in this proposal, as already well described by others. Anomie 14:56, 29 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Support – This is a "Like, duh!" proposal, so of course it's opposed. Welcome to Wikipedia. --IJBall (contribstalk) 00:16, 30 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose Needlessly bureaucratic and WP:CREEPy. Some1 (talk) 14:03, 30 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose for basically the same reasons as Visviva.-- Aervanath (talk) 10:05, 3 May 2023 (UTC)Reply[reply]
  • 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 (utc) 12:26, 3 May 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Support but enforcement should consist of removing admin rights on day 28. Aasim - Herrscher of Wikis ❄️ 15:08, 3 May 2023 (UTC)Reply[reply]
  • How often does this happen? Guy (help! - typo?) 17:11, 3 May 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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 (tc) 11:13, 6 May 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose per Tony. "Community desysop" should−explicitly and without exception−require community consensus. —Rutebega (talk) 19:44, 11 May 2023 (UTC)Reply[reply]
  • Support, though not an admin, my beliefs are the same as RickinBaltimore. InvadingInvader (userpage, talk) 04:15, 12 May 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]

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)Reply[reply]

"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)Reply[reply]

(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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]

"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)Reply[reply]

  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    @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. (talk) 00:59, 9 May 2023 (UTC)Reply[reply]
    @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)Reply[reply]
    @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)Reply[reply]
    @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)Reply[reply]
    The Neelix case took four days. Guy (help! - typo?) 17:17, 3 May 2023 (UTC)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
@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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
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)

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)Reply[reply]

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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support as above Ritchie333 (talk) (cont) 10:21, 18 April 2023 (UTC)Reply[reply]
  • Support per WTT. Thryduulf (talk) 10:35, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • "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)Reply[reply]
    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)Reply[reply]
    I never really agreed with that in the first place anyway. --Rschen7754 23:25, 18 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support, in addition to the original proposal above. Boing! said Zebedee (talk) 16:27, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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 (talkcontribs) 17:35, 18 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support Not much more to add. Admins and 'Crats must retain the community's trust --Enos733 (talk) 20:06, 18 April 2023 (UTC)Reply[reply]
  • 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 - 20:37, 18 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
    And, BTW this is a better proposal than the initial one. North8000 (talk) 17:29, 19 April 2023 (UTC)Reply[reply]
  • Support even if seldom used, this will be a start for community based decisions. Graeme Bartlett (talk) 23:19, 18 April 2023 (UTC)Reply[reply]
  • Support contains the spirit of the original proposal without the drama-adding elements. --Rschen7754 23:24, 18 April 2023 (UTC)Reply[reply]
  • Support as a minimum. AndyTheGrump (talk) 23:56, 18 April 2023 (UTC)Reply[reply]
  • Support for the same reasons I !voted support above. -FASTILY 02:09, 19 April 2023 (UTC)Reply[reply]
  • Support simple and straightforward. Legoktm (talk) 03:57, 19 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Support, as a CBAN is a clear indication of the loss of the community's trust. ScottishFinnishRadish (talk) 13:57, 19 April 2023 (UTC)Reply[reply]
  • Support per WTT. Ajpolino (talk) 14:59, 19 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • Support other have already said everything I could say. -- LCU ActivelyDisinterested transmissions °co-ords° 21:30, 19 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Support per my comments above. TonyBallioni (talk) 02:05, 20 April 2023 (UTC)Reply[reply]
  • Support Andre🚐 02:49, 20 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Support I think usage othis will be incredibly rare but it's conceptually sound. Best, Barkeep49 (talk) 07:52, 20 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support in addition to the proposal below. Beyond My Ken (talk) 09:11, 20 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Oppose, solution looking for a problem. Stifle (talk) 10:12, 20 April 2023 (UTC)Reply[reply]
    • 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)Reply[reply]
  • 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)Reply[reply]
    Hi Jehochman. The survey about long blocks is before this one. This one concerns site bans. - jc37 13:07, 20 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
  • Support per WTT Pharaoh of the Wizards (talk) 16:35, 20 April 2023 (UTC)Reply[reply]
  • Support a bit narrow but I don't see any problems with this —pythoncoder (talk | contribs) 18:09, 20 April 2023 (UTC)Reply[reply]
  • Support This sounds good too. - Who is John Galt? 21:33, 20 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose as pointless - it appears this situation has never happened in recent history. * Pppery * it has begun... 21:18, 21 April 2023 (UTC)Reply[reply]
  • Support as codifying what should be common sense. Giraffer (talk·contribs) 14:34, 22 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    Done - I already noted it did not include limited bans, but added the clarification anyway. - jc37 16:29, 22 April 2023 (UTC)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support - a natural, I'd say merely technical extension of ban. Lokys dar Vienas (talk) 03:56, 25 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose. Unnecessary, a solution in search of a problem. Nsk92 (talk) 11:47, 25 April 2023 (UTC)Reply[reply]
  • Support This formalises what should be obvious. talk to !dave 12:15, 25 April 2023 (UTC)Reply[reply]
  • Support.--Jerome Frank Disciple (talk) 13:57, 25 April 2023 (UTC)Reply[reply]
  • Oppose as an absurd weakening of the original proposal. Figureofnine (talkcontribs) 14:49, 25 April 2023 (UTC)Reply[reply]
    These proposal are not exclusive. — xaosflux Talk 12:45, 27 April 2023 (UTC)Reply[reply]
  • Support: a plainly fine proposal; far better than nothing. ~ Pbritti (talk) 19:39, 25 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • Oppose as unnecessary any C-banned admin would almost certainly be desysoped by Arbcom. Lightoil (talk) 08:39, 26 April 2023 (UTC)Reply[reply]
  • Support Seems like a great idea to me. -- Grapefanatic (talk) 14:45, 26 April 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)