User talk:Geo Swan
A blocked user on Wikipedia: https://en.wikipedia.org/wiki/Special:Contributions/Geo_Swan
Contents
First block on Wikipedia
March 2021
- You need to explain that article that Template:U deleted, Dan Trotta, which you seem to have created following a personal off-wiki dispute with the person. You cannot just move on as if nothing happened. I've placed a note at WP:AN for other administrators to weigh in on the matter. You may respond here, and your comments will be copied over. Drmies (talk) 15:09, 3 March 2021 (UTC)
- See Wikipedia:Administrators' noticeboard#Block of User:Geo Swan (permalink). Johnuniq (talk) 08:41, 4 March 2021 (UTC)
Second block on Wikipedia
Action review: Geo Swan and imissdisco
Template:Atop Background: [[1]]
Today I noticed a back-and-forth between these two editors at Geo Swan's talk page. Per the background link above, evidently Geo Swan was blocked almost a year ago for creating an article about Dan Trotta while involved in a dispute at commons with imissdisco, which claims to be Trotta's account (I have no way of confirming this). About two weeks ago Geo Swan began posting a "plan for reinstatement" to their talk page. imissdisco, who has not edited this wiki except in relation to this dispute, began to challenge various things that Geo Swan was adding to their "plan", and their conversation became hostile.
Reviewing the talk page, I came across a diatribe in which Geo Swan threatened to ping the blocking admin daily until getting a satisfactory response. Admins are required to be accountable but there is no requirement to be publicly flogged until the offended party is satisfied, particularly in this case where the blocking admin's action was already discussed by the community (background link above). As such, I revoked Geo Swan's talk page and email access, standard practice for overt threats of harassment.
I also par-blocked imissdisco from Geo Swan's talk page, given their unreasonably aggressive tone and threats of their own, because the dispute at commons that started this whole thing seems to still be ongoing and is spilling over here again, and because Geo Swan won't be able to respond anyway.
I understand that the situation between these two editors is somewhat sensitive because the deleted page I won't link to was characterized as an attack page and because one of the parties is allegedly the target of that page (in other words it began with harassment) and so I'm requesting a review of the situation and my actions. Ivanvector (Talk/Edits) 17:10, 24 February 2022 (UTC)
- Cat o'nine tails for Template:U obviously. But, seriously, that looks fine (Template:Nao), obvs); notwithstanding Geo Swan's plan for reinstatement, I would say he was more likely to be heading towards a site ban than away from it. It's a shame imissdisco has to be blocked from the talk, but they have absolutely no reason to be editing it that I can see. Although if GS is also harassing her on other wikis (did I see her say that?), that makes her ire very understandable, although not something we can address on en-wp. SN54129 17:24, 24 February 2022 (UTC)
- Endorse. This looks like a reasonable response to an unpleasant and disruptive situation. --Jayron32 17:30, 24 February 2022 (UTC)
- Template:Nao Partial endorsement. I've been observing this for some time. It seems to me that Template:Noping has been poking Template:Noping with a sharp stick. I am steering clear of the origfinal infraction. I consider, however, that all parties in a dispute are expected to conduct themselves with decorum. Perhaps the original issue was sufficient to cut the stick wielder some slack, but I wonder if the administrative action has gone far enough. My expectation is that, whatever the provocation they should avoid the talk page where they are poking with sticks. FiddleTimtrent FaddleTalk to me 17:55, 24 February 2022 (UTC)
- A clarification. Template:U is not the blocking admin. He gave a warning, and Template:U subsequently blocked. The block was overwhelmingly confirmed at a discussion here at AN [2]. Geo Swan seems to want to argue about the warning first, before requesting an unblock. I don't know if HJMitchell was even aware of the the posts: it doesn't seem required to watchlist a page almost a year after giving a warning, and the first actual ping was yesterday, I believe, though does it even work if you add a ping to previous text? In any case, Geo Swan continuing to argue that he was right, including ramping up the situation by asking for the undeletion of the contested picture at Commons (apparently in order to force Imissdisco to self-identify officially), seems very, very unlikely to convince editors to unblock him here. Slp1 (talk) 17:58, 24 February 2022 (UTC)
- A ping only causes a notification if you sign the same edit that you add it with. —Compassionate727 (T·C) 19:37, 24 February 2022 (UTC)
- And if you go to Special:Preferences#mw-prefsection-echo-blocknotificationslist and fill in a harasser's username, you won't see those pings no matter how often they're sent. WhatamIdoing (talk) 19:54, 26 February 2022 (UTC)
- A ping only causes a notification if you sign the same edit that you add it with. —Compassionate727 (T·C) 19:37, 24 February 2022 (UTC)
- Geo is incapable of collegiately editing, which is a shame because he has also provided good content. I don't know the IP, but agree with them in the request that Geo's response warranted further eyes, although I don't fault anyone in opting not to. Engagement with them is unnecessarily hostile, which is why I asked them not to email me. They had talk page access and did not need to resort to off wiki communications because they believe others need to be at their beck and call. Star Mississippi 18:01, 24 February 2022 (UTC)
- Wait, Geo Swan is still writing about Trotta and still using the photo Trotta objected to elsewhere on the Internet as recently as this month? It seems like we're moving closer to Trust & Safety territory than an unblock. The summary Imissdisco posted at Geo Swan's talk page seems helpful. As he admits, he's not a Wikipedian and made the initial photo request without understanding how things work simply because he didn't like the photo. That's something we see every day. Yes, it can be annoying when you're oriented towards building a free knowledge resource and someone wants to remove an illustration just because they don't like it, but from the subject's standpoint it's completely reasonable. So when it wouldn't hurt much, or when there's something unusual about the case, we try to accommodate those requests. But Geo Swan went to great lengths to ensure it would never be deleted and, moreover, spread the photo to even more locations. It's wildly inappropriate, and I really don't see a way forward for Geo Swan without owning up to that, without pointing fingers, doing everything they can to undo the harassment, volunteering for a topic ban about Dan Trotta, and probably some other BLP restrictions. Given the current situation, I support the actions at the top. (And btw I'm not even saying the photo should've been deleted. It was two years old, was just a crop of a group photo that wouldn't have been deleted, and Commons errs on the side of preservation both due to its broad scope and to protect anyone who may have used that photo outside of Wikimedia projects and is counting on Commons documenting the license.) — Rhododendrites talk \\ 18:23, 24 February 2022 (UTC)
- I participated at GeoSwan's talk page, but my advice was not taken. As I wrote there, he's an amazing editor and I hope he can eventually get over himself and be allowed to return here. In general we allow blocked users understandable latitude in expressing their frustration on their talk pages, so I hope we can avoid ourselves doubling down here, and at least avoid removing that; he's not doing a very good job of advocating for his return, but he is trying. --GRuban (talk) 18:34, 24 February 2022 (UTC)
- Template:Tq In the immediate aftermath of the block, yes. Not almost a year later.-- Pawnkingthree (talk) 18:45, 24 February 2022 (UTC)
- Maybe I'm looking at the wrong deleted article, but the last deleted article of GS doesn't look like an attack to the naked eye. imissdisco did look like they were wholesale deleting sections they didn't like. What about it is attack? What am I missing? Dennis Brown - 2¢ 01:20, 25 February 2022 (UTC)
- It was created for the purpose of bothering the BLP subject, while the GeoSwan was actively arguing with and insulting the subject on Commons. GeoSwan said ahead of time that it would be a dick move to create the article, and did so anyway. Cullen328 (talk) 01:50, 25 February 2022 (UTC)
- Ah, thank you. For what it is worth, the article itself was fairly benign. Dennis Brown - 2¢ 13:46, 25 February 2022 (UTC)
- It was created for the purpose of bothering the BLP subject, while the GeoSwan was actively arguing with and insulting the subject on Commons. GeoSwan said ahead of time that it would be a dick move to create the article, and did so anyway. Cullen328 (talk) 01:50, 25 February 2022 (UTC)
- GeoSwan's behaviour over the last few days suggests they need a community ban, and certainly not unblocking at any point. Black Kite (talk) 19:09, 25 February 2022 (UTC)
- I support any block or ban of Geo Swan that we have the power on en.wiki to implement or endorse. A year later, Geo Swan is still acting in an emotionally reactionary way, unable to control their temper in the way that I would expect a Wikipedian to be able to do were the incident something that happened yesterday, and making threats of harassment (to HJ Mitchell). They display no understanding of why they were blocked, and Imissdisco (whose comments are quite tame) alleges continued off-wiki harassment. Geo Swan says that they were drunk while committing harassment against Imissdisco, but that is a matter for more concern, not less. This is becoming a T&S matter, as Rhododendrites says.Template:PbLastly, while my condolences go to anybody who is experiencing grief, editing Wikipedia is a privilege and not a right, and we have precedent of not lifting blocks/bans that were issued after impulsive behaviour by a person experiencing serious negative life events due to the pandemic. The question here is "will this person be a net positive if unblocked?", not a question of fairness. — Bilorv (talk) 13:50, 26 February 2022 (UTC)
- Considering GeoSwan is using their Talk page to argue about the block, rather than attempting to appeal, I'd suggest revoking Talk page access & making them use UTRS. This obsession of his is getting out of hand. — The Hand That Feeds You:Bite 20:59, 26 February 2022 (UTC)
- Support full-fledged site ban of Geo Swan, and I'd probably support a T&S ban too. I do not recall crossing paths with Geo Swan, but I do recall having a high opinion of his past work, and being shocked to find he'd been indef'd... and then disgusted after reading why. We must reject and act against any forms of harassment; Imissdisco does not deserve this treatment. If Geo Swan is still obsessing over this matter nearly a full year on from the imposition of his indefinite block, then I think we can safely say that he is no longer "here". --Dylan620 (he/him · talk · edits) 00:10, 27 February 2022 (UTC)
- Support ban GeoSwan has been repeatedly counselled over many years for a range of BLP issues relating to their editing (e.g. creating negative articles on people for what appear to have been WP:COATRACK purposes, creating articles on non-notable people accused of terrorism, etc - see the various reports via [3], Wikipedia:Requests for comment/Geo Swan and the list of articles they created which have since been deleted at [4] - most of the 708(!) are BLPs). As they are continuing problematic behaviour related to BLP while blocked for this, a ban is clearly in order given there appears to be no likelihood they will be ever adhere to the key BLP policy. Nick-D (talk) 00:35, 27 February 2022 (UTC)
- Support per my original comment. SN54129 13:21, 28 February 2022 (UTC)
- This action seems entirely appropriate to me. There have been problems with Geo Swan's editing, especially concerning BLPs, for a very long time. It should not be necessary to explain to an editor of GS's experience why weaponising Wikipedia in such a way is abhorrent, and that he still doesn't get it a year later shows that the block is clearly still necessary. His conduct on his talk page unfortunately necessitated the removal of his ability to edit that as well. HJ Mitchell | Penny for your thoughts? 22:58, 28 February 2022 (UTC)
- Endorse admin action and support site-ban. I take a very dim view of using our internal processes to harass someone, regardless of good work that they did. Reminds me of Tenebrae, but arguably milder. Still, harassment is not to be tolerated. Jip Orlando (talk) 15:57, 3 March 2022 (UTC)
- Support Site-Ban. We don't need an editor who seems to have spent a year seeking vengeance. I haven't researched their record as a content editor, but we don't need editors whose desire for revenge appears to be greater than their desire to contribute to the encyclopedia. Robert McClenon (talk) 23:39, 3 March 2022 (UTC)
- He's one of the top 1000 editors of all time. Wikipedia:List of Wikipedians by number of edits/1–1000. He specializes in the losing side of politics - for example he wrote a huge series of articles about the Guantanamo Bay detainees. His desire to contribute to the encyclopedia is quite strong. I hope the revenge thing was a one-time aberration, and he will promise to cut it out - though I admit he hasn't yet. --GRuban (talk) 12:44, 8 March 2022 (UTC)
- Endorse removal of talk page and email.
- Endorse partial block of imissdisco
- Support site ban of GeoSwan . A once great editor who continues to try to harass people. --Deepfriedokra (talk) 00:37, 14 March 2022 (UTC)
- Laments being blocked on Wikipedia, yet continues the same destructive behavior?
While drunk? (what!) Classic lack of insight. Wikipedia is not therapy-- or AA.--Deepfriedokra (talk) 00:42, 14 March 2022 (UTC)- i cannot reach WikiAlpha. Is it me, or is it down? --Deepfriedokra (talk) 01:05, 14 March 2022 (UTC)
- Have a trout... ><((()))> Dennis Brown - 2¢ 01:13, 14 March 2022 (UTC)
- Laments being blocked on Wikipedia, yet continues the same destructive behavior?
- Support Site-ban The fact that he is still doing this means that any unblock should have to be approved by the community. This is unacceptable. Scorpions13256 (talk) 14:53, 15 March 2022 (UTC)
- Support site ban, as I reported to several blocks, it does not accept the unblock requests and to approved to ban in the English Wikipedia. Maanshen (talk) 04:21, 16 March 2022 (UTC)
Darkness Shines unban appeal (for discussion)
Template:Atop
Copied from User talk:Darkness Shines
It has now been four years since the community voted to ban me from Wikipedia. For the last two years I requested of the arbitration committee that I be allowed to edit again. However given it was Wikipedias editors who decided I had become a net negative, I believe it is those editors who I ought to need to appeal to. I fully admit to being short of temper, frequently drunk, and quite often profane to the extreme. But that was four years ago, and I have changed for the better. I no longer drink to excess . I am far calmer and not prone to losing my temper as I used to, perhaps because I drink far less, or maybe I've just gotten calmer with age. So I'm asking the community if they would allow me the privilege of editing again, should anyone have questions for me please feel free to post here. If someone would be so kind as to copy paste this to where a majority of editors will see it I'd be grateful. Thanks ¬¬¬¬
- I have one, why is this so important to you? Slatersteven (talk) 18:02, 6 March 2022 (UTC)
- I enjoy editing and creating articles, it's that simple really. Darkness Shines (talk) 18:04, 6 March 2022 (UTC)
- To expand on that, creating something that anyone in the world can access for free, well who wouldn't want to be allowed to do that? Darkness Shines (talk) 18:07, 6 March 2022 (UTC)
- Template:Tpw It's certainly ironic, considering the number of editors we have whose very successful wiki-careers are built around everything but content creation. Hey ho. SN54129 19:54, 6 March 2022 (UTC)
- Admittedly, I'm biased. But, assuming that there aren't any red flags (socks), I'd support allowing DS to edit again. Agree that DS is aggressive and often (apologies, DS) sloppy in their haste to add content. But they have added a lot of useful content to Wikipedia and I consider DS a net positive. I should also mention DS's ability to identify nangparbat socks is unparalleled. --RegentsPark (comment) 20:39, 6 March 2022 (UTC)
- A Checkuser was recently run on my account, hilly Billy Holiday socked with a similar sounding username. I have no other accounts and have not edited since my ban. Darkness Shines (talk) 21:34, 6 March 2022 (UTC)
- This is documented at Hillbillyholiday's SPI - it may read a little confusing, but I can confirm it's the case. I can also confirm, being somewhat familiar with the technical circumstances, that I have nothing to add from a checkuser perspective. In other words, it gets a tentative green light from me. -- zzuuzz (talk) 22:39, 6 March 2022 (UTC)
- A Checkuser was recently run on my account, hilly Billy Holiday socked with a similar sounding username. I have no other accounts and have not edited since my ban. Darkness Shines (talk) 21:34, 6 March 2022 (UTC)
- Admittedly, I'm biased. But, assuming that there aren't any red flags (socks), I'd support allowing DS to edit again. Agree that DS is aggressive and often (apologies, DS) sloppy in their haste to add content. But they have added a lot of useful content to Wikipedia and I consider DS a net positive. I should also mention DS's ability to identify nangparbat socks is unparalleled. --RegentsPark (comment) 20:39, 6 March 2022 (UTC)
- I generally prefer a formal probationary period for situations like this (where self control appears to be the issue) of something like 3 or 6 months. But I'd support without that as a second choice. The issue appears to be solely self control, and it's been ~4 years. Worth another try for someone with a strong content history IMO. Hobit (talk) 23:35, 6 March 2022 (UTC)
- Accept appeal and I'm willing to accept any probationary steps others think are appropriate. I remember DS vividly, as both an excellent defender of sources, and as a major pain in the ass. I'm glad he mentions drinking in the appeal, something some of us already knew was part of the problem. (but I wouldn't have mentioned it unless he had). If DS comes back and stays away from the extremes, he really is a big net plus. He has that potential. Whether or not he lives up to it, only time will tell, but it has been long enough that I feel we should give him a last, 2nd chance. Dennis Brown - 2¢ 23:42, 6 March 2022 (UTC)
- Strong oppose. I really don't know where some people are getting this idea from that DS was somehow a potentially useful contributor with only a short temper being a problem. No, DS was never a useful contributor. His main problems were always incompetence and tendentiousness. He wasn't forever edit-warring because he had a short temper; he was forever edit-warring because he was always drawn into editing articles where he had a massive tendentious POV, didn't have the self-restraint to stop him from filling articles with poorly-digested, poorly-written and poorly understood tendentious POV fluff, and lacked the intellectual acumen to engage meaningfully on talk about these issues. Yes, he wrote a lot of content – a lot of uniformly bad content. He's the only editor I ever knew who managed to get himself topic-banned from at least three political hot-issue areas at once (Eastern Europe, India/Pakistan, and US politics); this didn't happen just because he used to swear a lot when drunk. A net positive? Ridiculous. Fut.Perf. ☼ 06:51, 7 March 2022 (UTC)
- Accept per WP:ROPE, and four years being a long time in Wikipedia. It's certainly long enough for people, and their circumstances, to change. If FP@S's venom is at all justified, then we'll all be back here soon enough. Most importantly of all, DS must know that too: if he has another chance, it'll only be the one. SN54129 08:02, 7 March 2022 (UTC)
- Oh, the old "give them a last chance, re-blocks are cheap" mantra. No, re-blocks are never cheap, especially not with entrenched, experienced disruptors with wikifriends protecting them. This person has had dozens of second chances and last chances. He somehow managed to talk himself out of a block 12 times in 9 years. And every time he had to be re-blocked afterwards, it was a long-drawn-out, energy-draining procedure, devastating to all envolved. BTW, he now even denies [5] he was ever topic-banned from Eastern Europe. Yes, he was, under his "User:The Last Angry Man" sock account, in October 2011 (shortly after having talked himself out of the initial sock block for that one.) Fut.Perf. ☼ 08:31, 7 March 2022 (UTC)
Template:Od(General reply to all) It wasn't much of a denial when in the same sentence they admitted to being t-banned from two other topic areas. I think we can allow a gill of good faith for a memory lapse over something that occurred a decade ago for three months. What I'm looking for is the possibility that someone can change in the amount of time that has passed (I doubt anyone would argue that, except the most incorrigible), and signs of recent disruption (socking). CU gives that a (tentative) all-clear, and I suppose NOTPUNITIVE means something. Admittedly I have the advantage of looking at this as something of a historical episode, not being personally invested, but I assure anyone who wants to know that, should DS go back to their old ways—or discover new ways!—of disruption, then I will be the first back here calling for reinstallation of the site ban. And one where their feet won't touch the ground. SN54129 10:30, 7 March 2022 (UTC)
- Oppose. I'd like to see evidence of meaningful, constructive editing elsewhere (not necessarily a wikimedia project) before voting to support an unban. This user has been blocked before and convinced us they'd changed, only to demonstrate no significant improvement. Maybe this time, they really have, but there's nothing here that demonstrates that to me. --Yamla (talk) 10:40, 7 March 2022 (UTC)
- Support unblock per WP:STANDARDOFFER. — BillHPike (talk, contribs) 11:36, 7 March 2022 (UTC)
- Support unblock, four years of patience and still willing to volunteer? Open the door wide for those who wait. Randy Kryn (talk) 11:48, 7 March 2022 (UTC)
- Conditional support only under a formally logged restriction that, for at least one year, the indefinite siteban will be immediately reinstated if they are blocked for any reason whatsoever. This user has been blocked, conditionally unblocked, and then re-blocked twelve times; the average time to the recidivism block is 44.08 days thanks to an outlier at nearly 6 months; in all but three of these cases they were re-blocked less than a month later, the shortest time being less than two days. This doesn't count numerous blocks that expired with no action, nor the block logs of the ten confirmed socks in their SPI. This is a user who has shown, repeatedly and consistently through time, that they know how to talk themselves out of consequences, that blocks don't teach them anything, and that they either fully intend to reoffend or they can't help themselves. I'm all for second chances (although we're well into double-digit numbers of chances here already) but let's not waste our time if they show, again, that they still can't follow the rules. Ivanvector (Talk/Edits) 14:46, 7 March 2022 (UTC)
- {{safesubst:#invoke:Reply to|replyto||max=50}}, I'm honestly struggling to understand how this restriction is supposed to be effective. The threat of, and actual implementation of, indefinite blocks/bans has previously proven to have little deterrent value in this editor's case. Are we really giving that much benefit of the doubt that this time it will work? Eggishorn (talk) (contrib) 01:31, 8 March 2022 (UTC)
- Actually, I am concerned that such a "one strike and you're out again" rule would actually have the opposite effect, of effectively raising the bar for any sanction to be imposed. Given the long history of administrators bending over backwards to accommodate this person and of wikifriends protecting him, administrators might be even more reluctant to impose even just a short-term block if they knew that it would automatically trigger a permanent ban again. Fut.Perf. ☼ 08:31, 8 March 2022 (UTC)
- Template:Yo well, the fact that previous sanctions have done little to deter this editor is the point of the restriction. They have a long record of not learning from restrictions and we don't have any way to be sure that this time in the penalty box will be any different from the other dozens of times. The restriction is just a relief valve: if we unblock them and they just get in trouble again, we don't need to have another lengthy discussion about what to do about it this time, we just reinstate the ban. Ivanvector (Talk/Edits) 15:57, 8 March 2022 (UTC)
- Actually, I am concerned that such a "one strike and you're out again" rule would actually have the opposite effect, of effectively raising the bar for any sanction to be imposed. Given the long history of administrators bending over backwards to accommodate this person and of wikifriends protecting him, administrators might be even more reluctant to impose even just a short-term block if they knew that it would automatically trigger a permanent ban again. Fut.Perf. ☼ 08:31, 8 March 2022 (UTC)
- {{safesubst:#invoke:Reply to|replyto||max=50}}, I'm honestly struggling to understand how this restriction is supposed to be effective. The threat of, and actual implementation of, indefinite blocks/bans has previously proven to have little deterrent value in this editor's case. Are we really giving that much benefit of the doubt that this time it will work? Eggishorn (talk) (contrib) 01:31, 8 March 2022 (UTC)
- Conditional support, per IV. I remember DS well, he was among the first prolific editors I encountered in my own time on Wikipedia. He was impatient, sometimes careless, profane, and bloody rude. Also, to anyone who knew him well, it was obvious that he believed deeply in Wikipedia's mission, and he drew his motivation from writing content. He stepped over the line often enough that I don't see this being a "last chance": but I think four years off the site is long-enough, given his particular offences, that we can seriously consider an appeal that identifies and promises to correct behavioral problems. He's going to be on a very tight leash as is: I believe he's still under an ARBIPA TBAN (right?) and I would additionally suggest, per IV, that any further issues with copyvios or sockpuppetry should lead to a reinstatement of the ban. Vanamonde (Talk) 15:49, 7 March 2022 (UTC)
- Conditional support also per IvanVector and Vanamonde93. It's possible that he has overcome the issues that led to his siteban, but I'm afraid I don't trust him enough to support him coming back without strict restrictions. I note that he doesn't discuss all of the issues that led to the siteban. Doug Weller talk 17:16, 7 March 2022 (UTC)
- Conditional support under the terms outlined by Ivanvector. He has now stayed away from the project for almost half as long as he was ever active, and I don't think his failure to spell out why he kept being blocked is a sign of incorrigibility so much as the fact that he has already admitted to being an ass and not much else really needs to be said. I never have never encountered this editor or his contributions, so I cannot comment on the above question as to whether there was a fundamental content problem as well as a behavioral one; if there was, I hope that not being drunk will help with the quality of his edits as much as he claims it will help his behavior. Darkness Shines should understand, however, that if he is blocked again at any point in the nearish future, that block will be essentially permanent. —Compassionate727 (T·C) 17:54, 7 March 2022 (UTC)
- Oppose per Future Perfect at Sunrise. LEPRICAVARK (talk) 01:13, 8 March 2022 (UTC)
Strong oppose Per FutPerf.TrangaBellam (talk) 16:23, 8 March 2022 (UTC)- Oppose per FutPerf. I hate to say it, but the time for "one last chance" was past when the ban was implemented. RickinBaltimore (talk) 16:36, 8 March 2022 (UTC)
- Oppose The WP:STANDARDOFFER was expended long ago, they have had enough WP:ROPE to moor a battleship, and their content creation cannot offset a fundamental inability to cooperate. While I appreciate the intention behind Template:U's proposed restriction, I cannot support it. After looking through the history of blocks, bans, ANI threads, etc., I think that there will be lengthy discussions the next time that DS blows their top. There is copious evidence that such another incident is inevitable. I would like to believe their claims of growth but there is a years-long record of previous such claims not being borne out. If DS is able to show productive, civil editing for an extended period (six months or more) on a similar project, I would reconsider. Eggishorn (talk) (contrib) 17:23, 8 March 2022 (UTC)
- Oppose. There was probably a time where I would have been swayed by the appeals to personal growth, time served, right to an nth chance, etc. But that time is past, because I've seen over and over again how this community bends over backwards to rehabilitate endlessly problematic editors while denying even a scrap of empathy to the people whom they've harmed. We pat ourselves on the back for our graciousness, quote the-quality-of-mercy-is-not-strained and WP:ROPE, condemn as "venomous" anyone who objects to lifting sanctions... and then when these editors backslide, no one who's commenting here in favor of an nth chance will lift a finger. I'm no longer willing to participate in what increasingly strikes me as a cynical dynamic. MastCell Talk 18:11, 8 March 2022 (UTC)
- Oppose - I note that I was the original proposer at WP:ANI in February 2018 of the current site ban. I was about to propose that Darkness Shines be asked to identify a niche area in which they would be allowed to edit to demonstrate that they had, in four years, learned how to edit collaboratively, or at least to avoid the worst. Then I reviewed their history again. I see not only the longest block log I have ever seen, which is mostly in 2011 to 2014, but also repeated episodes of sockpuppetry. As a result, I don't trust Darkness Shines, and I don't think that I will trust Darkness Shines in 2026. They may and do mean to contribute positively to the encyclopedia, but they have demonstrated not only a lack of civility and a lack of discipline, but a lack of respect for the rules. As I said four years ago, Yuck. Ugh. I don't trust Darkness Shines. Robert McClenon (talk) 18:43, 8 March 2022 (UTC)
- Oppose per MastCell and FutPerf. This pattern stretches over years and does not inspire confidence. GABgab 00:49, 9 March 2022 (UTC)
- Accept appeal and unblock. Four years is a long time, and Darkness Shines has given a plausible explanation of why we can expect they will contribute more productively now than they did before. I know it's not guaranteed, and we've been burned before, but if we're not willing to accept their explanation then we might as well give up on the theory that indefinite does not mean infinite. -- RoySmith (talk) 15:30, 10 March 2022 (UTC)
- Oppose. Anyone who is thinking of supporting needs to first review Darkness Shines' block log, which contains three indefinite blocks (that is to say, Darkness Shines has successfully appealed an indefinite block in the past saying they've changed, exactly like this, and then gotten themselves blocked again, twice), as well as the discussion that led to the most recent block, their appeal to their previous block (which had an "it's been a long time, I have changed" tone similar to this one); the full text of the other time they successfully appealed an indefinite block is unavailable because it was via email, but the message here makes it clear they promised they had turned a new leaf and could be civil back then, too. The only rationale given here is "they may have changed", but note that in Darkness Shines' explanation for how they changed, they say almost nothing - they were not simply banned for being Template:Tq They were banned for continuous edit-warring and a sustained pattern of gross, repeated incivility across entire topic areas - something that goes way beyond the occasional loss of temper. --Aquillion (talk) 09:41, 11 March 2022 (UTC)
- Support, perhaps with the conditions mentioned above by Ivanvector. I'm certainly not saying that DS was ever a model editor (and nor is he, to be fair) but some of the attacks on DS above are slightly overblown, and at least one is exaggerated to the point of being economical with the truth. I don't see the downside of a WP:ROPE trial. Black Kite (talk) 10:01, 11 March 2022 (UTC)
- I'm not thrilled with the idea of Darkness Shines' return. He's expensive in volunteer time.—S Marshall T/C 14:30, 11 March 2022 (UTC)
- Support. I recall interacting once with Darkness Shines, whose action was (in my opinion) helpful for Wikipedia. I'd support a filter for foul language, but it should apply for everyone. Peter Gulutzan (talk) 14:46, 11 March 2022 (UTC)
- Oppose Looking through their edit history I have a hard time believing they would be a net positive should they return, and I place more importance on that than the length of time they've been blocked for.-- Pawnkingthree (talk) 15:04, 11 March 2022 (UTC)
- Oppose I'm all for extending some latitude for time served, but this was a community ban after 3 previous indefs, I don't think any more chances are going to change anything for the better. How many more hours are people supposed to waste on one editor when they have shown no interest in moderating their tone or editing behavours? Valeince (talk) 15:02, 14 March 2022 (UTC)
UCoC enforcement guidelines voting has begun
This is your unofficial reminder to vote in the UCoC enforcement guidelines ratification. Please, consider doing so if you haven't already!! Template:(: –MJL ‐Talk‐☖ 05:18, 7 March 2022 (UTC)
- Ah, the impenetrable Meta Strikes Back. Well, at least as a venue, it isn't a ghost town like Fakebook's Meta (Truth Sokial?). BTW, the Glossary cracked me up. Q: what is X? A: See X on Meta. What, we are on Meta? Well, we're still not gonna link it for ya, peasants! And... scene. El_C 08:53, 7 March 2022 (UTC)
- I linked the most obvious ones. --Floquenbeam (talk) 15:53, 7 March 2022 (UTC)
- Oh, Affcom is the Affiliations Committee and not the Affections Committee? Now I'm extra-sad. El_C 15:59, 7 March 2022 (UTC)
- I linked the most obvious ones. --Floquenbeam (talk) 15:53, 7 March 2022 (UTC)
- I'm not quite sure if there is a logical discussion venue - no doubt there should be one, not sure if it should be here, somewhere else local, or there Template:Ping - thoughts? Nosebagbear (talk) 10:38, 7 March 2022 (UTC)
- @Nosebagbear: I'm cool with whatever, but I'd check with Template:U since he's the one that gets paid for this. –MJL ‐Talk‐☖ 16:29, 7 March 2022 (UTC)
- Yes, that's pretty pathetic. Doesn't anyone there know how to link? Doug Weller talk 12:26, 7 March 2022 (UTC)
- This was a reply to El C, but reply didn't put it in the right place. Known problem? Doug Weller talk 12:28, 7 March 2022 (UTC)
- Template:Ping Your reply was (and still is) correctly positioned as a reply to El C. See WP:INDENT for the basic rules of threaded discussion: Template:Tq Floquenbeam's reply above (not made with the reply tool) is an example of one that is not correctly positioned. Modulus12 (talk) 01:32, 9 March 2022 (UTC)
- You're right of course. It's a problem with WP:INDENT, not the reply tool IMHO, in that it's not obvious unless you carefully look and line up the replied. Like it or not, User:Floquenbeam's post is an obvious reply to El C, mine is not. Doug Weller talk 09:05, 9 March 2022 (UTC)
- Template:Re Didn't read all of your post. So you are saying that the reply tool isn't doing what I expect/want it to? I did notice once that using it and saving after someone else posted didn't cause an edit conflict but put it after the other person posted, so I went in and moved mine. Doug Weller talk 09:08, 9 March 2022 (UTC)
- You're right of course. It's a problem with WP:INDENT, not the reply tool IMHO, in that it's not obvious unless you carefully look and line up the replied. Like it or not, User:Floquenbeam's post is an obvious reply to El C, mine is not. Doug Weller talk 09:05, 9 March 2022 (UTC)
- Template:Ping Your reply was (and still is) correctly positioned as a reply to El C. See WP:INDENT for the basic rules of threaded discussion: Template:Tq Floquenbeam's reply above (not made with the reply tool) is an example of one that is not correctly positioned. Modulus12 (talk) 01:32, 9 March 2022 (UTC)
- This was a reply to El C, but reply didn't put it in the right place. Known problem? Doug Weller talk 12:28, 7 March 2022 (UTC)
- Question, asking for a friend. Do administrators have to sign their names in blood when forced to agree to this or will a regular pen or pencil do? Randy Kryn (talk) 10:40, 7 March 2022 (UTC)
- Are You Now or Have You Ever Been A Metamate? El_C 10:53, 7 March 2022 (UTC)
- @Randy Kryn: Assuming your friend isn't an admin yet (because existing admins don't have to sign anything), I'm pretty sure it'll be a digital signature Template:Emoji –MJL ‐Talk‐☖ 16:34, 7 March 2022 (UTC)
- My friend is rejoicing as we speak, because apparently "All advanced rights holders" doesn't apply to admins, as in "The following individuals should be required to affirm (through signed declaration or other format to be decided) they will acknowledge and adhere to the Universal Code of Conduct: All Wikimedia Foundation staff, Board members, Wikimedia affiliate board members, staff and contractors; All advanced rights holders;". Randy Kryn (talk) 17:03, 7 March 2022 (UTC)
- Vote early, vote often, vote no. Dennis Brown - 2¢ 12:29, 7 March 2022 (UTC)
- Can someone please answer a procedural question (I don't want to e-mail the meta address to ask)? If I vote no, there is apparently a box to comment on why I'm voting no. Do I have to comment? If I don't, is there some kind of, uh, follow-up? I find the instructions confusing. Thanks.--Bbb23 (talk) 14:37, 7 March 2022 (UTC)
- Having just voted, you do not need to fill out the comment. There was no follow-up after submitting my vote, beyond receiving a PGP hash receipt of it for my own records. Sideswipe9th (talk) 14:49, 7 March 2022 (UTC)
- I think there actually is a box even if you vote yes, though I've not tested Nosebagbear (talk) 14:59, 7 March 2022 (UTC)
- The comments box is available regardless of the answer to question 1 (Options: No, -, Yes); it is for overall comments, not necessarily a justification for your vote. — xaosflux Talk 15:05, 7 March 2022 (UTC)
- For the record, upon voting No (a few min prior to commenting here, at AN), my vote box comment read (in full): Template:Tq I'm helping! El_C 15:22, 7 March 2022 (UTC)
- "Learn to condense"? That's rude! BeenAroundAWhile (talk) 15:34, 7 March 2022 (UTC)
- It's probably a violation of the UCoC. ScottishFinnishRadish (talk) 15:36, 7 March 2022 (UTC)
- To quote James Randal: I got scared. Template:)': El_C 15:39, 7 March 2022 (UTC)
- It's probably a violation of the UCoC. ScottishFinnishRadish (talk) 15:36, 7 March 2022 (UTC)
- "Learn to condense"? That's rude! BeenAroundAWhile (talk) 15:34, 7 March 2022 (UTC)
- For the record, upon voting No (a few min prior to commenting here, at AN), my vote box comment read (in full): Template:Tq I'm helping! El_C 15:22, 7 March 2022 (UTC)
- The comments box is available regardless of the answer to question 1 (Options: No, -, Yes); it is for overall comments, not necessarily a justification for your vote. — xaosflux Talk 15:05, 7 March 2022 (UTC)
- I highly recommend you include the reason why you voted no if you voted no. If ratification was to fail at this stage, then the revision committee that gets formed is going to use what people wrote as the basis for deciding what changes should get made. –MJL ‐Talk‐☖ 16:27, 7 March 2022 (UTC)
- Leaving comments no matter how you vote is helpful. Either it will pass and there will be an amendment process in a year (at which time it would still be good to know what people liked/disliked at ratification) and a U4C building committee (who might be able to address some issues that were disliked) or it won't pass and revisions will get made in which case again it's helpful to know what people liked and disliked so the right things are changed. If you already voted and didn't leave a comment you can go back and vote - only your most recent vote/comments are kept. Best, Barkeep49 (talk) 17:15, 7 March 2022 (UTC)
- In other words, we're going to keep having the vote with minor tweaks until we say "Yes". Black Kite (talk) 18:23, 7 March 2022 (UTC)
- They don't. But this is the WMF we're talking about here, I can't see them majorly revising this very important thing. Black Kite (talk) 18:28, 7 March 2022 (UTC)
- This may be a gross misreading on my part, but does the section on harassment, as currently written, prevent us from sending non-public off-wiki information about other editors to ARBCOM? If so, that's immediate grounds for opposition; we cannot hope to deal with off-wiki harassment and coordination without the ability to handle such information. Vanamonde (Talk) 20:34, 7 March 2022 (UTC)
- While I'm very confident that it's not intended as such, you're right that the base UCOC text doesn't include write-outs for it. It has a general category, that UPE (etc) combatting wouldn't fall into, and then names certain "included but not limited to" names buckets. Nosebagbear (talk) 11:30, 8 March 2022 (UTC)
- Thanks for this, Nosebagbear: do you know if ARBCOM members have commented on this before? I'm minded to ping some of them here, but I don't want to make a scene if it's been resolved elsewhere. I find this very concerning. ARBCOM has frequently banned users here because of their off-wiki activity; how is this to be brought to their attention going forward? Is the board aware that they are essentially preventing us from discussing off-wiki harassment anymore? Vanamonde (Talk) 15:29, 8 March 2022 (UTC)
- I hate to yell for attention, but given the off-wiki harassment I've seen, I think it's justified; Template:Ping I'd be interested in hear whether y'all think the the doxing section of the UCoC prevents editors from bringing off-wiki information to ARBCOM when it relates to things besides paid editing. Vanamonde (Talk) 19:54, 8 March 2022 (UTC)
- Speaking only for myself, I don't get that reading, but if you are not confident that the policy is clear enough, then that is a good reason to oppose. Section 3.1 of the UCoC, Harassment, includes a definition at the start Template:Tq Sharing non-public personal information with the arbitration committee in private for the purposes of administering the project does not seem to fall under that definition. My understanding of the doxing example in the text is that it is limited by that main definition, and covers the public sharing of non-public personal information as the main outcome of that action would be intimidation, outrage, or upset, but private reports have the main outcome of effective project administration. — Wug·a·po·des 20:07, 8 March 2022 (UTC)
- Thanks. I can see how it may be read that way; and if it's always read that way, it would address my concern. I'm not (yet) confident it will always be read that way, however. Vanamonde (Talk) 20:10, 8 March 2022 (UTC)
- Just noting that I am not speaking publicly about the UCoC Enforcment draft, other than to encourage people to vote and leave comments regardless of which way they're voting. Courtesy ping to Template:U who has been speaking about their interpretation of things. Best, Barkeep49 (talk) 20:16, 8 March 2022 (UTC)
- Thanks. I can see how it may be read that way; and if it's always read that way, it would address my concern. I'm not (yet) confident it will always be read that way, however. Vanamonde (Talk) 20:10, 8 March 2022 (UTC)
- Speaking only for myself, I don't get that reading, but if you are not confident that the policy is clear enough, then that is a good reason to oppose. Section 3.1 of the UCoC, Harassment, includes a definition at the start Template:Tq Sharing non-public personal information with the arbitration committee in private for the purposes of administering the project does not seem to fall under that definition. My understanding of the doxing example in the text is that it is limited by that main definition, and covers the public sharing of non-public personal information as the main outcome of that action would be intimidation, outrage, or upset, but private reports have the main outcome of effective project administration. — Wug·a·po·des 20:07, 8 March 2022 (UTC)
- I hate to yell for attention, but given the off-wiki harassment I've seen, I think it's justified; Template:Ping I'd be interested in hear whether y'all think the the doxing section of the UCoC prevents editors from bringing off-wiki information to ARBCOM when it relates to things besides paid editing. Vanamonde (Talk) 19:54, 8 March 2022 (UTC)
- Thanks for this, Nosebagbear: do you know if ARBCOM members have commented on this before? I'm minded to ping some of them here, but I don't want to make a scene if it's been resolved elsewhere. I find this very concerning. ARBCOM has frequently banned users here because of their off-wiki activity; how is this to be brought to their attention going forward? Is the board aware that they are essentially preventing us from discussing off-wiki harassment anymore? Vanamonde (Talk) 15:29, 8 March 2022 (UTC)
- While I'm very confident that it's not intended as such, you're right that the base UCOC text doesn't include write-outs for it. It has a general category, that UPE (etc) combatting wouldn't fall into, and then names certain "included but not limited to" names buckets. Nosebagbear (talk) 11:30, 8 March 2022 (UTC)
- Other than the apparently obligatory fear and loathing of anything WMF does, can somebody explain what the problem is with the UCoC? I get the objection made by Template:U about off-wiki evidence, but I assume that's something that can get fixed with a minor working tweak. So, what else about this has people upset? I've read through the whole thing and I really can't find anything it prohibits which I wouldn't want prohibited. I assume nobody's saying that sexual harassment, doxing, threat of violence, etc, are actually things they want to allow. So, what am I missing? -- RoySmith (talk) 15:49, 8 March 2022 (UTC)
- I'm perhaps in the "pass with fixes but not right now" camp. I'm leery about the lack of language describing who gets to decide when there are failures to resolve disputes locally or systemic failures to enforce the UCoC; if this is clearly a decision made by the community at the target project and/or Metawiki, there's no problem IMO, but right now it's vague and could be interpreted as a blank check for office actions. signed, Rosguill talk 15:54, 8 March 2022 (UTC)
- But there already is pretty much a blank check for office actions, and this doesn't change that one way or the other. Is there any fundamental difference between WMF doing something we don't like and justifying it with "Because T&S" vs "Because UCoC"? -- RoySmith (talk) 16:06, 8 March 2022 (UTC)
- I think it's reasonable to worry, even without indulging the "WMF is out to get us" mentality, that the community buy-in afforded by a successful passing of a UCoC would encourage the WMF to use its provisions more fully than the existing T&S. Given the possibility, I'd rather object now and push for language I am fully comfortable with rather than endorse something I don't necessarily agree with. signed, Rosguill talk 20:10, 8 March 2022 (UTC)
- But there already is pretty much a blank check for office actions, and this doesn't change that one way or the other. Is there any fundamental difference between WMF doing something we don't like and justifying it with "Because T&S" vs "Because UCoC"? -- RoySmith (talk) 16:06, 8 March 2022 (UTC)
- Template:Re I'm not convinced about the possibility of a minor working tweak. I'm also not sure how this impacts on fighting paid editing. Without something more official I shall probably vote no. Doug Weller talk 16:49, 8 March 2022 (UTC)
- Principal issues to me, @RoySmith with the enforcement guideliness (phase 2) include:
- i) There are numerous requirements of anonymity capacity, but no countervailing evidentiary safeguards for the accused. It moves the marker a very long way.
- ii) It also, despite it being the single most requested amendment to the 1st iteration of phase 2, has functionally zero right to be heard inclusion. Such a right definitely shouldn't be absolute, but given the community demand, its exclusion (other than one line that may refer to it, but only in specific regard to the U4C) is unacceptable
- iii) It is unclear - even in English, making the translations likely even harder to be confident on reasoning
- iv) The training is mandatory (the definition that grandfathers admins doesn't apply here), and doesn't give a community veto on its content
- v) We were guaranteed that phase 2 would be iterative, but they decided, right at the endgame, that we would not be permitted any chance to amend significant parts of the policy text prior to the vote. That is, we'd never seen it until December, and despite major discussion, if we don't vote no, we can't fix flaws with it.
- vi) We were not permitted a vote on phase 1, and then T&S policy stated that no-one in the community had requested a ratification vote prior to the ARBCOM open letter, and when I provided a diff demonstrating exactly that, six months earlier, they ceased communicating about it. Until all issues with prior engagement have been resolved, I am nervous about trusting future ones. Nosebagbear (talk) 18:48, 8 March 2022 (UTC)
- I'm perhaps in the "pass with fixes but not right now" camp. I'm leery about the lack of language describing who gets to decide when there are failures to resolve disputes locally or systemic failures to enforce the UCoC; if this is clearly a decision made by the community at the target project and/or Metawiki, there's no problem IMO, but right now it's vague and could be interpreted as a blank check for office actions. signed, Rosguill talk 15:54, 8 March 2022 (UTC)
- I hope any admins supporting this are looking forward to their compulsory UCoC training course. This hasn't been developed yet but the WMF's anti-harassment course lasts 8 weeks and includes coursework. Hut 8.5 18:14, 8 March 2022 (UTC)
- Where does it say there's going to be a compulsory training course? -- RoySmith (talk) 18:41, 8 March 2022 (UTC)
- Template:U "Individuals required to acknowledge and adhere to the Universal Code of Conduct will be required to attend training to ensure a common understanding of implementation". That includes all advanced rights holders. Black Kite (talk) 18:47, 8 March 2022 (UTC)
- Template:EcIndividuals required to acknowledge and adhere to the Universal Code of Conduct will be required to attend training... That includes admins: the "Affirmation of the UCoC among certain groups" section says The following individuals should be required to affirm... they will acknowledge and adhere to the Universal Code of Conduct...All advanced rights holders. The glossary says that "Advanced rights holders" includes admins. Hut 8.5 18:48, 8 March 2022 (UTC)
- Ah, OK. I had to go hunting to find that, but for future reference, it's here. -- RoySmith (talk) 18:56, 8 March 2022 (UTC)
- Template:Xt - Not gonna do that, personally. WP is suppose to be a fun hobby for me, and having to deal with a lengthy "seminar" and likely giving more personal information to the WMF than I would care to in the process of signing up does not sound enjoyable, plus whatever "follow-up" I'm sure they'll deem is necessary in a few months. I will almost certainly be resigning the mop if it comes to that. Hog Farm Talk 20:02, 8 March 2022 (UTC)
- I don’t think that’s going to happen. They must know that’s too much. Do we have any information about what they actually plan? Doug Weller talk 20:05, 8 March 2022 (UTC)
- Call me cynical, but I'm not sure the WMF wants us to know exactly what they plan, or they'd be making it more clear. Either that, or Hanlon's razor is at play here. Hog Farm Talk 20:08, 8 March 2022 (UTC)
- Template:Re As far as I am *personally* aware, no course has actually been made yet. –MJL ‐Talk‐☖ 23:57, 8 March 2022 (UTC)
- Which makes it difficult to support. A bit of a pig in a poke. Doug Weller talk 13:31, 9 March 2022 (UTC)
- ¯\_(ツ)_/¯
- Which makes it difficult to support. A bit of a pig in a poke. Doug Weller talk 13:31, 9 March 2022 (UTC)
- I don’t think that’s going to happen. They must know that’s too much. Do we have any information about what they actually plan? Doug Weller talk 20:05, 8 March 2022 (UTC)
- Template:Xt - Not gonna do that, personally. WP is suppose to be a fun hobby for me, and having to deal with a lengthy "seminar" and likely giving more personal information to the WMF than I would care to in the process of signing up does not sound enjoyable, plus whatever "follow-up" I'm sure they'll deem is necessary in a few months. I will almost certainly be resigning the mop if it comes to that. Hog Farm Talk 20:02, 8 March 2022 (UTC)
- Ah, OK. I had to go hunting to find that, but for future reference, it's here. -- RoySmith (talk) 18:56, 8 March 2022 (UTC)
- Where does it say there's going to be a compulsory training course? -- RoySmith (talk) 18:41, 8 March 2022 (UTC)
I'm just trying to share what I know. How the vote goes is beyond my control, but I'm glad the WMF is having a ratification process here. –MJL ‐Talk‐☖ 00:40, 11 March 2022 (UTC)
- Roy, with insufficient clarity about local control vs WMF control of enforcement, I worry that without further clarification in advance, this process as written will make it much easier to weaponize the UCOC, even easier than it is to weaponize our local policies. Some may recall we had a little dust up about that a few years ago, involving Fram? Voting yes on this, as written, seems to me to be giving up all the local control we painfully clawed back from WMF that time. Once approved, WMF will have zero incentive to modify things they like that we don't. Of course we all don't support harassment, but there is a thread on ANI right now where an editor is threatening to report another editor they're in a content dispute with to T&S for "bullying". I do not trust T&S to evaluate such a claim fairly. I think it will be easier to pull the wool over the eyes of T&S than even editors at ANI, or our local ArbCom. One thing I'm curious about; if editors of other language wikis - where there may be no functioning ArbCom, and where something like this might make sense as "better than nothing" - vote for this, and English WP editors vote against, I'm guessing WMF is going to interpret that as an approval to go ahead and apply it to us too? --Floquenbeam (talk) 20:21, 8 March 2022 (UTC)
- If 50.1% of voters support the enforcement guidelines, they will be applied to all editors. The UCoC was implemented by a Board resolution making it binding policy under section 11 of the Terms of Use, but also means it can only be modified with the consent of the Board. I expect the enforcement guidelines to be resolution'd into force the same way. Neither document allows the community to make amendments to the UCoC itself or the enforcement guidelines, the only indication such a thing might be possible is an announcement that is not binding on anyone and was signed only by the current Vice Chair of the Board. The latest I've heard from the WMF is that if the guidelines pass even with widespread opposition, there will be no amendments for at least a year. Of course, the Board can modify either document by resolution whenever they want. Template:PbPutting on my pile of non-enwiki hats, I think the UCoC will be a good thing for many wikis. But the enforcement guidelines are just not ready yet, and ideally the UCoC itself should have had another pass too. It is not possible to simply legislate social change into existence with a few Board resolutions, it is necessary to actively work Template:Em to fix problems and to find a mutually-acceptable solution. However, the WMF has decided to ignore this successful consensus-based model, and I think both documents are worse off because of it. AntiCompositeNumber (talk) 05:17, 12 March 2022 (UTC)
- Roy, with insufficient clarity about local control vs WMF control of enforcement, I worry that without further clarification in advance, this process as written will make it much easier to weaponize the UCOC, even easier than it is to weaponize our local policies. Some may recall we had a little dust up about that a few years ago, involving Fram? Voting yes on this, as written, seems to me to be giving up all the local control we painfully clawed back from WMF that time. Once approved, WMF will have zero incentive to modify things they like that we don't. Of course we all don't support harassment, but there is a thread on ANI right now where an editor is threatening to report another editor they're in a content dispute with to T&S for "bullying". I do not trust T&S to evaluate such a claim fairly. I think it will be easier to pull the wool over the eyes of T&S than even editors at ANI, or our local ArbCom. One thing I'm curious about; if editors of other language wikis - where there may be no functioning ArbCom, and where something like this might make sense as "better than nothing" - vote for this, and English WP editors vote against, I'm guessing WMF is going to interpret that as an approval to go ahead and apply it to us too? --Floquenbeam (talk) 20:21, 8 March 2022 (UTC)
- WP:Fram, if anyone has forgotten. Please everyone: vote! I might disagree with "the powers that be" here on en.wp from time to time, but I have a heck of a lot more trust in en.wp that I have in WMF. Huldra (talk) 20:41, 8 March 2022 (UTC)
- No, it takes place here. The explanation page on how to vote is on Meta, however. Jo-Jo Eumerus (talk) 09:58, 12 March 2022 (UTC)
- Not signing in at that other place, to vote. GoodDay (talk) 23:38, 12 March 2022 (UTC)
- Template:Re You don't have to (and in fact can't) sign in at vote.wikimedia.org. Just click the "Go to the voting server" button at this meta page and you'll be taken to the voting page. Suffusion of Yellow (talk) 00:01, 13 March 2022 (UTC)
- I believe I'll pass. GoodDay (talk) 00:03, 13 March 2022 (UTC)
- Template:Re Special:SecurePoll/vote/802 would be a non-meta way to the voting server. Habitator terrae (talk) 06:40, 13 March 2022 (UTC)
- I'll pass. GoodDay (talk) 06:45, 13 March 2022 (UTC)
- I've always held the opinion that those who don't vote also don't get to complain about the result — I'm sure you feel the exact same way. -- TNT (talk • she/her) 06:53, 13 March 2022 (UTC)
- The opposite, actually. George Carlin's observation on the vote/don't vote topic, is one that I tend to agree with. GoodDay (talk) 07:02, 13 March 2022 (UTC)
- So that logic actually suggests you should vote in referendums. You're not voting for a person here. No gargabe in, no garbage out. Unlike with a person by voting you are making an actual decision here. Best, Barkeep49 (talk) 10:24, 13 March 2022 (UTC)
- Template:Replyto sorry to add to a close discussion, but while it's your choice if you want to vote because of the above discussion I just want to ensure that you understand SecurePoll is the exact same way we've been voting in arbcom elections (and some others) since 2009. And the only difference I can think of between this vote and such votes other than the obvious i.e. what you're voting for (possibly including the area of effect) and timeframe, is the scrutineer selection process (although scrutineers for arbcom elections come from outside en.wikipedia) and instructions, and voter eligibility. The software you're voting on, connection of the software to en.wikipedia and the community etc is the same. Nil Einne (talk) 02:20, 15 March 2022 (UTC)
- So that logic actually suggests you should vote in referendums. You're not voting for a person here. No gargabe in, no garbage out. Unlike with a person by voting you are making an actual decision here. Best, Barkeep49 (talk) 10:24, 13 March 2022 (UTC)
- The opposite, actually. George Carlin's observation on the vote/don't vote topic, is one that I tend to agree with. GoodDay (talk) 07:02, 13 March 2022 (UTC)
- I've always held the opinion that those who don't vote also don't get to complain about the result — I'm sure you feel the exact same way. -- TNT (talk • she/her) 06:53, 13 March 2022 (UTC)
- I'll pass. GoodDay (talk) 06:45, 13 March 2022 (UTC)
- Template:Re Special:SecurePoll/vote/802 would be a non-meta way to the voting server. Habitator terrae (talk) 06:40, 13 March 2022 (UTC)
- I believe I'll pass. GoodDay (talk) 00:03, 13 March 2022 (UTC)
- Template:Re You don't have to (and in fact can't) sign in at vote.wikimedia.org. Just click the "Go to the voting server" button at this meta page and you'll be taken to the voting page. Suffusion of Yellow (talk) 00:01, 13 March 2022 (UTC)
- Not signing in at that other place, to vote. GoodDay (talk) 23:38, 12 March 2022 (UTC)
- No, it takes place here. The explanation page on how to vote is on Meta, however. Jo-Jo Eumerus (talk) 09:58, 12 March 2022 (UTC)