Wikipedia:Administrators' noticeboard: Difference between revisions
Smallbones (talk | contribs) |
→SashiRolls ban review: Replying to Eggishorn (using reply-link) |
||
Line 578: | Line 578: | ||
:::::::That.....makes no sense. Your objection is: "The vote count was wrong so we need to count the votes right even though we don't count votes in determining consensus." There is no reason to call for re-opening a discussion on supposed miscounting. [[WP:NOTDEM:This is no a democracy]], the discussion participants were not a jury, due process isn't a thing, and votes don't count. [[User:Eggishorn|Eggishorn]] [[User talk:Eggishorn|(talk)]] [[Special:Contributions/Eggishorn|(contrib)]] 18:24, 12 July 2020 (UTC) |
:::::::That.....makes no sense. Your objection is: "The vote count was wrong so we need to count the votes right even though we don't count votes in determining consensus." There is no reason to call for re-opening a discussion on supposed miscounting. [[WP:NOTDEM:This is no a democracy]], the discussion participants were not a jury, due process isn't a thing, and votes don't count. [[User:Eggishorn|Eggishorn]] [[User talk:Eggishorn|(talk)]] [[Special:Contributions/Eggishorn|(contrib)]] 18:24, 12 July 2020 (UTC) |
||
*'''Oppose''' 69 users commented in the main banning discussion and SashiRolls made 9 posts. Any light that could have been shed on the topic was. The close was not an abuse of discretion or process and any claims that this should be reopened are just re-litigating the original discussion. [[User:Eggishorn|Eggishorn]] [[User talk:Eggishorn|(talk)]] [[Special:Contributions/Eggishorn|(contrib)]] 19:05, 11 July 2020 (UTC) |
*'''Oppose''' 69 users commented in the main banning discussion and SashiRolls made 9 posts. Any light that could have been shed on the topic was. The close was not an abuse of discretion or process and any claims that this should be reopened are just re-litigating the original discussion. [[User:Eggishorn|Eggishorn]] [[User talk:Eggishorn|(talk)]] [[Special:Contributions/Eggishorn|(contrib)]] 19:05, 11 July 2020 (UTC) |
||
::::::::No, that's not my objection. My objection is that the close said {{tqq|At a rough count, there were approximately 40 editors supporting a ban and ~18-20 opposed.}} and that was incorrect. The close also said {{tqq|While there is no numerical threshold for consensus, it would be inappropriate to close a discussion like this—with >2/3 of commenters supporting action—as "no consensus".}} That sentence means that this discussion can ''only'' be closed as consensus for a ban, because a close of "no consensus" would be {{tq|inappropriate}}, because {{tq|>2/3 of commenters supporting action}}. Except, that's incorrect. It's not >2/3. Therefore, it's not inappropriate to close this some other way, such as "no consensus", under the closer's own logic. It's not me who's doing the counting, it's the closer. These are the ''only specific grounds'' given for the close. He makes no reference to any specific argument made by anyone, or to any specific incident, or to any specific diff, or to any specific policy. He just talks the numbers, and he gets the numbers wrong. Therefore, the close should be un-closed. That's reason #1. |
|||
:::::::: |
|||
::::::::Reason #2 is that 22 comments in the 17 hours prior to the close means it was closed too soon, especially with a swing towards oppose. That's a separate reason from the closing statement to re-open the discussion. <span style="white-space:nowrap;">[[User:Levivich|Levivich]] <sup>[''[[Special:Contributions/Levivich|dubious]] – [[User talk:Levivich|discuss]]'']</sup></span> 18:53, 12 July 2020 (UTC) |
|||
*'''Support''' - I did not participate in the original discussion but think it should be re-opened. Given the flawed analysis and how it was changing just before the close, with El_C's statement, I do not see why it could not of been left open until the weekend. Little copy edits and changes are not the same as having time to go through the evidence and properly respond to it. [[User:PackMecEng|PackMecEng]] ([[User talk:PackMecEng|talk]]) 04:02, 12 July 2020 (UTC) |
*'''Support''' - I did not participate in the original discussion but think it should be re-opened. Given the flawed analysis and how it was changing just before the close, with El_C's statement, I do not see why it could not of been left open until the weekend. Little copy edits and changes are not the same as having time to go through the evidence and properly respond to it. [[User:PackMecEng|PackMecEng]] ([[User talk:PackMecEng|talk]]) 04:02, 12 July 2020 (UTC) |
||
*'''Support''' reopening the discussion. Per SilkTork, the votes were closer to 60% in favor of a site ban, but the thread was new and lively, with the more recent !votes weighing in ''against'' a ban. I'd also suggest a multiple-admin close. And in my opinion, the door should not be open to editors who are using WP and !votes only to continue past grievances, but who are essentially retired from building the encyclopedia. <b style="text-shadow:7px 7px 8px #B8B8B8">[[User:Petrarchan47|<span style="color:#A0A0A0">petrarchan47</span>]][[User talk:Petrarchan47|<span style="color:deeppink">คุ</span>]][[Special:Contribs/Petrarchan47|<span style="color:orangered">ก</span>]]</b> 04:28, 12 July 2020 (UTC) |
*'''Support''' reopening the discussion. Per SilkTork, the votes were closer to 60% in favor of a site ban, but the thread was new and lively, with the more recent !votes weighing in ''against'' a ban. I'd also suggest a multiple-admin close. And in my opinion, the door should not be open to editors who are using WP and !votes only to continue past grievances, but who are essentially retired from building the encyclopedia. <b style="text-shadow:7px 7px 8px #B8B8B8">[[User:Petrarchan47|<span style="color:#A0A0A0">petrarchan47</span>]][[User talk:Petrarchan47|<span style="color:deeppink">คุ</span>]][[Special:Contribs/Petrarchan47|<span style="color:orangered">ก</span>]]</b> 04:28, 12 July 2020 (UTC) |
Revision as of 18:53, 12 July 2020
Welcome — post issues of interest to administrators. |
---|
When you start a discussion about an editor, you must leave a notice on their talk page. Pinging is not enough. Sections inactive for over seven days are archived by Lowercase sigmabot III.(archives, search) |
Open tasks
V | Jun | Jul | Aug | Sep | Total |
---|---|---|---|---|---|
CfD | 0 | 0 | 10 | 0 | 10 |
TfD | 0 | 1 | 12 | 0 | 13 |
MfD | 0 | 0 | 4 | 0 | 4 |
FfD | 0 | 0 | 3 | 0 | 3 |
RfD | 0 | 0 | 67 | 0 | 67 |
AfD | 0 | 0 | 0 | 0 | 0 |
- 6 bot-reported usernames for administrator attention
- 4 user-reported usernames for administrator attention
- 5 bot-generated requests for intervention against vandalism
- 2 user-generated requests for intervention against vandalism
- 127 sockpuppet investigations
- 10 Candidates for speedy deletion
- 11 Fully protected edit requests
- 12 Candidates for history merging
- 7 requests for RD1 redaction
- 32 elapsed requested moves
- 3 Pages at move review
- 44 requested closures
- 125 requests for unblock
- 1 Wikipedians looking for help from administrators
- 16 Copyright problems
Pages recently put under extended-confirmed protection
Report
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Template editor
I propose that The Rambling Man (TRM) be granted the template editor user right. His raising of many issues at WP:MPE shows that he has a need for the right. TRM is a former admin, who lost his admin privileges about 4 years ago due to an ARBCOM case. It is for this reason that I feel that any granting of advanced permissions needs to be done with the consensus of the community at large. I believe that granting the user right to TRM will result in a reduction of workload at MPE and ITNC, as TRM will be able to make productive edits in those areas which he currently cannot do. I believe that he will not abuse the user right if granted it. Mjroots (talk) 08:21, 1 July 2020 (UTC)
- Cheers. And if any admin is available now, there are a few issues I noted two days ago which are currently live on the main page. The Rambling Man (Stay indoors, stay safe!!!!) 08:23, 1 July 2020 (UTC)
- @Mjroots: please, no half measures, restore the administration rights also. ——Serial # 08:34, 1 July 2020 (UTC)
- I have added the flag, since it does not require a vote and is clearly needed.--Ymblanter (talk) 08:35, 1 July 2020 (UTC)
- Actually, as I feared, this doesn't mean I can address the errors on the main page as we speak. Perhaps an admin could help with that please? And Serial Number 54129, thanks!! The Rambling Man (Stay indoors, stay safe!!!!) 08:37, 1 July 2020 (UTC)
- @Mjroots: As much as I appreciate TRM's contributions to MP and otherwise, all main page elements are cascade-protected, so TPE is pointless. (the correct measure is in what SN said) --qedk (t 愛 c) 08:50, 1 July 2020 (UTC)
- Well, I can't do what Serial Number 54129 suggested. So The Rambling Man will just have to run for admin again. Mjroots (talk) 09:02, 1 July 2020 (UTC)
- Not sure how well that would go, but there'd be a support from me - if there's anyone who needs the admin tools for the volunteer work they've chosen to do (and do so thoroughly well), it's TRM. Boing! said Zebedee (talk) 10:18, 1 July 2020 (UTC)
- This is why we needed WP:Main page editor. Wouldn’t have had to put TRM through the RfA bunfight. P-K3 (talk) 11:52, 1 July 2020 (UTC)
- Well, I can't do what Serial Number 54129 suggested. So The Rambling Man will just have to run for admin again. Mjroots (talk) 09:02, 1 July 2020 (UTC)
- As PK3 notes, this is why Valereee and I proposed creating the WP:Main page editor group: TRM is among those who needs this userright. No objections to him receiving template editor, but it doesn't address any of the main page issues; in fact in this use case, it wouldn't help at all. Vanamonde (Talk) 14:50, 1 July 2020 (UTC)
- Agree that we now have at least one example of where WP:Main page editor makes sense. Hobit (talk) 17:37, 1 July 2020 (UTC)
- To be accurate, TRM is the probably the only editor trusted enough to have MPE as an ex-admin/crat. --qedk (t 愛 c) 17:46, 1 July 2020 (UTC)
- Hardly. There are several others, who I am not going to name because this isn't a discussion where anything can come of doing so, but who've done more work with main page content than the vast majority of admins. Vanamonde (Talk) 20:23, 1 July 2020 (UTC)
- You missed my point, I still don't trust them enough to have them edit the main page (probably). In contrast, I can trust TRM because of their previous positions of trust (remember that all this is just my opinion, the community might have a different view and the point of having MPEs was one that the community denied). --qedk (t 愛 c) 14:51, 6 July 2020 (UTC)
- Hardly. There are several others, who I am not going to name because this isn't a discussion where anything can come of doing so, but who've done more work with main page content than the vast majority of admins. Vanamonde (Talk) 20:23, 1 July 2020 (UTC)
- To be accurate, TRM is the probably the only editor trusted enough to have MPE as an ex-admin/crat. --qedk (t 愛 c) 17:46, 1 July 2020 (UTC)
@Konli17: with his disruptive editing
This user keep changing topics according his own point of view. For example "Syria" into "Rojava", or "Turkey or "Southeastern Anatolia Region" into "Turkish Kurdistan" as if these things are even a country, not even a historical region, it's like calling Tabriz is a city in Iranian Azerbaijan instead of Iran. Ins't this disruptive? This user has ongoing disputed with different users in different pages, please check his history. Sometimes, he also adds some tricky stuff meantime his editing, which the source doesn't even talk about. Beshogur (talk) 13:27, 2 July 2020 (UTC)
- The second sentence of the Tabriz article says it's in Iranian Azerbaijan. Konli17 (talk) 15:08, 2 July 2020 (UTC)
- East Azerbaijan is a province, administrative division, so your suggestions are not valid. Beshogur (talk) 15:16, 2 July 2020 (UTC)
- East Azerbaijan Province is very much a province and administrative division. However, it makes its appearance in the first sentence of the Tabriz article, not the second, detracting somewhat from the validity of your argument. Konli17 (talk) 18:21, 2 July 2020 (UTC)
- East Azerbaijan is a province, administrative division, so your suggestions are not valid. Beshogur (talk) 15:16, 2 July 2020 (UTC)
Here is good examples [[1]] [[2]],where he deletes large sources information. You can see what his POV is. Shadow4dark (talk) 14:08, 3 July 2020 (UTC)
- User Konli17 was recently blocked for edit-warring behavior. They seem to be on an aggressive POV crusader, and their contributions sound more like propaganda publishers websites/fora. See this page they created. More edit-warring examples here and here, in addition to the articles pointed out above. Amr ibn Kulthoumعمرو بن كلثوم (talk) 22:26, 5 July 2020 (UTC)
- FYI:The Block of Konli17 was quite unusual as both editors (Konli17 and Amr Ibn) reverted the same amount of times and at the end Amr Ibn didn't make any explanations at the tal page, edit warred and reported the editor at the ANI where the active editor (Konli17) at the Tell Abyad talk page was blocked for 48h for reverting 9 times, actually both reverted 8 times (without breaking the 1RR rule) but only Konli17, the active user at the talk page was blocked. I too had my issues with Amr Ibn, Amr Ibn reverted me twice more without leaving an explanation at the talk page even though he was warned not to revert by the blocking Sysop of the first editor. I adverted the blocking Sysop of it, but to no avail. The Tell Abyad page dispute is currently at the DRN (request filed by me) and is awaiting a solution. I advise the Sysops to check the available (=provided) information about the conflicts mentioned here.Paradise Chronicle (talk) 00:41, 6 July 2020 (UTC)
- @Paradise chronicle: I did provide thorough answers and explanation on the Tel Abyad Talk page starting by this edit. Your unfounded claims here are no surprise to me given that you are the other user involved with Konli's POV campaign, reverting my Washington Post story from the Tel Abyad page and calling it nonsense, may be because it goes against the propaganda sites you both prefer using. Amr ibn Kulthoumعمرو بن كلثوم (talk) 21:21, 6 July 2020 (UTC)
- FYI:The Block of Konli17 was quite unusual as both editors (Konli17 and Amr Ibn) reverted the same amount of times and at the end Amr Ibn didn't make any explanations at the tal page, edit warred and reported the editor at the ANI where the active editor (Konli17) at the Tell Abyad talk page was blocked for 48h for reverting 9 times, actually both reverted 8 times (without breaking the 1RR rule) but only Konli17, the active user at the talk page was blocked. I too had my issues with Amr Ibn, Amr Ibn reverted me twice more without leaving an explanation at the talk page even though he was warned not to revert by the blocking Sysop of the first editor. I adverted the blocking Sysop of it, but to no avail. The Tell Abyad page dispute is currently at the DRN (request filed by me) and is awaiting a solution. I advise the Sysops to check the available (=provided) information about the conflicts mentioned here.Paradise Chronicle (talk) 00:41, 6 July 2020 (UTC)
- User Konli17 was recently blocked for edit-warring behavior. They seem to be on an aggressive POV crusader, and their contributions sound more like propaganda publishers websites/fora. See this page they created. More edit-warring examples here and here, in addition to the articles pointed out above. Amr ibn Kulthoumعمرو بن كلثوم (talk) 22:26, 5 July 2020 (UTC)
It seems that editor Konli17 is on Wikipedia for the sole purpose of pushing his POV. He needs to stop. The last block did not seem to do anything. Tradediatalk 05:52, 6 July 2020 (UTC)
Grove music online
I was told when I got access to Grove Music online through the Wikipedia Library that it was a requirement of using it that you had to cite references to it like this, for instance - <ref name=Grove>|title=Prophète, Le|author= Huebner, Stephen|access-date=8 July 2016, with the "ref brackets of course. of course. That added a note which said "subscription required". I used it for years, very useful, no problem, grateful for the facilty. Nothing in the footnotes ever came up in red. Suddenly yesterday and today this cite of GroveOnline has been changed somehow and the "subscription required" notice has vanished, instead a note in red has taken its place saying "access-date= requires |url=". Someone appears to have changed it somehow because of this discussion [3] at Template talk:GroveOnline, which is completely over my head, I don't have a clue what they are talking about. Now a bot run by PBS is gong though every article which was cited to GroveOnline "the old way" taking out the access date, also not replacing the "subscription required" notice, leaving an edit summary Remove access-date from GroveOnline because there is no url paramter and possibly some other changes on hundreds of article pages I maintain. My question, other than "why in the world are they doing this" is, I was told that "subscription required" notice must be included when GroveOnline is cited. has that changed? I really hate these kinds of mass changes with fussy little stuff that clog up my watchlist, at times like these I wonder why I bother to edit WP.Smeat75 (talk) 23:07, 2 July 2020 (UTC)
- This is the primary reason I stopped using cite templates many years ago. I just add the citation information manually to avoid this problem. I recommend you do the same. Viriditas (talk) 23:12, 2 July 2020 (UTC)
- Smeat75, what happens if you paste the url into ProveIt? Guy (help!) 00:00, 3 July 2020 (UTC)
- The bot is changing them all and I'm not techy enough to intervene. Smeat75 (talk) 00:04, 3 July 2020 (UTC)
- I could be in over my head and not know it, but from reading through the discussion I think the reasons for the change in template were sound. However, when templates are changed and those changes cause working references to become broken, we need a better response than "user error". The user did not error in making a reference that, at the time, worked. I know that other kinds of templates get changed regularly and yet they don't end up showing up at AN with the same frequency as changes in reference templates end up here. So let's keep improving ref templates but also, and this is where I back-off in hopes that people better qualified than I pick up the baton, let's improve our process around what happens when improvements to reference templates break things. Best, Barkeep49 (talk) 02:07, 3 July 2020 (UTC)
- Better yet, let's make very, very, very sure that the benefits which will come from changing a reference template are worth the inevitable problems the change will cause. If it ain't broke, don't fix it. Beyond My Ken (talk) 02:42, 3 July 2020 (UTC)
- Barkeep49, 100%. There should be no shame in backing out a change that has unforeseen effects, and there should be way more discussion and testing before changing widely-used templates. Guy (help!) 10:39, 3 July 2020 (UTC)
I can't find a BRFA for this operation. It is being run from User:PBS-AWB which should cause a ping. Can someone block that bot until this is sorted? 2601:648:8202:96B0:0:0:0:C4FC (talk) 07:44, 3 July 2020 (UTC)
- I don't think it's a bot, it's an alt account using AWB. Guy (help!) 10:45, 3 July 2020 (UTC)
- Irrelevant, see WP:MEATBOT. 2601:648:8202:96B0:0:0:0:C4FC (talk) 17:33, 3 July 2020 (UTC)
I ran WP:AWB manually the actions were not taken by a bot. See the recent discussions on Template talk:GroveOnline as to why this was necessary given the desirable reasons for changing the template. However in simple terms I broke nothing. What I did was to remove an error message. Almost all the citation templates and their wrapper templates will give an error message if someone adds an "access-date" parameter to a citation that does not have a url link. The whole point of access-date[s] is to inform a reader when a web page was accessed as a warning that the current content of the page may have changed sine it was cited. There is no point in adding an "access-date" parameter to a citation that has no url. Recent changes to the template means that all the instances of {{GroveOnline}}
which had an "access-date" parameter were now displaying an error message:
{{GroveOnline|title=Traviata, La||access-date=3 July 2020}}
produces:
- Sadie, Stanley; Tyrrell, John, eds. (2001). "Traviata, La". The New Grove Dictionary of Music and Musicians (2nd ed.). London: Macmillan Publishers. ISBN 978-1-56159-239-5.
{{cite encyclopedia}}
:|access-date=
requires|url=
(help)
So for example Revision as of 00:14, 22 September 2018 by user:Smeat75 added the citation:
{{GroveOnline|title=Traviata, La|author= Parker, Roger|access-date=21 September 2018}}
The AWB script (Revision as of 17:34, 2 July 2020) changed it to
{{GroveOnline |last=Parker |first=Roger |title=Traviata, La}}
The reason for also changing the "author" parameter to "first" and "last" is because it is standard to split name (rather than the kludge using "Parker, Roger" as a string in the parameter "author") and allows the long citation be be cited in the standard short format using the {{harv}}
templates. In fact across the 660 articles there was a mixture of "first-names second-name" and "second-name, first-names" sometimes in the same citation. The reason for placing the names first and the title after them is it makes finding and or (in a reference list) alphabetically sorting on author easier. This is also the order in which the template displays the parameters (WYSIWYG).
Now to address the subscription required. If there is no link to the online subscription service then no subscription is required—instead, if one is rich, one can purchase the book (published 2001) or use a library. On the template talk page (see above) there is a discussion about whether, if there is a url parameter, to rely on the standard citation templates' red padlock (which is also used at the Grove web site), or continue with a subscription postscript. Opinions on the talk page differ, however if no consensus to remove the postscript, for those templates that have an online link, it can be reinstated.
The primary reason for making the change is that there are currently 3 different and overlapping templates {{GroveOnline}}
{{Cite Grove}}
and {{Cite NewGrove2001}}
. The intention is to merge all three (starting with {{GroveOnline}}
{{Cite Grove}}
). The first step of which was to alter the oldest one, {{GroveOnline}}
, so that the script was converted from calling {{cite encyclopedia}}
directly into using the Lua template wrapper. This move most of the script complications down into the standard Lua code. For example the GroveOnline script prior to the change had 41 line now it has 11 line and far more functionality.
-- PBS (talk) 14:01, 3 July 2020 (UTC)
Just a note from the Wikipedia Library team that we don't require any particular citation formatting if you get access to content through the library. We previously had some text on the signup pages which unfortunately implied a requirement but was just our best attempt to provide an example of a full citation per the then best practices. See a previous discussion on this in the VPP archive. Samwalton9 (WMF) (talk) 14:17, 3 July 2020 (UTC)
- Further to what PBS says above, yes you could go out and buy Grove Music (published in 2001) or use a library but Grove Music online is part of Oxford Music Online and when you have access to that you also have access to " to search The Oxford Dictionary of Music and The Oxford Companion to Music". Further the online version is constantly updated, it's not the same as the book published in 2001, just last month for instance "We are pleased to have added 3 new articles, 12 new images, 67 revised entries, and refreshed data for 4 entries for this site update." So how am I supposed to cite it now? It worked perfectly well before these (completely unnecessary imo) changes messed it up.Smeat75 (talk) 14:30, 3 July 2020 (UTC)
- As it happens, before I went through the pages that did not have URL, I went through those that that did adding a full citation including the date and checking the link to the Grove online site. Those examples can be found in:
- I also added some to six other templates using "doi" and "id" see:
- So you can use those articles to see how to link the article to the website and how to date them correctly. -- PBS (talk) 14:40, 3 July 2020 (UTC)
- Never mind, I'll just do it manually from now on as Viriditas suggests and not use cite templates. I thought you were supposed to as a condition of having access through the Wikipedia library. I don't have an effing clue what a "template with a doi parameter" or an "id paraamter" is and could not care less, I edit articles on MUSIC because readers come hear to learn about MUSIC not all that technical bollocks.Smeat75 (talk) 15:02, 3 July 2020 (UTC)
- As it happens, before I went through the pages that did not have URL, I went through those that that did adding a full citation including the date and checking the link to the Grove online site. Those examples can be found in:
- @PBS: as I indicated upthread I read the original discussion and understood the reasoning for this change. The change made sense. But you've either not seen, don't understand, or disagree with the point I was also trying to make. So let me try making it again . Your technical change was good. But a reference that was added, even one added incorrectly, that didn't produce an error when added and now produces an error is a broken reference and it was broken by the change in template. The response that seems to be common in these situations is to blame the editors who didn't do the technical side correctly in the first place. I think that attitude means that reference template changes end up at AN far too often. And for that I firmly believe something can be done but stop short of saying what the right solution out of respect for people who understand this better than I do. Best, Barkeep49 (talk) 23:10, 3 July 2020 (UTC)
- I have sympathy with your argument, for example changing "cite ..." templates to match
{{citation}}
template in regards to the way that the ref parameter works has left a long tail of problems. However (MRDA) in this case I assessed the problem of the issues that would appear and knew that I could fix them in a few days (2,3?). I fixed the instances I knew would be broken after the change (unnamed parameters) before the change, but others which produced red warning I did not fix prior to the change, because potentially other editors not seeing the problem (red warnings) would probably have revert some of the changes. Once the change was made then making a revert of a revert would be needed. This would have made work for people that was fruitless and would I think have caused more resentment. Not running the AWB script would also have caused resentment with editors who had not expressed an opinion in the change forced to clean up someone else's red mess. -- PBS (talk) 06:34, 4 July 2020 (UTC)
- I have sympathy with your argument, for example changing "cite ..." templates to match
- Hang on — so, to me as a casual passer-by, the above and linked discussion seems to be missing the forest for the trees. Wouldn't the fix for the underlying issue be to allow access-date without URL for online reference works like this that could reasonably be cited without a URL (Grove Online, OED, etc.)? The access-date information seems logically applicable to citations such as these, since the sources' text can change and then no longer support the content sourced to it. It sounds like the reason for excluding it is lack of support in a dependency of the template, which doesn't sound like something intractable to remedy (imagining logic to the effect of, "if the title matches 'Grove', then don't treat 'access-date without url' as an error"). Just my 2¢… —{{u|Goldenshimmer}} (they/them)|Talk|Contributions 05:01, 8 July 2020 (UTC)
|access-date=
requires the use of|url=
in CS1/2 templates, which is a long-standing requirement for template input (see category). {{Cite Grove}} is a derivative of {{cite encyclopedia}} and thus has the same requirement. However, before this change, the template provided an automatic link to the DOI in the URL field rather than in the expected field, which is|doi=
. This allowed for the use of template with the access date provided to take no URL. Now that the template does not have this automatic fallback, the template is falling back to the default behavior in the core template, which is to warn the user that the access date has no URL. And so we're here today where PBS has since stated that he was aware of what would happen and was going to fix it after the change in Cite Grove, with some reasonable rationale. It is not the case that you cannot have an accessdate, it is the case that if you have one, you must have selected some particular URL to go with that accessdate. (Permanent identifiers do not need access dates because they are anticipated/expected to be usable for a reasonably long time to find the work so-identified.) --Izno (talk) 15:09, 8 July 2020 (UTC)- Thanks. I still tend to think it would be better to (at least temporarily) change the tradition at CS1 to carve out an exception to that requirement for references to this sort of work, until the offending references are re-checked against the source and updated with URL and accessdate, since just removing the accessdate would confusingly imply it's a static source à la print… I guess it's perhaps overly optimistic to think that process would get taken care of quickly, though, since it would essentially just be yet another maintenance backlog. Oh well, I guess there are substantially more important fish to fry. —{{u|Goldenshimmer}} (they/them)|Talk|Contributions 02:42, 9 July 2020 (UTC)
- {{cite Grove}} has 800 transclusions. Module:Citation/CS1 has 4 million and change. Which do you think is more likely to be changed when the change in one is a routine update and one is a rather significant departure from previous behavior? :) --Izno (talk) 02:48, 9 July 2020 (UTC)
- Mm, fair enough. :) —{{u|Goldenshimmer}} (they/them)|Talk|Contributions 06:34, 9 July 2020 (UTC)
- {{cite Grove}} has 800 transclusions. Module:Citation/CS1 has 4 million and change. Which do you think is more likely to be changed when the change in one is a routine update and one is a rather significant departure from previous behavior? :) --Izno (talk) 02:48, 9 July 2020 (UTC)
- Thanks. I still tend to think it would be better to (at least temporarily) change the tradition at CS1 to carve out an exception to that requirement for references to this sort of work, until the offending references are re-checked against the source and updated with URL and accessdate, since just removing the accessdate would confusingly imply it's a static source à la print… I guess it's perhaps overly optimistic to think that process would get taken care of quickly, though, since it would essentially just be yet another maintenance backlog. Oh well, I guess there are substantially more important fish to fry. —{{u|Goldenshimmer}} (they/them)|Talk|Contributions 02:42, 9 July 2020 (UTC)
- As the author of the alternate Grove templates that (eventually) prompted the merger discussion referenced above, my plan was to make a parallel implementation that was clean, consistent, and without all the quirky behaviour of the original Grove templates (they were written by different people, at different times, using different implementation strategies, for different driving purposes, and implement various non-standard behaviour and logic that only work in very limited situations); and then to manually and article-by-article and cite-by-cite go through and replace the old templates with the new. Beyond the technical aspects, this makes sure any changes in output after the changeover have been assessed, individually (because usages are individual), by a human being; and that the editors that care about a particular article have a real chance to object, point out problems, and, possibly, to be persuaded that the changes are acceptable. Once the old templates have zero mainspace transclusions they can be MfD'ed and possibly AWB-replaced.Changing the implementation of the existing templates in breaking ways and then AWB-modifying usages to what you think they should be is not taking into account the fact that people who are here to write articles care about their citations, and has put considerable effort into making them just the way they want them. It is prioritising factors such as the edit history artefacts in Template:-space, automatability of mass changes (which, yes, requires BRFA, regardless of whether you implement your (meat)bot using pywikibot or AWB, for precisely this reason; check the terms of use for AWB), and clean metadata. It is making this prioritisation over all the editors that have worked hard on actual articles and their citations, and who spend a lot of time and effort maintaining those articles. It is making that prioritisation at the expense of the actual output in the affected articles. And it is doing so based on one editor's opinion, made outside of the local article (where all such issues should be discussed, unless a community-wide consensus overrules it), and in de facto contravention of CITEVAR.Editors proclaiming they'll stop using citation templates sounds, at first blush, like childishness or sour grapes. It's not. It is fast becoming the only reasonable approach to a culture that permits running roughshod over local consensus just because the change in question was one that was automatable and had some desirable technical effects. That permits people running a bot to impose their idea of the one true Wikipedia citation style, despite broad consensus that Wikipedia has no one true citation style. Where adding
{{bots|deny=botname}}
to an article to prevent changes the local editors see as undesirable is mass bot reverted because, they argue,{{bots|deny=botname}}
has zero valid use cases (just try to grasp the level of Kafkaesquity of this from a content editor's point of view: this behaviour by a human on one article would be sanctioned as edit warring, but when performed by a bot over hundreds or thousands of articles it's somehow ok?). Using citation templates creates the technical possibility to make mass changes, but being possible is not the same as being desirable or permitted. And, in fact, in many of these cases, is explicitly forbidden and explicitly requires approval to make sure there is consensus for the changes before they are made. Just because the technical effects are good and desirable in themselves does not ipso facto mean they are more important then their effects on articles and the editors there.These issues keep appearing at AN/ANI because AN/ANI is failing to actually enforce existing policy. Such mass changes are disruptive if not handled properly, and a lot of these changes violate CITEVAR, completely irrespective of whether the changes also happen to have some desirable technical effects. Anyone that wants to mass change citations on the project should head on over to the Village Pump and make the case for why their One True Citation Style should be mandatory across English Wikipedia, and anyone ending here at AN/ANI after mass changes without a community-wide RfC to back up their specific changes over local consensus should be treated like any other user engaging in mass disruptive behaviour. There is absolutely no reason why these issues should have to end up at ArbCom (we've had citation styles once, and infoboxes twice) if ANI would actually enforce existing policy (WP:BOTPOL, WP:AWBRULES, WP:CITEVAR). Give editors working in content space and who actually care about their citations a break, will you? Editors who care is a good thing: we want to attract more of them, not drive away the dwindling number we have left.PS. Just to give some context of where I'm coming from… I'm a techie that will routinely spend hours automating a task that can be done manually in mere minutes more. I'm passionate about semantic and correct metadata, and have as a personal bugaboo that inaccurate or incorrect metadata is actively harmful. I'll happily approach any problem on-wiki through technical means if technical means are feasible. I am the kind of person that gets disproportionately grateful for gnomes doing stuff like this on "my" articles. I am in no way shape or form opposed to technical solutions—in fact, I advocate for them—when technical solutions are actually feasible. In the cases that have ended up here lately, they haven't been, but have been rammed through regardless.PPS. Note that while the above certainly contains criticism of the approach PBS took here—and, in fairness I have to admit I am a little personally miffed they decided to overwrite the new templates I'd made—it's not really criticism of PBS. They were clearly acting in good faith and doing their best to be transparent, open, and inclusive, and to make these changes responsibly. What I'm saying is that in this case they walked into a trap, of sorts, created by our inability to actually enforce existing policy: I am here criticising a systemic issue, not a single editor doing their best within that system. --Xover (talk) 10:08, 9 July 2020 (UTC) - Eloquent post User:Xover, thank you. Smeat75 (talk) 16:52, 10 July 2020 (UTC)
3nk1namshub
- 3nk1namshub (talk · contribs · deleted contribs · logs · filter log · block user · block log)
In attempting to understand 3nk1namshub's frankly bizarre behaviour I found this [4], which may perhaps identify a root cause. Regardless, having reviewed their edits I am pretty confident that Wikipedia is going to be bad for their mental health (and the evidence suggests that they are also going to be bad for ours) so I have blocked per WP:NOTHERE. If anyone feels that they can fix this through kindness and patience then they are more than welcome to unblock. Guy (help!) 09:01, 3 July 2020 (UTC)
- Endorse block. I am fine with having them address problems through the venue of an unblock appeal, if they're serious about continuing to contribute. This level of vitriol falls well bellow expectations and require significant correction. El_C 10:48, 3 July 2020 (UTC)
- Endorse, recommend standard offer. Six months working on other wikis will allow them to demonstrate that they can beahve collegially.— Preceding unsigned comment added by Serial Number 54129 (talk • contribs) 2020-07-03T11:20:55 (UTC)
Standard offer, 6 months constructivity other projects. (Last I looked, they had an active unblock. --Deepfriedokra (talk) 11:28, 3 July 2020 (UTC)- Switch to unblock when GW's mentorship is in place/ FWIW, I identify as autistic, and that should not be a factor. --Deepfriedokra (talk) 17:18, 3 July 2020 (UTC)
- Or Jasper's. Or both. --Deepfriedokra (talk) 17:20, 3 July 2020 (UTC)
- I have a great deal of sympathy with this user's cause. The Signpost page which they are talking about is, frankly, disgusting, and I can clearly understand why a new user would feel that it absolutely should be deleted post-haste, not being familiar with the consensus process. However, we do, of course, have a consensus process, and neither AN nor the user's talk page or user page is the place to question an existing consensus. I think it ought to be questioned why the discussion at WT:SIGNPOST was closed so soon, even with the incivility issues, but I do not object to the block itself; it is clear that they have been extremely uncivil, and whilst I might quibble about the consistency with which a block might or might not be applied for those same actions, I think the decision that has been taken here is a good one. That being said, I think an unblock should be considered after a short period of time (shorter than the standard offer, certainly); I don't think the editor is here with an intent to be disruptive. Perhaps I'm taking WP:AGF to an extreme here, but I think they are genuinely trying to make the encyclopedia better, albeit the case that they clearly need to consider the way that they do that, and the way that they interact with other people. If they were to continue being uncivil after an unblock, then an indef without standard appeals would be warranted. Naypta ☺ | ✉ talk page | 11:51, 3 July 2020 (UTC)
- And I would agree with Naypta were it not for the s aforementioned edit summary. Taken as a whole, 3nk1namshub needs to calm down. --Deepfriedokra (talk) 11:56, 3 July 2020 (UTC)
- @Deepfriedokra: That's understandable, for sure. I think it's worthy of note that the user did later try to post an apology for that after their 24 hour block for it expired, but reasonable people can disagree on whether or not that is sufficient to make up for it. I wonder what RandomCanadian thinks is appropriate, seeing as they were the target of the abuse in this case - please don't feel you have to reply to this ping if you'd rather not, though, as I appreciate this is a difficult subject. Naypta ☺ | ✉ talk page | 12:01, 3 July 2020 (UTC)
- Nothing difficult at all. Taken as a whole, 3nk1namshub is not ready for a collaborative environment. Perhaps six months from now, they will be. --Deepfriedokra (talk) 12:03, 3 July 2020 (UTC)
- @Deepfriedokra: I do, however, wonder if they deserve this kind of gravedancing? I suggest not; it's childish, unhelpful mockery. In my book, even if it were true, anyone who thinks it necessary to say that on the user's own page is demonstrating extremely poor judgement. ——Serial # 12:47, 3 July 2020 (UTC)
- I have removed the offending comment. And will warn the user about this sort of thing being totally unacceptable. El_C 12:56, 3 July 2020 (UTC)
- Thanks, El_C, no need to make this worse than it has to be. ——Serial # 13:19, 3 July 2020 (UTC)
- Serial Number 54129, absolutely. Thank you for bringing this to our attention. El_C 13:27, 3 July 2020 (UTC)
- Hell, I'd have suggested blocking the one who posted that comment since it's clearly not their first disruptive salvo against the indeffed user, and considering that they just "lol"ed off the first warning, there's no indication that they plan to stop.--WaltCip-(BLM!Resist The Orange One) 14:01, 3 July 2020 (UTC)
- Hell, and that’s why you’re not an admin, lol. And where’s the indication I plan to continue? I’ll answer for you; nowhere. End of discussion. Good day. – 2.O.Boxing 14:25, 3 July 2020 (UTC)
- I concur with WaltCip. And Squared.Circle.Boxing would do well to consider that ANIs often conclude with sanctions against multiple parties, not just the one named in the heading. "Mooning the jury" here with personalized hostility as you did is a strong indication that WaltCip's assessment is correct. — SMcCandlish ☏ ¢ 😼 22:17, 9 July 2020 (UTC)
- Hell, and that’s why you’re not an admin, lol. And where’s the indication I plan to continue? I’ll answer for you; nowhere. End of discussion. Good day. – 2.O.Boxing 14:25, 3 July 2020 (UTC)
- Hell, I'd have suggested blocking the one who posted that comment since it's clearly not their first disruptive salvo against the indeffed user, and considering that they just "lol"ed off the first warning, there's no indication that they plan to stop.--WaltCip-(BLM!Resist The Orange One) 14:01, 3 July 2020 (UTC)
- Serial Number 54129, absolutely. Thank you for bringing this to our attention. El_C 13:27, 3 July 2020 (UTC)
- Thanks, El_C, no need to make this worse than it has to be. ——Serial # 13:19, 3 July 2020 (UTC)
- I have removed the offending comment. And will warn the user about this sort of thing being totally unacceptable. El_C 12:56, 3 July 2020 (UTC)
- @Deepfriedokra: I do, however, wonder if they deserve this kind of gravedancing? I suggest not; it's childish, unhelpful mockery. In my book, even if it were true, anyone who thinks it necessary to say that on the user's own page is demonstrating extremely poor judgement. ——Serial # 12:47, 3 July 2020 (UTC)
- Nothing difficult at all. Taken as a whole, 3nk1namshub is not ready for a collaborative environment. Perhaps six months from now, they will be. --Deepfriedokra (talk) 12:03, 3 July 2020 (UTC)
- @Deepfriedokra: That's understandable, for sure. I think it's worthy of note that the user did later try to post an apology for that after their 24 hour block for it expired, but reasonable people can disagree on whether or not that is sufficient to make up for it. I wonder what RandomCanadian thinks is appropriate, seeing as they were the target of the abuse in this case - please don't feel you have to reply to this ping if you'd rather not, though, as I appreciate this is a difficult subject. Naypta ☺ | ✉ talk page | 12:01, 3 July 2020 (UTC)
- And I would agree with Naypta were it not for the s aforementioned edit summary. Taken as a whole, 3nk1namshub needs to calm down. --Deepfriedokra (talk) 11:56, 3 July 2020 (UTC)
- Clearly not ;) Old news, nothing to see here, move along. – 2.O.Boxing 02:39, 11 July 2020 (UTC)
- Personally I think this could have been discussed prior to a block, but that notwithstanding I'm inclined to agree with Naypta. Either we can try a 2-week time-limited block and see their behaviour on return; alternatively, stick with the indef but use 2 weeks or a month as the functional base time for unblock discussions instead of 6 months. I'm tempted to go for the latter as the unblocking admin will probably need to have a fairly lengthy discussion to work out whether the editor has had a chance to consider, as well as setting up any editing restrictions appropriate. Nosebagbear (talk) 13:29, 3 July 2020 (UTC)
- Nosebagbear, preference for the latter. El_C 13:31, 3 July 2020 (UTC)
- Post mentorship offers, so as long as a 3rd party unblocker (ie not a mentor) was happy with any unblock conditions, a mentor was in place and accepted by the user, and sufficient understanding demonstrated, I'd be happy to back an unblock at any point. Nosebagbear (talk) 18:32, 3 July 2020 (UTC)
- Endorse the user in question has made a grand total of 10 mainspace edits. The disruption clearly outweighs any contributions made to the encyclopedia. LEPRICAVARK (talk) 15:33, 3 July 2020 (UTC)
- Why is an edit summary from a week ago being brought up as reasoning for a block now? I was on the receiving end of some of 3nk1namshub's less-than-charitable comments surrounding the Autism issue, and I've had their user page watchlisted since, which is why I'm showing up here now. They were briefly blocked for their behavior in that dispute, and shortly after they realized that they had reacted inappropriately due to the very personal nature of the issue, and apologized. It seems like double jeopardy for their behavior then to be used against them now. Their behavior in this latest dispute was disruptive, yes, but they were also trying to raise what I believe to be legitimate concerns. An indef block seems excessive, and their recent unblock request suggests to me they've cooled down. GorillaWarfare (talk) 16:20, 3 July 2020 (UTC)
- GorillaWarfare, only that it's an indication (backed by subsequent statements) that the user identifies as autistic, which explains the obsessive behaviour but also speaks to the likelihood of that changing. That's why El C and I were distinctly unimpressed with Squared.Circle.Boxing's bullshit noted above.
- This is not about attacks that have long since blown over, but about the very odd behaviour around the old Signpost article.
- This is also not a cool down block. It's a discussion about whether someone has the reserves of kindness and patience to help 3nk1namshub to have a Wikipedia experience that will not cause them serious distress, which is what's happened to date. Guy (help!) 17:01, 3 July 2020 (UTC)
- We are not medical professionals caring for 3nk1namshub, and so I do not believe it is appropriate for us to try to decide what is best for them based on their autism nor predict their behavior based on it. It should not factor in to any sanctions; they can make the decision for themself around whether they wish and are able to contribute here within our policies and guidelines. If what you are looking for is some sort of mentor for them, I am happy to volunteer if they are open to that solution. GorillaWarfare (talk) 17:09, 3 July 2020 (UTC)
- GorillaWarfare, if you're willing to volunteer for that, I would support taking any action you see fit. El_C 18:12, 3 July 2020 (UTC)
- I think the best thing to do right now is wait to hear from 3nk1namshub. If they're willing to move forward with a mentor, that might be the best option. I see Jasper Deng has also offered to mentor, so I'd leave it up to 3nk1namshub to decide who they'd prefer. GorillaWarfare (talk) 18:20, 3 July 2020 (UTC)
- GorillaWarfare, if you're willing to volunteer for that, I would support taking any action you see fit. El_C 18:12, 3 July 2020 (UTC)
- We are not medical professionals caring for 3nk1namshub, and so I do not believe it is appropriate for us to try to decide what is best for them based on their autism nor predict their behavior based on it. It should not factor in to any sanctions; they can make the decision for themself around whether they wish and are able to contribute here within our policies and guidelines. If what you are looking for is some sort of mentor for them, I am happy to volunteer if they are open to that solution. GorillaWarfare (talk) 17:09, 3 July 2020 (UTC)
- Unpopular opinion, but overturn per @GorillaWarfare:. I am willing to take on the role of mentoring them as they appear to at least be willing to communicate about these issues. The user has acknowledged multiple times that their behavior was inappropriate and I've suggested them multiple times to edit content, though I don't have much in the way of specific articles they could work on. I think a conditional unblock, including a topic ban from the Signpost piece (bad as it was) and the condition of mentorship, would be a much better alternative to the standard offer.--Jasper Deng (talk) 17:12, 3 July 2020 (UTC)
- Jasper Deng, you may wish to review my unblock decline. El_C 17:14, 3 July 2020 (UTC)
- @El C: Honestly, I don't think it addresses what GorillaWarfare said. What's important is that they know they were (not "are") disruptive and are willing to work to change their behavior.--Jasper Deng (talk) 17:18, 3 July 2020 (UTC)
- Jasper Deng, based on their past behaviour, I still think they need more time away from the project, for a while, at least. El_C 17:22, 3 July 2020 (UTC)
- @El C: I even suggested that too, but I would rather not have it done by a block, especially as they have disengaged from the topic in question at my suggestion (there is little to prevent). But now that we're here, I think it's better to offer a conditional unblock along these lines (and GW's) rather than merely decline their request.--Jasper Deng (talk) 17:28, 3 July 2020 (UTC)
- Jasper Deng, in time. I still think we need more time. El_C 17:29, 3 July 2020 (UTC)
- @El C: How about we be specific, and not vague. Why make it involuntary when they themselves have offered to take a wikibreak? Look, I agree they need time away from the project. But they already offered to do so voluntarily, and they already have made an earnest promise to change their behavior. I don't really see what purpose this block serves.--Jasper Deng (talk) 17:33, 3 July 2020 (UTC)
- Now the temptation to act inappropriately (even if from admirable reasons) is removed. El_C 17:39, 3 July 2020 (UTC)
- @El C: I don't think it was there anymore in the first place, to be quite honest. Read the conversation I had with them before the block in full detail. I highly suggest the WP:ROPE approach and mentorship in lieu of the block.--Jasper Deng (talk) 17:40, 3 July 2020 (UTC)
- Jasper Deng, they are welcome to make another unblock appeal. Alternatively, if there is consensus to unblock in this report, I will likewise not stand in its way. El_C 17:46, 3 July 2020 (UTC)
- Also, I strongly endorse what GW said: never tell anyone that their actions are due to a disorder, even when they say they have said disorder. It's not our place to make such assumptions.--Jasper Deng (talk) 17:35, 3 July 2020 (UTC)
- Jasper Deng, I didn't, they did. Guy (help!) 18:04, 3 July 2020 (UTC)
- Also, I strongly endorse what GW said: never tell anyone that their actions are due to a disorder, even when they say they have said disorder. It's not our place to make such assumptions.--Jasper Deng (talk) 17:35, 3 July 2020 (UTC)
- As the previous blocking administrator, who believed that there was a good chance that 3nk1namshub would reconsider, I was vindicated by their response. Realistically, I also believed that this might recur, but I was willing to give them the benefit of the doubt. I continue to hold that belief. While we have a policy of not issuing cool-down blocks, in the case of this particular user, and in view of their self-description, that might be the best and kindest approach. I remain opposed to an indef, on the basis of my interactions with the user. Acroterion (talk) 17:32, 3 July 2020 (UTC)
- I still think the user has been too disruptive to immediately unblock. El_C 17:39, 3 July 2020 (UTC)
- I'm not suggesting an immediate unblock. I'm opposed to an indefinite NOTHERE block. Acroterion (talk) 17:49, 3 July 2020 (UTC)
- Acroterion, understood. El_C 17:55, 3 July 2020 (UTC)
- I'm not suggesting an immediate unblock. I'm opposed to an indefinite NOTHERE block. Acroterion (talk) 17:49, 3 July 2020 (UTC)
- I still think the user has been too disruptive to immediately unblock. El_C 17:39, 3 July 2020 (UTC)
- I don't think I've ever seen a new user get involved in so many nasty disputes so quickly. If that really is the main reason they're here then the NOTHERE block is appropriate. Not opposed to an unblock but I'd like to see a commitment to doing something else, e.g. writing content or doing some useful maintenance task. Hut 8.5 17:39, 3 July 2020 (UTC)
- @Hut 8.5: I think a few explicit content suggestions would indeed be good, and a good way to offer them mentorship. I would rather they stay out of maintenance tasks, if by that you mean anti-vandalism or spam work, if only because I think it would be best if they take their interactions with others slowly and carefully.--Jasper Deng (talk) 17:45, 3 July 2020 (UTC)
- I think a large part of the problem is that most of their interactions with others have been on emotionally charged topics they obviously care deeply about, e.g. trans issues and autism. I suspect they might do better if they avoided those areas. I don't necessarily mean dealing with vandalism or spam, any sort of gnoming work might work. Hut 8.5 17:56, 3 July 2020 (UTC)
- @Hut 8.5: I think a few explicit content suggestions would indeed be good, and a good way to offer them mentorship. I would rather they stay out of maintenance tasks, if by that you mean anti-vandalism or spam work, if only because I think it would be best if they take their interactions with others slowly and carefully.--Jasper Deng (talk) 17:45, 3 July 2020 (UTC)
- That Signpost article is disgusting. It should have the "keep but blank" consensus overturned and be rev-delled. Everyone who was involved in the publication of it should be ashamed. Everyone who defended it (and we know who they are) should likewise be ashamed. If I were on the target side of that horrible thing, I would be filled with rage and anguish, too. So I get it. They're disruptive, but honestly no one seems to give a shit and maybe this disruption is necessary to bring eyeballs back to it. I think with Jasper and GW's mentorship, this user may become productive, so I sit with them.--Jorm (talk) 17:51, 3 July 2020 (UTC)
- Unblock per Jasper and GW. I think that a fair amount of the editor's behavior can be explained as a response to a whole lot of biting, some unintentional and some seemingly intentional. They have expressed contrition, and appear to have already stood down at the time that the block was put in place. This feels a bit like a trans-rights analogue to WP:Don't overlook legal threats. signed, Rosguill talk 17:57, 3 July 2020 (UTC)
- Unblock. Wholeheartedly agree with GW, Jasper, Jorm, et al. The Signpost piece is abhorrent. It's dehumanizing, and the fact that it was allowed to be kept and not deleted disgusts me. I'm absolutely going to call people out here: SMcCandlish, Barbara (WVS), you should be ashamed, as should everyone else who thinks this shit is funny. For as long as I've been here, Wikipedia has been a heteronormative, cisnormative place, and if we want to build the best free knowledge resource that the world has ever seen, we have to be welcoming to (almost) everybody. As for the block, I agree that I'd like to see 3nk1namshub unblocked at some point, so long as they are involved in some content-related work. They're clearly passionate about a number of subjects, so they could definitely be a net positive, but mentorship would probably be a good idea. – Frood (talk) 18:19, 3 July 2020 (UTC)
- Frood, it's incredibly disruptive to shame-ping two users (one of whom hasn't edited this year) over an old issue. Please don't do that again. LEPRICAVARK (talk) 19:06, 3 July 2020 (UTC)
- Especially when it's completely off-topic, having nothing to do with the blocked user nor their autism-related editing and battlegrounding focus. [And the accusation is incorrect anyway. We've been over this 1,000 times already: just because something involves pronouns doesn't make it trans-related; the piece was about egotistical, religious/mystical, and commercial aggrandizement. To the extent the point it makes could be applied to trans/NB matters at all, it is actually valid: While WP should use he/she/they gender-referential writing practices to suit subjects' source-attested gender identity, WP absolutely should not implement pseudo-pronouns like zir or shim just because a subject does so. It's fine to mention in the article that the subject uses one, as we do at Genesis P-Orridge, but otherwise write around the matter with a neutral singular-they, by repeating the surname, etc.] — SMcCandlish ☏ ¢ 😼 21:23, 3 July 2020 (UTC)
- Frood, it's incredibly disruptive to shame-ping two users (one of whom hasn't edited this year) over an old issue. Please don't do that again. LEPRICAVARK (talk) 19:06, 3 July 2020 (UTC)
- Endorse block but unblock with mentoring - The editor had been disruptive and the block prevented further disruption, so good block. If there are editors willing to mentor, then yes, let's give that a shot, as always. BTW, may I remind everyone that, while I of all editors certainly understand having strong feelings about the deletion of a page :-), there were many editors who !voted to keep that page, some of whom are, of course, themselves transgender or non-binary, and so suggesting that everyone who defended that page is transphobic is probably off the mark. Levivich [dubious – discuss] 18:49, 3 July 2020 (UTC)
- I think it important to remember the subject of this thread is whether 3nk1namshub can edit constructively. There have been issues part from objecting to that Signpost piece. Others have objected without becoming disruptive.3nk1namshub's resounding question,
What is Wikipedia (and the Wikimedia Foundation) doing to challenge the environment they created, that clearly encourages and condones transphobia?
needs to be asked and answered elsewhere, perhaps WP:VPP? --Deepfriedokra (talk) 19:15, 3 July 2020 (UTC)- Deepfriedokra, if at all: we are not actually bad at getting rid of transphobes. Guy (help!) 22:50, 3 July 2020 (UTC)
- Endorse block. Commenting because I like to provide more sympathetic viewpoints for new editors at times, though I'm not sure how well I can do that here. In other cases of new editor 'mistakes', where new editors have apologised for their actions and promise to improve, the community often insists on a ban or a block regardless, and that's in first time cases. In this case, unusually, it seems like arguments are already tending towards more sympathetic, yet the conduct here is more egregious than typical cases, and this isn't the first major issue, it's not even the second - they've promised to stop before. They told an editor to fuck off for closing an edit request, and proceeded to call them a scumbag. That was dealt with and given a 24h block. About 2 weeks later, the trend continues. Even some of their 'calmer' discussions, eg the deadnaming one, started off well and quickly descended beyond appropriate conduct. Multiple editors, across multiple noticeboards and talk pages, have expressed concerns, with Levivich labelling them a RGW SPA. Earlier today they changed their user page (see Special:Permalink/965765536), note the edit summary. Combined with their other comments, I've seen this many times especially in younger editors on various forums, ime it's conflated emotions and there has not been the proper time to reflect, and no benefit ever came, to any party, from undoing the block soon after.
- That said, although much of what they wrote was a sore to read, the discussion at ANI § Why is this ok? was thought-provoking, and I sympathise with their initial comments. The final remark sticks out at me,
Y'all claim you want a more diverse editing population, but do nothing to foster an environment that allows that.
If this were anyone else, I wouldn't even have to comment because everyone else would be moving to keep the block and this discussion would already be closed. Nevertheless, I believe that creating an echo-chamber isn't beneficial to the encyclopaedia. After this mess of conduct, and the recency of it, I firmly oppose an unblock currently. But, after things have calmed down (i.e. in a month's time), should they still wish to contribute to improving Wikipedia, especially in the areas we've gotten wrong across articles, I strongly believe it would be beneficial for the encyclopaedia to grant the request. I also agree mentorship would be a great help, and I do truly hope that they make said unblock request in a month's time; I'd love to have them contributing to fixing the very real problems they describe. ProcrastinatingReader (talk) 19:19, 3 July 2020 (UTC)
- Strongly support unblock, essentially per User:GorillaWarfare's comments. This is someone who didn't handle their anger well, but the indef block is an overreaction (especially as it was partly for something they'd already been blocked for previously). Boing! said Zebedee (talk) 20:06, 3 July 2020 (UTC)
- Boing! said Zebedee, for the avoidance of doubt, that played no part in the block decision, other than as a pattern of weirdness. I think Levivich has the right of it here. Guy (help!) 22:49, 3 July 2020 (UTC)
- @JzG: OK, thanks for the explanation. I still strongly oppose the indef block and support the unblock. Boing! said Zebedee (talk) 06:39, 4 July 2020 (UTC)
- Boing! said Zebedee, unblock with friendly support is 100% the result I hoped for here. Guy (help!) 10:12, 4 July 2020 (UTC)
- Oppose indef I'm ambivalent on the current block, but either way I believe the indef is inappropriate and do not agree the NOTHERE rationale is correct. While the linked diff is obviously disruptive, it was in the context of an edit request so I don't see how that substantiates a NOTHERE block. Their approach may be abrasive and inappropriate, but that does not mean they are not trying to help build an encyclopedia. As for overturning the block, I lean towards unblocking per GorillaWarfare, but given the WP:NPA issue understand why a definite block of a month or two may be reasonable. — Wug·a·po·des 22:51, 3 July 2020 (UTC)
- I have struckthrough my decline for their unblock appeal, per my discussion with GorillaWarfare above. The request should be considered re-opened. El_C 23:12, 3 July 2020 (UTC)
- Block was warranted. Indef was too much. Unblock with mentorship was a good move. I'm late to this, but as an admin who was responding yesterday and trying to de-escalate the situation, I wanted to chime in. I think Levivich matches my view best. 3nk1namshub was being disruptive and resumed doing so less than 2 hours after the ANI was closed for the second time. For that, a block was warranted. The user's (justified) anger was overriding others' attempts to help. As someone the Signpost's bullshit directly relates to, I understand the anger over it. Despite "no cool down blocks", I'd say one was warranted here (IAR) given the info 3nk1namshub provided. All said, the unblock seems reasonable and I hope mentorship is successful. 3nk1namshub, FWIW, i'm happy to offer my view and input as a non-binary admin should you wish to hear it. EvergreenFir (talk) 05:27, 4 July 2020 (UTC)
- EvergreenFir, What you just said :-) Guy (help!) 10:11, 4 July 2020 (UTC)
Unblocked
Given the consent of Guy and El C and the general thrust of this thread I didn't see a reason to leave this user blocked any longer and so I have unblocked them. Best, Barkeep49 (talk) 23:19, 3 July 2020 (UTC)
- I'm good with that, Barkeep49. El_C 23:22, 3 July 2020 (UTC)
- Reading this back, certain sections seem confrontational. I apologize for them, as that is certainly not my intent. I'm really not good with words. I hope you'll understand, thank you. 3nk1namshub (they/them) (talk) 03:16, 4 July 2020 (UTC)
- I'd like to thank everyone here for speaking their mind. Whether or not they voted to endorse or oppose, I think everyone here made some very good points that I will certainly be taking into account in the future. I would be more than happy to have GorillaWarfare as a mentor. I haven't interacted much with her, but it's clear she's incredibly kind, and has the patience of a saint, in addition to being understanding of queer issues. However, I haven't yet decided on whether I will be returning to Wikipedia. If I were to make that decision now, it would be a very clear no. However, as I intend to take a break from Wikipedia anyway, I don't want to make any hasty decisions.
- Before I go, I'd just like to say that I feel this thread has proven my point exactly. While a vast majority of the points brought up are perfectly fine, some of them have speculated on completely unrelated issues about me. My mental health should not come into play here. My autism should not come into play here. One user claimed I was "looking for an argument" when politely asking an editor about the hategroup dogwhistle on their user page. If polite questions about TERFy dogwhistles are looking for an argument, why are TERFy dogwhistles not?
- Additionally, throughout this whole thing I've had several editors acknowledge the issues of transphobia on Wikipedia, and claim that my frustration is justified. Several people have asked me to stay to try and make Wikipedia more welcoming for queer people, but I'm really not sure that's do-able. You cannot ask trans people to help fix your mistakes, refuse to listen to us, and then give a topic ban for trans issues when we get angry. It really seems like what's wanted is trans people who accept the status quo, not trans people who want to fix your mistakes since you will not. And before anyone says anything, yes, I am aware I am not topic banned; it's been mentioned at least once though.
- Wikipedia isn't just passively hostile to trans people though, it's actively hostile. Even ignoring that article of The Signpost, user pages are seemingly free to contain whatever, including TERF dogwhistles, and "beliefs" about the English language that are demonstrably false and intended to dehumanize trans people. I will be more than happy to provide examples if asked. I've also seen someone in this thread tokenize trans people's opinions on the article from The Signpost (although this may just be a misinterpretation on my end). @JzG: I apologize for pinging you directly, but I would be more than willing to show you why Wikipedia isn't actually that good at ridding itself of transphobes.
- I'm aware this is not helping the case about me being an RGW SPA, but I think it's important to at least try and make you all aware of the issues here. I don't like to assume identities, but I think it's a pretty safe bet that most of the people in this thread are cis (I'm aware not all of the people are, however), and I'll hope you'll be at least a bit open-minded to what I'm saying here. Being trans brings a completely different life experience, and cis people are (in my experience) unable to accurately put themselves in our places without a trans person trying to explain detail what things are like. There's a reason that the vast majority of trans people off Wikipedia do not like this place or its editors, and whether or not I return, I'd appreciate it if everyone here attempted to ask themselves why that is (hint: the answer is not because we're sensitive snowflakes who want to censor history).
- I'm going to monitor this thread, but I won't be responding unless someone asks for clarification on something. If you would like to chat about the things I've said here, my Freenode nick is enki_nam_shub (I've talked to several editors on Freenode under a different nick in the past. However, due to some opsec issues, this is a long overdue nick change, and I will be happy to prove that both nicks are me if you have any concerns).
- Again, thank you all, especially the people who supported the block. You've all given me a great deal to think about and made fantastic points. Whether or not I return, this has been a learning experience. It certainly could've happened in a much better way, but in a strange way, I think this has been good for me. 3nk1namshub (they/them) (talk) 03:13, 4 July 2020 (UTC)
- Thanks for sharing your thoughts, 3nk1namshub. Good luck with your future edits. El_C 03:19, 4 July 2020 (UTC)
- Sorry, one last thing: I would really, really appreciate it if editors did not use transphobic slurs in this thread, thanks. Throwing transphobic slurs around does not help the case that you're actually not a transphobe. 3nk1namshub (they/them) (talk) 03:29, 4 July 2020 (UTC)
- @3nk1namshub: Note that I have also offered mentorship, which can be in addition to GW. I do recommend you accept GW's offer though, she's one of the best you can ask for.--Jasper Deng (talk) 04:49, 4 July 2020 (UTC)
- Barkeep49, thank you Guy (help!) 10:11, 4 July 2020 (UTC)
- @3nk1namshub: Thank you for coming here and sharing your thoughts, which I think we would all do well to read and reflect upon. I understand entirely that you do not wish to immediately return to editing, and are unsure if you ever will. If you do decide to, and I hope you will, please feel free to either leave a message on my talk page or contact me via email (Special:EmailUser/GorillaWarfare or gorillawarfarewikipedia@gmail.com) and I will happily work with you to try to ensure your next foray into editing is a pleasant one. It seems we may have some overlap in our editing interests, so perhaps we could collaborate on an article sometime. GorillaWarfare (talk) 16:40, 4 July 2020 (UTC)
- I wanted to add a comment based on Nosebagbear's modified indef above. For a while I've advocated for what I've called "indef-lite". The basic idea is the indef has no minimum time until appeal and the appeal doesn't need to be anything too big. In short the blocks are to protect wikipedia, not punish. Rather than blocking for say 1-week we block for a relatively minor thing, we simply block until the editor acknowledges the issue and agrees not to do it again. At that point the block is lifted. It doesn't let them just "wait it out" and it does force them to at least articulate what others were upset about. However, if they come to that realization in just 12 hours, well that would mean the rest of the block, be it 1 week, 1 month or the typical 6 months until an indef appeal is punitive. Having read the original ANI and this follow up regarding the editor in question I think the decision to lift the indef with conditions was the right one. What the community actually implemented was similar to my "indef-lite" idea. I'm mentioning this here to put the idea in people's minds in a case where I'm totally uninvolved. Springee (talk) 11:33, 4 July 2020 (UTC)
- I think there should be a minimum time before 'acknowledgement' at least. One doesn't often come to a realisation and change within 12 hours of being blocked, even if one thinks they 'get it' imo. It just takes time. But my thought is perhaps counter-productive, kinda like what was said at the Kiev-Kyiv RM yesterday: if you set a minimum duration of block/moratorium/whatever, the date that duration ends will probably be the date of appeal. Slightly different for blocks because if it's a reasonable duration (a few weeks, a month) it's likely it won't be appealed unless the person really wants to come back, and hopefully (probably?) it's for good reasons this time. And the standard offer of 6 months, while I'm aware it's only a guide, is quite long imo. ProcrastinatingReader (talk) 13:02, 4 July 2020 (UTC)
- @Springee: that's something we do already: with indefinite blocks, which seems to work fine. ——Serial # 11:42, 4 July 2020 (UTC)
- In the past I've received pushback when I've suggested similar blocks which is why I've mentioned it here. I think a different lable vs "indef" might be helpful when looking at block logs. I think most people see "indef" and assume the crime was a big one. As I proposed this I would suggest it's not meant to be a "last resort" sort of block and I wouldn't want it read that way. Anyway, even if it's not formalized it's good to know it was happening more in practice than I was aware. Springee (talk) 11:55, 4 July 2020 (UTC)
- @Springee: - possibly, we obviously have "soft blocks" which are usually for non-bad incidents, but also include things like legal threats, but are purely contingent on the blockee's actions. I wouldn't be against a more standard term on block logs for where it's specifically felt that waiting for the SO is genuinely felt as not needed (rather than just an occasional option). Further discussion probably warrants at least its own sub-section, if not a distinct discussion on ideas or with interested individuals. Nosebagbear (talk) 13:12, 4 July 2020 (UTC)
- In the past I've received pushback when I've suggested similar blocks which is why I've mentioned it here. I think a different lable vs "indef" might be helpful when looking at block logs. I think most people see "indef" and assume the crime was a big one. As I proposed this I would suggest it's not meant to be a "last resort" sort of block and I wouldn't want it read that way. Anyway, even if it's not formalized it's good to know it was happening more in practice than I was aware. Springee (talk) 11:55, 4 July 2020 (UTC)
Image competition?
- Joy Ayara (talk · contribs · deleted contribs · logs · filter log · block user · block log)
I noticed this user adding very large amounts of images to articles, almost all of which were poorly formatted without captions, at high rates of speed, with an edit summary including "#wpwp #wpwpng". After asking the user (see this thread on their talk page) and some asking around, I found out that this is apparently related to a contest at meta: m:Wikipedia Pages Wanting Photos. There are apparently cash prizes for quantity of images added, with very poorly spelled out rules. This seems like a pretty terrible idea just begging for low-quality dumping of images into articles without understanding how to do so correctly or appropriately. I don't know how widespread the problem is or if it's worth setting up an edit filter, but others may want to be aware of this. –Deacon Vorbis (carbon • videos) 14:03, 3 July 2020 (UTC)
- There's a whole bunch of them doing it. Thought it might have been a sock-farm at first, but I guess a competition for doing it sounds more likely. Érico (talk · contribs · deleted contribs · logs · filter log · block user · block log) is another one. There have been others on my watchlist in the last 48hrs or so. Lugnuts Fire Walk with Me 14:13, 3 July 2020 (UTC)
- It's a bit of a pain, you'd think they would at least add a guideline on the quality of images? Completely random images and unnecessary ones are being added to bring up the count. I personally agree with Deacon Vorbis, it is quite a terrible idea. I suggest perhaps suspending the competition until some proper rules about the quality and type of images that can be added are created, as well as saying that poor and low-quality images will not be counted into the competition. — Yours, Berrely • Talk∕Contribs 14:17, 3 July 2020 (UTC)
- I've also noticed this on my watched pages, especially as non-free images are being uploaded. Here is another uploader: Eluwa Stephanie (talk · contribs · deleted contribs · logs · filter log · block user · block log). Both the edit filter and suspending the competition sound like good ideas. Thanks, Yoninah (talk) 14:20, 3 July 2020 (UTC)
- Add edit filter blocking those hashtags sounds like it could be urgency. In the meantime, how does one get a meta-organised competition to stop? It's outrageous that there was no notice, or warning, here. Pinging User:T Cells who, while inactive here, seems to have had a role in its organisation. ——Serial # 14:23, 3 July 2020 (UTC)
- And there you have it. Turns out that T-cells is none other than User:Wikicology, whom some might remember as frequenting these parts. Specifically, this board. ——Serial # 14:24, 3 July 2020 (UTC)
- @Serial Number 54129:, I've put a notice on Meta, they seem to be quite active there. — Yours, Berrely • Talk∕Contribs 14:26, 3 July 2020 (UTC)
- And there you have it. Turns out that T-cells is none other than User:Wikicology, whom some might remember as frequenting these parts. Specifically, this board. ——Serial # 14:24, 3 July 2020 (UTC)
- Add edit filter blocking those hashtags sounds like it could be urgency. In the meantime, how does one get a meta-organised competition to stop? It's outrageous that there was no notice, or warning, here. Pinging User:T Cells who, while inactive here, seems to have had a role in its organisation. ——Serial # 14:23, 3 July 2020 (UTC)
- I've also noticed this on my watched pages, especially as non-free images are being uploaded. Here is another uploader: Eluwa Stephanie (talk · contribs · deleted contribs · logs · filter log · block user · block log). Both the edit filter and suspending the competition sound like good ideas. Thanks, Yoninah (talk) 14:20, 3 July 2020 (UTC)
- It's a bit of a pain, you'd think they would at least add a guideline on the quality of images? Completely random images and unnecessary ones are being added to bring up the count. I personally agree with Deacon Vorbis, it is quite a terrible idea. I suggest perhaps suspending the competition until some proper rules about the quality and type of images that can be added are created, as well as saying that poor and low-quality images will not be counted into the competition. — Yours, Berrely • Talk∕Contribs 14:17, 3 July 2020 (UTC)
Cheers Berrely, I meant to but got distracted by the WC saga...again :) ——Serial # 14:28, 3 July 2020 (UTC)
- I thought Wikicology was already site banned? LSGH (talk) (contributions) 14:33, 3 July 2020 (UTC)
- Oh dear. This edit summary has been showing up at RC all day. I do not know if the most recent site banner has indirectly led this group of accounts to upload images. I checked a few of those, and they could appear to be of less than ideal quality. LSGH (talk) (contributions) 14:33, 3 July 2020 (UTC)
- Sock-farm? Lol, no. It's a annual campaign that occurs on all wikis. First, the images that I add to the articles are adequate. Second, as sysop at Commons I know the copyright rules very well. Anyway, If adding appropriate photos to articles is a problem here, it certainly won't be for me, because in hundreds of other wikis this work will be welcomed. Regards, Érico (talk) 14:34, 3 July 2020 (UTC)
- This is some of the poorest content organisation I've seen, I mean, what did they think what did they think was going to happen? This was literally begging to occur, giving a cash prize to add any images to a site with 6 million articles that anyone can edit — Yours, Berrely • Talk∕Contribs 14:39, 3 July 2020 (UTC)
- Apparently, the account Joy Ayara was created two years ago, but began editing only two days ago. It would be quite unusual to participate in the campaign at such an unusually fast edit rate and suspicious manner of editing. Could there be other sleeping socks around? LSGH (talk) (contributions) 14:41, 3 July 2020 (UTC)
- @Érico: are you saying that these additions will be welcomed? Irrelevant and useless images that offer no use to the reader? — Yours, Berrely • Talk∕Contribs 14:43, 3 July 2020 (UTC)
- I definitely didn't say that. My actual quote: the images that I add to the articles are adequate [...] in hundreds of other wikis this work will be welcomed. I am not referring to other participants, but to me, because I was mentioned above (by user Lugnuts). Érico (talk) 14:45, 3 July 2020 (UTC)
- @Érico: are you saying that these additions will be welcomed? Irrelevant and useless images that offer no use to the reader? — Yours, Berrely • Talk∕Contribs 14:43, 3 July 2020 (UTC)
- Apparently, the account Joy Ayara was created two years ago, but began editing only two days ago. It would be quite unusual to participate in the campaign at such an unusually fast edit rate and suspicious manner of editing. Could there be other sleeping socks around? LSGH (talk) (contributions) 14:41, 3 July 2020 (UTC)
- This is some of the poorest content organisation I've seen, I mean, what did they think what did they think was going to happen? This was literally begging to occur, giving a cash prize to add any images to a site with 6 million articles that anyone can edit — Yours, Berrely • Talk∕Contribs 14:39, 3 July 2020 (UTC)
- Sock-farm? Lol, no. It's a annual campaign that occurs on all wikis. First, the images that I add to the articles are adequate. Second, as sysop at Commons I know the copyright rules very well. Anyway, If adding appropriate photos to articles is a problem here, it certainly won't be for me, because in hundreds of other wikis this work will be welcomed. Regards, Érico (talk) 14:34, 3 July 2020 (UTC)
- Oh dear. This edit summary has been showing up at RC all day. I do not know if the most recent site banner has indirectly led this group of accounts to upload images. I checked a few of those, and they could appear to be of less than ideal quality. LSGH (talk) (contributions) 14:33, 3 July 2020 (UTC)
If you search mainspace for #WPWP #WPWPUIL
there are loads of examples of not just crappy images, but the hashtag being inserted into the article itself. Ffs... ——Serial # 14:50, 3 July 2020 (UTC)
- Here is another uploader: Hormorkunmy (talk · contribs · deleted contribs · logs · filter log · block user · block log). Again, the account was created in 2018 but edited barely anything until two days ago. LSGH (talk) (contributions) 14:51, 3 July 2020 (UTC)
- Before people rush to judge the whole competition, how about some data? The spot check I just did returned 9/10 productive additions. I don't doubt there are lousy images being added and people trying to game the system for prizes, just as there are people who game everything about Wikipedia and add lousy content all the time. Every competition we do, edit-a-thon, upload drive, etc. results in some amount of undesirable content ... and a lot of desirable content. it's when it's more trouble than it's worth that it merits some sort of intervention. And for that I'd expect to see more than a handful of anecdotes. — Rhododendrites talk \\ 14:55, 3 July 2020 (UTC)
- There are likely hundreds of accounts that have been created just to enter this. Deacon Vorbis highlighted this, where they have literally just taken a photo from the lead and put it in the infobox. This is inevitable, if there is a prize, people will willingly put useless content into articles to get it. — Yours, Berrely • Talk∕Contribs 14:56, 3 July 2020 (UTC)
- @Rhododendrites: most contributors are probably submitting and adding good photos, but 9/10 is still a lot, just look at the damage 1 person has done. Unless some proper guidelines are made, this will keep happening. — Yours, Berrely • Talk∕Contribs 14:58, 3 July 2020 (UTC)
likely hundreds of accounts that have been created just to enter this
- sooo a competition brought hundreds of new contributors, most of whom are adding content productively. This is... not a problem. FWIW I don't disagree with having clearer guidelines. — Rhododendrites talk \\ 15:00, 3 July 2020 (UTC)
- @Rhododendrites: most contributors are probably submitting and adding good photos, but 9/10 is still a lot, just look at the damage 1 person has done. Unless some proper guidelines are made, this will keep happening. — Yours, Berrely • Talk∕Contribs 14:58, 3 July 2020 (UTC)
- There are likely hundreds of accounts that have been created just to enter this. Deacon Vorbis highlighted this, where they have literally just taken a photo from the lead and put it in the infobox. This is inevitable, if there is a prize, people will willingly put useless content into articles to get it. — Yours, Berrely • Talk∕Contribs 14:56, 3 July 2020 (UTC)
- Before people rush to judge the whole competition, how about some data? The spot check I just did returned 9/10 productive additions. I don't doubt there are lousy images being added and people trying to game the system for prizes, just as there are people who game everything about Wikipedia and add lousy content all the time. Every competition we do, edit-a-thon, upload drive, etc. results in some amount of undesirable content ... and a lot of desirable content. it's when it's more trouble than it's worth that it merits some sort of intervention. And for that I'd expect to see more than a handful of anecdotes. — Rhododendrites talk \\ 14:55, 3 July 2020 (UTC)
Anyways, can we just take a second to acknowledge what @Serial Number 54129: just said? Look at this — Yours, Berrely • Talk∕Contribs 15:02, 3 July 2020 (UTC)
- Apparently, those new users seem to not follow other policies and guidelines regarding the insertion of photos in articles. And many of them came here for only one purpose, which is to win prizes. LSGH (talk) (contributions) 15:08, 3 July 2020 (UTC)
- (edit conflict)And many photos being inserted into infoboxes with the wrong syntax - example Blessatayo (talk · contribs · deleted contribs · logs · filter log · block user · block log). Not a massive issue in terms of visual output but a large job to clear up. I'm not against adding decent images to more article, I'm in favour of it but I wish the competition designers had been clearer about the instructions and communicated that it was going to happen. Nthep (talk) 15:09, 3 July 2020 (UTC)
- You'd think they'd at least drop a note on ANI or something? — Yours, Berrely • Talk∕Contribs 15:11, 3 July 2020 (UTC)
So looking at the most recent activity, we have User:Bukky658 adding hundreds of images with the wrong syntax, and User:Blessatayo doing the same. An edit filter blocking this hashtag seems rather urgent. Fram (talk) 15:37, 3 July 2020 (UTC)
Not sure blocking would help, since they might upload anyway with a different hashtag. Perhaps logging is better?I guess if the hashtag is #WPWP, it would follow they won't mass-upload if they can't use the hashtag. Block/throttle seems fine? ProcrastinatingReader (talk) 15:40, 3 July 2020 (UTC)- Yes, the instructions at the competition explicitly state "Include the hashtag #WPWP in the edit summary of all articles improved with images. Then click on "Publish changes"." so stopping them from using this hashtag would be helpful. Fram (talk) 15:44, 3 July 2020 (UTC)
- Fram, Procrastinating Reader, I will whip one up shortly. GeneralNotability (talk) 15:46, 3 July 2020 (UTC)
- Since the low quality ones tend to be non-confirmed and adding pictures at a rapid speed, I'm thinking perhaps maybe a throttle of more than X per hour from non-confirmed accounts would get rid of the crap from the contest, whilst making it possible for those that perhaps know what they're doing to contribute? ProcrastinatingReader (talk) 15:50, 3 July 2020 (UTC)
- Tracking as 1073 (hist · log) (log-only mode for now), if someone wants to whip up a variant of MediaWiki:Abusefilter-disallowed for this filter I'll put it into play as soon as I'm satisfied with the filter's performance. GeneralNotability (talk) 15:54, 3 July 2020 (UTC)
- (edit conflict) The problem is, alongside edit summaries, some users have been inserting the hashtag into articles and talk pages as well, so it might be good to make sure the edit filter accepts those namespaces. — Yours, Berrely • Talk∕Contribs 15:55, 3 July 2020 (UTC)
- I'm also happy to just have it as a warning - "hey, you, welcome to Wikipedia, you appear to be participating in whatever competition, please keep in mind that images should be relevant, yadda yadda yadda" GeneralNotability (talk) 15:55, 3 July 2020 (UTC)
- I guess see how it goes in log? If, indeed, the majority of contributions are positive and it's just a few users with a large number of edits between them making problematic edits, they the problematic bunch can just be handled manually. If it's a lot of different users, then perhaps move to warn / throttle. ProcrastinatingReader (talk) 16:00, 3 July 2020 (UTC)
- @GeneralNotability: If I read the filter correctly, that only catches edits where the hashtag uses uppercase letters ('#WPWP' not '#wpwp'). Lowercase versions should probably be included as well. – Majavah talk · edits 07:33, 4 July 2020 (UTC)
- Majavah, I'll double check, but I thought I used irlike (case-insensitive regex match). GeneralNotability (talk) 13:35, 4 July 2020 (UTC)
- Fram, Procrastinating Reader, I will whip one up shortly. GeneralNotability (talk) 15:46, 3 July 2020 (UTC)
- Yes, the instructions at the competition explicitly state "Include the hashtag #WPWP in the edit summary of all articles improved with images. Then click on "Publish changes"." so stopping them from using this hashtag would be helpful. Fram (talk) 15:44, 3 July 2020 (UTC)
- No, having people add relevant images to an article but using the wrong syntax is not reason to shut down the initiative they're participating in. Syntax issues can be fixed with AWB. Finding images to use in an article and adding them to the best of your ability cannot. The only actual problems I've seen here are (a) someone who added duplicate images to articles -- now blocked, and (b) someone adding "#WPWP" to article text -- now blocked. Oppose filtering out the competition without more evidence of net harm. — Rhododendrites talk \\ 15:53, 3 July 2020 (UTC)
- I left a msg on the talk page for Bukky658 asking them to use the correct infobox image syntax (they were also putting images into
|image_flag=
that aren't flags). The last half-dozen edits were to add images AFTER the infobox. MB 15:55, 3 July 2020 (UTC)- @Rhododendrites: is right, this isn't like the TikTok swarming, because there are actually people who are contributing with good images. This hole is proving quite hard to get out off. — Yours, Berrely • Talk∕Contribs 15:56, 3 July 2020 (UTC)
- I wonder why the mechanics at Meta do not say anything about the eligibility of participants. For example, the user has been around for a few months and has made at least a few hundred edits already. It's probably a reason why we are seeing an influx of new users whose edits are mostly related to this contest. For some comparison, ArbCom elections have eligibility criteria. LSGH (talk) (contributions) 16:03, 3 July 2020 (UTC)
- LSGH, we're not really electing anything. It's a contest to encourage a drive to create content. Or rather, make use of already-created content. There's no eligibility criteria to edit Wikipedia. The issue here is that some people only see the cash bounty and run in to add pictures for the money, rather than spend any time familiarising with the guidelines first. But any attempt to add a guideline on activity prior to the contest date would just limit the number of participants, including the good ones. I think it's a slightly iffier problem than it appears at first glance. ProcrastinatingReader (talk) 16:14, 3 July 2020 (UTC)
- Yes, that cash prize, and then some would just run away with it rather than stay around and contribute productively elsewhere. Maybe the quantity criteria there is being taken for granted in order to just add photos (whether they are helpful or not) without even having experienced dealing with them before the contest. That probably shows why they may be placed improperly or are not even given proper captions, which other more experienced editors would need to fix. LSGH (talk) (contributions) 16:26, 3 July 2020 (UTC)
- Adding on, often with campaigns like this, one of the goals is to bring in new editors (for example, for Wiki Loves Monuments on the Commons, in many nations the majority of participants are brand new to the project despite the relative complexity of uploading images + dealing with copyright/licensing). Contests like WPWP that involve simple editing are a nice way to engage new editors, but yes, you do end up with some who don't grasp the rules and make poor edits. Contests like Wiki Loves Monuments, Wiki Loves Earth, etc. on Commons result in the upload of hundreds (probably thousands?) of copyvios and out-of-scope images, but it's taken on the chin and dealt with on a per-file/per-user basis since the net positive is considered worth it. Spot-checking through recent hashtag contributions, I think the vast majority of contributions are positive, and that shutting it down is an overreaction. Adding a tag for #wpwp edits would be helpful for patrolling these edits. I think GeneralNotability's idea above to have an edit filter warning with advice for new users is a good one as well. For WPWP, I think a good path forward would be to expand the "How to participate" rule set to include more explicit notes on image relevant and quality, requiring captions for all image additions, and disqualification criteria (i.e. adding multiple inadequate images may result in the user being disqualified). ~SuperHamster Talk Contribs 16:47, 3 July 2020 (UTC)
- Yes, that cash prize, and then some would just run away with it rather than stay around and contribute productively elsewhere. Maybe the quantity criteria there is being taken for granted in order to just add photos (whether they are helpful or not) without even having experienced dealing with them before the contest. That probably shows why they may be placed improperly or are not even given proper captions, which other more experienced editors would need to fix. LSGH (talk) (contributions) 16:26, 3 July 2020 (UTC)
- LSGH, we're not really electing anything. It's a contest to encourage a drive to create content. Or rather, make use of already-created content. There's no eligibility criteria to edit Wikipedia. The issue here is that some people only see the cash bounty and run in to add pictures for the money, rather than spend any time familiarising with the guidelines first. But any attempt to add a guideline on activity prior to the contest date would just limit the number of participants, including the good ones. I think it's a slightly iffier problem than it appears at first glance. ProcrastinatingReader (talk) 16:14, 3 July 2020 (UTC)
- I wonder why the mechanics at Meta do not say anything about the eligibility of participants. For example, the user has been around for a few months and has made at least a few hundred edits already. It's probably a reason why we are seeing an influx of new users whose edits are mostly related to this contest. For some comparison, ArbCom elections have eligibility criteria. LSGH (talk) (contributions) 16:03, 3 July 2020 (UTC)
- @Rhododendrites: is right, this isn't like the TikTok swarming, because there are actually people who are contributing with good images. This hole is proving quite hard to get out off. — Yours, Berrely • Talk∕Contribs 15:56, 3 July 2020 (UTC)
- I left a msg on the talk page for Bukky658 asking them to use the correct infobox image syntax (they were also putting images into
- By the way, for anyone curious about the significance of the "NG" in the "#wpwpng". It's the 2 letter country code for Nigeria, and they have extra prizes on top of the general contest prizes. ProcrastinatingReader (talk) 16:23, 3 July 2020 (UTC)
- Hardly surprising as the organiser founded Wikimedia Nigeria. — Yours, Berrely • Talk∕Contribs 16:31, 3 July 2020 (UTC)
- Ugh - just saw this. I'm in the process of one-by-one rolling back all the images additions made by Godstime Elijah - several dozen just rammed in a) apparently randomly chosen by keyword, b) without regard to quality, c) without caption, at d) unsuitable positions in the article (just pasted at very top). Often duplicates of already present images, often bad quality, often almost unrelated. The hashtag is lacking, but I'm pretty sure this is the impetus. That shit ain't helpful. If an admin wants to save my wrist and do a mass rollback, I wouldn't say no. --Elmidae (talk · contribs) 16:43, 3 July 2020 (UTC)
- ...and since they apparently don't notice what's going on and are keeping at it, it's like shoveling back the tide. Holding for now pending application of brakes / heavier machinery. --Elmidae (talk · contribs) 16:47, 3 July 2020 (UTC)
- Elmidae, I've pblocked them from mainspace. GeneralNotability (talk) 16:50, 3 July 2020 (UTC)
- @GeneralNotability: Thanks. Would you agree this is best rolled back en masse? From my current sample 90% are in the wrong location, about half are unsuitable for the topic, about one third are duplicates, another third of too low quality to use. I think that suggests a complete do-over rather than picking out the few possibly-suitable-after-cleanup ones. --Elmidae (talk · contribs) 16:58, 3 July 2020 (UTC)
- Elmidae, I'd rather a different administrator make that call, I'm not certain enough in either direction. GeneralNotability (talk) 18:37, 3 July 2020 (UTC)
- I would !vote that they be rolled back. User:Ababio70's additions are of similarly low value. -22:37, 3 July 2020 (UTC)
- I've gone through and removed the obvious duds. Some have been vetted, captioned and repositioned by others, using three times the effort this editor spent in horking them into the articles in the first place :/ --Elmidae (talk · contribs) 19:05, 4 July 2020 (UTC)
- Elmidae, I'd rather a different administrator make that call, I'm not certain enough in either direction. GeneralNotability (talk) 18:37, 3 July 2020 (UTC)
- @GeneralNotability: Thanks. Would you agree this is best rolled back en masse? From my current sample 90% are in the wrong location, about half are unsuitable for the topic, about one third are duplicates, another third of too low quality to use. I think that suggests a complete do-over rather than picking out the few possibly-suitable-after-cleanup ones. --Elmidae (talk · contribs) 16:58, 3 July 2020 (UTC)
- Elmidae, I've pblocked them from mainspace. GeneralNotability (talk) 16:50, 3 July 2020 (UTC)
- ...and since they apparently don't notice what's going on and are keeping at it, it's like shoveling back the tide. Holding for now pending application of brakes / heavier machinery. --Elmidae (talk · contribs) 16:47, 3 July 2020 (UTC)
@GeneralNotability, Elmidae, ProcrastinatingReader, Berrely, and Fram: (and others here) This is an international contest which was prepared in total good-faith and with the best of intentions to help improve Wikipedia articles with images mainly from the other contests, like Wiki Loves Monuments, Wiki Loves Africa and Wiki Loves Earth. I understand that some of the participants are doing significant damage adding irrelevant and out of place images to the articles, but please, try to refrain attacking the organizers, including User:T Cells, which is a much respected member of the Wikimedia community except on this Wikipedia, where he was banned for a very (write random insult here) reason years ago, as some of you certainly know and remember - and that's why he can't come himself here and explain what's going on. I also can't understand why ppl are mentioning Nigeria at all in this discussion. Ok, there's a problem with the contest. I'm part of the team that is supporting and organizing the contest. If the decision to ban the hashtag (and, therefore, the contest) from here is not definitive, I'll do my best to help solving the issues that are happening. Please, let's try to handle this with the proverbial wiki cordiality and AGF. I believe the contest has an excellent potential of being a very positive input for Wikipedia, and nobody wants that damage being done to the articles. Can we possibly work out a solution together? Darwin Ahoy! 17:21, 3 July 2020 (UTC)
- @DarwIn: If I may refresh your memory—and without inserting any random insults—Wikicology was banned for, among other things: socking, undeclared autobiographical editing, self-promotion, introducing errors to articles, introducing copyright-violating text and images, and frankly lying with regard his own credentials. An excellent CV for a "much respected" member of the Wikimedia community. Note, I hold him no grudge: but it's an insult to this project to dismiss the evidence as "random insults". ——Serial # 17:59, 3 July 2020 (UTC)
- @Serial Number 54129: I know the process, I've checked it recently, and my own POV is that it was grossly exaggerated (that's why the "random insult" thing), and that some errors were done, but T Cells has improved incredibly since then. But all that is not ontopic here, since it's not related in the least with the current situation. I hope we can work out some kind of solution here. Darwin Ahoy! 15:52, 4 July 2020 (UTC)
- @DarwIn: If I may refresh your memory—and without inserting any random insults—Wikicology was banned for, among other things: socking, undeclared autobiographical editing, self-promotion, introducing errors to articles, introducing copyright-violating text and images, and frankly lying with regard his own credentials. An excellent CV for a "much respected" member of the Wikimedia community. Note, I hold him no grudge: but it's an insult to this project to dismiss the evidence as "random insults". ——Serial # 17:59, 3 July 2020 (UTC)
- DarwIn, I can understand it was in good faith, and I hold much respect for T Cells, as of course there are many Wikipedia articles with images available but not inserted. I guess some say, "It was a good idea, with semi-poor execution", I think maybe if the rules had been made clearer this could have been heavily prevented, but I'm not one to say. — Yours, Berrely • Talk∕Contribs 17:27, 3 July 2020 (UTC)
- Also, GeneralNotability, here is an edit filter notice if needed: User:Berrely/Photos — Yours, Berrely • Talk∕Contribs 17:29, 3 July 2020 (UTC)
- DarwIn, just to be clear, my comment wasn't anything to do with T Cells or me making any implication of impropriety. I was just curious what the "ng" meant, since it isn't listed on the main contest page and most edits aren't including #wpwpng, only #wpwp. I did some digging, and saw that there's a simultaneous Nigeria contest going on which requires "#wpwp #wpwpng" hence I made the statement linking to that contest page, which is this, in case anyone else is curious what the ng means, or if it might affect what we put in the edit filter etc. I support things which gets more editors into Wikipedia. ProcrastinatingReader (talk) 17:44, 3 July 2020 (UTC)
- I've messaged WPWP organizers proposing to add the following to the rules:
- All image additions must include a caption that describes what the image is of.
- Images should be placed in the article in a spot where it is relevant and helpful for the reader to understand the subject
- Users who repeatedly violate these guidelines may be disqualified.
- Rules won't prevent poor edits 100% (there are always those who won't read them), but I think this can help increase contribution quality and hopefully serve as one of the solutions coming out of this discussion. ~SuperHamster Talk Contribs 17:43, 3 July 2020 (UTC)
- Cash prizes for editing? Is that a regular WMF thing or is this new? Levivich [dubious – discuss] 17:41, 3 July 2020 (UTC)
- DarwIn: For future reference, if you're going to be running these sorts of competitions with hashtags and contribution tracking, it would probably help if someone dropped a note at WP:EFN about it - we can literally add a filter to tag these edits based on the hashtag, so for example there could be a "2020 WPWP competition" tag. That would help both organizers (you can filter a user's contributions based on the tag we apply) and enwiki patrollers (so that people know to watch that specific tag). It also encourages the new editors to actually use the hashtag (a few haven't been great about that) - if they don't use the hashtag, it doesn't show up when you search for the tag, and they don't get credit. GeneralNotability (talk) 20:02, 4 July 2020 (UTC)
Comment: Saying that this campaign was "organized" is an insult to the world organize. -Jason A. Quest (talk) 19:47, 3 July 2020 (UTC)
- I participate in this. I have to say the instruction is unclear and tracking results likewise is opaque. But we will always run into people who don't understand instructions no matter what kind of events we do (editathon, GAN backlog elimination drive, Wiki Loves Earth, Art & Feminish, Wiki Ed etc.), whether it be writing an article about someone who doesn't meet notability guidelines, doing poor but speedy reviews, poor referencing, close paraphrasing, uploading non-free content as "free" content, not respecting NPOV. My point is, people have been adding crap to Wikipedia with or without any of these events. By Rhododendrites's account, most of the contribution are productive so the campaign so far as a whole should be viewed as net-positive. OhanaUnitedTalk page 06:30, 4 July 2020 (UTC)
- OhanaUnited, most are positive, but the 1/10 of people who are adding crap photos that are unrelated and random are still a lot. The problem with the edit filter that GeneralNotability set up is that there are genuinely some people who are adding useful photos in short periods of time. Take a look. I propose putting starting by putting the edit filter warning, that should deter users with unconstructive edits (something like this) and if that doesn't work just blocking edits with the hashtag altogether. — Yours, Berrely • Talk∕Contribs 08:44, 4 July 2020 (UTC)
- I found SuperHamster suggestions very good. I would perhaps even make them a bit more draconian, and include a clear rule that any reverted action would be disqualified, and a large number of reverted actions could imply the whole disqualification of the participant. I hope monitoring the actions and warning when necessary as Berrely suggest is enough to keep it going. Darwin Ahoy! 16:00, 4 July 2020 (UTC)
- OhanaUnited, most are positive, but the 1/10 of people who are adding crap photos that are unrelated and random are still a lot. The problem with the edit filter that GeneralNotability set up is that there are genuinely some people who are adding useful photos in short periods of time. Take a look. I propose putting starting by putting the edit filter warning, that should deter users with unconstructive edits (something like this) and if that doesn't work just blocking edits with the hashtag altogether. — Yours, Berrely • Talk∕Contribs 08:44, 4 July 2020 (UTC)
- Greeting, I am also involved in this competition. First of all I understand the validity of the concerns and frustration of the AV users. From what I understand, the WPWP campaign rules clearly say images must be constructive and proper captions should be added. The hashtag is to allow easier tracking of the edits under this campaign. From my point of view, can we just block the users who violate the standard EN WIKI guidelines? If someone is not adding proper images, we can warn them first, and block them immediately if they ignore the warnings. Even if they created new account their contributions will be lost (not counted), so it won't be a viable option for them. Also, I feel that in this thread some experienced users are aggressive and not very polite. While I understand the frustration, I request everyone to calm down and see the bright side of this campaign. Although I was a bit disappointed by the 'aggression', but we are human. I request everyone to understand the good faith and to solve this issue without getting enraged or jeopardizing the campaign. Also, isn't 1 out of 10 edit on EN WIKI is damaging already, with or without a campaign going on? I hope I'm not offending anyone, thanks for understanding. --Navinsingh133 (talk) 14:49, 5 July 2020 (UTC)
- Navinsingh133, you have made valid points, but it is a little bit hard to not get frustrated at this campaign — something like this could have easily been predicted occurring. — Yours, Berrely • Talk∕Contribs 16:21, 5 July 2020 (UTC)
- The idea behind this competition is a good one - who could be against improving Wikipedia with images? - but the execution is very poor. When there are significant cash prizes at stake (in many parts of the world $500 is several months' earnings for someone not considered poor) there need to be much clearer rules, and they need to be clear before the competition starts. For example most of the prizes are for "unique Wikipedia articles improved with" something, but I can see no obvious definition of "improved with", or indication of who decides that. In such circumstances it is natural than people will go for objective quantity rather than subjective quality. Phil Bridger (talk) 16:46, 5 July 2020 (UTC)
- While I understand that $500 is a significant amount of money -- it is to me as well -- I can't say that I'm thrilled at the idea of being paid for editing Wikipedia, as it seems antithetical to the Wikipedia ethos. Are there other projects or competitions in which monetary prizes are offered? What does that do to the volunteer nature of editing? Adding images to articles is not -- despite the fact that I often do it -- the most important need around here that it alone should get compensated. How about paying our admins for the b.s. they have to put up with? Or paying editors who have to struggle through the usual mud-throwing of editing contentious subjects? Maybe deletionists should put up prizes for those who delete the most material from the encyclopedia in any month, and inclusionists do the same for those who save articles from being deleted at AfD?No, I don't like the idea of cash prizes one little bit, and I'm surprised that the WMF -- so anxious to put its boot into local projects and kick around a little -- allows it. Beyond My Ken (talk) 23:15, 5 July 2020 (UTC)
- @Beyond My Ken: I'm pretty sure they actually don't allow paying for editing, including in the context of contests. (It's in the Grant guidelines, and I think affiliates typically use the same rule.) But, strictly speaking, the prize is a $500 "gift voucher", per m:WPWP. :/ --Yair rand (talk) 00:27, 10 July 2020 (UTC)
- There is no real difference between a gift voucher and cash, the result is the same, payment for editing. Beyond My Ken (talk) 01:10, 10 July 2020 (UTC)
- @Beyond My Ken: It's certainly a lot closer to cash than I'm comfortable with, especially given the amount, but I think we need to make the boundary of "payment for editing" a bit clearer. There have been contests/events in the past with prizes (t-shirts, swag), for the purpose of slightly increasing the enthusiasm of the participating volunteers, while still being clearly not "payment" as we'd normally think of it, as in, people definitely weren't participating just to get the prize. I'm not sure there's anything wrong with that. However, the spectrum from that to, well, $500 gift certificates, is one we probably should have stopped on somewhere along the way. --Yair rand (talk) 01:51, 10 July 2020 (UTC)
- Giving out swag is one thing, cash or cash vouchers is another. Beyond My Ken (talk) 05:15, 10 July 2020 (UTC)
- There is no real difference between a gift voucher and cash, the result is the same, payment for editing. Beyond My Ken (talk) 01:10, 10 July 2020 (UTC)
- While I understand that $500 is a significant amount of money -- it is to me as well -- I can't say that I'm thrilled at the idea of being paid for editing Wikipedia, as it seems antithetical to the Wikipedia ethos. Are there other projects or competitions in which monetary prizes are offered? What does that do to the volunteer nature of editing? Adding images to articles is not -- despite the fact that I often do it -- the most important need around here that it alone should get compensated. How about paying our admins for the b.s. they have to put up with? Or paying editors who have to struggle through the usual mud-throwing of editing contentious subjects? Maybe deletionists should put up prizes for those who delete the most material from the encyclopedia in any month, and inclusionists do the same for those who save articles from being deleted at AfD?No, I don't like the idea of cash prizes one little bit, and I'm surprised that the WMF -- so anxious to put its boot into local projects and kick around a little -- allows it. Beyond My Ken (talk) 23:15, 5 July 2020 (UTC)
Change in blocking policy
As a result of this 3RN report wherein I block an editor for 48 hours for a first time 3RR violation, it has come to my attention that Ritchie333 changed the blocking policy on June 19 to state that partial blocks should be the default for edit warring blocks. Given that the changes were made with very little discussion, I'm noting the recent policy change here as the change effects most active admins.-- Jezebel's Ponyobons mots 21:02, 6 July 2020 (UTC)
- Not quite how I read that, and I would note that written policy follows practice, not the other way around. Dennis Brown - 2¢ 21:06, 6 July 2020 (UTC)
- Good call, Ritchie. I've adopted that modality pretty much since the implementation of partial blocks. It is incredibly useful in curtailing edit warring, with little downside. I'm still surprised when I see AN3 reports closed with a sitewide block. What is that now — a punishment? El_C 21:10, 6 July 2020 (UTC)
- It seems like the most relevant change here is
Edit warring, especially breaches of the three-revert rule often result in a block from the pages the user is disrupting, or, if required, the entire site.
. I disagree that that instructs "partial blocks should be the default for edit warring blocks", it seems to just say that some admins use them for edit warring. It does seem reasonable to at least consider a partial block when an edit warring issue arises, though, I'll keep that in mind. Still getting used to the whole idea. GorillaWarfare (talk) 21:13, 6 July 2020 (UTC)- Oh, having now read the discussion at ANEW I see why you have said this. I disagree with Ritchie333 that the policy requires us to default to partial blocks—that policy change would require a broader discussion and certainly a notification to admins. GorillaWarfare (talk) 21:15, 6 July 2020 (UTC)
- There was a significant support for allowing the feature. In my specific case, the de facto example I wanted partial blocks was Eric Corbett (talk · contribs), where we could have blocked him for 12 hours on a page he was edit warring on and got a discussion, instead of protecting the page (antagonising other editors) or sitewide blocking him (which made the heavens tremble). Ritchie333 (talk) (cont) 21:20, 6 July 2020 (UTC)
- (edit conflict) Option four (something else). The RfC was to determine whether partial blocks should be enabled, and broadly how they should be applied. Edit warring was certainly discussed as a good candidate for partial blocks, but there was no formal discussion around changing the blocking policy to require partial blocks be the default for edit warring. Like I said, such a policy change would not only need a formal discussion but would also need to be communicated broadly to admins, so it doesn't catch them by surprise like it (sort of) did with Ponyo. GorillaWarfare (talk) 21:27, 6 July 2020 (UTC)
- Weird, this is the second time today someone's changed their comment while I replied but I didn't get an edit conflict. This time I edit conflicted with El C, but your change didn't show up in the EC diff. Anyway, to reply to your changed comment, I have no objection to allowing partial blocks to be used for edit wars, I think that's more than appropriate. My objection is with requiring admins to default to it, for the reasons I've outlined above. GorillaWarfare (talk) 21:31, 6 July 2020 (UTC)
- I'm in the same camp, it is fine to have another tool but we don't need to tell admin which way to block. As I stated early, policy is a reflection of practice, and we need to see how it hammers out now that it is in place, rather than try to dictate to admin why type of block to use. Dennis Brown - 2¢ 01:09, 7 July 2020 (UTC)
- Weird, this is the second time today someone's changed their comment while I replied but I didn't get an edit conflict. This time I edit conflicted with El C, but your change didn't show up in the EC diff. Anyway, to reply to your changed comment, I have no objection to allowing partial blocks to be used for edit wars, I think that's more than appropriate. My objection is with requiring admins to default to it, for the reasons I've outlined above. GorillaWarfare (talk) 21:31, 6 July 2020 (UTC)
- (edit conflict) Option four (something else). The RfC was to determine whether partial blocks should be enabled, and broadly how they should be applied. Edit warring was certainly discussed as a good candidate for partial blocks, but there was no formal discussion around changing the blocking policy to require partial blocks be the default for edit warring. Like I said, such a policy change would not only need a formal discussion but would also need to be communicated broadly to admins, so it doesn't catch them by surprise like it (sort of) did with Ponyo. GorillaWarfare (talk) 21:27, 6 July 2020 (UTC)
- A discussion worth having. Sure, Ponyo was well within their rights to sitewide block, but the user has only edited one article. That's what partial block are for par excellence. El_C 21:24, 6 July 2020 (UTC)
- Indeed. It's not the first time I've questioned why somebody has used sitewide vs. partial blocking; the responses previously have been either "good point, I'll remember that next time" or "yes, this had to be sitewide because of [x]". To be clear, I'm not disputing the block (I think there's a solid case for some sort of block there) or wanting it appealed - I just want to make sure admins are considering the wider range options available to them. If they're getting defensive or think I'm having a go at them, or think their block is bad, they've missed the point I was trying to make. Ritchie333 (talk) (cont) 21:32, 6 July 2020 (UTC)
- (edit conflict) In response to the block at the 3RN report I linked you wrote "According to the policy, Edit warring, especially breaches of the three-revert rule often result in a block from the pages the user is disrupting, or, if required, the entire site. Why was it required?" (all bolding and emphasis yours). You were quoting policy that you, yourself, changed just days before. It's important that admins are at least aware of the changes you made if you will be challenging them on such.-- Jezebel's Ponyobons mots 21:41, 6 July 2020 (UTC)
- I don't think this is on Ponyo for missing the point. Your conversation at ANEW did suggest that admins must default to partial blocks. GorillaWarfare (talk) 21:34, 6 July 2020 (UTC)
- Indeed. It's not the first time I've questioned why somebody has used sitewide vs. partial blocking; the responses previously have been either "good point, I'll remember that next time" or "yes, this had to be sitewide because of [x]". To be clear, I'm not disputing the block (I think there's a solid case for some sort of block there) or wanting it appealed - I just want to make sure admins are considering the wider range options available to them. If they're getting defensive or think I'm having a go at them, or think their block is bad, they've missed the point I was trying to make. Ritchie333 (talk) (cont) 21:32, 6 July 2020 (UTC)
- There was a significant support for allowing the feature. In my specific case, the de facto example I wanted partial blocks was Eric Corbett (talk · contribs), where we could have blocked him for 12 hours on a page he was edit warring on and got a discussion, instead of protecting the page (antagonising other editors) or sitewide blocking him (which made the heavens tremble). Ritchie333 (talk) (cont) 21:20, 6 July 2020 (UTC)
- I've changed this to "Edit warring, especially breaches of the three-revert rule, often results in a block, either from the pages the user is disrupting or from the entire site." SarahSV (talk) 21:30, 6 July 2020 (UTC)
- Makes sense. Partial blocks are an option, but we should apply WP:CLUE. Guy (help!) 23:21, 6 July 2020 (UTC)
- I've raised this issue before at Wikipedia talk:Edit warring/Archives/2020/May#Partial blocks, but it didn't attract much attention. I think we should work towards greater guidance, either to find a default first-offense block scope and duration that should be used absent motivation for the contrary, or to come up with a set of guidelines of when admins should use full blocks vs. partial blocks. Otherwise, we risk the same behavior being subject to either a 24-hour siteblock, 72-block pblock, or whatever the blocking admin's default is. Admin discretion is fine, but basing disciplinary actions solely on the personal preferences of the blocking admin is too arbitrary. Again, I believe that both full and partial blocks continue to have a place in combating edit warring, but there should be a default setting that all admins use for 50%+ of cases. -- King of ♥ ♦ ♣ ♠ 21:56, 6 July 2020 (UTC)
- My gut sense is that sitewide blocks may still be an appropriate course of action for brand-new SPA accounts engaged in edit warring past 3RR (as was the case here), given the high likelihood that the editor may continue their disruption on related or non-mainspace pages. For cases where the editor is less clearly engaging in bad faith or has a history of positive contributions, I do think that partial blocks will generally be the best course of action. signed, Rosguill talk 22:03, 6 July 2020 (UTC)
- Rosguill, I think that would fall more under a WP:DE than an WP:EW block. El_C 22:13, 6 July 2020 (UTC)
- El C, It's at the intersection, no? The offense that clearly licensed the block was a violation of 3RR, but the manner in which 3RR was violated suggests further problems that do fall under the more general category of disruption. signed, Rosguill talk 22:18, 6 July 2020 (UTC)
- I am of the opinion that, in that scenario, DE should take precedence over EW. With DE we want an enhanced restriction (user talk page only, if that), whereas with EW, there's also the article talk page being available, or if not that, different articles, or if not those, even different namespaces. El_C 22:25, 6 July 2020 (UTC)
- El C, It's at the intersection, no? The offense that clearly licensed the block was a violation of 3RR, but the manner in which 3RR was violated suggests further problems that do fall under the more general category of disruption. signed, Rosguill talk 22:18, 6 July 2020 (UTC)
- Rosguill, as above: let's not be prescriptive, we should apply Clue. Guy (help!) 23:22, 6 July 2020 (UTC)
- Rosguill, I think that would fall more under a WP:DE than an WP:EW block. El_C 22:13, 6 July 2020 (UTC)
- There isn't uniform agreement on the usefulness of partial blocks; at least one admin thinks other tools are more effective and won't use them. (Some research and evaluation of their efficacy might help establish community norms more rapidly.) isaacl (talk) 04:18, 7 July 2020 (UTC)
- Since I’ve been mentioned indirectly, I’ll point out that my prediction that partial blocks create controversy when used and vastly expand the power of admins beyond anything any policy before them envisioned has largely been proven true. Basically Ponyo was right here. The full block was justified and a partial block wouldn’t have accomplished anything. I’m probably the loudest voice on this project pointing out that they cause just as much disruption as they prevent, if not more, but there’s a significant minority of us across the projects, including multiple stewards and other highly respected users who refuse to use them. TonyBallioni (talk) 04:32, 7 July 2020 (UTC)
- My gut sense is that sitewide blocks may still be an appropriate course of action for brand-new SPA accounts engaged in edit warring past 3RR (as was the case here), given the high likelihood that the editor may continue their disruption on related or non-mainspace pages. For cases where the editor is less clearly engaging in bad faith or has a history of positive contributions, I do think that partial blocks will generally be the best course of action. signed, Rosguill talk 22:03, 6 July 2020 (UTC)
- "Basically Ponyo was right here. The full block was justified and a partial block wouldn’t have accomplished anything." And that's why I get annoyed at other admins. You didn't say why. I assume you're saying it for a good reason, but without explaining your working out, all I can do is shake my head and say "you are wrong". :-( Ritchie333 (talk) (cont) 10:54, 7 July 2020 (UTC)
- Ritchie333 it is an SPA that was edit warring on the only page that it has edited. That’s indicative that it is extremely likely to cause issues elsewhere on the project. Some admins would have NOTHERE blocked if they saw it outside of ANEW. From a big picture point of view, partial blocks have created far more dramah than almost any other technical feature: people get just as mad when you partial block them and instead of limiting that anger to one page, where you can eventually talk them down and hopefully unblock them in the case of an edit warring block, they can be angry and spread that anger on multiple pages because they are Right(tm). It makes more sense just not to block someone and give them a warning than to partial block them in 99% of cases. In this case, however, there was enough to suggest that disruption would continue that a full block was preventative. When a full block is preventative and a partial block is likely to spread the issue elsewhere, then a full block makes total sense. Basically if you’re going to partial block, you should just warn since it is more likely to achieve long-term good. This passed the threshold for a warning there was indications that this user was likely to be a problem if they were page blocked (SPAs who are “right” tend yo cause issues everywhere.) TonyBallioni (talk) 11:21, 7 July 2020 (UTC)
- "Basically Ponyo was right here. The full block was justified and a partial block wouldn’t have accomplished anything." And that's why I get annoyed at other admins. You didn't say why. I assume you're saying it for a good reason, but without explaining your working out, all I can do is shake my head and say "you are wrong". :-( Ritchie333 (talk) (cont) 10:54, 7 July 2020 (UTC)
- The change by SarahSV mentioned above is good. An admin should always use clue and sometimes a partial block would be appropriate, and sometimes a site block. Johnuniq (talk) 05:18, 7 July 2020 (UTC)
- The change by Sarah is a positive. If someone has rocked up and the first or functionally first thing they do is EW then a siteblock is probably warranted. If there's even a little more helpful activity then a pageblock becomes much more warranted. Nosebagbear (talk) 09:18, 7 July 2020 (UTC)
- Why would you think that? It depends on the circumstances, but a genuine brand new user who reverts a few times because they don't understand why the system isn't accepting their changes properly (sic), good faith should be assumed. Ritchie333 (talk) (cont) 10:54, 7 July 2020 (UTC)
- Probably more helpful than trading anecdotes and impressions is to gather and analyze data. Since pblocks have been instituted, how many editors have been pblocked? How many of those editors were then given a full block? If 90% of the pblocked editors went on to do something that resulted in a full block, then we can conclude pblocks are not effective. If it's only 10%, then we can conclude that pblocks are effective. Data > opinion. Levivich [dubious – discuss] 15:49, 8 July 2020 (UTC)
- Data would be good. Sure, when deciding whether to impose a partial block or a sitewide one, one walks a fine line sometime between being judicious and assuming an abundance of good faith. My impression is that most partial blocks I, at least, apply do not escalate further, but that's obviously anecdotal. El_C 15:58, 8 July 2020 (UTC)
- Not exactly prolific, but of the 6 partials I've issued, 4 have caused the editor to stop editing, 1 to resume the disruption after the end of the block, and 1 to immediately begin content dispute resolution on the talk page. --Izno (talk) 16:14, 8 July 2020 (UTC)
- Data time! I tried doing this with SQL, but it ended up timing out even on Toolforge SQL directly, so I've gone about it a slightly different way: rather than looking at the actual logging tables, which I couldn't find an easy way of doing without causing a timeout, I grabbed a list of user talk pages that had a partial block template on, and then checked those users against the API to see if they had any blocks. I then wrote a quick little bit of JS to pull out that API query and refine for only the users who had a currently active non-partial block.
- The result? 210 users were included in the query (that is to say, I had a sample of 210 users who had been partially blocked from editing). Of that 210, 42 of them are now fully blocked from editing. 32 of them are blocked indefinitely, whilst the other 10 have varying levels of temporary blocks.
- That seems like pretty good numbers to me, to be honest, but I'll leave that to those who are actually doing the blocking day to day to confirm or rebuke. Naypta ☺ | ✉ talk page | 20:25, 8 July 2020 (UTC)
- Naypta, that's very interesting, thank you for the analysis, although it immediately makes me long for a control group. I wonder: do we know what the sitewide recidivism rate is for full blocks? (Or was, before pblocks?) Levivich [dubious – discuss] 21:26, 8 July 2020 (UTC)
So, there’s a reason people talk about lies, damn lies, and statistics. The presentation of data as well as whether it is capable of answering the question asked are both extremely important factors. In this case, the numbers might be interesting, but they don’t actually tell us all that much. First, as Izno points out, people could just quit after one. Next, the question is not if a full block later would occur, but if a full block at that point in time would have been better and cause less disruption. Those are subjective standards that are also point in time, and the data collected can’t really answer those questions at all. Finally, there’s the question of if the reaction to the block is better or worse if it’s partial from the blocked user. My experience observing this has been worse (people tend to get angrier is what I’m saying) and that causes more issues elsewhere. Anyway, just pointing out that “data>opinions” usually isn’t the best way to go about testing the effectiveness of subjective questions, since the data points on these topics tend to have many confounding factors. Basically you can pre-select your outcomes by asking the right question and picking a metric that corresponds to it. Something like that isn’t particularly useful in decision making, even if done with an attempt to be objective: the things being measured inherently can’t be. TonyBallioni (talk) 20:47, 8 July 2020 (UTC)
- @TonyBallioni: To be totally clear, I certainly don't mean to present a bunch of numbers and go "yes, this in and of itself should decide policy"; rather, I hope that having those numbers might be useful in terms of the decision-making here. You are, of course, completely right that you can pull out many conclusions from the same datasets.
- For what it's worth, I've checked, and of those 210 partially blocked users, 43 are not indefinitely blocked and have made edits in the last 30 days. So that's 32/210 indefinitely blocked, 35/210 not blocked at all and have edited in the last 30 days, 8/210 have been temporarily blocked but active within the last 30 days, and the rest are presumably inactive. Naypta ☺ | ✉ talk page | 21:56, 8 July 2020 (UTC)
- Right. I wasn’t assigning intent to you. Just noting that data in itself can often be misleading and that in real life, interpreting data related to subjective judgements is something you normally hire a professional to do (as an example: your income taxes; all based on actual numbers, but if they’re in complex areas you should hire a tax accountant or tax lawyer.) Basically when we are asking as subjective a question as “Did this one technical feature prevent more or less disruption then this other technical feature”, raw numbers are rarely that useful as a decision making aid. TonyBallioni (talk) 22:04, 8 July 2020 (UTC)
- Isn't it interesting though that Naypta's numbers match Izno's. Of Izno's set of 6 pblocks, 4/6 stopped editing, 1/6 continued to be disruptive, and 1/6 went on to be productive. Of Naypta's set of 210 pblocks, 32 (or about 1/6th) continued to be disruptive, 35 (again 1/6th) were productive, 8 somewhere in between disruptive and productive, and the remaining 135 (3.85/6) stopped editing. Which raises the question: would that 1/6th that was productive still have been productive if they were fully blocked instead of partially? Levivich [dubious – discuss] 00:50, 9 July 2020 (UTC)
- Policy pages are nothing but a reflection of current community consensus. I will absolutely lose it at any editor who's trying to change policy pages based on a local consensus or "common sense". Any changes must be made in line with a community-level consensus. With all that being said, I view both Ritchie's and Sarah's updates to be uncontentious and in line with this standard, simply reflecting an update in the overarching community consensus. The OP's accusation that Ritchie "changed the policy" is an egregious falsehood, unbecoming of the admin who made the accusation. It was clearly a simple update in wording meant to reflect the new partial blocking mechanism. This thread should be closed and condemned to the archives, never to be spoken of again. ~Swarm~ {sting} 04:59, 9 July 2020 (UTC)
- @Swarm: Did you read the discussion at WP:ANEW that I linked to in my opening post? There were other administrators commenting here, including GorillaWarfare and TonyBallioni, who did read that discussion and agreed that it did appear that the intent of the change in wording Ritchie333 made to Wikipedia:Blocking policy was to make partial blocks the default for edit warring where any site-wide blocks used in lieu of partial blocks need to be justified. I noted the change here as, if site-wide blocks for edit warring are only to be made "if required", administrators should be aware of this change so they aren't caught by surprise if asked to defend a site-wide block as I was in this case. I'm at a loss to understand how you determined that noting the change here is "unbecoming" of me, and accusing me of making "an egregious falsehood" is no different than accusing me of lying, which is a personal attack. Will you be levying the same "egregious falsehood" claim against EdJohnston, who does a great deal of the heavy lifting at WP:ANEW, and who made similar observations regarding the change in that specific discussion?-- Jezebel's Ponyobons mots 17:16, 9 July 2020 (UTC)
- For what it’s worth, I think Sarah’s wording is fairly uncontentious and clearer, and wouldn’t object to it. If it’s the default, I think that’d be a policy change which would need further discussion. TonyBallioni (talk) 17:21, 9 July 2020 (UTC)
- I completely agree.-- Jezebel's Ponyobons mots 17:23, 9 July 2020 (UTC)
- I did not read the relevant AN3 thread. While I did not see any intent of changing policy at face value based on the wording alone, looking at Ritchie's comments at AN3 I can see the clear motivation to delegitimize regular blocks in favor of partial blocks. This is unacceptable coming from one who had supposedly changed policy wording without motivation; a retroactive breach of WP:INVOLVED, perhaps. My apologies for condemning you without the full context. I'm actually extremely disappointed with Ritchie's behavior given this context and it's obvious that it was inappropriate. ~Swarm~ {sting} 09:48, 11 July 2020 (UTC)
- I completely agree.-- Jezebel's Ponyobons mots 17:23, 9 July 2020 (UTC)
- For what it’s worth, I think Sarah’s wording is fairly uncontentious and clearer, and wouldn’t object to it. If it’s the default, I think that’d be a policy change which would need further discussion. TonyBallioni (talk) 17:21, 9 July 2020 (UTC)
- @Swarm: Did you read the discussion at WP:ANEW that I linked to in my opening post? There were other administrators commenting here, including GorillaWarfare and TonyBallioni, who did read that discussion and agreed that it did appear that the intent of the change in wording Ritchie333 made to Wikipedia:Blocking policy was to make partial blocks the default for edit warring where any site-wide blocks used in lieu of partial blocks need to be justified. I noted the change here as, if site-wide blocks for edit warring are only to be made "if required", administrators should be aware of this change so they aren't caught by surprise if asked to defend a site-wide block as I was in this case. I'm at a loss to understand how you determined that noting the change here is "unbecoming" of me, and accusing me of making "an egregious falsehood" is no different than accusing me of lying, which is a personal attack. Will you be levying the same "egregious falsehood" claim against EdJohnston, who does a great deal of the heavy lifting at WP:ANEW, and who made similar observations regarding the change in that specific discussion?-- Jezebel's Ponyobons mots 17:16, 9 July 2020 (UTC)
- I was expecting it to be a year or more from the implementation of partial blocks before sneaky changes to policies started compelling admins to use them, but I'm pretty sure in the initial RfC I predicted this exact thing was going to happen. I hadn't anticipated that silent changes would also compel an explanation for not using a tool in the set; good job on that escalation. That said, admins are servants of the community and I'm on board with the update if that's the community's wish, but I expect any such change will be the result of thorough consensus in a very-well-advertised RfC, and will be communicated in the admins' newsletter before it comes into effect. A short discussion among a few policy hawks on the policy's talk page is so egregiously not good enough that you should be ashamed, and the fact you tried to challenge an action based on a change you made and which you hadn't told anyone about is thoroughly within WP:POINT territory. Ivanvector (Talk/Edits) 18:03, 9 July 2020 (UTC)
8 years-undetected hoax article
I guess the hoax I nominated for speedy deletion deserves to be at WP:HOAXLIST since it went undetected for 8 years. Page title: Battle of Ceber –User456541 23:02, 6 July 2020 (UTC)
- I added it ☆ Bri (talk) 03:50, 7 July 2020 (UTC)
- I'm not so sure this is a hoax, see pl:Bitwa pod Cebrem as well as pl:Przyczółek_baranowsko-sandomierski, which mentions it. If it's a hoax, it's one that's well-integrated and sourced on Polish Wikipedia. I'm not qualified to assess the reliability of those sources though...paging K.e.coffman, who I know edits in the WW2-in-Poland area. I'm going to restore the page for now so it can be checked over. ♠PMC♠ (talk) 00:21, 8 July 2020 (UTC)
- It is included in e.g. this book from 2000 or this one from 1966, no idea why it was considered a hoax and speedy deleted. It was created by User:Halibutt, who was a well-respected editor, so unlikely to create hoaxes. At the very least this deserved an AfD as there was nothing blatant about the supposed hoax. Perhaps User:Koridas and User:User456541 can explain their reasoning? Oh, and User:Anthony Bradbury, who actually speedy deleted the page? Seems like a rather poor decision... Fram (talk) 07:28, 8 July 2020 (UTC)
- Not sure about Koridas, but User456541 has some issues with speedy deletions, per his talk page. That's actually how I found this - he unnecessarily G8-tagged the talk page of an article I had tagged as A7, so I checked his contribs and found more issues. There's a number of messages on his talk page from people asking him to stop CSD-tagging. ♠PMC♠ (talk) 14:03, 8 July 2020 (UTC)
- I added some sources, but then ReFill let me down, naturally...I'll try again in a bit. ——Serial # 15:10, 8 July 2020 (UTC)
- Not sure about Koridas, but User456541 has some issues with speedy deletions, per his talk page. That's actually how I found this - he unnecessarily G8-tagged the talk page of an article I had tagged as A7, so I checked his contribs and found more issues. There's a number of messages on his talk page from people asking him to stop CSD-tagging. ♠PMC♠ (talk) 14:03, 8 July 2020 (UTC)
- It is included in e.g. this book from 2000 or this one from 1966, no idea why it was considered a hoax and speedy deleted. It was created by User:Halibutt, who was a well-respected editor, so unlikely to create hoaxes. At the very least this deserved an AfD as there was nothing blatant about the supposed hoax. Perhaps User:Koridas and User:User456541 can explain their reasoning? Oh, and User:Anthony Bradbury, who actually speedy deleted the page? Seems like a rather poor decision... Fram (talk) 07:28, 8 July 2020 (UTC)
- I dropped a note at WT:MILHIST for further investigation. Rgrds. --Bison X (talk) 17:29, 8 July 2020 (UTC)
"Draft:Sample page/(eight digit number)" - what's happening with them?
Hi all,
Late June 2020 and early July 2020 a whole lot of draftspace pages have been created with the format Draft:Sample page/(eight digit number)
.
Examples:
I am teh fail when it technical matters like this, and despite the "When you start a discussion about an editor, you must notify them on their user talk page" message I don't have a clue which editor to notify about this discussion.
Could you possibly look into this? Pete AU aka --Shirt58 (talk) 09:37, 7 July 2020 (UTC)
- After a little personal investigation, these sample pages seem to be created/edited when an IP user clicks the "Edit using wiki markup" button in Help:Introduction to Wikipedia. Gricehead (talk) 11:07, 7 July 2020 (UTC)
- Yikes, that was implemented on 16 June 2020 by Sdkb (diff). Johnuniq (talk) 10:31, 7 July 2020 (UTC)
- @Johnuniq and Shirt58: Yes, that was added via this discussion. There has been some follow-up discussion at the Technical Pump here, although that seems to have stalled a bit. Those two discussions should hopefully explain the change, and if you have any additional questions feel free to ask. Help would certainly be welcome if anyone wants to pick up where the VPT discussion left off. Cheers, {{u|Sdkb}} talk 10:50, 7 July 2020 (UTC)
- I think it's time to BRD revert User:Sdkb's change there - these are creating a mess and the process should be better designed. — xaosflux Talk 11:27, 7 July 2020 (UTC)
- Xaosflux, when we left off at VPT, you were going to try to see if there was a way to link to User talk:x.x.x.x/sample page that cleared the content there and then preloaded the sample page. Did you ever find anything on that? Also, was the idea to use an adminbot to auto-delete the pages after a preset period deemed viable?
- For now, we can switch anytime to directing IP editors to a subpage of their talk page if draftspace is creating too much trouble. There are several pages later on in the tutorial that use a similar setup to the present one for a different sample page (e.g. an image-filled page at the end of the images tutorial), but the number of IPs reaching these seems to be vanishingly small, since most editors dedicated enough to keep reading also followed the instruction shown to IPs at Help:Introduction to Wikipedia to log in. The system seems to be working fine for the large number of editors who do log in, so hopefully that part can be retained. {{u|Sdkb}} talk 16:39, 7 July 2020 (UTC)
- Also should speedy delete all these drafts: Special:PrefixIndex/Draft:Sample_page/ - who would ever find these to resume working on them with nonsense page titles? — xaosflux Talk 15:10, 7 July 2020 (UTC)
- Thanks all, and apologies for sending User talk:Primefac a teh random "{{subst:AN-notice}}". Pete AU aka--Shirt58 (talk) 09:33, 8 July 2020 (UTC)
- Yikes, that was implemented on 16 June 2020 by Sdkb (diff). Johnuniq (talk) 10:31, 7 July 2020 (UTC)
Large backlog at Category:Wikipedia files with the same name on Wikimedia Commons
As of this message, the speedy deletion category Category:Wikipedia files with the same name on Wikimedia Commons, with its subcategories, contains a rather large backlog of 2,411 pages. (See Category:All Wikipedia files with the same name on Wikimedia Commons.) Administrator assistance to clear out this backlog would be appreciated, considering that it has to be done by administrators since clearing the entries requires page deletions. Steel1943 (talk) 16:35, 7 July 2020 (UTC)
- I'll take a crack at it later this week. Anybody else interested in helping out should first familiarize themselves with Wikipedia:Moving files to Commons. Files which were inappropriately moved to Commons must not be deleted locally and should be nominated for DR on Commons. -FASTILY 23:49, 8 July 2020 (UTC)
What to do about RHaworth's talk page
The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
As most of you will remember, one of the most prolific admins in deletion, RHaworth (talk · contribs), was desysopped earlier this year, and is still getting regular traffic to his talk page from new and newish users asking about getting articles undeleted or pages salted. I've fielded a couple of these, as have others, but it would be helpful to get a few more eyes looking at. I would not be in favour of putting any sort of talk page messages or edit notices saying something like "This user is not an admin, please go elsewhere" as I'm not sure people would read it, plus it rubs RHaworth's face in it. I think just managing them as and when they come in will do for the time being. Ritchie333 (talk) (cont) 22:12, 7 July 2020 (UTC)
- I've added to my watchlist and will try to remember but teaching Japanese toddlers the word "no" for 40 hours a week makes it unlikely that I'll catch many of the requests. Ian.thomson (talk) 22:19, 7 July 2020 (UTC)
- @Ritchie333: It's still on my watchlist and I've fielded some requests. The only problem is that many of the requests I've looked at were good deletions of unsalvageable non-notable individuals and companies where the deleted article would be a lousy starting point for a re-write. I suppose we could just REFUND on request and count on the AfC process to catch the dross, but it feels a little unfair on them. --RexxS (talk) 22:48, 7 July 2020 (UTC)
- Even in that case, a holding reply of "This article has more puffery than Puff Daddy eating Sugar Puff sandwiches with Puff the Magic Dragon while wearing a puffer jacket" (albeit maybe phrased more diplomatically) would still be useful. Ritchie333 (talk) (cont) 23:13, 7 July 2020 (UTC)
- @Ritchie333: It's still on my watchlist and I've fielded some requests. The only problem is that many of the requests I've looked at were good deletions of unsalvageable non-notable individuals and companies where the deleted article would be a lousy starting point for a re-write. I suppose we could just REFUND on request and count on the AfC process to catch the dross, but it feels a little unfair on them. --RexxS (talk) 22:48, 7 July 2020 (UTC)
- Maybe archiving his talkpage and changing the edit notice would help. Also is there a userpage template to say that someone is less active? Lugnuts Fire Walk with Me 09:46, 8 July 2020 (UTC)
- He still has the admin/mop pip in the header of the page. There is no policy against that, that I'm aware of, and I doubt that is the source of all these questions, but wanted to bring it to his and other's notice. Dennis Brown - 2¢ 11:11, 8 July 2020 (UTC)
- Dennis Brown, Maybe somebody who had a good relationship with him should email him and ask him how he would like to proceed? He's still quasi active. His last edits were just a couple of weeks ago. I get that the needs of the project outweigh the needs of the individual editor, but hijacking somebody's talk page isn't very nice. We should at least make some attempt to contact him before we do so. -- RoySmith (talk) 11:22, 8 July 2020 (UTC)
- Honestly, I think he will see it in this discussion. Dennis Brown - 2¢ 11:25, 8 July 2020 (UTC)
- Dennis Brown, Maybe somebody who had a good relationship with him should email him and ask him how he would like to proceed? He's still quasi active. His last edits were just a couple of weeks ago. I get that the needs of the project outweigh the needs of the individual editor, but hijacking somebody's talk page isn't very nice. We should at least make some attempt to contact him before we do so. -- RoySmith (talk) 11:22, 8 July 2020 (UTC)
- I was thinking of something like:
![]() | This user is no longer very active on Wikipedia. If you would like assistance with an article that was speedy deleted or proposed for deletion, please go to Requests for undeletion. If you are asking for help with an article deleted via Articles for deletion, please see Deletion Review. If you cannot create an article because it is create-protected, please go to Requests for page unprotection. |
- I guess you're either left with not putting a notice on his talkpage, and relying on talkpage stalkers to work through the detritus, or adding a notice so editors aren't wasting their time in posting requests there. So a choice between tough love or soft hate. Lugnuts Fire Walk with Me 18:44, 9 July 2020 (UTC)
- No objection to adding Ritchie333's banner. -- RoySmith (talk) 18:51, 9 July 2020 (UTC)
- That notice seems pretty reasonable. If they have an issue with it they can let us know here or just remove it from their talk page. -Ad Orientem (talk) 19:50, 9 July 2020 (UTC)
- Ad Orientem, I concur. S Philbrick(Talk) 01:53, 10 July 2020 (UTC)
- I have put the banners up, as there have been no objections. Ritchie333 (talk) (cont) 11:52, 10 July 2020 (UTC)
- I do think that when an admin is desysopped or leaves there should be someone assigned to their workload. I actually thought about running for RFA when I found out he had been desysopped, but then realised I'm too chicken to go through the process.--Launchballer 12:41, 10 July 2020 (UTC)
- Given that we're an all volunteer work group - I don't see how that would be doable. — Ched (talk) 13:17, 10 July 2020 (UTC)
- I do think that when an admin is desysopped or leaves there should be someone assigned to their workload. I actually thought about running for RFA when I found out he had been desysopped, but then realised I'm too chicken to go through the process.--Launchballer 12:41, 10 July 2020 (UTC)
- I have put the banners up, as there have been no objections. Ritchie333 (talk) (cont) 11:52, 10 July 2020 (UTC)
- Ad Orientem, I concur. S Philbrick(Talk) 01:53, 10 July 2020 (UTC)
- That notice seems pretty reasonable. If they have an issue with it they can let us know here or just remove it from their talk page. -Ad Orientem (talk) 19:50, 9 July 2020 (UTC)
- No objection to adding Ritchie333's banner. -- RoySmith (talk) 18:51, 9 July 2020 (UTC)
- I guess you're either left with not putting a notice on his talkpage, and relying on talkpage stalkers to work through the detritus, or adding a notice so editors aren't wasting their time in posting requests there. So a choice between tough love or soft hate. Lugnuts Fire Walk with Me 18:44, 9 July 2020 (UTC)
Discussion at Wikipedia:Reference_desk/Humanities
Hello, am looking for an administrator to please review Wikipedia:Reference_desk/Humanities#Is Walter Breuning's death record available on Ancestry.com? and worse, the follow-up at Wikipedia:Reference_desk/Humanities#If someone has esophagus problems and they proceed to die from starvation, is the likely explanation for their death that they starved themselves on purpose?. Could this speculation about the death and possible suffering of a recently deceased person please be removed? I posted this request first at Wikipedia:Biographies_of_living_persons/Noticeboard#Reference_desk/Humanities and they asked me to put it here. Thanks 70.67.193.176 (talk) 20:49, 8 July 2020 (UTC)
- Breuning died 9 years ago, so he's not covered by our BLP policy which defines "recently deceased" as having died less than two years ago. Still, I blanked the second discussion per WP:NOTFORUM because it's unrelated to the encyclopedia and just generally in poor taste; if anyone cares it's in the page history, but I dont find retaining or encouraging off-topic discussion like that particularly valuable. The first discussion I've left alone since a request for particular public records is within our scope, so despite the subject matter, it's still worthwhile for improving the encyclopedia. — Wug·a·po·des 01:37, 9 July 2020 (UTC)
- Wugapodes, Reference desk is for off-topic discussion, unrelated to building Wikipedia. WP:FORUM specifically gives Reference desk as the alternative venue for users looking to make article talk pages into Q&A fora. "Poor taste" sounds like WP:IDLI. Since WP:BLP doesn't apply and WP:RD is open for all kinds of discussion as long as they remain a dispassionate intellectual exercise, I do not see any valid rationale for removal. Regards! Usedtobecool ☎️ 02:38, 9 July 2020 (UTC)
- I disagree with that being the point of the reference desk. If
youone wants to wax philosophical about whether people who cannot eat are technically killing themselves, take it to a forum or a chat room. wikipedia is an encyclopedia, and WP:RD doesn't get a pass from that just because they say they do. Pointing to IDLI sounds like WP:ATAATA. Participants in that discussion characterized it as both cruel and off-topic, so there's an independent reason for my characterization of out of scope and poor taste beyond my personal feelings. You're free to revert, but please explain how that discussion has contributed to the encyclopedia? — Wug·a·po·des 02:54, 9 July 2020 (UTC)- Thanks for removing the pointless speculation. Those who frequent the ref desks, and those that merely like them, have often been unable to work out when discussion should stop and I support admin action to remind everyone that the ref desks are part of Wikipedia. Johnuniq (talk) 03:55, 9 July 2020 (UTC)
- I apologise if you felt attacked. I have no interest in reverting, I wasn't participating there, nor had I even seen it before your edit summary caught my eye; I was only trying to get some clarification as I didn't see the removal justified per WP:RD/G. Discussions on RDs rarely contribute to improving the articles; when they do, it's only incidental. And only the main namespace is the encyclopedia. The question was somewhat loaded and the discussion does try to veer toward philosophising on potentially controversial issues, but volunteers do also get it back in control keeping it informative, citing Wikipedia articles and science behind the topic. (I hope by you, you meant the generic you and not me. In any case, I would like to clarify that I do not go about the internet looking for places to "wax philosophical about whether people who cannot eat are technically killing themselves") Regards! Usedtobecool ☎️ 04:02, 9 July 2020 (UTC)
- I did mean the generic you, and I've replaced it with the third person to remove that ambiguity. Sorry for coming off so confrontational. — Wug·a·po·des 05:05, 9 July 2020 (UTC)
- NOTFORUM bans generic discussion on article talk pages, but allows specific content questions to be asked and answered at Refdesk. The removed thread was not a "specific" question, but a "general" question, seeking personal opinions, interpretations, and debate. Refdesk is analogous to a library reference desk, in which factual questions are provided with factual, source-based answers. It is not a NOTFORUM-exempt forum for general discussion, speculation and debate. That discussion was inappropriate if not trollish. The IP's request to shut it down is appropriate. Wugapodes' removal was appropriate. Reverting the removal, although Wug has allowed for such, would be disruptive. ~Swarm~ {sting} 04:07, 9 July 2020 (UTC)
- Thank you Swarm, that answers all my questions (thought or spelled out). Usedtobecool ☎️ 04:21, 9 July 2020 (UTC)
- I disagree with that being the point of the reference desk. If
- Wugapodes, Reference desk is for off-topic discussion, unrelated to building Wikipedia. WP:FORUM specifically gives Reference desk as the alternative venue for users looking to make article talk pages into Q&A fora. "Poor taste" sounds like WP:IDLI. Since WP:BLP doesn't apply and WP:RD is open for all kinds of discussion as long as they remain a dispassionate intellectual exercise, I do not see any valid rationale for removal. Regards! Usedtobecool ☎️ 02:38, 9 July 2020 (UTC)
- Sincere thanks, administrators, for looking after this. 70.67.193.176 (talk) 14:30, 9 July 2020 (UTC)
Incorrect non-admin closure
Can this be addressed?
I was looking at the Special:Userlist and noted that the username that immediately follows mine is that of a blocked account named (Redacted) (clearly I ruffled someone's feathers!). Is there any way this account name can be changed so that this insult doesn't just remain out in the world forever? Not super important, but it is a bit of a slap. WikiDan61ChatMe!ReadMe!! 13:35, 9 July 2020 (UTC)
- @WikiDan61: please use meta:Special:EmailUser/Wikimedia_Stewards and report that name for a "global lock and HIDE" - it will remove it from all lists. — xaosflux Talk 13:49, 9 July 2020 (UTC)
- That sounds like good advice. I personally feel we should be much more active in deleting these long-standing 'attack-name' accounts, and any new ones that come along. They maintain their insulting effect by the fact that they simply sit there, next to the genuine users name, and have a negative effect on this project long after their creators have been blocked. I haven't checked recently, but Oshwah had amassed quite a nice collection of them last time I looked. I suspect many others have too, and I imagine there are innumerable offensive/racist/homophobic and degrading account names there, also. They serve no purpose other than to illustrate how people can get away with being puerile and offensive and, in my view, Wikipedia should have matured enough by now to have addressed and removed them, whether they have actually edited, or not. Nick Moyes (talk) 13:51, 9 July 2020 (UTC)
- @Nick Moyes: while we can do something locally (oversight blocks with the hide option) it is almost always better to send an obvious attack name that has no constructive global edits to the stewards to deal with, you can send them an entire list by email if you have one - since it will remove the name from drop-downs/search suggestions/etc on every WMF project. — xaosflux Talk 14:09, 9 July 2020 (UTC)
- @Xaosflux: I don't have any list, as yet, but maybe I should start with Nigger', 'Cunt' and Oshwah (see here) and see how we get on. (Point of order: I make no linkage whatsoever between the three words - honest). Nick Moyes (talk) 14:25, 9 July 2020 (UTC)
- 😯 --Deepfriedokra (talk) 14:31, 9 July 2020 (UTC)
- Does oversighting the username on the block actually remove it from the list of users?
I haven't actually tested that yet.It does say in the oversight documentation that doing so will remove it from the list of users, but from my experience, I don't believe that to be true... Can someone confirm that it is?Actually, hold that thought. I can do it. I'll just look up a username in the oversight log where it was removed upon blocking and then try to find it... Stand by. ~Oshwah~(talk) (contribs) 00:43, 11 July 2020 (UTC)- It does. The reason that I could see it in the list was because, well, I'm an oversighter. Duh! Testing it using incognito mode and while logged out did not display hidden users in Special:ListUsers. :-) ~Oshwah~(talk) (contribs) 00:47, 11 July 2020 (UTC)
- Oshwah-TEST is an alternate account that I created, FYI. :-) I have many doppelgänger accounts that I created to prevent impersonation, but I blocked them immediately after creation; they don't need to edit or have any functionality whatsoever. See this page if you want the list. ;-) ~Oshwah~(talk) (contribs) 00:53, 11 July 2020 (UTC)
- @Xaosflux: I don't have any list, as yet, but maybe I should start with Nigger', 'Cunt' and Oshwah (see here) and see how we get on. (Point of order: I make no linkage whatsoever between the three words - honest). Nick Moyes (talk) 14:25, 9 July 2020 (UTC)
- @Nick Moyes: while we can do something locally (oversight blocks with the hide option) it is almost always better to send an obvious attack name that has no constructive global edits to the stewards to deal with, you can send them an entire list by email if you have one - since it will remove the name from drop-downs/search suggestions/etc on every WMF project. — xaosflux Talk 14:09, 9 July 2020 (UTC)
- That sounds like good advice. I personally feel we should be much more active in deleting these long-standing 'attack-name' accounts, and any new ones that come along. They maintain their insulting effect by the fact that they simply sit there, next to the genuine users name, and have a negative effect on this project long after their creators have been blocked. I haven't checked recently, but Oshwah had amassed quite a nice collection of them last time I looked. I suspect many others have too, and I imagine there are innumerable offensive/racist/homophobic and degrading account names there, also. They serve no purpose other than to illustrate how people can get away with being puerile and offensive and, in my view, Wikipedia should have matured enough by now to have addressed and removed them, whether they have actually edited, or not. Nick Moyes (talk) 13:51, 9 July 2020 (UTC)
- @Xaosflux: Thanks for the info. I've followed your advice. WikiDan61ChatMe!ReadMe!! 15:22, 9 July 2020 (UTC)
- If it didn't predate my account by six years I'd accuse "Nosebig Fathead" of offensive truth-telling! Nosebagbear (talk)
- LOL. ...OK, so I've now managed to build this list of 282 deeply offensive usernames, solely relating to the 'N-word' that have all been blocked, but are still capable of being presented to users anywhere on our projects. Some might think I'm being prudish by recommending their complete removal, but I see no reasonable justification in continuing to cause offence by retaining names that clearly either attack, harass or belittle certain individuals or groups. Nick Moyes (talk) 19:37, 9 July 2020 (UTC)
- Not prudish but prudent. — SMcCandlish ☏ ¢ 😼 22:29, 9 July 2020 (UTC)
- I'd disagree with the selection being based on names starting "Ni..." as users searching the list at that point pretty much know what they're going to find. More disruptive are those where the "ni..." occurs mid-name where their appearance will definitely be unanticipated. 164 found in quarry:query/21637 -- Cabayi (talk) 12:49, 10 July 2020 (UTC)
- Both are good lists. I just wish that quarry (or our level of SQL) would take full regex as string input for statements. Else, I'd recommend the query string be
'.*ni+gg+e+r+.*'
or even'%ni+gg+e+r+%'
if the.
and the*
couldn't be used... ~Oshwah~(talk) (contribs) 02:41, 11 July 2020 (UTC)- Oshwah, you really know how to make an editor spit out his coffee while scrolling through AN :-) Levivich [dubious – discuss] 05:33, 11 July 2020 (UTC)
- Of course it does. Our "level" of sql is mariadb, and googling that and regex tells you exactly how.
quarry:query/46558quarry:query/46559 also handily shows whether they're blocked. —Cryptic 03:10, 11 July 2020 (UTC)- Cryptic - Excellent! Thank you for letting me know this. I couldn't find any documentation that specifically stated what "level" of SQL or regex that we use, so I had to guess from what I could find in past statements. I'll definitely give it a google and see what regex wildcards are allowed, and their syntax (if different). Thanks again! :-) ~Oshwah~(talk) (contribs) 06:19, 11 July 2020 (UTC)
- I assume that the data
ipb_expiry
is a string, but when I addedAND ipb_expiry = null;
,AND ipb_expiry = "";
, or evenAND ipb_expiry != 'infinity';
- nothing returned. Ugh, it's been too long since I've done any SQL queries... I'm obviously quite rusty now... :-/ ~Oshwah~(talk) (contribs) 06:28, 11 July 2020 (UTC)- You were looking for "AND ipb_expiry IS NULL" (see Null (SQL)#Common mistakes). Though the easiest way here would be to click the sort buttons on the ipb_expiry column. (Insert obligatory WP:Request a query ad here.) —Cryptic 13:40, 11 July 2020 (UTC)
- I assume that the data
- Cryptic - Excellent! Thank you for letting me know this. I couldn't find any documentation that specifically stated what "level" of SQL or regex that we use, so I had to guess from what I could find in past statements. I'll definitely give it a google and see what regex wildcards are allowed, and their syntax (if different). Thanks again! :-) ~Oshwah~(talk) (contribs) 06:19, 11 July 2020 (UTC)
- Both are good lists. I just wish that quarry (or our level of SQL) would take full regex as string input for statements. Else, I'd recommend the query string be
- I'd disagree with the selection being based on names starting "Ni..." as users searching the list at that point pretty much know what they're going to find. More disruptive are those where the "ni..." occurs mid-name where their appearance will definitely be unanticipated. 164 found in quarry:query/21637 -- Cabayi (talk) 12:49, 10 July 2020 (UTC)
- At least one name (NiggiV) shouldn't be in the list (and probably shouldn't be blocked) - Niggi is a name, probably similar to Nick (de:Niggi Schmassmann, de:Niklaus Starck, de:Niggi Schoellkopf). Similar names in the German Wikipedia haven't been blocked. Peter James (talk) 11:30, 11 July 2020 (UTC)
- Not prudish but prudent. — SMcCandlish ☏ ¢ 😼 22:29, 9 July 2020 (UTC)
I think we need an anti-harassment WikiProject to address derogatory usernames like these and other forms of harassment and personal attacks on the wiki, especially in the wake of the George Floyd protests. SuperGoose007 (Honk!) 00:47, 10 July 2020 (UTC)
SashiRolls ban review
- Wikipedia:Arbitration/Requests/Case#SashiRolls
- Wikipedia:Administrators' noticeboard/Archive321#Site ban proposal: SashiRolls
ArbCom has declined this case, which punts it back to us. My concerns are I think representative of those who have challenged this:
- The "consensus" appears to be a bare majority of votes, whereas I would expect consensus to be more robust where it comes to something as serious as a ban;
- While the minimum 24 hours was met, this seems a very short time in this specific case.
Accordingly, I propose that we reopen the discussion, and request that the final closure provide a rationale in line with what would be needed at a contentious AfD or whatever.
I'm not accusing anyone of acting in bad faith, I just don't think this represents our best work as admins. Guy (help!) 23:17, 9 July 2020 (UTC)
- I don't think admins are solely to blame; I don't think this represents our best work as editors. ——Serial # 23:24, 9 July 2020 (UTC)
- Support Paul August ☎ 23:22, 9 July 2020 (UTC)
- Support reopening I'm assuming we are discussing if we should in fact open a review? Or is the subect officially already reopened per Admin Guy? Jusdafax (talk) 23:29, 9 July 2020 (UTC)
- Oppose because MastCell gave a detailed and reasonable response at the case request, and more than sufficient time for discussion was given. As was pointed out in the case request, over 90% of comments had been made before the day of the close, things were slowing down, and there was a consensus based both on arguments and numbers. ~60% with strong arguments is enough for a consensus. Sashi’s efforts to appeal the ban proved what everyone who supported it said: this is an editor who has a list of enemies and views everything as a battleground. We’ve already wasted more than enough time on this, and the community has already resolved it. SashiRolls is site banned, and the close was within administrative discretion. We should not overturn it. TonyBallioni (talk) 23:46, 9 July 2020 (UTC)
- TonyBallioni, that response does not address the miscounting of comments supporting and opposing. If such things don't matter then why even bother with a consensus? Just let admins do whatever they feel is proper per their discretion. Mr Ernie (talk) 09:58, 11 July 2020 (UTC)
Depending on how you count it, you’re looking at 60-62% (SilkTork below. I think I’ve counted a few times and get in that range as well.) Sashi had it at 55% by counting neutrals as opposed in his math I believe, which is also a way to do it. In my mind, I’d say that 60% is roughly 2/3. MastCell didn’t say exactly 67% he said approximately 2/3. 60% is around where I start referring to things as “about two-thirds” in my own speech, so I don’t think there really was any overcounting going on. People just have different thresholds for where they start using common fractions in their colloquial speech. MastCell and I both apparently share the trait of seeing it at around 3/5. 1/4, 1/3, 1/2, 2/3, and 3/4 are the most commonly used fractions in every day speech, and people tend to reference them rather than the less common ones. I get the frustration here by some, but I also think the easier explanation was that MastCell was just typing like he talks. TonyBallioni (talk) 16:46, 11 July 2020 (UTC)- The close said greater than 2/3 (">2/3"). When I asked MastCell about it [5], he characterized it as "a clear (super-)majority" [6]. Levivich [dubious – discuss] 17:03, 11 July 2020 (UTC)
- Ha! I’ve been working too hard. I read it as “~2/3” every time. I don’t really think that changes much in terms of consensus. I think 60% with good reasoning is a perfectly fine percentage to ban someone with since that is a supermajority and consensus is not just numbers. Anyway, apologies for misreading that. Striking the above :)TonyBallioni (talk) 17:51, 11 July 2020 (UTC)
- TonyBallioni, a site ban is one of the most serious sanctions possible. Consensus for such a measure should be rock solid and accurately reflect the tenor of the comments. I get it, you opened the ban discussion and are happy Sashi won't be around here anymore to annoy some deeply entrenched and connected editors a couple years ago. What percentage of content discussions with 60% consensus are closed as "successful?" It's probably less than 10%. Shouldn't a site ban closure aim a little higher than that? Mr Ernie (talk) 17:30, 12 July 2020 (UTC)
- Ha! I’ve been working too hard. I read it as “~2/3” every time. I don’t really think that changes much in terms of consensus. I think 60% with good reasoning is a perfectly fine percentage to ban someone with since that is a supermajority and consensus is not just numbers. Anyway, apologies for misreading that. Striking the above :)TonyBallioni (talk) 17:51, 11 July 2020 (UTC)
- The close said greater than 2/3 (">2/3"). When I asked MastCell about it [5], he characterized it as "a clear (super-)majority" [6]. Levivich [dubious – discuss] 17:03, 11 July 2020 (UTC)
- TonyBallioni, that response does not address the miscounting of comments supporting and opposing. If such things don't matter then why even bother with a consensus? Just let admins do whatever they feel is proper per their discretion. Mr Ernie (talk) 09:58, 11 July 2020 (UTC)
- WP:AGF O3000 (talk) 17:36, 12 July 2020 (UTC)
- I actually think content discussions are the best analogy here, and yes, I’m aware of my biases. 60% is in the range where it usually can go either way in content discussions. Much above that, and it’s an obvious consensus, significantly less and it’s obvious no consensus. High 50s to low 60s is about where the “discretionary range” is for non-policy RfCs. If the arguments are strong, it’s enough to carry. I’m biased in this case obviously, but if there were another close, I’d find literally everything else has been tried to be a much stronger argument than try something less drastic. Again, I’m biased, but I think I’d feel that way if I was uninvolved too. TonyBallioni (talk) 18:18, 12 July 2020 (UTC)
- i'd quibble with Tony about a lot of things, but not about the difference between 60% and 67%; this doesn't hinge on that. I think the broader point is, "what level of consensus to site ban?", to which I'd answer "overwhelming consensus", also known as the Kemp standard ("damsure of our evidence"). Because of the late oppose swing and because comments were still rolling in at an active clip, I didn't feel like this discussion got to that level of consensus, whatever the exact numbers might have been. Levivich [dubious – discuss] 18:28, 12 July 2020 (UTC)
- Support to simply put the matter to bed. (I commented but didn't vote in the discussion, and don't expect to vote) I don't see a fatal flaw in the close, but the numbers seemed to not jibe, which is a good reason to not give numbers in a close. It is a ban, after all, and simply continuing the discussion for an addition 48 hours (my guess) isn't going to hurt anyone, and whatever the outcome, we can have faith in it. Dennis Brown - 2¢ 23:53, 9 July 2020 (UTC)
- You think that opening another couple of noticeboard free-for-alls will "put the matter to bed"? Oh, Dennis—you must be new here. :P MastCell Talk 19:24, 10 July 2020 (UTC)
- Support reopening and allowing it stay open through the weekend (or however-long) per Sashi's original request. Levivich [dubious – discuss] 23:55, 9 July 2020 (UTC)
- Support reopening. I do not believe a consensus was reached in the initial thread. LEPRICAVARK (talk) 23:58, 9 July 2020 (UTC)
- Support MastCell did pretty well even if we're thinking maybe not perfect and so a big thank you to MastCell for jumping into the breech on this. I think that a more thorough process and slower close is in order. North8000 (talk) 00:28, 10 July 2020 (UTC)
- Support for the reasons most thoroughly described by Darouet below. North8000 (talk) 21:00, 10 July 2020 (UTC)
- Oppose - Arbcom declined 9-0. How many bites at the apple do you get? Sashi continues to blame everyone else, bring up old, irrelevant grudges, and hasn't displayed an iota of introspection. Their only admission is that they may not have presented the case well enough -- not that they present an obvious, ongoing problem to the community. But, let's waste another month, and then another month. If they want to reenter, let them spend a few months examining why their block log is so long and consider the possibility that their actions, not those of everyone else, are the cause. As Pope Julius supposedly said to Michelangelo, when will you make it end? O3000 (talk) 00:41, 10 July 2020 (UTC)
- Numerous arbs explicitly stated that they were punting this back to the community, so the unanimous decline hardly precludes further discussion here. LEPRICAVARK (talk) 02:27, 10 July 2020 (UTC)
- Oppose If you think Mastcell's close was within admin discretion, and ARCOM's decline seems to say that it was. Then the appropriate thing would be for Sashirolls to wait the 6 months per the standard offer and appeal to the community. Why would we do any different in this case as opposed to others? Valeince (talk) 01:01, 10 July 2020 (UTC)
- @Valeince: I don't think ARBCOM's discussion meant that they felt it was within discretion. As is quoted below they said things like "If the community wants to reopen the ban discussion or start a new one, it can be done without our involvement." They argue it's the community's job to figure this out, not theirs. Hobit (talk) 02:46, 10 July 2020 (UTC)
- @Hobit: In my mind, the only reason for an out of usual process review, which this is, is because the closer was found to have closed the discussion outside of their discretion. The ARBCOM case was built around this argument and was declined to be heard with the arbs confirming that since this was within admin discretion then the community can review. To me, that means that the review can happen when SashiRolls appeals the ban, which per usual circumstances is after the standard offer. Valeince (talk) 18:17, 10 July 2020 (UTC)
- I'd have said that they were pretty clear that the community can reopen the ban discussion at its own discretion. Hobit (talk) 18:33, 10 July 2020 (UTC)
- I agree, and I think our discretion should lead us to use the normal procedures in these cases. Which is the aforementioned standard offer unblock request. Valeince (talk) 19:14, 10 July 2020 (UTC)
- I'd have said that they were pretty clear that the community can reopen the ban discussion at its own discretion. Hobit (talk) 18:33, 10 July 2020 (UTC)
- @Hobit: In my mind, the only reason for an out of usual process review, which this is, is because the closer was found to have closed the discussion outside of their discretion. The ARBCOM case was built around this argument and was declined to be heard with the arbs confirming that since this was within admin discretion then the community can review. To me, that means that the review can happen when SashiRolls appeals the ban, which per usual circumstances is after the standard offer. Valeince (talk) 18:17, 10 July 2020 (UTC)
- @Valeince: I don't think ARBCOM's discussion meant that they felt it was within discretion. As is quoted below they said things like "If the community wants to reopen the ban discussion or start a new one, it can be done without our involvement." They argue it's the community's job to figure this out, not theirs. Hobit (talk) 02:46, 10 July 2020 (UTC)
- Wait for a statement (appeal?) from SashiRolls, whenever they are ready; Oppose until then. There was a clear consensus there is a conduct problem. There was a sideshow whether the situation should be taken up by ArbCom rather than the community, indirectly causing a perhaps unfortunately-timed discussion close. Regardless, an open-ended discussion reopen right now will just become us chewing our own cud and won't solve a thing. A reopen in response to a reflective statement/appeal by SashiRolls indicating how they would change their editing behaviour would be much more productive. The Arbcom interlude didn't resolve much, but did establish that while opinions how good it was may vary, the previous close is certainly not so egregiously bad to require just being set aside. That being so, let's continue the discussion if and when it has a hope of resolving the situation better, not as an exercise in procedural fairness or just trying to reverse the flow of time. Martinp (talk) 01:07, 10 July 2020 (UTC)
- Support per Guy's concerns. This is the nuclear option, the state of the consensus should not be in dispute. Springee (talk) 01:09, 10 July 2020 (UTC)
- Oppose per TonyBallioni & O3000. MastCell already gave further clarification specifically referencing weight of viewpoints at ArbCom,[7] which contradicts this idea put out there that they were just counting !votes. Most arbs were also not impressed with Sashiroll's WP:NOTTHEM behavior, dubious requests for extensions, etc., so even if the ban was overturned, there's a pretty clear indication that the behavior wasn't going to change after their final-final-final warning. Even if the !votes had been 50-50, it still could have been closed in favor of the ban because the continued problem was demonstrated that other sanctions had been exhausted (i.e., opinions no matter the percentage opposing the ban did not carry sufficient weight). That is how WP:CONSENSUS works.
- WP:CLOSECHALLENGE has guidance on following that up:
Simply believing a closure is wrong, even if reasonable people would have closed it differently, is not usually sufficient for overturning the result.
The better approach would have been to take the first step of asking MastCell on their talk page to add clarification to their close with respect to weight if that is really the sticking point. They gave a further explanation elsewhere, so we're at a point there would need to be a very high bar for reopening the discussion. When an editor has a history of tendentious behavior that's repeatedly established to the point of needing the "nuclear" option, part of a closer's discretion is to not let the discussion languish when the problems/endpoints are clear and the situation is unlikely to get better by letting it sit longer. There would need to be a pretty grand reason for exception at this point after both the initial close and what happened at ArbCom. Kingofaces43 (talk) 01:30, 10 July 2020 (UTC)
- Oppose per TonyBallioni & 03000. I found MastCell's reasoning to be very compelling, and SashiRolls has eaten enough of our time.--Jorm (talk) 01:39, 10 July 2020 (UTC)
- Support Not only do we need a fair process, we need the appearance of a fair process. I don't think we have that. I'm concerned about a number of issues: 1) that the discussion was still very much ongoing, 2) that the editor asked for a delay until the weekend and didn't get it, 3) that reasonable people could have reasonable concerns that the closer was "rushing" to the close due to a bias. I don't have a clue if the 3rd one is true, but the arguments for it (active in a similar area on opposite sides, only minimally active with admin actions) aren't crazy. A ban is a really serious thing and closing such a discussion should inspire confidence that the right process happened in addition to the right result. I don't think we are there at the moment. Hobit (talk) 01:42, 10 July 2020 (UTC)
- Comment - what arbs said about re-opening: "If people want to reopen the ban discussion for greater input, that's a community issue." [8] "nothing in the closure of the request would prevent further community discussion" [9] "giving leave to the community to decide whether to re-open" [10] "If the community wants to reopen the ban discussion or start a new one, it can be done without our involvement." [11] "there is nothing to stop the community from re-discussing the matter or overturning the close" [12] "leave it up to the community whether they wish to reopen the ban discussion" [13] the remaining 3 votes didn't address re-opening [14] [15] [16] Levivich [dubious – discuss] 01:50, 10 July 2020 (UTC)
- Oppose MastCell’s close was within admin discretion, Sashirolls participated and there was enough time for everyone to have their say. P-K3 (talk) 02:29, 10 July 2020 (UTC)
- Support - A close on false premises does not 'admin discretion' make, and particularly not on something as serious as a site-ban. Mr rnddude (talk) 02:38, 10 July 2020 (UTC)
- Oppose Sashirolls had plenty time to respond to the previous thread dozens of times, and they just kept digging themselves in deeper. Just their behavior during the discussion would be enough to justify a ban, never mind the constant battleground behavior and general unpleasantness they brought to basically every page they edited, plus the harassment that was the immediate cause of the discussion. Sashiroll's behavior in their arbitration request just confirms that they have learned nothing and will continue to cause problems if allowed back. Obviously, the correct result was reached, and that's what is important. Sashiroll can ask for a community appeal themselves if that's really what they want to do. Otherwise, this is just a pointless exercise. Red Rock Canyon (talk) 04:50, 10 July 2020 (UTC)
general unpleasantness they brought to basically every page they edited
- Every page? Sashi's top edited page is Yellow vests movement. Is there anygeneral unpleasantness
or any disruption on that page? How about their other top pages: 2019–2020 Algerian protests, Sudanese Revolution, or François Rabelais? Actually, Sashi's conflicts are limited to a small group of pages (e.g. Jill Stein, Bernie Sanders) and editors. Case in point: the antecedent to the site ban proposal was a partial block, not even disruptive enough to merit a full block. I think you exaggerate. Levivich [dubious – discuss] 05:38, 10 July 2020 (UTC)
- Support. "The close was within admin discretion" and "the discussion would benefit from being open longer and seeing more thoughtful input" are not mutually exclusive positions, and so I don't know why the former is being advanced as an argument against the latter. Furthermore, citing pieces of CLOSECHALLENGE out of context isn't helpful; this isn't so much about whether the close was wrong (I'm not certain it was) as that it was too soon. A site-ban discussion can always use more input, especially from uninvolved editors. Vanamonde (Talk) 05:10, 10 July 2020 (UTC)
- Since I'm the only one that cited CLOSECHALLENGE so far, I will clarify that nothing was cited out of context. It also does mention the aspect of the timing of the close being challenged sometimes, but my main focus was on the weight aspect many people had brought up in previous conversations before this one. Some mistakenly thought that MastCell basically ignored WP:!VOTE and basically tallied votes. There was an easier route to clarifying that wasn't the case before initiating this next step is all. It's not extremely rare for a request to the closer to add clarification to their close as part of that process. Kingofaces43 (talk) 05:56, 10 July 2020 (UTC)
- Comment - Not much comment on the wikilegal bureaucracy this particular thread concerns, but I want to point something out: in the time since the ban went into effect and discussion began about reopening discussion and doing an arb case request, instead of being introspective or acknowledging any problems, SashiRolls has spent hundreds and hundreds of edits creating userspace pages that continue to point fingers everywhere else. Far and away the biggest reason I supported a ban is because, from what I've seen, it seems like SR is quick to turn a disagreement into a personal investigation, digging up dirt, combing through user histories, finding patterns, connecting dots in conspiracies, making lists, making winking insinuations about motives, etc. It's fundamentally incompatible with healthy interpersonal communication/collaboration here. — Rhododendrites talk \\ 06:10, 10 July 2020 (UTC)
- Well, he did just get banned in what I think was a flawed process. That would cause a lot of people to get pretty upset and act poorly. That said, I suspect if this discussion does get reopened and he doesn't get banned it won't be long until he is unless he figures out how to behave here. If does get reopened I imagine that a lot of folks, including me, will be expecting to see evidence of improvements now. He seems to be a really productive contributor with big interpersonal skill issues (mainly a temper which also makes him really easy to troll). We've had a lot of those and most of them end up banned. But some improve. In any case, for me, it's a lot more about the process than the actual case at the moment. I'd like to see close ban discussions be taken at least as seriously a close RfA. This one wasn't IMO. Hobit (talk) 06:20, 10 July 2020 (UTC)
- Support I think we probably got the right result, but not in the right way. The close was made too soon - there were three discussions, all ongoing, the main one was trending toward oppose, and the user had requested a more nuanced ArbCom case where they would be able to address the concerns raised as they would be busy until the weekend (although the user had continued to comment in the thread, these do not appear to be considered posts, but quick emotional responses). The tally was vague and inaccurate - on my count there was less than 60% in favour of a ban, so not quite the 3/4 mentioned in the close. And the oppose views were not appropriately considered. I don't see a strong enough community support for a ban in that discussion. If we are to site ban this user (and it appears to me that SashiRolls is the sort of user we should be considering for a site ban because of their long history of personalising disputes with little understanding of how that impacts the individuals they are attacking and the wider community as a whole) then we should at least have the decency of allowing them to address the concerns raised, and to consider carefully the views of those in the community who feel a site ban is not appropriate. SilkTork (talk) 08:24, 10 July 2020 (UTC)
- Support review. ArbCom's decline to take the case does not mean they endorse the ban, just that a review of it is not within their remit. So that outcome says nothing about numbers of chances, bites of apples, etc. The ban itself is an issue where reasonable people can disagree and have opposite opinions, and I think there has been enough challenge to the closure of the ban discussion to warrant a review of it. I think SilkTork presents the problems perfectly, just above (and that's from someone who thinks a ban is probably the right result). We are, after all, talking about a total ban for an editor who has contributed a lot of content to Wikipedia, and I think anyone in that position deserves fair treatment and to be seen to have received fair treatment. Whether one supports the ban or opposes it (for the record, I oppose it), I would hope everyone would agree that we should have a fair review process - and I'd say exactly the same about a ban that I supported. Boing! said Zebedee (talk) 09:48, 10 July 2020 (UTC)
- I'll just add that I think MastCell's close was made in good faith, and that there's a strong argument that it was within admin discretion. But that does not mean it can not be challenged, and those who suggest otherwise do not appear to understand the basics of how Wikipedia admin actions work. All admin actions are open to challenge and review, be they good ones, bad ones, indifferent ones. All that's needed is a consensus to review. Boing! said Zebedee (talk) 09:54, 10 July 2020 (UTC)
- Oppose. I !voted at the SashiRolls' ANI to send the case to ArbCom to give them a full hearing (but did not !vote on the siteban issue), and even though ArbCom only considered MastCell's close, the 9-0 decision (and I assume ArcCom are familiar with the subject), makes me think we are at an end here. We have seen very good editors who – for various reasons – were just not compatible with editing on a collaborative project and had to leave. During the recent case, I have seen very reasonable editors like Cullen328, who advocated strongly for SashiRoll's most recent return, now !vote for their siteban. The long-term pattern is not good, and there is no evidence that it is changing. Regretfully, oppose and move on. Britishfinance (talk) 11:57, 10 July 2020 (UTC)
- Support review - that was not a great close at all. Only in death does duty end (talk) 12:05, 10 July 2020 (UTC)
- Support - the close was not unreasonable by Mastcell, but I think was based on a couple of premises that we might as well take the chance to clarify. If only, because satisfying more of the community that a ban issued in their name was reasonable is hardly a negative. Given some of SR's behaviour around everything, I'm actually more hostily inclined, but I view it as important to not skip a process just because it gets me the result I might want in that instance. Nosebagbear (talk) 12:14, 10 July 2020 (UTC)
- Support - I supported a ban and still do however it was closed too soon for my liking, Also supporting per Hobbit and NoseBagBear. –Davey2010Talk 12:19, 10 July 2020 (UTC)
- Oppose as a matter of procedure. The previous discussion was closed and closed properly. Arbcom reviewed it and agreed; so absolutely NO need to "re"-open. NOW if (and only if) SR were to request an unban, (with perhaps some considerations they'd be willing to give) and you were to say OPEN a NEW discussion - I might consider that. I know it's a silly point of order - but that's how wiki has always worked IMO. If you'd rather consider this a comment - then so be it. — Ched (talk) 13:40, 10 July 2020 (UTC)
- Oppose per TonyBallioni. I haven't been following the details of this saga, but I see absolutely nothing wrong with the AN close by MastCell, particularly in light of their reasoned defence of it at the ArbCom page. We promote our admins to make calls like these and unless it's completely out of left field (which with a 2:1 majority in favour of the ban doesn't seem plausible) we should accept the decision. — Amakuru (talk) 13:54, 10 July 2020 (UTC)
- MastCell certainly had the impression that it was 67%, which is why he closed it that way; but I have read through the discussion twice, and both times come up with a figure around 60% (59% first time, then 62% second time - some folks comments are not quite clear). I'd be interested in your own reading of the consensus tally in that discussion Amakuru. My view might be quite wrong, and it would be valuable to get a third admin opinion. SilkTork (talk) 14:45, 10 July 2020 (UTC)
- Oppose. While I was opposed to the community ban, I don't believe it is necessary for the community to re-open the discussion. I know much has been made about how "soon" the discussion was closed, but I would note it was kept open for nearly 72 hours, which certainly does more than just meet the 24-hour minimum. I also realize SR had asked for the discussion to be kept open until the weekend so they could have time to respond, but the fact that they contributed to the discussion more than 30 times (as was pointed out in the arbcom request) shows they in fact had time to respond. If Sashi wishes to be unbanned by the standard process, they are welcome to do so, but procedurally there was nothing wrong with the original discussion. Calidum 15:19, 10 July 2020 (UTC)
- Support - I believe MastCell gave a great explanation of the close rationale, but like Dennis Brown stated, reopening will "put the matter to bed" and then we can alleviate any doubt. Jauerbackdude?/dude. 15:57, 10 July 2020 (UTC)
- Oppose. As MastCell's explanation in the Arbcom thread amply demonstrates, the close was procedurally sound. Not only that, the outcome was substantively correct. There is no need for "putting the matter to bed" more than it already has been. Reopening the thread would just mean piling up a heap of pointless wikilawyering and drama. Nsk92 (talk) 16:24, 10 July 2020 (UTC)
- Oppose the way to "put this to bed" is to put this to bed, not to have another discussion about it. MastCell gave a lengthy explanation for the close at the ArbCom request and I don't see that there's any new arguments or anything else which would change the outcome. Dealing with disruptive users is a timesink. Hut 8.5 17:17, 10 July 2020 (UTC)
- Oppose definitely a close call, but within reasonable discretion to me. Cheers, all. Dumuzid (talk) 17:22, 10 July 2020 (UTC)
- Support- When the closing admins feels it is necessary to exaggerate the level of support, that's a bad close. If you are using good judgement, there's no reason to be dishonest.--Rusf10 (talk) 17:27, 10 July 2020 (UTC)
- Oppose – per Ched: the previous discussion was closed within admin discretion and Arbcom reviewed it and agreed. SR is free to request a new discussion of the ban at any time. Mojoworker (talk) 18:18, 10 July 2020 (UTC)
- Support per Rusf10. -- puddleglum2.0 18:41, 10 July 2020 (UTC)
- Support reopening. There were valid concerns raised and I don't see any downside in reopening a discussion especially when it is about sitebanning a user. Sir Joseph (talk) 18:45, 10 July 2020 (UTC)
- Support per Rusf10 and my reasoning at the arbcase request. The ban discussion suffered from a number of major procedural issues and cannot be treated as definitive for a discussion as contentious as this one has been. CactusJack2 (talk) 19:00, 10 July 2020 (UTC)
- I guess put me in the oppose camp, as the closer of the prior thread, but maybe that doesn't need to be said. My gut instinct is that these procedure-obsessed arguments obscure the fact that SashiRolls is fundamentally a poor fit for this project, and in some cases they're more a vehicle for people to pick a bone with me, personally, than the product of any conviction that SashiRolls is a net positive here. (That was evident in the WP:RFARB request as well). But maybe that's just my solipsism talking.
I guess I also think that, if you look around the world today and decide that the single greatest injustice worthy of your discretionary time and outrage was the closure of the SashiRolls's community-ban discussion, then we have different sets of priorities. Partly for that reason, I don't intend to participate in further wiki-litigation on this subject, other than to say that an admin would have to be crazy, stupid, or both to volunteer to close this or subsequent discussions. MastCell Talk 19:27, 10 July 2020 (UTC)
- I don't think anyone would dispute that there are far greater injustices currently going on elsewhere in the world. In fact, I'm not comfortable using the term 'injustice' to describe this situation at all. However, I'm puzzled by your apparent implication that real-world issues over which the average Wikipedian has little control should be preclude us from participating in this discussion. Any admin could respond to scrutiny of their admin actions by pointing out that there are more important things to worry about. I don't think it helps the situation for you to use red herrings to dismiss the scrutiny of your close. LEPRICAVARK (talk) 1:21, 11 July 2020 (UTC)
- I support reopening the discussion that was held here to consider banning SashiRolls. There are several important reasons why the discussion should be reopened:
- There was not a "consensus" for banning them at the time the decision was made, and
- The vast majority of editors here who commented in the later phases (e.g. a couple days after the discussion opened) opposed the ban.
- El_C, who in my mind was unfairly criticized by SashiRolls, nevertheless explained that they sought "no siteban or any other additional sanction against SashiRolls."
- SashiRolls has suggested that longstanding content disputes may be playing a role in (at least some) admin views towards them, and that probably deserves some investigation.
- A decision to ban a longtime and productive editor should be made on the basis of largescale community support. When a discussion by editors here has turned against banning, but a decision to ban is made anyway, that decision can come across as reckless. Using very powerful administrator tools in the such a context, and closing down discussion, would not be responsible.
- SashiRolls asked for one weekend to defend themselves, and that time was not granted. Some have written that SashiRolls' posts prior to the weekend prove no such time was needed. I find that to be an extraordinary position, and not the conclusion of an unbiased observer. First, if any of us take editing and collaboration here seriously, we know that some disputes on Wikipedia go back for many years. It is wholly legitimate that an explanation of conflict might take at the very least a weekend of research, and a few edits in the interim prove nothing otherwise. Suppose that after SashiRolls' request for more time, they had written nothing at all: could their silence have been used to ban them? With such faulty logic, any outcome no matter how unwarranted can be justified. Second, what is lost by waiting a week to ban someone? Editors were still commenting frequently, and our views are what determine consensus. Lastly, if someone asks for time when they may be banned, the least we can do is honor that request.
- I apologize if I offend any admins with these comments: I understand that admin work is difficult, and that work helps, among other things, keep the vandals at bay. But for regular contributors the bar for admin action is higher, and that's particularly true when we're discussing indefinite banning. -Darouet (talk) 20:05, 10 July 2020 (UTC)
- Oppose It was close, and a difficult decision to make, but the correct decision was made in the end. FWIW, if the consensus was close to NOT banning, and this question was asked I would felt the same way. I'm with MastCell. Any admin willing to take this up now has my sympathies. RickinBaltimore (talk) 20:14, 10 July 2020 (UTC)
- Neutral I agree with Vanamonde that closing within admin discretion isn't a strong reason to oppose reexamining a closure, and I agree with SilkTork and Nosebagbear that, even if the outcome is probably correct, it is worth being absolutely clear on that in this instance. What keeps me from supporting is that beyond the optics of the close, few people bring up valid problems with the outcome. Others have pointed out the weaknesses of the procedural points such as the length of time and being within discretion, and many of those in support acknowledge that they think the outcome was correct even if the close was not up to their standards. I don't think either side should be taken lightly, but WP:NOTBURO makes me lean towards considering whether we think the result was correct, and from the discussion here I don't see much reason to think it wasn't. I think the ideal course is to let SashiRolls make an unblock request themselves rather than decide an appeal on their behalf. This shouldn't be considered a veiled oppose---I agree with others that there's value in reopening the discussion---but I'm not convinced it's the ideal path for the community to take right now. — Wug·a·po·des 20:29, 10 July 2020 (UTC)
- Support per Sir Joseph (;tldr). Having seen the editor's username before but being unfamiliar with the rest of it, I had been watching the discussion intently and was looking forward to more discussion and the promised defence when it was unexpectedly (to me) closed. I disagree that the user's request for extension until the weekend is invalidated by their level of participation; they were reacting to a situation which requires much less time and effort than preparing a coherent defence. It is not lost on me that we are talking about banning a long-time editor. A request for unban is sure to require a much stronger consensus; it only makes sense that so should the ban. If there is a community consensus, it can only get more clear from prolonging the discussion, not less. Revisiting the issue doesn't amount to a verdict on the previous close one way or the other. Usedtobecool ☎️ 20:51, 10 July 2020 (UTC)
- Oppose as an unnecessary timesink. The close was adequately explained, 3 times the required length of time elapsed before the close, and there was a consensus to site ban. --Floquenbeam (talk) 21:13, 10 July 2020 (UTC)
- Oppose as I believe there was consensus for the block. And anyone who pulls out the ol' "reblocks are cheap" chestnut in the future should be forced to review this debacle in its entirety.-- Jezebel's Ponyobons mots 21:22, 10 July 2020 (UTC)
- Oppose as the close was well within administrative discretion, which also seems to have been the arbitrators' opinion. If SashiRolls has this much-ballyhooed "defense" they can write it in a ban appeal just like anyone else. All of this procedural wrangling is wasting all of our time. Ivanvector (Talk/Edits) 21:37, 10 July 2020 (UTC)
- Support per SilkTork. And the vote count fault is even more serious because the late votes were trending to opposing the siteban after El C's comment. That reminds of the vote trend discussion about bureaucrat RfA closes. SashiRolls should be allowed to present a defence with a less stressful time schedule, as the filer clearly had the time to his homework before presenting it as well. --Pudeo (talk) 22:42, 10 July 2020 (UTC)
- Oppose. First of all, there is WP:AAB#Appeals by third party, which indicates that SashiRolls has to initiate the process. If he wants a review, he can say so on his talk page, and the request can be copied to here. (And in that event, the discussion probably should be reopened.) In fact, there has been no notification of this discussion on his talk page. I'd also recommend that he post on his talk page the detailed response that he said he wanted to post in the original discussion if given more time, so that editors here can see that. It's strange to have the community try to evaluate the reopening prospect based on a request from a third party, and without the banned editor indicating whether or not he wants to go through it or what reasons he wants to give. Secondly, the community has a lot better things to do than to waste time on another discussion that will end up not changing anything. This really would be an unnecessary time-sink. And how many times does the community have to discuss this person, given how many problems there have been before? Thirdly, some editors don't much like MastCell's close, but it was a reasonable (and, I think, correct) close, so the case that it wasn't perfect does not mean that the participation of so many editors in the original discussion should be essentially set aside. ArbCom determined that the process wasn't manifestly flawed, and at most a further discussion will only determine that MastCell's close was reasonable and good-faith, but not unanimously agreed about. Fourth, SashiRolls' comments at the Arb request page are not particularly indicative that he will come forth with a good argument for leniency. Even though Guy advised him to take some amount of responsibility and avoid blaming others ([17]), SashiRolls' ended up saying "I will agree that I react badly to being continually targeted by a small group" of editors [18]. That's essentially saying that I regret that you treated me so badly. It's pretty unlikely that there will be a strong enough consensus to undo the ban. And finally, as I write this, the raw !vote count is 22 support and 24 oppose. Given how some editors clutched their pearls over the need that there be an overwhelming numerical consensus in these things, there better be a clear consensus to overturn the previous consensus. --Tryptofish (talk) 23:25, 10 July 2020 (UTC)
- I have gone ahead and notified SashiRolls via talk page template for completeness. Best, Darren-M talk 01:19, 11 July 2020 (UTC)
- Oppose: the close was within discretion and the user in question made 45 edits to the thread during the discussion, while also alleging they were being "lynched". The arguments about a
productive editor
are not convincing given the amount of community time already spent on various discussions. --K.e.coffman (talk) 00:25, 11 July 2020 (UTC) - Oppose as "an unnecessary time sink" to quote Floq. I recommend that this editor spend six months or more in self-reflection and attitude adjustment. An appeal based on an acknowledgement of the full range of past bad behaviors, and specific promises of much better behavior in the future, without any blaming of others, might well succeed. Cullen328 Let's discuss it 01:53, 11 July 2020 (UTC)
- Oppose - My review of the CBAN discussion and MastCell's explanation of the closing are sufficient to show that there was nothing wrong with the discussion or the close, and SashiRolls should remain site-banned. Common sense says so as well. Beyond My Ken (talk) 02:17, 11 July 2020 (UTC)
- Oppose Initial closure was correct and well reasoned IMO. I see no legitimate reason to continue beating this horse carcass. -FASTILY 02:58, 11 July 2020 (UTC)
- Comment ( I previously !voted above ): A number of oppose !votes are based on the view that the editor is happy with the outcome or that SR's is just going to waste more time. Those are arguments for the ANI discussion. They are not arguments as to if the closing was handled properly. The question here shouldn't be if SR was rightly CBAND. The question should be if the irregularities are sufficient to call the close into disrepute. The fact that so many editors are saying the close was bad is a serious issue. If we can't get a consensus that the close was good the ANI should re-opened (unarchived) to allow the discussion to continue and a new and better closing to occur else editors will rightly loose a level of faith in the system. Additionally, Mastcell's comments above should give editors pause. The comments aren't saying why the close was proper (thought they as defend their closing in the Arbcom discussion). Instead Mastcell states they don't think SR's is a good fit for Wikipedia. They may be right but as a closer they need to be an impartial arbiter of the arguments. Saying they think SR shouldn't be here certainly looks like a super vote. The closing must stand on the merits of how the closer weighed the arguments, not on the closer's personal feelings on the matter. Springee (talk) 03:19, 11 July 2020 (UTC)
- @Springee:I agree, Mastcell's comments above are just as bad if not worse than his close. When he says "My gut instinct is that these procedure-obsessed arguments obscure the fact that SashiRolls is fundamentally a poor fit for this project", he basically admitted that his close was a "super vote", not an objective assessment of consensus. In his mind, Sashi needed to be banned regardless so the procedure by which it was done doesn't matter. Then to cap things off he makes a afallacy of relative privation by comparing our complaint of his improper close to other injustices around the world. So Mastcell, next time you go to a restaurant and there is a problem with your food and you complain to the manager, I hope he tells you that you have no right to complain because there are starving people in Africa.--Rusf10 (talk) 05:42, 11 July 2020 (UTC)
- Support - for the most part per SilkTork but with difference regarding the result. I'm of the mind that community site bans should not be closed by a single admin., especially in cases where there are strong arguments on both sides. Atsme Talk 📧 05:02, 11 July 2020 (UTC)
- Oppose per Cullen328. – Majavah talk · edits 07:27, 11 July 2020 (UTC)
- Oppose The close was fine, there was enough time given for SashiRolls to respond, this is just wasting time. ThePlatypusofDoom (talk) 08:28, 11 July 2020 (UTC)
- Support the closing statement misrepresented the discussion by overcounting those supporting Sashi's ban. That ought to be a bigger deal, but seeing many admins in this thread come down against a questioning of an admin's potential mistakes is not encouraging. You can chalk just about anything up to "admin discretion," but misrepresenting a consensus ought not to be discretionary. Mr Ernie (talk) 09:55, 11 July 2020 (UTC)
- Oppose - ShashiRolls has been afforded more than adequate due process concerning their editing privileges on this privately owned website. MastCell's assessment of the CBAN discussion was a reasonable weighing of consensus. Arbcom did not "punt it back to us"; they declined an Arbcom case after the community banned an editor. That should be the end of it, unless and until ShashiRolls chooses to appeal the ban to the community. - MrX 🖋 14:31, 11 July 2020 (UTC)
- By my count, 6 of the 9 arbs plainly stated that this was a matter for the community to discuss further if we chose to do so. I don't know what you call that, but I call it punting the issue back to the community. LEPRICAVARK (talk) 22:10, 11 July 2020 (UTC)
- Support - While the whole thing met the bare minimum for procedure, it didn't seem as thorough as many bans have been. Combined with the fact it was on the bare edge of supporting for banning numerically, and I think redoing it more properly is a good idea. 74.124.47.10 (talk) 15:21, 11 July 2020 (UTC)
- Oppose - How many times are we going to re-litigate this matter? The close was a valid, proper assessment of community discussion, especially as measured by strength of arguments, and the outcome was substantively correct. Diffs were presented, both recently and from years earlier, demonstrating consistent battleground behavior and a campaign of harassment, as well as SR's extensive past block/sanction history. This misconduct has gone on for years and years (for just a flavor, see here) and SR has shown no willingness to conform his/her behavior to the community's (generous) norms. I would affirm the community's consensus to ban and move on. Neutralitytalk 16:13, 11 July 2020 (UTC)
- Neutrality, help me to understand, because I really am not able to, how it is "valid" or "proper" to misstate the vote count? Personally I have to think a valid and proper close would get that part right. That would simply not fly at RFA, for example. Mr Ernie (talk) 19:58, 11 July 2020 (UTC)
- Oh, I doubt that SashiRolls would pass an RfA. Beyond My Ken (talk) 03:00, 12 July 2020 (UTC)
- I dunno, hard to say given some that have made it. Though standards have gotten a lot tougher compared to the early days. Which may or may not help. PackMecEng (talk) 15:55, 12 July 2020 (UTC)
- Because, Mr Ernie, discussions are explicitly not a vote count. Why are experienced editors belaboring this supposed vote miscounting when we have a long-standing and unchallenged policy that these are not votes? Eggishorn (talk) (contrib) 18:11, 12 July 2020 (UTC)
- Eggishorn, maybe it's because the closing statement explicitly stated that it would be inappropriate to close the discussion as "no consensus" with >2/3 in favor of a ban, yet it wasn't true that >2/3 were in favor of a ban. And the close didn't weigh votes or address any specific diffs, incidents, or arguments. So, maybe that's why people are thinking the close should be re-opened, because it's not a vote. Levivich [dubious – discuss] 18:14, 12 July 2020 (UTC)
- That.....makes no sense. Your objection is: "The vote count was wrong so we need to count the votes right even though we don't count votes in determining consensus." There is no reason to call for re-opening a discussion on supposed miscounting. WP:NOTDEM:This is no a democracy, the discussion participants were not a jury, due process isn't a thing, and votes don't count. Eggishorn (talk) (contrib) 18:24, 12 July 2020 (UTC)
- Eggishorn, maybe it's because the closing statement explicitly stated that it would be inappropriate to close the discussion as "no consensus" with >2/3 in favor of a ban, yet it wasn't true that >2/3 were in favor of a ban. And the close didn't weigh votes or address any specific diffs, incidents, or arguments. So, maybe that's why people are thinking the close should be re-opened, because it's not a vote. Levivich [dubious – discuss] 18:14, 12 July 2020 (UTC)
- Because, Mr Ernie, discussions are explicitly not a vote count. Why are experienced editors belaboring this supposed vote miscounting when we have a long-standing and unchallenged policy that these are not votes? Eggishorn (talk) (contrib) 18:11, 12 July 2020 (UTC)
- I dunno, hard to say given some that have made it. Though standards have gotten a lot tougher compared to the early days. Which may or may not help. PackMecEng (talk) 15:55, 12 July 2020 (UTC)
- Oh, I doubt that SashiRolls would pass an RfA. Beyond My Ken (talk) 03:00, 12 July 2020 (UTC)
- Neutrality, help me to understand, because I really am not able to, how it is "valid" or "proper" to misstate the vote count? Personally I have to think a valid and proper close would get that part right. That would simply not fly at RFA, for example. Mr Ernie (talk) 19:58, 11 July 2020 (UTC)
- Oppose 69 users commented in the main banning discussion and SashiRolls made 9 posts. Any light that could have been shed on the topic was. The close was not an abuse of discretion or process and any claims that this should be reopened are just re-litigating the original discussion. Eggishorn (talk) (contrib) 19:05, 11 July 2020 (UTC)
- No, that's not my objection. My objection is that the close said
At a rough count, there were approximately 40 editors supporting a ban and ~18-20 opposed.
and that was incorrect. The close also saidWhile there is no numerical threshold for consensus, it would be inappropriate to close a discussion like this—with >2/3 of commenters supporting action—as "no consensus".
That sentence means that this discussion can only be closed as consensus for a ban, because a close of "no consensus" would beinappropriate
, because>2/3 of commenters supporting action
. Except, that's incorrect. It's not >2/3. Therefore, it's not inappropriate to close this some other way, such as "no consensus", under the closer's own logic. It's not me who's doing the counting, it's the closer. These are the only specific grounds given for the close. He makes no reference to any specific argument made by anyone, or to any specific incident, or to any specific diff, or to any specific policy. He just talks the numbers, and he gets the numbers wrong. Therefore, the close should be un-closed. That's reason #1. - Reason #2 is that 22 comments in the 17 hours prior to the close means it was closed too soon, especially with a swing towards oppose. That's a separate reason from the closing statement to re-open the discussion. Levivich [dubious – discuss] 18:53, 12 July 2020 (UTC)
- No, that's not my objection. My objection is that the close said
- Support - I did not participate in the original discussion but think it should be re-opened. Given the flawed analysis and how it was changing just before the close, with El_C's statement, I do not see why it could not of been left open until the weekend. Little copy edits and changes are not the same as having time to go through the evidence and properly respond to it. PackMecEng (talk) 04:02, 12 July 2020 (UTC)
- Support reopening the discussion. Per SilkTork, the votes were closer to 60% in favor of a site ban, but the thread was new and lively, with the more recent !votes weighing in against a ban. I'd also suggest a multiple-admin close. And in my opinion, the door should not be open to editors who are using WP and !votes only to continue past grievances, but who are essentially retired from building the encyclopedia. petrarchan47คุก 04:28, 12 July 2020 (UTC)
- Oppose - I think the arguments made at ArbCom relating to finding this to be within the closer's discretion are persuasive. I would decline a second community review for largely the same reasons that ArbCom chose to decline the case. We should not be looking here at whether we agree with the impacts of the close (i.e. whether we agree with the site ban), but rather whether we believe the close was so procedurally unfair that it merits starting from scratch. I do not believe that it does. Best, Darren-M talk 09:47, 12 July 2020 (UTC)
- Oppose. As K.e.coffman and MrX have described, there is no need for us to reopen the discussion, and this has taken too much community time already. I'd say an appeal in over six months would be a more reasonable path. ~ ToBeFree (talk) 12:14, 12 July 2020 (UTC)
- Oppose. Per TonyBallioni. Snooganssnoogans (talk) 16:03, 12 July 2020 (UTC)
- Oppose. I feel MastCell’s close was a well reasoned close, it seems evident that he carefully weighed the discussion. There is a consensus that this editor has caused ongoing disruption across many articles for a long time now; that is not to say editing opponents of SashiRolls have not caused some level of disruption too. Further reasons for supporting MastCell’s close was that additional comments to the ban discussion had slowed considerably, the editor in question had made dozens of posts to the discussion so their viewpoint was well known and they were given a fair hearing. Numerically there was clearly a consensus. The party to whom the ban applies, SashiRolls, can always apply for the ban to be partially lifted say, for example, after six to twelve months time. Then if continued improvement with a partial lifting occurs then they could ask for the ban to be fully lifted. This is my view on things anyway.--Literaturegeek | T@1k? 17:01, 12 July 2020 (UTC)
... discussion had slowed considerably ...
- There were 22 comments in the 17 hours before the close. Levivich [dubious – discuss] 18:17, 12 July 2020 (UTC)
- Oppose per Tony. There is nothing out of line with MastCell's closure. If you want to enforce a policy in a manner that is different than what is written, then you should be looking at changing that policy for future instances where something similar happens, which I believe is being done. Even so, changing that will not retroactively apply to this close, so relitigating it is unnecessary. Nihlus 18:21, 12 July 2020 (UTC)
Topic bans from articles based on unpaid COI, with no evidence of problematic editing?
Bnguyen1114 was the subject of an article on The Intercept recently about his edits to the Kamala Harris page. He was subsequently doxed/outed on Twitter and here. Following that, he disclosed that he has donated money to and volunteered for various politicians over the years. Based just on the fact of those COIs, SlimVirgin topic banned Bnguyen1114 from articles about all of the politicians he has volunteered for in the past "and their opponents", without evidence of any problematic editing regarding those subjects.
I find this unsettling. It may be that there's sufficient evidence provided in the Intercept piece and in the history of the various Kamala Harris pages for a tban about her, but topic banning someone from other subjects because of disclosed past unpaid volunteering, with no evidence of problematic edits of those subjects, does not seem in line with our WP:COI policy.
I'm not arguing that Bnguyen1114 doesn't have a COI, that all of his edits were good, etc. The central question here is whether it's ok to topic ban someone from several pages due not to evidence of problematic editing on those pages but to the fact of a disclosed unpaid COI. — Rhododendrites talk \\ 15:25, 10 July 2020 (UTC)
- Endorse. It looks to me like Sarah acted entirely appropriately. The COI precludes the user from editing those articles, but Sarah invited them to engage the respective talk pages. El_C 15:30, 10 July 2020 (UTC)
- Could you cite the policy text that says that disclosing an unpaid COI disqualifies someone from editing that article? Or that sanctions should be based on possible problems rather than evidence of problems? There's a spectrum of COI, and this isn't even at the far end of it. — Rhododendrites talk \\ 15:36, 10 July 2020 (UTC)
- It's a discretionary sanction, not per the COI policy. DS gives admins pretty broad discretion. ProcrastinatingReader (talk) 15:40, 10 July 2020 (UTC)
- ... And the user was alerted by Barkeep on 3 July to the existence of AP2 DS, so this action looks valid under DS. --Izno (talk) 15:46, 10 July 2020 (UTC)
- Izno, this comment has made me think. As a purely procedural point I would note that this editor disclosed their COI prior to 3 July (the date they were given the DS warning). After being DS warned, they did not edit Kamala Harris. They reiterated (effectively) the same COI disclosure after 3 July when Sarah asked at WP:COIN, a disclosure which resulted in their topic-ban. The only mainspace articles they've edited since the DS warning is adding list entries to List of Joe Biden 2020 presidential campaign endorsements. So this makes me wonder, can editors be sanctioned under DS for actions they committed before being warned of DS? The warning at WP:ACDS doesn't suggest this is forbidden, but it would make the requirement for warning moot if this were permissible. ProcrastinatingReader (talk) 22:07, 10 July 2020 (UTC)
- ... And the user was alerted by Barkeep on 3 July to the existence of AP2 DS, so this action looks valid under DS. --Izno (talk) 15:46, 10 July 2020 (UTC)
- Rhododendrites, it's right in {{uw-coi}}. El_C 15:43, 10 July 2020 (UTC)
- It's not, though. It provides suggested practices and says "avoid". These are indeed good practices, but it doesn't say you're prohibited from doing so, and doesn't acknowledge the spectrum of COI. By the same language, if I showed up for a day to phonebank for McCain in 1999 (I didn't), then it doesn't matter whether I've edited articles about him or how I edited them -- any admin can just come by and impose a topic ban "because DS"? — Rhododendrites talk \\ 15:50, 10 July 2020 (UTC)
- That's right, Rhododendrites. WP:ACDS is by definition at the discretion of the enforcing admin. El_C 15:54, 10 July 2020 (UTC)
- It's not, though. It provides suggested practices and says "avoid". These are indeed good practices, but it doesn't say you're prohibited from doing so, and doesn't acknowledge the spectrum of COI. By the same language, if I showed up for a day to phonebank for McCain in 1999 (I didn't), then it doesn't matter whether I've edited articles about him or how I edited them -- any admin can just come by and impose a topic ban "because DS"? — Rhododendrites talk \\ 15:50, 10 July 2020 (UTC)
- It's a discretionary sanction, not per the COI policy. DS gives admins pretty broad discretion. ProcrastinatingReader (talk) 15:40, 10 July 2020 (UTC)
- Could you cite the policy text that says that disclosing an unpaid COI disqualifies someone from editing that article? Or that sanctions should be based on possible problems rather than evidence of problems? There's a spectrum of COI, and this isn't even at the far end of it. — Rhododendrites talk \\ 15:36, 10 July 2020 (UTC)
- Endorse as I expressed a few days ago at Talk:Kamala Harris, I don't believe they were a bad faith editor or paid, but I do think their edits were problematic. In my lengthy reply at WP:COIN I noted specific diffs I believe to be problematic or attempting to remove unflattering information. Other admins like Drmies have labelled it problematic, as well. The topic ban is a DS, not per the COI policy, and I think the ban is well within admin discretion for DS, to ensure the smooth running of problematic areas. The editor in question can always appeal at WP:AE ProcrastinatingReader (talk) 15:39, 10 July 2020 (UTC)
- Endorse. Per WP:COICAMPAIGN. Quite frankly, a one-week block might have been too lenient given their attempts to whitewash the Harris article. Calidum 15:41, 10 July 2020 (UTC)
- Just to note, they weren't blocked for something relating to the Harris article, they were blocked for making an edit in violation of their topic ban. ProcrastinatingReader (talk) 15:45, 10 July 2020 (UTC)
- I'm aware. They both involve editing topics for which the user has a conflict of interest, however, and should not be editing. Calidum 15:55, 10 July 2020 (UTC)
- Just to note, they weren't blocked for something relating to the Harris article, they were blocked for making an edit in violation of their topic ban. ProcrastinatingReader (talk) 15:45, 10 July 2020 (UTC)
- Comment. Rhododendrites's accusation, unsupported by a diff, that Bnguyen1114 was
doxed/outed on Twitter and here
(emphasis added) is false. He was doxed/outed on Twitter, including confirmation of his identity (Redacted) by Katherine Maher, chief executive officer and executive director of Wikimedia Foundation, which owns and hosts Wikipedia. But he was not doxed/outed on Wikipedia. NedFausa (talk) 15:51, 10 July 2020 (UTC)- ^^ This is gross. I'm not going to link to evidence of being outed obviously, and it's outrageous that people are ok with Ned repeatedly linking to tweets that dox Wikipedians while claiming with a straight face that it means Maher "confirmed his identity" (or, as Ned said on Bnguyen's talk page, "found him guilty"). — Rhododendrites talk \\ 15:57, 10 July 2020 (UTC)
- It is certainly not okay. Redacted and strongly warned. What were you thinking, Ned? El_C 16:10, 10 July 2020 (UTC)
- FWIW I said "repeatedly" because there's another instance of the link that Ned just redacted on Bnguyen1114's talk page (but should be revdelled too), and both of these came after two other redacted edits last week on Bnguyen1114's talk page and at User talk:Katherine (WMF) (by Barkeep49 and Stwalkerster), but possibly for different reasons. — Rhododendrites talk \\ 16:19, 10 July 2020 (UTC)
- It is certainly not okay. Redacted and strongly warned. What were you thinking, Ned? El_C 16:10, 10 July 2020 (UTC)
- ^^ This is gross. I'm not going to link to evidence of being outed obviously, and it's outrageous that people are ok with Ned repeatedly linking to tweets that dox Wikipedians while claiming with a straight face that it means Maher "confirmed his identity" (or, as Ned said on Bnguyen's talk page, "found him guilty"). — Rhododendrites talk \\ 15:57, 10 July 2020 (UTC)
- I understand Rho's point and agree with the general proposition that volunteering for a political campaign should not, in and of itself, prohibit an editor from editing articles related to the candidate or their opponents. However, the devil is always in the details, and in this case, it all depends on what "volunteering" means, exactly. I'm not going to get into outing anybody but there is a difference between a person who volunteers to hold a sign on a street corner on a Saturday afternoon, and someone who volunteers, say, for a high-level leadership position within the campaign organization. In other words, there's a difference between being a "front line worker" volunteer, and being a "boss" or "executive"-level volunteer. It also matters if, for example, an editor's COI disclosures are accurate; if they're not (and I'm not saying they were or weren't in this case), but if they're not, that could be grounds for sanctions. In this particular case, putting together all the evidence, I think the TBAN was justified, and this edit definitely violated that TBAN, and so the block was justified. Still, I'd support some revisions to WP:COICAMPAIGN to clarify these issues and address the general problems Rho raises about volunteering and COI. Levivich [dubious – discuss] 16:22, 10 July 2020 (UTC)
- Question What the Hell is the WMF doing doxxing Wikipedia editors? It's bad enough when Wikidemocracy does it. (waves at many off-wiki fans). --Deepfriedokra (talk) 16:25, 10 July 2020 (UTC)
- Technically, Maher responded stating that doxing Wikipedia editors is wrong, she criticised the person who did it, although simply by responding she did inadvertently bring more attention to the dox. I don't think Maher actually confirmed or denied that identity, or did any checking to see if the dox was accurate. Her only mistake was responding at all, imo. ProcrastinatingReader (talk) 16:28, 10 July 2020 (UTC)
- It's important to note the timing here. Katherine Maher, in her official capacity, publicly corroborated the off-wiki outing of Bnguyen1114 and insinuated that he was guilty of COI, nearly five full days before that charge was made at Wikipedia:Conflict of interest/Noticeboard. NedFausa (talk) 16:38, 10 July 2020 (UTC)
- Ned, she strongly warned against the doxxing, though. That's pretty key. El_C 16:40, 10 July 2020 (UTC)
- No, she didn't. Someone on the Internet said "hey you have an editor with a COI" and she responded ~"COI is bad. so is doxing". That doesn't corroborate anything. You're repeatedly presenting this like Katherine Maher issued a statement on WMF letterhead explaining that somehow she knows the identity of Bnguyen1114 and confirms it is the person in the doxing tweet. It doesn't say that. It could be any tweet from someone saying "you have an editor with a COI" that she responded to with ~"COI is bad". It's frankly bizarre that you're repeatedly bringing up this tweet and engaging in hard core framing ("in her official capacity", "which owns and hosts Wikipedia", etc.) to make it say something it doesn't. — Rhododendrites talk \\ 16:54, 10 July 2020 (UTC)
- Tweeting from her verified account, Katherine Maher decried the off-wiki doxing. But significantly, Twitter neither suspended the account she responded to nor forced deletion of that tweet, which remains online despite Twitter's strong policies against doxing. Maher is a highly experienced Twitter user, having posted 27.5K tweets since joining that platform in 2008. It's fair to presume she is familiar enough with its rules to realize that the user she chastised did not violate them. I infer that she was at minimum grandstanding, if not trying to influence the outcome of the formal on-wiki COI case, which anyone knowledgeable about Wikipedia could by then foresee was inevitable. NedFausa (talk) 17:03, 10 July 2020 (UTC)
- You're suggesting Maher posted a tweet on July 2 to
influence the outcome of the formal on-wiki COI case
that was brought on July 8? Are you drunk? Levivich [dubious – discuss] 17:11, 10 July 2020 (UTC)- On July 3, even a drunk (and I'd never accuse Katherine Maher of insobriety) acquainted with Wikipedia's internal workings could have predicted that a formal COI case would ensue from The Intercept′s exposé. When Maher tweeted "You're both wrong" she obviously meant the Twitter user she was directly addressing and the person editing Kamala Harris's Wikipedia page, whom that user had identified through simple deduction and whom The Intercept had named as Bnguyen1114. NedFausa (talk) 17:28, 10 July 2020 (UTC)
- So your theory is that, in order to influence an on-wiki discussion she predicted would come in the future, Maher responded to a tweet by saying that both COI and doxxing is bad? That's insane. That's patently insane.
- You really should strike what you've written here about what Maher tweeted. "He was doxed/outed on Twitter, including confirmation of his identity, by Katherine Maher", "in her official capacity," "publicly corroborated", and "insinuated that he was guilty of COI" are all false accusations. These aren't matters of opinion where reasonable people disagree, these are straight-up lies. If you said these things about a fellow editor, you'd be sanctioned for it. Levivich [dubious – discuss] 17:38, 10 July 2020 (UTC)
- That's right, Ned. You are acting below par at this time. Please make an effort to do better. El_C 17:41, 10 July 2020 (UTC)
- On July 3, Katherine Maher tweeted that the person editing Kamala Harris's Wikipedia page was "wrong." That person (Bnguyen1114) had not doxed anyone. He had edited Wikipedia. How was he "wrong" in doing so if not by violating WP:COI? NedFausa (talk) 17:54, 10 July 2020 (UTC)
- Ned, you're not getting it and you should probably withdraw. You cannot cast aspersions on Katherine Maher with various conjecture. El_C 18:01, 10 July 2020 (UTC)
- NedFausa, I am puzzled; I thought you knew better. Levivich is correct: your assessment of the situation is wrong, and you're just adding fuel to the fire by those misrepresentations. There is no need to respond: refraining from further commentary on this matter is response enough. Please take El C's comment, above, as a final warning. Drmies (talk) 21:03, 10 July 2020 (UTC)
- Ned, you're not getting it and you should probably withdraw. You cannot cast aspersions on Katherine Maher with various conjecture. El_C 18:01, 10 July 2020 (UTC)
- On July 3, even a drunk (and I'd never accuse Katherine Maher of insobriety) acquainted with Wikipedia's internal workings could have predicted that a formal COI case would ensue from The Intercept′s exposé. When Maher tweeted "You're both wrong" she obviously meant the Twitter user she was directly addressing and the person editing Kamala Harris's Wikipedia page, whom that user had identified through simple deduction and whom The Intercept had named as Bnguyen1114. NedFausa (talk) 17:28, 10 July 2020 (UTC)
- You're suggesting Maher posted a tweet on July 2 to
- Tweeting from her verified account, Katherine Maher decried the off-wiki doxing. But significantly, Twitter neither suspended the account she responded to nor forced deletion of that tweet, which remains online despite Twitter's strong policies against doxing. Maher is a highly experienced Twitter user, having posted 27.5K tweets since joining that platform in 2008. It's fair to presume she is familiar enough with its rules to realize that the user she chastised did not violate them. I infer that she was at minimum grandstanding, if not trying to influence the outcome of the formal on-wiki COI case, which anyone knowledgeable about Wikipedia could by then foresee was inevitable. NedFausa (talk) 17:03, 10 July 2020 (UTC)
- Ned's description of Maher's tweets bear no resemblance to fact. Levivich [dubious – discuss] 17:05, 10 July 2020 (UTC)
- It's important to note the timing here. Katherine Maher, in her official capacity, publicly corroborated the off-wiki outing of Bnguyen1114 and insinuated that he was guilty of COI, nearly five full days before that charge was made at Wikipedia:Conflict of interest/Noticeboard. NedFausa (talk) 16:38, 10 July 2020 (UTC)
- Rhododendrites, I don't know what else can be said about this. WP:COICAMPAIGN is clear: "If you edit articles while involved with campaigns in the same area, you may have a conflict of interest. Political candidates and their staff should not edit articles about themselves, their supporters, or their opponents." If you're arguing that unpaid campaign workers don't count, I disagree. In addition, the article is covered by DS, which allows admins to impose sanctions, including topic bans. Taking all the circumstances into account, I thought it best to topic ban him from editing about the politicians for whom he said he had volunteered, and their opponents. SarahSV (talk) 21:39, 10 July 2020 (UTC)
- I'm unclear whether the DS sanction was in-process here. Bnguyen1114 was given a DS alert on 3 July and received the sanction on 8 July. Between those two events they made a handful of edits to List of Joe Biden 2020 presidential campaign endorsements but nothing I would consider excessive. The letter of the law says
No editor may be sanctioned unless they are aware that discretionary sanctions are in force for the area of conflict
but doesn't explicitly say that the editor must have made problematic edits, but I feel like that's kind of implied. I really mean this as a question (and not an implicit accusation) since I don't work AE, it just seems a little iffy from what I understand. GeneralNotability (talk) 23:56, 10 July 2020 (UTC) - I want to return to the "no evidence of problematic editing" phrase in the original post. I hold SarahSV in very high regard and learned a lot from her when I first started editing over a decade ago. And I have no problem with the topic ban she imposed on Bnguyen1114 regarding Kamala Harris, most obviously, and also Joe Biden. I have no problem with the short block. But I have some concern about the topic bans she imposed regarding Josh Harder and Claire McCaskill and their opponents. As far as I know, Bnguyen1114 has not edited either of those articles, and McCaskill is no longer in elected office. I feel uncomfortable with what looks like pre-emptive topic bans when there has been no known disruption by this editor regarding these two BLPs. The only basis that I can see is that the editor behaved inappropriately at the Kamala Harris BLP and later voluntarily disclosed without prompting that they had done volunteer work for the other two politicians. SarahSV, can you explain why you concluded that these two additional topic bans were necessary? And why you exempted Jill Biden from the Joe Biden topic ban, broadly construed? Cullen328 Let's discuss it 01:17, 11 July 2020 (UTC)
- Thank you for the kind words, Cullen. GeneralNotability, this is a reply to your post too. I've been discussing COI on Wikipedia for several years, and I helped to write the COI guideline. COI is not about advocacy, or good and bad editing. It's about a tendency to bias that we assume exists when people have real-life roles and relationships that conflict with their role on Wikipedia. It's about the disquiet within the community and the undermining of public confidence when those conflicts are not dealt with. Most COI editing takes place under the radar. But in the case of the upcoming U.S. election, everything is being scrutinized, and suspicions about COI harm everyone, including the candidates (most unfairly when they have no involvement). I therefore felt it was important to bring to an end the discussions about Bnguyen1114's editing, which were harming him too.Drmies expressed concern in May about Bnguyen's editing of Kamala Harris, and Jpgordon asked him to step back from it, but he continued. At 01:47, 3 July, he was alerted to the DS (although he was aware of them already from the Harris page). He continued editing about Joe Biden's endorsements. On 7 July, Pudeo opened a COIN, and during that discussion on 8 July, Bnguyen1114 disclosed that he had volunteered in 2018 for Claire McCaskill and Josh Harder, in 2019 for Kamala Harris, and in 2020 for Joe Biden. I therefore imposed a topic ban in relation to all four. You asked why I included McCaskill and Harder. It would have made no sense not to include them. Either he can edit about them or he can't; the topic ban covered the area of his disclosure. As for Jill Biden, he disclosed only having had his photograph taken with her, so I did not include her by name, but being banned from Joe Biden broadly construed would include family members. SarahSV (talk) 03:01, 11 July 2020 (UTC)
- It sounds like you're saying the tban isn't because of content policy violations/problematic edits or even necessarily because this COI is an example of an egregious enough COI such that it merits a preemptive tban, but because of the integrity of
public confidence
in Wikipedia. This seems to presume that some critical number of people who read the Intercept article will be able to follow on-wiki happenings and their concerns about Wikipedia will be assuaged by learning that he was topic banned/blocked. More importantly, going back to my original statement, I'm very uneasy with enacting sanctions against editors to send a message to external critics. As with any article-specific Wikipedia controversy, the process should be a highly visible investigation of the edits, using the talk page to discuss their merits/problems, and fixing what needs to be fixed. Maybe even writing up a summary in the Signpost for the external observers. But the editors involved should be treated just as anyone else. — Rhododendrites talk \\ 03:43, 11 July 2020 (UTC)- I don't recall ever having sanctioned someone to send a message to external critics. SarahSV (talk) 04:30, 11 July 2020 (UTC)
- Apologies if my indenting is incorrect, SarahSV, but I started donating to and volunteering for American political candidates way back in 1972, continuing right through the present moment. If I posted a list on Wikipedia of all the campaigns I voted and volunteered for, I would not expect to be topic banned from any of them unless I engaged in unacceptable editing behavior on specific ones of them. I will give you a specific example: I donated to and volunteered for the Walter Mondale presidential campaign in 1984. Should I be topic banned now from Mondale and Ronald Reagan, and every person that Mondale ever ran against? Even though I never disrupted those articles? Cullen328 Let's discuss it 05:22, 11 July 2020 (UTC)
- SlimVirgin, my query above is simply re the DS. I agree with your topic-ban (at least in principle), and as I stated above and at COIN and the other talk I do find the edits to be problematic, but per my response at the top of this section I'm also curious on DS' limitations here.
- The disclosure he gave to you on the 8th at COIN is pretty much the same as the one he gave on 2 July in Special:Diff/965696863. All his editing at Kamala Harris, and the COI disclosure, were made prior to the DS notice. After the DS notice, as far as mainspace edits go, he only added uncontroversial bullet list items to List of Joe Biden 2020 presidential campaign endorsements. It doesn't seem procedurally correct to sanction an editor based on DS, for actions done prior to notification. And although WP:AC/DS doesn't explicitly prohibit this, it does seem to go against the point of requiring a warning using an unmodified {{ds/aware}} template before you can sanction an editor. The notice on Kamala Harris' talk isn't sufficient per AC/DS#Awareness. So while I agree with the tban, I just want to query if this is indeed procedurally correct? Because, if it is, this kind of DS enforcement makes the very strict & specific alert/awareness requirements moot. For clarity, I don't disagree that the block was warranted per your topic-ban, I'm only questioning if the topic-ban itself was correct per the above. ProcrastinatingReader (talk) 03:53, 11 July 2020 (UTC)
- It sounds like you're saying the tban isn't because of content policy violations/problematic edits or even necessarily because this COI is an example of an egregious enough COI such that it merits a preemptive tban, but because of the integrity of
- Thank you for the kind words, Cullen. GeneralNotability, this is a reply to your post too. I've been discussing COI on Wikipedia for several years, and I helped to write the COI guideline. COI is not about advocacy, or good and bad editing. It's about a tendency to bias that we assume exists when people have real-life roles and relationships that conflict with their role on Wikipedia. It's about the disquiet within the community and the undermining of public confidence when those conflicts are not dealt with. Most COI editing takes place under the radar. But in the case of the upcoming U.S. election, everything is being scrutinized, and suspicions about COI harm everyone, including the candidates (most unfairly when they have no involvement). I therefore felt it was important to bring to an end the discussions about Bnguyen1114's editing, which were harming him too.Drmies expressed concern in May about Bnguyen's editing of Kamala Harris, and Jpgordon asked him to step back from it, but he continued. At 01:47, 3 July, he was alerted to the DS (although he was aware of them already from the Harris page). He continued editing about Joe Biden's endorsements. On 7 July, Pudeo opened a COIN, and during that discussion on 8 July, Bnguyen1114 disclosed that he had volunteered in 2018 for Claire McCaskill and Josh Harder, in 2019 for Kamala Harris, and in 2020 for Joe Biden. I therefore imposed a topic ban in relation to all four. You asked why I included McCaskill and Harder. It would have made no sense not to include them. Either he can edit about them or he can't; the topic ban covered the area of his disclosure. As for Jill Biden, he disclosed only having had his photograph taken with her, so I did not include her by name, but being banned from Joe Biden broadly construed would include family members. SarahSV (talk) 03:01, 11 July 2020 (UTC)
- ProcrastinatingReader, I cannot speak for Sarah, but with respect to procedure, the discretion authorized for admins by WP:ACDS, allows for AE action in this instance. Yes, even if the optics may not be that great in the limited sense of the post-WP:AWARE edits not having been particularly problematic. El_C 04:08, 11 July 2020 (UTC)
- El C, say, hypothetically, he had made no mainspace edits post-notification (pretending those edits at List of Joe Biden 2020 presidential campaign endorsements didn't happen), and hence this topic-ban would be based solely off pre-notification actions, would you say that topic ban is still permissible (per WP:ACDS)? ProcrastinatingReader (talk) 04:12, 11 July 2020 (UTC)
- ProcrastinatingReader, failure to satisfy the requirements of WP:AWARE would make it against procedure to impose sanctions. El_C 04:16, 11 July 2020 (UTC)
- El C, sorry, let me clarify a bit... The scenario I'm trying to understand is: editor does something stupid, they get a DS notification, they get sanctioned for that pre-notification stupid thing they did. In this scenario, they are sanctioned after the warning, but for actions before the warning. WP:AWARE doesn't seem to explicitly say this isn't allowed? Applied to my hypothetical above, the editor was given the DS notice on the 3rd. Say he didn't make those edits on that list article about Biden, would it be permissible for an admin to give him a topic ban on the 4th as a DS, for his edits prior to notification on the 3rd? ProcrastinatingReader (talk) 04:20, 11 July 2020 (UTC)
- ProcrastinatingReader, no, it would not be permissible in that scenario. El_C 04:23, 11 July 2020 (UTC)
- ProcrastinatingReader, his 2 July post was not the same as his COIN disclosure on 8 July; the latter was more specific. It was then that he acknowledged having worked as a volunteer for Biden and Harris, his main topics: "In 2019, I volunteered on Kamala Harris' presidential campaign. In 2020, I phonebanked for Joe Biden's presidential campaign in the run up to the New Hampshire primary."I'm curious about the amount of interest in this. This is an SPA, created in November, that focused on Biden and Harris: 2,682 edits, 97.5 percent to mainspace; 1,626 edits to List of Joe Biden 2020 presidential campaign endorsements; 11 talk page edits. The topic ban is limited to his disclosure; he's blocked only because he violated it immediately. He was alerted to the DS and he continued making edits about Biden. How many should I waited for? Five edits, 50? SarahSV (talk) 04:27, 11 July 2020 (UTC)
- SlimVirgin, just the one :) -- I was only curious on the awareness part for the t-ban itself. I think El C cleared some of that up for me. I guess 'discretion' applies even wider than the wide interpretation I had for it before, with regards to the list edits (clue's in the name, I suppose). I was only curious about procedure, not your judgement. ProcrastinatingReader (talk) 04:39, 11 July 2020 (UTC)
- From upthread
The only mainspace articles they've edited since the DS warning is adding list entries to List of Joe Biden 2020 presidential campaign endorsements.
and the ban placed:is required not to edit certain articles because of a disclosed COI. The affected articles are anything to do with Joe Biden, Kamala Harris, Claire McCaskill, Josh Harder, and their opponents
. I read the ban in question as being "broadly construed" without using that wording (it should have, I think), of which List of Joe Biden 2020 presidential campaign endorsements is among the set of articles broadly construed. That's 100% a topic ban violation. Sometimes we give leeway to oldhands here and there as they adjust and sometimes we give leeway to new hands to see if they really can find something new to edit, but a SPA for these articles doesn't really fit into those categories. I think SV's actions here were within administrative remit. I also agree with El_C's interpretation, but that interpretation isn't interesting here if so. --Izno (talk) 04:41, 11 July 2020 (UTC)
- El C, sorry, let me clarify a bit... The scenario I'm trying to understand is: editor does something stupid, they get a DS notification, they get sanctioned for that pre-notification stupid thing they did. In this scenario, they are sanctioned after the warning, but for actions before the warning. WP:AWARE doesn't seem to explicitly say this isn't allowed? Applied to my hypothetical above, the editor was given the DS notice on the 3rd. Say he didn't make those edits on that list article about Biden, would it be permissible for an admin to give him a topic ban on the 4th as a DS, for his edits prior to notification on the 3rd? ProcrastinatingReader (talk) 04:20, 11 July 2020 (UTC)
- ProcrastinatingReader, failure to satisfy the requirements of WP:AWARE would make it against procedure to impose sanctions. El_C 04:16, 11 July 2020 (UTC)
- ProcrastinatingReader, I cannot speak for Sarah, but with respect to procedure, the discretion authorized for admins by WP:ACDS, allows for AE action in this instance. Yes, even if the optics may not be that great in the limited sense of the post-WP:AWARE edits not having been particularly problematic. El_C 04:08, 11 July 2020 (UTC)
IP Users 74.111.2.34 and 24.177.130.98 promoting false, biased, dangerous, and unsourced information about COVID-19
On the page for Security Theater, these users have promoted information that currently poses a public health hazard:
https://en.wikipedia.org/w/index.php?title=Security_theater&action=history
The revision in question: https://en.wikipedia.org/w/index.php?title=Security_theater&type=revision&diff=967010122&oldid=966999876 — Preceding unsigned comment added by Lfax-nimbus (talk • contribs) 15:56, 10 July 2020 (UTC)
Semi-protected for a period of 2 weeks, after which the page will be automatically unprotected. El_C 16:00, 10 July 2020 (UTC)
Thousands of strange edits to Vietnam geography
Do the edits by 30ChuaPhaiLaTet (talk · contribs) look familiar to you? I'll notify them, but I'm not going to discuss it with them on their talk page--I have the feeling I'm not going to get an answer. Drmies (talk) 20:36, 10 July 2020 (UTC)
- Tobias Conradi, maybe? The pattern of haphazardly moving things around and a fixation on obscure bits of geographical subdivisions fits, and his incarnations regularly change focus (I've seen him hit Mexico, Belarus, and East Timor at different times). The Blade of the Northern Lights (話して下さい) 21:01, 10 July 2020 (UTC)
- The Blade of the Northern Lights, what if there were a few more such accounts, with similar names, making the same kinds of edits? Drmies (talk) 21:06, 10 July 2020 (UTC)
- Yep, that sounds about right. See here for one of the more spectacular messes. The Blade of the Northern Lights (話して下さい) 21:13, 10 July 2020 (UTC)
- The Blade of the Northern Lights, what if there were a few more such accounts, with similar names, making the same kinds of edits? Drmies (talk) 21:06, 10 July 2020 (UTC)
- Drmies, you never actually attempted to discuss the problem with me, yet you brought it to the noticeboard and claiming that "I have the feeling I'm not going to get an answer". Does that even make any sense?
- If you need an answer, then what I'm doing is creating stubs about locations (mostly about capitals). However, instead of creating a new page, I drafted the article in a redirect and then move it to the correct title. For example, when I created the article about Sóc Sơn, the capital of Sóc Sơn District, I drafted it on Soc Son, which is initially a redirect to Sóc Sơn District and then moved it to the correct title, Sóc Sơn, Hanoi 30ChuaPhaiLaTet (talk) 21:42, 10 July 2020 (UTC)
- The slightly stilted English seems awfully familiar too... The Blade of the Northern Lights (話して下さい) 22:41, 10 July 2020 (UTC)
- Yeah, 30ChuaPhaiLaTet, let me discuss a couple thousand edits with you on your talk page after you couldn't be bothered to respond to anyone else. Later! Drmies (talk) 00:46, 11 July 2020 (UTC)
- The Blade of the Northern Lights, what about all these moves? I'm about to add the accounts to the SPI and I rolled back the regular edits, but there's more to do. Drmies (talk) 00:52, 11 July 2020 (UTC)
- If it turns out to be him, we'll have to revert all the moves too; I did this with Eldizzino, that was around 1,500. As an aside, could some tech people please make a mass move revert tool? The Blade of the Northern Lights (話して下さい) 01:12, 11 July 2020 (UTC)
- Yes, mass move revert tool is really badly needed.--Ymblanter (talk) 10:13, 11 July 2020 (UTC)
- Do you think it'd be worth making some noise for it at WP:VPT? It gets annoying to have to spend several days cleaning up the messes Conradi's socks create. The Blade of the Northern Lights (話して下さい) 16:09, 11 July 2020 (UTC)
- Yes, it might help, may be worthwhile opening a topic.--Ymblanter (talk) 19:14, 11 July 2020 (UTC)
- I don't see a listing for conradi at WP:LTA, maybe I just missed it? Those listings can be helpful to other editors attempting to clean up behind a LTA sockpuppet. Is it worth it to create one? Eggishorn (talk) (contrib) 19:08, 11 July 2020 (UTC)
- Yes, I think it is worthwhile to create one, especially since TC has a number of characteristic features making them easy to detect.--Ymblanter (talk) 19:14, 11 July 2020 (UTC)
- Do you think it'd be worth making some noise for it at WP:VPT? It gets annoying to have to spend several days cleaning up the messes Conradi's socks create. The Blade of the Northern Lights (話して下さい) 16:09, 11 July 2020 (UTC)
- Yes, mass move revert tool is really badly needed.--Ymblanter (talk) 10:13, 11 July 2020 (UTC)
- If it turns out to be him, we'll have to revert all the moves too; I did this with Eldizzino, that was around 1,500. As an aside, could some tech people please make a mass move revert tool? The Blade of the Northern Lights (話して下さい) 01:12, 11 July 2020 (UTC)
RfC: Wikiprofessionals Inc, and paid editing
![]() |
|
Should we site ban Wikiprofessionals, a paid-editing ring, from the project? ——Serial # 09:24, 11 July 2020 (UTC)
- A more comprehensive analysis can be found at Wikipedia:Conflict of interest/Noticeboard#wikiprofessionals inc. Sockpuppet investigations are at Wikipedia:Sockpuppet investigations/Belmop and Wikipedia:Sockpuppet investigations/BrookeCook/Archive
On WP:COIN, we have discovered a paid editing firm known as Wikiprofessionals Inc. The firm dates back to the early 2010s, and is suspected of creating multiple articles. This is a list of what articles Wikiprofessionals is suspected of creating:
- Claimed by company
- Wissam Al Mana (edit | talk | history | links | watch | logs)
- Gaby Natale (edit | talk | history | links | watch | logs)
- David F. D'Alessandro (edit | talk | history | links | watch | logs)
- Rachel Cruze (edit | talk | history | links | watch | logs)
- Shaherose Charania (edit | talk | history | links | watch | logs)
- James D. Marks (edit | talk | history | links | watch | logs)
- Pete Flint (edit | talk | history | links | watch | logs)
- Linx Cargo Care Group (edit | talk | history | links | watch | logs)
- Standard Media (edit | talk | history | links | watch | logs)
- Odibets (edit | talk | history | links | watch | logs)
- XING Mobility (edit | talk | history | links | watch | logs)
- Russell McVeagh (edit | talk | history | links | watch | logs)
- Delivery Hero (edit | talk | history | links | watch | logs)
BATS Chi-X Europe (edit | talk | history | links | watch | logs)(created too early for this company, but subject to substantial promotional SPA editing thereafter)- Brown & Brown (edit | talk | history | links | watch | logs)
- TheBlaze (edit | talk | history | links | watch | logs)
- Firefly Aerospace (edit | talk | history | links | watch | logs)
- Day Software (edit | talk | history | links | watch | logs)
- Pedego Electric Bikes (edit | talk | history | links | watch | logs)
- Neil Young (video game executive) (edit | talk | history | links | watch | logs)
- More created by the editor who created Neil Young (video game executive)
- Brian Farrell (video game executive) (edit | talk | history | links | watch | logs)
- Frank Gibeau (edit | talk | history | links | watch | logs)
- Aaron Loeb (edit | talk | history | links | watch | logs)
- Kevin Chou (edit | talk | history | links | watch | logs)
- Eric Schiermeyer (edit | talk | history | links | watch | logs)
- Mike Verdu (edit | talk | history | links | watch | logs)
- Roger Dickey (edit | talk | history | links | watch | logs)
- Bill Jackson (video game designer) (edit | talk | history | links | watch | logs)
- Paul Bettner (edit | talk | history | links | watch | logs)
- John Schappert (video game executive) (edit | talk | history | links | watch | logs)
- Mark Skaggs (edit | talk | history | links | watch | logs)
I, along with Bri and BD2412, support a site ban for Wikiprofessionals and their related accounts. We do not want another Wiki-PR and Orangemoody on our hands. Personally, I just think that paid editing firms are unethical and goes against Wikipedia's mission. SuperGoose007 (Honk!) 23:50, 10 July 2020 (UTC)
- Support. The firm is actually (we think) "Get Wikified" but has a habit of spinning off different brand names, over two dozen of which are listed at WP:PAIDLIST#Get Wikified. PAIDLIST also documents several OTRS tickets related to their drumming up article-creation business (pretending to represent Wikipedia officially) that was later reported to the WP community. As far as I know there is not a single editor with proper paid disclosure related to this group. You can find more background/documentation at this COIN thread (2019) ☆ Bri (talk) 23:56, 10 July 2020 (UTC)
- Well, this one have the same quotes of get wikified on their web site The creeper2007Talk! Be well, stay safe 03:23, 11 July 2020 (UTC)
- Support Clear and deliberate breach of a range of our policies, most notably WP:COI. Nick-D (talk) 23:58, 10 July 2020 (UTC)
- Support. Note that an WP:SPI investigation has been opened at Wikipedia:Sockpuppet investigations/Belmop. BD2412 T 00:03, 11 July 2020 (UTC)
- I am ambivalent about deletion, as some of the articles created have been substantially de-puffed by intervening editors, but I would definitely support moving them to draftspace with a note about their questionable origin for a thorough scouring before restoring to mainspace. BD2412 T 00:55, 11 July 2020 (UTC)
- Support a site ban as a blot on Wikipedia. Should the articles included in the list above be (speedy) deleted? --K.e.coffman (talk) 00:08, 11 July 2020 (UTC)
- Support deletion of the listed articles. Listing each at AfD would be yet more community time dedicated to these bad-faith editors. --K.e.coffman (talk) 15:29, 11 July 2020 (UTC)
- Support site ban and (reluctantly) deletion - we have to teach a lesson to customers as well as spammers: hire the scum and see the "article" deleted. --Orange Mike | Talk 00:14, 11 July 2020 (UTC)
- Support site ban and deletion per WP:TNT. If any of the subjects they made articles about are notable, they can be recreated with no credit to them whatsoever. Ian.thomson (talk) 00:34, 11 July 2020 (UTC)
- Oppose. I'm not clear how a site ban against the company as a whole would be effective in practice - we clearly can't innately know who is editing on their behalf. We would already block repeated violations of WP:PAID anyway. I have no qualms with us levying a site ban against individual editors for this, but banning the organisation seems symbolic and ultimately futile. I'm also opposed to mass deletion - let's work through articles and assess against usual standards instead rather than going nuclear. Best, Darren-M talk 00:45, 11 July 2020 (UTC)
- It isn't just a matter of bookkeeping - Banning a user means that their edits can be reverted/deleted on sight once it is clear they're another wikiprofessionals/Get Wikified mercenary. —A little blue Bori v^_^v 2020's a bust; thanks SARS-CoV-2 00:50, 11 July 2020 (UTC)
- The only way we're likely to know that they're a member of the organisation is if they disclose per PAID, in which case they're then being sanctioned for abiding by the policy that the organisation was banned for breaching. Seems like a non-sequitur to me. Banning the organisation will just encourage them to continue editing in a clandestine way. Darren-M talk 01:26, 11 July 2020 (UTC)
- It isn't just a matter of bookkeeping - Banning a user means that their edits can be reverted/deleted on sight once it is clear they're another wikiprofessionals/Get Wikified mercenary. —A little blue Bori v^_^v 2020's a bust; thanks SARS-CoV-2 00:50, 11 July 2020 (UTC)
- Comment 2 points. 1) Perhaps would've been worth waiting until after the SPI to make this, since there's possibly (probably?) other accounts we're unaware of, since we only got this list from one source. So, if we get more accounts (hence articles) due to a CU check those should probably be added to this. 2) I'm not sure how I feel about mass-deleting these pages, many of which are noteworthy and some not too promo, but if mass-deletion encourages these companies/people to chargeback the company, perhaps the company will abide by WP:PAID next time, so perhaps it's the greater good. Not sure. ProcrastinatingReader (talk) 00:46, 11 July 2020 (UTC)
- Support ban and deletion - If they never cared enough to abide by the Terms of Use and disclose and did everything in their power to stay under the radar, then they're not someone we want around. There is a right way and a wrong way to be a mercenary on Wikipedia, and if you insist on the wrong way then we're not obligated to host your trash. —A little blue Bori v^_^v 2020's a bust; thanks SARS-CoV-2 00:50, 11 July 2020 (UTC)
- If these are established articles that other editors have worked on, policy pretty much prevents us from deleting them en masse. They can be cleaned up and if they aren't notable, sent to AFD, but deleting all of them isn't really kosher unless you go through them one by one and determine if they are valid articles. Dennis Brown - 2¢ 01:06, 11 July 2020 (UTC)
- I would also note that there are some articles which this company has claimed to have created which they clearly did not (including articles that preceded their apparent existence and created by well-established editors). The articles that we have identified are those that are claimed by the company as their own, and that were created by obvious SPAs that typically were only active for a few months, at most. There is a slim possibility that some articles so identified are still innocent, so some further review is warranted prior to deletion. BD2412 T 01:22, 11 July 2020 (UTC)
- Support. Undisclosed paid editing and persistent abuse clearly warrants a ban. Regarding deletion, moral support but that should probably be a separate proposal laying out the individual or group basis for including articles in the list or other relevant points. I haven't looked at the individual articles and I think we'd want a bit more detail and examination before spamming the delete button. Alsee (talk) 01:18, 11 July 2020 (UTC)
- Comment. Any of these articles that seems to merit deletion can go to AfD. I notice that James D. Marks is there already. -- Hoary (talk) 01:35, 11 July 2020 (UTC)
- Support ban
and draftifying- The onus is against these articles, so send them to draftspace, where they can worked on and moved back into articlespace if warranted. Beyond My Ken (talk) 02:05, 11 July 2020 (UTC)
- After looking through a bunch of these, I'm changing my !vote to Support and delete. Editors wanting specific articles to be undeleted can use WP:REFUND and explain why. Just as with sockpuppetry or site-banned editors, it's important that undisclosed paid editors not see their dishonesty rewarded. Beyond My Ken (talk) 02:44, 11 July 2020 (UTC)
- I added some other articles in case of draftification; some are G5/G11 noms already ☆ Bri (talk) 02:26, 11 July 2020 (UTC)
- Note: there is nothing CU can do here. Drmies (talk) 02:13, 11 July 2020 (UTC)
- I support a ban here. I support banning all commercial editing. I’ll add on to what Drmies said above CheckUser is rarely useful against paid editing these days for a few reasons. Admins should block under WP:NOTSPAM when they see it and not wait on CU. TonyBallioni (talk) 03:04, 11 July 2020 (UTC)
- Support Ban and deletion I support to ban all of the users and to delete all of their pages. If there are any pages that are actually worth keeping, we could refund it (and try give no credit for the company due to their dishonest moves). Note: The company(on their Q&A) acknowledge this policy but calls Ignore all rules a loophole for the whole COI thing(obviously not)The creeper2007Talk! Be well, stay safe 03:23, 11 July 2020 (UTC)
- I think we should run a CU also. The creeper2007Talk! Be well, stay safe 05:47, 11 July 2020 (UTC)
- Ban, delete, do not pass go, do not violate WP:COI. Per BMK, anyone who wants to take responsibility for improving work produced by TOS violators can ask for undeletion. ♠PMC♠ (talk) 04:19, 11 July 2020 (UTC)
- Support - ban, delete blatant promo, others send to draft or userfy - nope, not good for our volunteer spirit, the project or our reputation. Atsme Talk 📧 04:40, 11 July 2020 (UTC) On 2nd thought, I clarified. 13:21, 12 July 2020 (UTC)
- Site ban, but not a fan of deletion. If you think an article should be removed, send it to AFD. (For example, Firefly_Aerospace looks fairly reasonable after multiple editors-worth of rework.) --Izno (talk) 04:46, 11 July 2020 (UTC)
- Support ban and deletion per above. "Hire UPE, get your article deleted." Sending the articles to AFD puts the burden on volunteer time. Editors are more important than pages: we shouldn't ask our volunteers to review the work of UPE. Just delete it. Levivich [dubious – discuss] 05:11, 11 July 2020 (UTC)
- To be clear, I only support deleting the articles we know were the work of UPE; I have no idea if the specific articles on the above list are all eligible or not, or if there are others that aren't on the list. Levivich [dubious – discuss] 18:01, 11 July 2020 (UTC)
Oppose I work for this companySupport duh Naleksuh (talk) 05:16, 11 July 2020 (UTC)- Ban and delete. Mccapra (talk) 05:17, 11 July 2020 (UTC)
- Comment: Of Frank Gibeau (among the list above), we don't learn much; but we do learn that "Gibeau's 2016 compensation as Zynga's CEO was $24.5 million." So there could be quite a lot of moola sloshing around this vanity article racket. -- Hoary (talk) 06:34, 11 July 2020 (UTC)
- Support ban and deletion per above. The way to restore the asymmetry in our favour is that we take such action whenever we discover UPE – E.g. despite paying your money, your PAID article has to evade detection every day until the end of time, whereas Wikipedia only needs be lucky on one of those days and your article is gone. Britishfinance (talk) 07:24, 11 July 2020 (UTC)
- We should also automatically WP:SALT every article that has been deleted as WP:PAID, which would increase the asymetry even further, and head-off the legion of 50-edit new editors that instantly re-apppear to re-create these deleted articles (normal editors can apply to get them released). Britishfinance (talk) 09:59, 11 July 2020 (UTC)
- Support ban and deletion per Levivich. AFD is also risky - it is not uncommon to see ads on freelancing websites for keep votes at AFD. It is also not uncommon to see socks show up to get spam pages retained at AFD too. MER-C 08:30, 11 July 2020 (UTC)
- @SuperGoose007: what is your brief and neutral statement? At over 2,000 bytes, the statement above (from the
{{rfc}}
tag to the next timestamp) is far too long for Legobot (talk · contribs) to handle, and so it is not being shown correctly at Wikipedia:Requests for comment/Wikipedia policies and guidelines. The RfC may also not be publicised through WP:FRS until a shorter statement is provided. --Redrose64 🌹 (talk) 09:02, 11 July 2020 (UTC)- @Redrose64: I've boldly added a short statement which should be picked up by the bot, does that work? Of course, SuperGoose007 should feel free to change/ re-sign it when they're back. ——Serial # 09:24, 11 July 2020 (UTC)
Thank you It looks fine; we'll find out for sure at 10:01 (UTC) - when Legobot next updates WP:RFC/POLICY. --Redrose64 🌹 (talk) 09:44, 11 July 2020 (UTC)
- @Redrose64: I've boldly added a short statement which should be picked up by the bot, does that work? Of course, SuperGoose007 should feel free to change/ re-sign it when they're back. ——Serial # 09:24, 11 July 2020 (UTC)
- Support ban/ deletion per Thomson/ Levivich. To coin a phrase, since this material is clearly contentious, it seems only fair that the onus be on those wishing to keep the contested material in mainspace. ——Serial # 09:18, 11 July 2020 (UTC)
- Support ban, and deletion where no other editor has participated significantly - there might have been a benefit in a broader CU-op on the accounts (a la OM) before coming here, but in any case, a ban seems reasonable. I'm also increasingly thinking that we should consider any known director of a banned UPE company as "carrying" that status to any new organisation. I've backed a CSD criteria in the past for clearly badfaith UPE (that is, where a username is the company name, I'm okay to let them disclose if they do so on demand rather than insta-CSDing), so long as no other editor has participated significantly. Nosebagbear (talk) 11:14, 11 July 2020 (UTC)
- Support site-ban and deletion. We can't keep content created in violation of the Terms of Use, regardless of whether others have edited it or whether the topic is notable – the TOU take precedence over any other consideration. We urgently need to establish a process for immediate removal/deletion of all WP:UPE, just as we unquestioningly remove or delete copyright violations. Justlettersandnumbers (talk) 11:36, 11 July 2020 (UTC)
- Perhaps WP:IAR should be amended to note that the Terms of Use do in fact override. It is "ignore all rules" that this firm was using as their raison d'être. ☆ Bri (talk) 15:24, 11 July 2020 (UTC)
- Which, if they'd bothered to read IAR, they would have realised that isn't how it works. Writing blatantly promotional material and editing sans disclosure are disruptive, whereas IAR only applies to actions that would benefit the encyclopaedia if not for the rules. And even then, IAR does not override Foundation-derived policy or the ToU. —A little blue Bori v^_^v 2020's a bust; thanks SARS-CoV-2 16:41, 11 July 2020 (UTC)
- Support site-ban, deletion and salting as default provided the evidence that the article was created in violation of terms of use is good on balance of probability, but if anyone wants to nominate specific articles for draftification which they are willing to decontaminate, that would be OK. · · · Peter Southwood (talk): 11:45, 11 July 2020 (UTC)
- Support bans and deletions. I agree entirely with Levivich: sending the articles to AFD puts the burden on volunteer time. Compare Wikipedia:Buy one, get one free and don't ask our volunteers to review UPE work. Since the company has apparently falsely claimed some articles as theirs, review is warranted (were they created by SPAs typically only active for a short time? Delete!), but AFD is not. Deletion will surely be a stronger strike against UPE editing than bans of long since inactive SPAs. (I'm not saying they shouldn't be banned; they should.) How hard will it be for the individuals involved to create new accounts and write new articles? Incredibly easy, considering how soon CU evidence goes stale. (I won't say how soon, because WP:BEANS.) Bishonen | tålk 12:32, 11 July 2020 (UTC).
- Procedural/administrative question: are we sure that all of these pages were created for pay? I remember when WikiWhateverIt'sCalled started advertising their services, and we found they were claiming TONS of pages that were likely not written by them. Haven't looked at the pages, but it's a concern when I see so many people clamoring to immediately delete with no review (and yes, I know there is also a group saying that only those pages that haven't been edited, which is better). Primefac (talk) 12:43, 11 July 2020 (UTC)
- They did claim a bunch of pages which they didn't create (see COIN discussion), but those were omitted here. I believe the above list are the pages from the list on their site which turned out to be created by SPAs. Though this isn't certainty that they were created for pay (or, even if they were for pay, that it was this company which created them), but it's probably the closest we can get to certainty given their opsec. ProcrastinatingReader (talk) 16:05, 11 July 2020 (UTC)
- I took the liberty of striking out one which was created in 2007. It may have later experienced UPE which we can just revert or edit out. ☆ Bri (talk) 16:28, 11 July 2020 (UTC)
- @Bri: Whether or not BATS Chi-X Europe was created by this company, it has a long history of SPA edits, and certainly bears scrutiny. BD2412 T 17:50, 11 July 2020 (UTC)
- Support bans and deletions No. Just no. RickinBaltimore (talk) 13:04, 11 July 2020 (UTC)
- Support bans but review the articles before deleting them. Wikipedia needs to vigorously defend itself from being used as an advertising billboard, so the offending spammers have to be shown the door. The articles shouldn't be given the benefit of the doubt but I'd prefer them to be given at least a quick appraisal before being deleted. Reyk YO! 15:34, 11 July 2020 (UTC)
- Support ban but oppose deletion without review. I went through that list and recognised one of them as a major NZ law firm who were recently in the news a lot. This in itself doesn't mean much but if this paid editing firm dates back to the early 2010s, can someone explain to me how they created an article on 2006 [19]? The creator was active for that short time and disappeared Special:Contributions/Lawgeek18, so the possibility of it being paid can't be easily ruled out but it illustrates the problem with deleting articles just because someone has claimed they were created for pay without evidence. Either they've been around for a lot longer then early 2010s or they weren't the creator. Even looking at the major edits after creation, I see [20] from 2008 and [21] from 2013 by the same editor which whatever their flaws, look to be an editor with a genuine interest in NZ law etc over a long period of time Special:Contributions/Sammy2008, i.e. not likely someone who was part of the paid editing farm. Special:Contributions/Tessatelle contributions in 2017 look questionable [22] [23] except they seem to have been mostly rejected by User:Drmies anyway [24] [25]. This [26] which is by an editor Special:Contributions/MarkoMetal who does seem to be associated with the paid editing farm (I'm assuming from the block log) which is interesting since it doesn't seem to be the sort of thing the law firm would pay for. It could be a competitor, but I wonder if more likely it was content added to try and seem like an innocuous editor. I guess an additional possibility is they recognised that there was no way that the content could not be covered in our article, and so tried to get ahead of good faith editors by adding a section but keeping it as mundane as possible. That section has undergone major changes and IMO it would be weird not to cover it (it was a big deal in NZ). Still, I can perhaps see people arguing for deletion of even the current version of that section for complete recreation by someone who isn't violating the ToU. But the whole article? Finally I see [27] which seems to be from a public library in the Lower Hutt library system [28], IMO it's unlikely it's from a paid editing farm. Nil Einne (talk) 17:07, 11 July 2020 (UTC)
- Has wikiprofessionalsinc even claimed all those articles? I looked at the 'portfolio' on their website, I don't see where they say they created those articles. Whether they created them, worked on them, whatever seems unclear from the website. I looked at the chat, and I don't see whey they said they created all those articles they listed on their website. Nil Einne (talk) 17:20, 11 July 2020 (UTC)
- @Nil Einne: My review of their claimed articles was not aimed at determining whether they were created for pay, but whether there was evidence that they were subject to COI editing. That said, almost all of the articles on the list were created by SPAs doing clearly promotional work. Of course, there were also some articles "claimed" by them which were created much earlier by established Wikipedians and with no indication of COI editing at any point along the way. In examining the claimed articles, I erred on the side of suspicion. BD2412 T 17:55, 11 July 2020 (UTC)
- @BD2412: Wait what? That mean's if an article was created earlier by established Wikipedians with indication of COI editing after creation they are in the list? Only articles created by established Wikipedians with no indication of COI editing are saved? That's even worse. At first I thought this list had no review. Then I look more carefully and find there was review, although as I said, at least with the Russell McVeagh, the creation has a question mark even if it's well before the claimed time frame and at least some of the major contributors don't seem to be associated with the paid editing farm, and of the only editor clearly associated with the paid farm added negative information. The proposal here is to delete all the articles listed. WTF would we deleted articles created by established Wikipedians just because some fuckhead paid editor edited at one point of time? Delete the fucking COI editing. Don't delete the work of the established Wikipedians! Even in cases of copyvio problems, surely far more serious, we may delete any contributions after the copyvio was added including from editors acting in good faith because we can't hope to recover the non copyvio from the copyvio. But if there is a version before the copyvio, we revert to that. Sorry I find this so disgusting I don't think I'll be participating further. Nil Einne (talk) 18:11, 11 July 2020 (UTC)
- @Nil Einne: My review of their claimed articles was not aimed at determining whether they were created for pay, but whether there was evidence that they were subject to COI editing. That said, almost all of the articles on the list were created by SPAs doing clearly promotional work. Of course, there were also some articles "claimed" by them which were created much earlier by established Wikipedians and with no indication of COI editing at any point along the way. In examining the claimed articles, I erred on the side of suspicion. BD2412 T 17:55, 11 July 2020 (UTC)
- Has wikiprofessionalsinc even claimed all those articles? I looked at the 'portfolio' on their website, I don't see where they say they created those articles. Whether they created them, worked on them, whatever seems unclear from the website. I looked at the chat, and I don't see whey they said they created all those articles they listed on their website. Nil Einne (talk) 17:20, 11 July 2020 (UTC)
- Comment (EC) I've mentioned this discussion at Wikipedia:New Zealand Wikipedians' notice board. (This was before I read the above reply, as I said there, I won't be participating further.) Nil Einne (talk) 18:11, 11 July 2020 (UTC)
- Ban and delete every contribution - Wikipedia is not a PR tool and violating our policies on such a large scale is irredeemable. - MrX 🖋 18:22, 11 July 2020 (UTC)
- Oppose if there is confirmed UPE I would support a ban and deletion, but these are probably not their articles and accounts. Peter James (talk) 18:34, 11 July 2020 (UTC)
- In this case, if there isn't UPE then this is Orangemoody redux, as we already know they're loosey-goosey with the facts and have claimed credit for pages that others have worked on. Either they're mercenaries or they're scammers; either way they should be excluded. —A little blue Bori v^_^v 2020's a bust; thanks SARS-CoV-2 18:48, 11 July 2020 (UTC)
- Support site ban. HOWEVER: we really have no proof, as far as I can see, if any of the stated accounts or edits or articles are theirs. We should review articles for UPE and notability as per usual.ThatMontrealIP (talk) 18:39, 11 July 2020 (UTC)
- Support site ban and deletion of articles created by them I appreciate that that will delete pages of notable companies and individuals but the best remedy to combat this kind of behaviour is to be staunch and nuke the lot. It gets more complex when they added to articles created by legitimate users. In that case, I suggest we revision delete up to the point prior to their involvement. Schwede66 19:49, 11 July 2020 (UTC)
- That would only hold if no-one had made a single substantive edit at any stage during or after their edits. I am against acting on articles not created by them, it's just asking for issues. Nosebagbear (talk) 21:53, 11 July 2020 (UTC)
- Support ban and delete Unchecked abuse just encourages more abuse. Sensor1776 (talk) 01:08, 12 July 2020 (UTC)
- Support ban and deletions. I don't like deleting articles that might have some value, especially if other editors have improved them. But when we see this kind of insidious abuse of Wikipedia policy and of basic ethics, we need to send the strongest message we can and try to attack these people where it hurts most - in the wallet. Boing! said Zebedee (talk) 07:23, 12 July 2020 (UTC)
- Support ban and delete Unchecked abuse just encourages more abuse. Sensor1776 (talk) 01:08, 12 July 2020 (UTC)
- Ban, but we cannot delete work to which good faith editors have substantially contributed on the basis of G5. And we cannot delete as contrary to the claims of serice unless we have evidence thatit actually is. It's common for undeclared paid editors to claim credit forwork they have not done. Usually they do this to buildup an impresive but false resume, but sometimes it's to harass competitors.. The way yo deal with bad articles on nonnotable people is to delete them. The way to do with hopelessly promotional articles that could not be rewritten if usually to delete them as G11, but the much better way if the person or organization is really so important that readers would expect to find an article is to stubbigy or merge or redirect. We should not use afch, because far too many articles sent there never get fixed; subiffying or merging, the original methods, at least provide some information for the readers while a proper article is writtten by a good faith editor. DGG ( talk ) 07:44, 12 July 2020 (UTC)
- As a longer range solution, it seems that these bad faith promotional editors seem to be able to convince reasonably respectable companies and people, including acadeics who should know better, that their paid editing will be acceptable; this is to a considerable degree because of our comoplicated rules, by which some paid editing if declared according to the correct technicalities declared is acceptable. We can fix this ourselves, without the WPF; we can fix this simply and immediately, by resolving that 'No paid editing shalll ever be permitted on the enWP. . We have the right to make requirements for enWP beyond the WMF's TOU. If other language WPs wish to follow us, that's their look out. (to be fair, there will be a number of problwms, such as dealing with existing articles, and improving requests for articles and requests for changes. (I have no personal animus against declared paid editors as people--at least two are personal friends, and I think both of them recognize their practices are not really defensible) DGG ( talk ) 07:44, 12 July 2020 (UTC)
- Ban, Delete, Snow. Zero tolerance for UPE. Cabayi (talk) 12:25, 12 July 2020 (UTC)
- Support ban and deletions. According to their FAQ page (Internet Archive: 20200712120055, "wikiprofessionalsinc" .com, subpage "faqs"), their justification for policy violations is using WP:IAR as a "loophole". They "absolutely" "guarantee acceptance of the article to Wikipedia", stating that "there is no doubt that it will be accepted". We should change this, indefinitely. ~ ToBeFree (talk) 12:27, 12 July 2020 (UTC)
- Support ban and deletions - Paid editing like this should not be tolerated on this website, If these articles are found to be notable they can be recreated by neutral editors, Deleting these would show we're serious and that paid editing like this won't be tolerated here. –Davey2010Talk 15:18, 12 July 2020 (UTC)
- Support site ban, deletion and salting of articles created by these accounts: As Britishfinance suggests above, there is a need to establish asymmetry such that the consequences are worse than neutral for a firm's clients. AllyD (talk) 15:58, 12 July 2020 (UTC)
Note about CheckUser and paid editing
I'm writing this just as myself and without having consulted the team, but as there are several people asking for CheckUser above, I think it is worth giving a longer explanation of changes in behaviour here over time. As a bit of background, I've been involved with paid stuff from an SPI angle since at least early 2017, which was before I was an admin. I continued to help in the area as a sysop, and initially was fairly involved as a CU with paid cases.
In the 3.5 year timeframe I mention, we have seen a pretty large shift in how the paid editing model works. Previously we would regularly see fairly large sockfarms of 10, 15, 20, 30 plus accounts. These invariably were operating on VPNs, and given the degree of coordination and the technical details of some of them, they were likely in the same physical location, either being coworkers or the same person.
In 2018 and 2019 User:SQL and myself started a project that for the most part blocked the overwhelming majority of commercially available VPNs from en.wiki. User:Jon Kolbert, after his election as a steward, began a similar project on a global scale, and earlier this year, ST47 created a bot that targeted other types of open proxies on en.wiki. The combined result of these efforts is that while possible, it is difficult for a commercial operation to maintain a profitable sockfarm by relying on VPNs.
Over 2018 and 2019 as the impact of these blocks began to manifest, there was actually a sharp decline in the number of large sockfarms for paid editing. What instead became apparent from the technical and behavioural data was a few things:
- Different people were writing the same commissioned articles
- The people were unlikely to be working in collaboration with one another
- The majority of spam we were seeing was coming from freelancers, not marketing firms
I can think of a specific case where we know for a fact that the individual who was commissioned to write the article was living in North America, but where the accounts involved in its creation were operating from two different cities on another continent. These were white-label products being farmed out to individual people. When there are multiple people in multiple locations showing up, CheckUser is going to show them as Unrelated because they are.
I'm saying all this because I think there is a lot of misunderstanding in the community of how these organizations currently work. Risker did a lot of work with the Orangemoody investigation, and can speak to how it was then, but the type of commercial editing we're seeing today has a very different model from Orangemoody. I see Ivanvector has commented at SPI against fishing in a case, and Drmies above has already indicated that CU can't do much. I'll send a note to checkuser-l in case there is anyone else from the team who wants to comment here on what they have seen, but I think that the community should be aware of what our limits are in terms of effectiveness. We'll look at cases where there appears to be socking, but our time is one of our most valuable assets, and trying to figure out if two different freelancers are the same person usually isn't that useful. Especially in the time of COVID, where even if they work for the same firm, they're probably on their home wifi and won't show up related.
Administrators should block spam as they see it and not wait for CU if it is obviously a violation of our core content policies. We relied on CU for a long time to help deal with paid editing, but it is becoming less useful now as our other tools to fight against the mass paid farms have worked extremely well. TonyBallioni (talk) 03:39, 12 July 2020 (UTC)
- Let’s talk about how admins can block spam when they see it. Suspected spammers, or only after they confess or have a WP:DUCK outcome at SPI? Draftify or delete? Tony, this is not a criticism of you; you have done and continue to do a good job of policing this area. But I think we are in a bit of a limbo wrt proper procedures for well intentioned admins. Is there an admin field guide to a) identifying actionable material and b) what to do once it is positively identified? You made a very good case for not depending on checkuser for (a), but now what? It is very frustrating for all concerned to file what feels like a solid SPI report only to have it returned as "too late for cu" or whatever. And an SPI "warrant" is really the key to g5 else the whole system grinds to a stop under the weight of the full blown AfD process times tens to hundreds of bad-faith article creations. This RfC is certainly a special case, we can’t sustain a community ban for every entity on WP:PAIDLIST. ☆ Bri (talk) 05:00, 12 July 2020 (UTC)
- Bri, no need to worry about offending me. We've worked closely together in the past on this stuff and I still really value the work of people at COIN even though I'm less involved there than I used to be. My motivation for posting this is that while we've discussed this as a CU team on calls and trainings, I don't think it really has been communicated as well to the community, so I want to be clear what they can expect from us.In terms of how admins can handle it, my thought process would be something like this: is an account clearly creating promotional content? If yes, have they created content elsewhere on the project? If the answer to that is no, they're a spam-only account and they should be blocked. Our policy is not "you can spam unless you sock" it is "you cannot create promotional content." If the content isn't bad enough for G11, it can be dealt with after the block by PROD or AfD by other uninvolved editors at COIN or ANI. When I'm going through SPI and I get to a case where it is clearly just two freelancers, I block them both as a regular admin action for promotion.We've done a pretty good job at decreasing these large farms, and we're now at a level where a bunch on lone wolfs and white-label writers are trying to make a buck. That's a lot easier to be dealt with effectively at the regular admin level without functionary involvement if its clear what is going on from the edits. TonyBallioni (talk) 05:22, 12 July 2020 (UTC)
- as a checkUser myself, although not a very active one, I agree with Tony. There's usually no need for a check. Promotional editing is clear enough on the face of it. Specific undeclared paid editors are often clear enough, wihtout checkuser, and the way they work , usually makes the additional information from checkuser not really necessary or worth the trouble.At present, if there's really as case of private information or doxing or impersonation, I think the sipler course is to invovle arb com directly. Back 3 years ago, arb com was less willing to get invovkled , so therere was a reason for using checkusers instead. That is no longer the case. DGG ( talk ) 07:55, 12 July 2020 (UTC)
- Bri, no need to worry about offending me. We've worked closely together in the past on this stuff and I still really value the work of people at COIN even though I'm less involved there than I used to be. My motivation for posting this is that while we've discussed this as a CU team on calls and trainings, I don't think it really has been communicated as well to the community, so I want to be clear what they can expect from us.In terms of how admins can handle it, my thought process would be something like this: is an account clearly creating promotional content? If yes, have they created content elsewhere on the project? If the answer to that is no, they're a spam-only account and they should be blocked. Our policy is not "you can spam unless you sock" it is "you cannot create promotional content." If the content isn't bad enough for G11, it can be dealt with after the block by PROD or AfD by other uninvolved editors at COIN or ANI. When I'm going through SPI and I get to a case where it is clearly just two freelancers, I block them both as a regular admin action for promotion.We've done a pretty good job at decreasing these large farms, and we're now at a level where a bunch on lone wolfs and white-label writers are trying to make a buck. That's a lot easier to be dealt with effectively at the regular admin level without functionary involvement if its clear what is going on from the edits. TonyBallioni (talk) 05:22, 12 July 2020 (UTC)
- Just noting that while I agree with the message Tony is delivering, it is definitely sometimes still useful to run a checkuser, as we can often pick up large farms of socks and articles. I's still quite common to come across large UPE farms through checkuser. It's difficult for a non-CU to distinguish between a freelancer meat farm and a paid sock farm, I appreciate that. Sometimes - perhaps often - a CU will say that nothing can be done, or they won't look for whatever reason. But sometimes something can be done. So as Tony says, don't necessarily wait for a CU, but also definitely don't afraid from requesting one. -- zzuuzz (talk) 08:26, 12 July 2020 (UTC)
- I agree with everything that's been said. In response to the ping: I declined that case because we're required by policy to see justification for a check before using the tool; I don't see it but offered that I would take another look if a more concise case could be made. With respect, I think that the filer doesn't understand SPI very well: for one, of the 29 accounts listed, only three can actually be checked. Several that cannot are already related to other investigations which were certainly not involved in paid editing, which indicates to me that the filer has not really investigated and is counting on the CU to do it for them, and that's not our role (as I had said, checkuser is not for fishing, and I hadn't said it but the clerks' job is not to make your case for you, though they often do comment on evidence and/or dig up their own).
- I may be quicker than some to decline investigations ported from COIN, for the reasons TonyBallioni suggests, that we're unlikely to find anything useful for a COIN investigation. COIN investigates multiple accounts working together commercially, while SPI investigates multiple accounts operated by one person: CU tools really can't do anything else. We've been advised recently that "suspicion of paid editing" is not in and of itself sufficient grounds for checking, and I tend to agree. There can be overlap between COIN and SPI, and like zzuuzz says we can sometimes uncover large operations when they're technically related (but as Tony says they're more often not these days), but we need to see valid suspicion of sockpuppetry supported by evidence before we can check. That's the rules we're given. All that said, and despite Arbcom being more assertive about compliance in the last year or so, that bar is still pretty low honestly.
- As for what can "regular" admins do to counter paid editing? Advocate for stronger policies against it. We're evidently still relying on these paid operations to do something else wrong (like sockpuppetry) before they can be blocked. That strongly indicates (to me) that our policies against this activity don't go far enough. I don't have suggestions to offer in this regard, just commentary. Ivanvector (Talk/Edits) 11:29, 12 July 2020 (UTC)
- Range blocks work well on some ISPs. Depends on the ISP. NinjaRobotPirate (talk) 12:24, 12 July 2020 (UTC)
- Just in regards to Tony's comments above, one of the things I've been noticing recently - especially in regards to sites like Freelancer - is that a large portion (and posisbly a majority) of paid editing jobs are being subcontracted to other paid editors once someone is hired, with a preference towards people who do not have a history of socking. I recently was curious about the extent of this and started mapping the relationships between paid editors on Freelancer, but we're looking at situations ranging from people who are regularly hired but always subcontracted, to people who subcontract 10-30% of their work, and of the major paid-editing accounts I could identify well over half were subcontracting in some fashion. This would create CU problems, because even if you know which sockmaster was originally hired to perform the task, it could be a completely different farm (or not a farm at all) that then does the job. This isn't insurmountable from a DUCK perspective, but does damage the effectiveness of CU. - Bilby (talk) 12:36, 12 July 2020 (UTC)
- Bilby, yes, that’s what I’m getting at. As I mentioned above, I can think of one case where Freelancer or Upwork, etc. confirmed the identity of the person and that they were in North America. The accounts that created the article(s) they had been hired to create were from two distinct locations using two different devices on legitimate ISPs on a different continent than North America. The Upwork person had subbed the work out white-label. In cases like this, CU isn’t going to help you, and I agree that subcontracting is likely the majority practice these days. TonyBallioni (talk) 15:08, 12 July 2020 (UTC)
- It is close to being the majority practice of Freelancer. I was suprprised just how often I'd see a FFreelancer have reviews from other Freelancers whom I know are doing paid WP work. Not only does it help avoid CU, but it hides the job, as the subcontractor just hires someone for "wikipedia editing" without specifying what the work is for, even if the original advertisement was more specific. (Although duck blocks based on original job remain viable). In the case of Upwork there are fewer clear cases of subcontracting from other freelancers as it is against their ToU, but there is a much higher percentage of subcontracting from companies such as Wikiprofessionals Inc. Just looking quickly today, in the last 48 hours 1/5 of WP editing ads on Upwork are very likely to be subcontracting, but the problem is less about number of ads as the number of separate jobs each ad can represent. - Bilby (talk) 15:58, 12 July 2020 (UTC)
- Bilby, yes, that’s what I’m getting at. As I mentioned above, I can think of one case where Freelancer or Upwork, etc. confirmed the identity of the person and that they were in North America. The accounts that created the article(s) they had been hired to create were from two distinct locations using two different devices on legitimate ISPs on a different continent than North America. The Upwork person had subbed the work out white-label. In cases like this, CU isn’t going to help you, and I agree that subcontracting is likely the majority practice these days. TonyBallioni (talk) 15:08, 12 July 2020 (UTC)
- Thank you TonyBallioni and Bilby for these details, they're very informative and do inform on what is most useful. This would need to be a separate discussion, but it's probably also worthwhile having a discussion on other potential methods (such as fr-wiki's use of "fake buyers", which I suggest we'd want community sign-off and a degree of ARBCOM oversight, were we to go that route). Nosebagbear (talk) 13:06, 12 July 2020 (UTC)
- @TonyBallioni and Ivanvector: both suggest that a change in policy could help here (Tony's was way above, saying that he supports banning all commercial editing). I've had some mixed feelings on this. Often it seems that we have the policies, it's just that they aren't enforced. Other times it seems like we have people willing to enforce the policies, but it seems like there is a glitch in the way many people interpret the policy. I suppose we should just take one step at a time, whichever will be more effective at the time. Coming up with a new policy on Commercial editing would probably be effective now. So all we need to do is define commercial editing, ban it, make it easy to enforce. I will suggest that we leave WP:Paid editing disclosure alone - since it is part of the ToU it has special status and is very difficult to revoke. If we were to go through the complete process to change the disclosure process, the resulting policy would be weaker (easier to change) than the combination of the current disclosure policy plus a new policy on commercial editing. This is not the best place to discuss a new policy - can somebody suggest the best place to take this? Smallbones(smalltalk) 16:03, 12 July 2020 (UTC)
- Yes, I’d support a ban on commercial editing and specifically phrase it that way so that the “What about WiRs/WMF employees” strawman doesn’t derail the discussion like it does every time any policy change in this area is discussed. Something I disagree with Ivanvector on to an extent is that we need some sort of change to work effectively now: spam-only account is a valid reason for a block. Always has been. Admins have just been trained to go the SPI route post-Orangemoody since for a while the biggest threat were these massive sockfarms. Admins can apply existing policy more liberally than they are today and have a big impact without requiring something like a commercial editing ban. TonyBallioni (talk) 16:09, 12 July 2020 (UTC)
- I agree that promotional editing is probably the biggest issue facing enwiki today. Given my druthers, I'd be a lot more free with WP:G11 than I am, but I try to hew to the community opinion, which seems to be a lot more accepting of this, especially in draft space. The past year or so, I've spent a fair amount of time reviewing drafts at WP:AfC. Left to my own devices, I'd G11 90% of what comes through there, but I figure if I did that, I'd find myself on the wrong end of an Arbcom case. I'd be more than happy to see an RfC that put some teeth into our WP:COI policies. -- RoySmith (talk) 16:27, 12 July 2020 (UTC)
- I agree that the current policies are not stopping the problem. The question, then, is if progressivly tougher policies will change anything? The people we are talking about are already banned and will already have their content removed on sight. It makes no difference. I do think we need to have a discussion about solutions, and the WMF needs to be invovled, but if we're really serious about the problem the solution is unlikely to be in hardening policies that don't make a difference anyway. We need to work out better methods of detecting paid editing, better means of stopping the ads, or better means of removing the demand. If we achieved that we'd either be able to enforce the policies we have or we would have less need to enforce them. - Bilby (talk) 16:54, 12 July 2020 (UTC)
- Yes, I’d support a ban on commercial editing and specifically phrase it that way so that the “What about WiRs/WMF employees” strawman doesn’t derail the discussion like it does every time any policy change in this area is discussed. Something I disagree with Ivanvector on to an extent is that we need some sort of change to work effectively now: spam-only account is a valid reason for a block. Always has been. Admins have just been trained to go the SPI route post-Orangemoody since for a while the biggest threat were these massive sockfarms. Admins can apply existing policy more liberally than they are today and have a big impact without requiring something like a commercial editing ban. TonyBallioni (talk) 16:09, 12 July 2020 (UTC)
- @TonyBallioni and Ivanvector: both suggest that a change in policy could help here (Tony's was way above, saying that he supports banning all commercial editing). I've had some mixed feelings on this. Often it seems that we have the policies, it's just that they aren't enforced. Other times it seems like we have people willing to enforce the policies, but it seems like there is a glitch in the way many people interpret the policy. I suppose we should just take one step at a time, whichever will be more effective at the time. Coming up with a new policy on Commercial editing would probably be effective now. So all we need to do is define commercial editing, ban it, make it easy to enforce. I will suggest that we leave WP:Paid editing disclosure alone - since it is part of the ToU it has special status and is very difficult to revoke. If we were to go through the complete process to change the disclosure process, the resulting policy would be weaker (easier to change) than the combination of the current disclosure policy plus a new policy on commercial editing. This is not the best place to discuss a new policy - can somebody suggest the best place to take this? Smallbones(smalltalk) 16:03, 12 July 2020 (UTC)
- I also agree that spam is currently our biggest problem and have the numbers to back it up. I swing the banhammer at everyone I suspect of UPE and shove their articles into draftspace because sending them to AFD is too laborious and risky (of being kept, either by spammer intervention, default or, rarely, because they are actually notable). My experience is similar to TonyBallioni and Bilby - I don't bother with SPI unless I know it will be useful, which isn't very often. That said, I rolled up a 25 article spam sock farm because they used the same tactics last week. I welcome any constructive RFC that either enhances COI, PAID, increases the notability threshold (especially for sportspeople, or maybe propagating the enhanced CORP sourcing to living people to enhance sourcing for spam-prone occupations) or otherwise make it harder for spammers to spam.
- But what's missing here is measures to reduce demand for spamming services. This is particularly hard, given that PR is valued in the corporate world. MER-C 16:52, 12 July 2020 (UTC)
- I've been thinking along the same lines. There are so many ads from people seeking a WP page so that they can be verified on Instgram, or to help their career as a minor speaker/hypnotist/author/colsultant/surgeon/whatever, that if we killed the possibility of these minor articles we'd make a huge difference. Only then we'd need to delete a lot of existing articles. - Bilby (talk) 17:15, 12 July 2020 (UTC)
- Another thing we can do is to set up a venue like Wikipedia:Copyright problems but for UPE. After seven days, if there is no rewrite by a legitimate editor and there is credible suspicion of UPE the suspected text or the entire article can be deleted at the discretion of the closing administrator (regardless of notability). The spammer can't remove the tag (unlike PROD) and there is less overhead than AFD. This venue could also work well with paid-en-wp at wikipedia . org for the handling of private evidence. MER-C 18:13, 12 July 2020 (UTC)
- I've been thinking along the same lines. There are so many ads from people seeking a WP page so that they can be verified on Instgram, or to help their career as a minor speaker/hypnotist/author/colsultant/surgeon/whatever, that if we killed the possibility of these minor articles we'd make a huge difference. Only then we'd need to delete a lot of existing articles. - Bilby (talk) 17:15, 12 July 2020 (UTC)
Outlining a new policy on Commercial editing
Let me try a general outlinke before moving this to Village Pump of a better space .
- Intro
- Defining commercial. editing
- Allowed editing
- Prohibited editing
- Enforcement
Commercial editing Commercial editors, those who edit Wikipedia as part of a commercial transaction, have historically caused problems on Wikipedia by violating our policies on NPOV, No advertising, No spam, No promotion, .... Their actions are currently regulated by WP:COI, and WP:Paid editing disclosure, but problems have continued. This policy supplements WP:COI and WP:PAID and all commercial editors must follow all of these rules.
Defining commercial editing
A commercial editor is any editor who accepts payment or similar inducements to edit a Wikipedia article. The following type of editors are automatically considered to be commercial editors.
- Firms that advertises that they will edit or create Wikipedia articles for pay or similar inducements.
- The owners, managers, employees, and contractors of these firms.
- Firms that sell goods or services that do not include Wikipedia editing or writing services, if they edit Wikipedia
- Owners, managers, board members or employees of the legal, public relations, marketing or sales departments, or employees who receive a commission based on sales or revenue (more later) ````
Straight and curly apostrophes on iPads
- User:Tribe of Tiger put this query in Wikipedia:Requested moves/Technical requests. Anthony Appleyard (talk) 04:54, 12 July 2020 (UTC)
- Help with moves using Ipad
- I am not sure if this the correct place to request assistance. I edit on a aprrox. 1.5 year old up-to-date Ipad. I was attempting to help move articles with a curly apostrophe in the title. Although my Ipad would allow me to correct "curly" in the article body, when I tried to correct/move the title, it kept producing a curly apostrophe, instead of a straight apostrophe. By using my really old desk computer, I could do the move and change from curly to straight. Because one device works, and the other does not, I wonder if this is a problem with the WP software. I am not a techinically savvy person, by any means. Thanks for your consideration. Tribe of Tiger Let's Purrfect! 00:07, 12 July 2020 (UTC)
- @Tribe of Tiger: This is a feature (if you can call it that...) enabled by default across Apple OSes. You can go into your Settings, finding the section pertaining to keyboard and turn off smart quotes/smart punctuation, or something like that. --qedk (t 愛 c) 11:40, 12 July 2020 (UTC)
- Thanks, I've had the same issue with my stupid iphone. Springee (talk) 11:49, 12 July 2020 (UTC)
- I am not sure if this the correct place to request assistance. I edit on a aprrox. 1.5 year old up-to-date Ipad. I was attempting to help move articles with a curly apostrophe in the title. Although my Ipad would allow me to correct "curly" in the article body, when I tried to correct/move the title, it kept producing a curly apostrophe, instead of a straight apostrophe. By using my really old desk computer, I could do the move and change from curly to straight. Because one device works, and the other does not, I wonder if this is a problem with the WP software. I am not a techinically savvy person, by any means. Thanks for your consideration. Tribe of Tiger Let's Purrfect! 00:07, 12 July 2020 (UTC)
Appeal Close request
A non-closed appeal by @Steverci: could use a look at by a non-participating admin. I've copied the archived discussion into a collapsed form below. If anyone instead wants to continue the discussion, please de-collapse it. Nosebagbear (talk) 13:07, 12 July 2020 (UTC)
Archived discussion copy
|
---|
Topic ban appeal
Six months ago, I made a standard offer unblock request on this noticeboard. The reviewing admins had generously decided to give me another chance, while still reinstating my topic ban on all broadly construed topics related to Armenia and Azerbaijan and related ethnic conflicts. Over the past six months, I've been editing articles outside of my topic ban area, and have not engaged in sock puppetry or edit warring. If the topic ban is removed, I promise I will continue to be a productive editor in my topic ban area as well. I understand if there will be any hesitation, given that I've appealed this topic ban before over 4 years ago. However, I'm now a lot older and more mature, and I'm also more familiar with the rules and regulations of Wikipedia. I ask that the administration once again let me prove this not just with words, but actions as well, by removing my topic ban. If there are still any doubts, I would happily accept a 1RR condition in my topic ban area, so that I could further demonstrate I will edit constructively in this field. --Steverci (talk) 02:07, 1 July 2020 (UTC)
|