Currently, there are no requests for arbitration.
Request name | Motions | Case | Posted |
---|---|---|---|
Amendment request: Article titles and capitalisation | none | ( orig. case) | 7 June 2024 |
Clarification request: mentioning the name of off-wiki threads | none | none | 4 June 2024 |
Amendment request: India-Pakistan | none | ( orig. case) | 7 June 2024 |
Clarification request: Contentious topics restrictions | none | none | 10 June 2024 |
No arbitrator motions are currently open.
Use this section to request clarification or amendment of a closed Arbitration Committee case or decision.
To file a clarification or amendment request: (you must use this format!)
{{subst:
Arbitration CA notice|SECTIONTITLE}}
to do this.This is not a discussion. Please do not submit your request until it is ready for consideration; this is not a space for drafts, and incremental additions to a submission are disruptive.
Arbitrators or Clerks may summarily remove or refactor discussion without comment.
Requests from blocked or banned users should be made by e-mail directly to the Arbitration Committee.
Only Arbitrators and Clerks may remove requests from this page. Do not remove a request or any statements or comments unless you are in either of these groups. There must be no threaded discussion, so please comment only in your own section. Archived clarification and amendment requests are logged at Wikipedia:Arbitration/Index/Clarification and Amendment requests. Numerous legacy and current shortcuts can be used to more quickly reach this page:
General consensus among participating Arbitrators is that nothing needs to be done at this point in time. Primefac ( talk) 20:01, 7 June 2024 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Initiated by HouseBlaster at 02:23, 13 May 2024 (UTC)
Statement by HouseBlasterThe
Manual of Style and
Article title policy are jointly authorized contentious topics. Speaking for myself, I have It seems that others are also unaware (in the conventional sense) that article titles are CTOPICs; at Wikipedia:Arbitration/Requests/Case#Persistent WP:IDONTLIKEIT behavior in WP:NCROY discussions it was about three days and 26KB of discussion before Guerrillero pointed out that article titles are already designated as a CTOP. The MOS and article titles are related, but distinct, issues. I think they should be split into seperate CTOPs to reflect the fact that they are distinct issues. House Blaster ( talk · he/him) 02:23, 13 May 2024 (UTC)
Statement by Extraordinary WritSplitting the remedy is probably more trouble than it's worth. But while we're here: there hasn't been a logged sanction under this case since 2020, and that's probably because its scope is so narrow that most title- or MOS-related disruption isn't covered. Honestly there's a strong argument for just repealing it altogether, although the timing may not be right for that. An alternative would be to expand it to include RMs and the like (certainly there have been plenty of issues there), but that would give administrators an awful lot of discretion. The status quo of having the CTOP cover just the policy/guideline pages (which are often less contentious than the RMs) doesn't really make sense to me, though, and the lack of use suggests it's not doing much of value. Extraordinary Writ ( talk) 03:13, 13 May 2024 (UTC) Statement by SarekOfVulcanI would oppose splitting them, because the application of the MOS guidelines to the article titles policy was a large part of the controversy that caused me to file the case in the first place. See also Comet Hale–Bopp. -- SarekOfVulcan (talk) 18:48, 20 May 2024 (UTC) Statement by {other-editor}Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the amendment request or provide additional information. Article titles and capitalisation: Clerk notes
Article titles and capitalisation: Arbitrator views and discussion
|
Initiated by Just Step Sideways at 22:38, 4 June 2024 (UTC)
List of any users involved or directly affected, and confirmation that all are aware of the request:
Two recent situations have revealed what appears to be some vagueness regarding when and if users should email private evidence to the committee, the utility of doing so when it concerns a curent on-wiki, but non-ArbCom discussion, and also if merely saying that a thread exists is not permitted.
(I seem to recall that there is a case somewhere where the committee discussed very similar issues, but I've been unable to locate it in the archives.)
I feel like this has the potantial to create a chilling effect where users will be afraid to post anything at all on off-wiki criticism sites, no matter how innocuous their posts are the topic being discussed may be, and that even mentioning the name of a thread on such a site is now forbidden, which seems a bit extreme to me.
I understand and agree that directly posting a link on-wiki to a specific post that contains outing is a clear violation of the outing policy. It is less clear to me that posting merely the name of an extremely long thread with no actual link to the thread at all is a violation. I would therefore ask that the committee clarify where the line is.
I've deliberately not named the individuals involved in these incidents as this is matter of interpretation of policy, specifically Wikipedia:Oversight. I can email more detailed information if needed but I imagine it should be fairly easy for you all to determine what I'm referring to. Just Step Sideways from this world ..... today 22:38, 4 June 2024 (UTC)
there is never a situation that calls for linking to or discussing a Wikipediocracy thread.seems a bit extreme to me. Do I agree with everything that is said and done over there? No, but I could say the same about here. There are several ongoing threads over there that contain valid and insightful criticism of Wikipedia content and policy. I have personally taken multiple actions here that have improved the project, that I likely wouldn't have done had I not read the criticism over there. I'd tell you which ones but right now it is unclear to me if I'm even allowed to say. Dispairaiging remarks like
No need to point people to WPO to hear ten blocked trolls give their opinions on it.aren't helpful. I seem to recall you saying at some point that you have never actually read anything over there, so it's hard to understand how you formed your opinions. Just Step Sideways from this world ..... today 17:56, 11 June 2024 (UTC)
I think it would be very interesting to hear ArbCom opinions on this question. In part, this issue comes up in the context of the 2024 RfA reform discussions heading in the direction of wanting accusations of wrongdoing against RfA candidates to be backed up with specific evidence, and the question comes up of how to provide specific evidence when it cannot be posted onsite. Does ArbCom want editors to submit such evidence about RfA candidates to ArbCom, and if so, can ArbCom respond to the evidence in a way that is sufficiently timely to be useful for RfA? -- Tryptofish ( talk) 22:56, 4 June 2024 (UTC)
I have lots of thoughts, but they boil down to: we will not link to (or obliquely mention) any thread with outing/doxxing; consider whether it is accessible to the public so it can be verified; and consider whether the WP user has linked themselves to the off-wiki account. If any of the 3 tests fail, then you can't bring it up at RFA (or anywhere else at WP). Sorry, the world is imperfect. Based on this, you would very often be able to discuss a Discord discussion, and very often not be able to discuss a WO discussion, but with exceptions in both cases. It seems like further details on this aren't useful until and unless I become God Emperor of WP, and can just implement it, but I can expand if someone wants. -- Floquenbeam ( talk) 23:28, 4 June 2024 (UTC)
I see this as a matter for the community, rather than ARBCOM. To me the heart of the matter is if, and how, we can discuss Wikipedia editors' off-wiki activities. ARBCOM has a role to play when off-wiki conduct impinges on on-wiki matters enough; typically, for harassment, collusion, or other disruption of our core purpose. The off-wiki conduct that has become a matter of discussion at RFA is very different: it isn't a violation of any of our PAGs, it is just behavior some editors find objectionable in an RFA candidate. We treat the off-wiki lives of our editors as private, and rightfully so. Discord and WPO are weird, in that they are strictly off-wiki fora populated by a large number of Wikipedians in good standing. I don't think it's an unreasonable position to take that behavior there shouldn't be immune to on-wiki scrutiny if it becomes relevant to on-wiki matters; I also don't think it's unreasonable to say that what happens off-wiki should stay there until and unless our PAGs are being violated, and then it needs to go to ARBCOM. But that's an area in which current policy seems to not cover all the contingencies, and the community needs to grapple with that. I don't see how a comment like this is useful to send to ARBCOM, or what ARBCOM could do if it was; but we're clearly unsettled as a community that it was posted, and we need to figure out guidelines for it. Vanamonde93 ( talk) 01:23, 5 June 2024 (UTC)
I agree that some clarification from the committee on these matters would be helpful. This isn't entirely up to them—for example, the ban on discussing Discord discussions is the result of a community RfC and it would be inappropriate to modify it either way here—but ArbCom has historically played a role in making editors feel generally uncomfortable about linking to things off-wiki. More specifically, a 2007 remedy pronouncing that quoting private correspondence is a copyright violation is still on the books and still cited in WP:EMAILPOST. Does the current committee agree with this interpretation?
In addition, ArbCom has a responsibility to regulate the oversight team, and I've had a feeling for a long time now that they been enforce an extremely broad understanding of what constitutes "outing" that is not necessarily reflective of broader community opinion. Some direction there could also be very helpful: OS is used as "tool of first resort", or so the mantra goes, but we shouldn't underestimate how chilling it is to have an edit suppressed. – Joe ( talk) 08:47, 5 June 2024 (UTC)
profiles on external sites, and by extension posts associated with those profiles, can reasonably be considered "personal information". For me it's the latter that is the problem here; the former is a good rule when applied to genuine personal information. Interestingly, it's also a relatively recent addition to the harassment policy, [1] [2] following this discussion in December 2020. The reason given for the addition was to bring the policy in line with the practice of oversighters, which rather speaks to my point of the OS team pushing things in a more conservative direction, not necessarily the community as a whole. – Joe ( talk) 06:36, 6 June 2024 (UTC)
I'd like an opinion on this as well, not necessarily just for RFA. Specific to WP:Discord, I !voted in the Discord RFC to restrict copying and linking Discord messages. I did so based on my reading of OUTING, HARASSMENT, and the community expectations of IRC logs, rather than strictly what I'd prefer. That consideration included what Joe references about the copyright concern of "private" messages, which seems to be part of the long standing rationale around IRC messages. I've also seen several times people suggest that OUTING goes as far as covering someone outing themselves on another Wikimedia project (i.e. a user page on eswiki), meaning that's not good enough to mention here on English Wikipedia. Prior to SUL, that may well have been, but SUL is long done. So what I'm really driving at is: Where is the line on identifying yourself sufficiently to be mentioned on site? Particular to the Discord, we have OAuth integration through an open source bot hosted on WMF resources. Is this enough to count as self-disclosure? Or does the connection to Discord have to be on-site (i.e. a userbox or otherwise)? Revisiting the Discord RFC is on the community, but some of these questions, such as EMAILPOST and how OS will act, are at least partially under Arbcom as Joe notes. -- ferret ( talk) 13:43, 5 June 2024 (UTC)
Regarding Ferret's comments regarding disclosures on other SUL wikis. I have a vague recollection that this was discussed previously, but I don't remember where. I don't think a single hard and fast rule can be applied to that, but it's a matter of how reasonable it is to expect en.wp editors to be aware of the disclosure. For example if you make a disclosure on another wiki and you prominently link to that page from your userpage here, that should count as disclosing it here. If you disclose something on your e.g. eswiki userpage and make it clear on your userpage here that you contribute to eswiki, then again it's reasonable to take that as having been disclosed to the English Wikipedia. However, if you state something on the e.g. Russian wikisource's equivalent of Wikipedia talk:Manual of Style, and don't link to that page here, then it has not been disclosed to the English Wikipedia. Obviously there will be many things in between the extremes that can only be decided on a case-by-case basis. However, unless you are sure it has been intentionally or obviously disclosed somewhere it is reasonable to expect English Wikipedia editors to be aware of, then assume it has not been disclosed. Thryduulf ( talk) 18:54, 5 June 2024 (UTC)
I think the community wants to have pretty firm protections against doxxing
I'd like the committee to make an explicit distinction between persons involved in the act of doxxing (or say vote canvassing or any other misconduct) on third-party sites, and persons who participate on those sites but are not abettors. It's futile to overreach and police what editors do and say outside wikipedia. Hypothetically speaking, I can say whatever I want on any third party site with a fictitious name, without any possibility of repercussion on my activity on wikipedia. Arbcom should act exclusively on cases where they find evidence of misconduct by an editor off-wiki without attaching any vicarious liability to other participants on that off-wiki platform. —
hako9 (
talk) 19:40, 5 June 2024 (UTC)
@
Levivich JSS/Beebs, you posted in that same thread over there six times since that post was made, and not a single word about this very open threat.
What is JSS supposed to do? Chide Vigilant aggressively so that they stop doxxing? As if that would work? The doxxing is going to happen whether editors here participate there or not. —
hako9 (
talk) 23:14, 11 June 2024 (UTC)
CaptainEek Statements like there is never a situation that calls for linking to or discussing a Wikipediocracy thread
are problematic. Are you suggesting that if I were to discuss my resignation of the tools in late 2013, a Wikipediocracy post--that persists to this day in somewhat redacted form--doxxing me and listing my employer's name and phone number and my home address and phone number (that were redacted so quickly by WPO leadership I couldn't confirm their accuracy) and several other identifying bits of information would be off limits for me to bring up to discuss the circumstances of my tools resignation? I'd like to think that, as the person doxxed, it is my prerogative to mention, discuss, or even link to such a thread, and the clear sense of
WP:OUTING is that such linkage would be permitted if done by me. (For the record, none of the information is particularly threatening to me 10 1/2 years later. Those overly interested can Google my current employer and discover why.)
Jclemens (
talk) 18:24, 11 June 2024 (UTC)
One of the first things I did after learning about it was searching my own name on there; boy was that a bad decision.CaptainEek, you highlight one of the ongoing negatives of Wikipediocracy: regulars there have a love/hate, but mostly hate, relationship with Wikipedia administrators that can have a demoralizing effect on Wikipedia editors. While I would also not recommend any admin or outspoken user search the site for their username, once having done so, it can be instructive to see how particular actions are discussed. In at least one case, only after being pointed to Wikipediocracy and reading the relevant thread did I understand the opposition to a stance I took. So while linking to criticism of another editor may well remain off limits, each mentioned editor should be made aware of the potential to review critics' unfiltered thoughts at the site. Jclemens ( talk) 23:11, 11 June 2024 (UTC)
A couple of days ago on WPO, Vigilant, the WPO user who most often doxes Wikipedia editors and openly threatens to continue doing so, wrote, in response to Eek's comments here, "Sounds like Eek needs an exposé" (link omitted). JSS/Beebs, you posted in that same thread over there six times since that post was made, and not a single word about this very open threat. Here, your third post is "Dispairaiging remarks like 'No need to point people to WPO to hear ten blocked trolls give their opinions on it.' aren't helpful." That's pretty bad: you take the time to criticize someone for criticizing WPO, but you don't criticize WPO for threatening to 'expose' editors.
(Also, Beebs, give up the "but they read it!" line of argument. Of course people who criticize WPO read it. Just like people on WPO read Wikipedia even though they criticize Wikipedia. This is not the "gotcha" that you seem to think it is: if people didn't criticize things they read, or didn't read the things they criticize, there would no criticism at all. Perhaps that's what you want?)
So w/r/t JSS's comment in the OP that "this has the potential to create a chilling effect where users will be afraid to post anything at all on off-wiki criticism sites," that chilling effect is good and we want that. Just like WPO is trying to create a chilling effect on Wikipedia by threatening to dox editors they disagree with, Wikipedia should create a chilling effect, or a taboo, about participating in off-wiki websites that dox editors, even if those websites refer to themselves as "criticism sites." There are other reasons not to have a blanket prohibition on linking or referring to another website (one of those reasons is so we can call people out for their wikipediocracy hypocrisy, as I am doing here), but "chilling effect" ain't it.
Levivich (
talk) 19:08, 11 June 2024 (UTC)
While I think the idea of prohibiting mention of the ignominious badsites and offsites was done with the best of intentions, it seems to very obviously and directly facilitate and enable any manner of bad behavior. In general, the way it ends up working in practice is something like:
Here is another example:
Another:
Whatever the reasoning was behind this omerta stuff, it seems in practice to have almost entirely bad implications -- it certainly doesn't stop people from going to WPO and doing whatever they want (trash-talking other editors, getting out the vote for RfCs/AfDs/etc, weird mafioso larping) -- the only thing it actually stops is us talking about it or doing something about it.
Contrariwise, this isn't even much of a benefit for WPO -- people onwiki are also completely free to just say stuff with no evidence because "well I can't link to it or tell anybody what it is". jp× g 🗯️ 03:27, 12 June 2024 (UTC)
Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.
Its not that you're forbidden from discussing the nonsense at WPO, but its not recommended and can in fact be avoided. CaptainEek Edits Ho Cap'n! ⚓ 18:57, 11 June 2024 (UTC)
we will not link to (or obliquely mention) any thread with outing/doxxing; consider whether it is accessible to the public so it can be verified; and consider whether the WP user has linked themselves to the off-wiki account. If any of the 3 tests fail, then you can't bring it up at RFA. However, I do agree with Joe and others that the Committee has some role to play, though I would prefer to share that role with the broader Oversight team. With OS, I find that 98% or so of the OS requests are clear yes or clear no under policy and require little thought on my part to action. It's the remaining 2% where the OS team should work to have consistency (I think ArbCom should set the expectation that there be less variation in OS response than in other admin areas, including CU). In the noticeboard example that JSS gives, this fell in that 2% which is why I consulted with someone else before taking action. Beyond this, there has been a lot of discussion about WPO of which I have a number of opinions about but is also not a unique use case when it comes to mentioning/linking to off-wiki threads/discussions which I see as the matter before us and thus doesn't need any special analysis beyond what I've written above. Barkeep49 ( talk) 21:57, 11 June 2024 (UTC)
Initiated by Jéské Couriano at 16:07, 7 June 2024 (UTC)
Over the past month or so we've been having members of the Indian Armed Forces either editing or attempting to create articles concerning military regiments in India. It's only recently come to light that this is a concerted effort by the Indian Army itself; practically all accounts involved have failed to disclose their connexions and very few have used their talk pages (and those that do tend to describe it as an order from higher up that they don't really have a choice but to obey). I'm not as concerned about the drafts, as they're G5-eligible. What I am concerned about are the pages already in mainspace that have been targeted by this campaign, such as 1889 Missile Regiment (India) and a host of others; see User:Jéské Couriano/2024 Indian Military Regiment Spam for a more complete list. I'm seeking to have the 500/30 rule apply specifically in the Indian military regiments topic area to stymie editing of this sort and to force these editors to the talk pages of the articles to make their case.
Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the amendment request or provide additional information.
there's no realistic way to predict which specific article the newest sock, either registered or IP, is going to editmeans that short of applying ECP to most or all of the articles in this topic area (which isn't reasonable) WP:ARBECR doesn't seem like it would address the issue. It would, however, create more barriers to other editors who would like to edit those articles. - Aoidh ( talk) 21:09, 7 June 2024 (UTC)
Initiated by EggRoll97 at 03:36, 10 June 2024 (UTC)
List of any users involved or directly affected, and confirmation that all are aware of the request:
Multiple pages protected under contentious topics procedures this year alone (see
WP:AEL#Armenia-Azerbaijan_(CT/A-A) for just a sample) have been protected under arbitration enforcement but have no editnotice or other restriction notice applied to the page. This is despite a line recurring in contentious topics procedures pages being, in part, When a page has active page restrictions, the following template must be used as an editnotice
, and the
contentious topics procedures page itself stating that an editnotice is required prior to blocking an editor for a violation, even if they are aware of contentious topics procedures, with the language of However, breaches of a page restriction may result in a block or editor restriction only if: The editor was aware that they were editing in a contentious topic, and The restricted page displayed an editnotice ({{Contentious topics/page restriction editnotice}} or a derived topic-specific template) specifying the page restriction.
Because of this, I ask for clarification as to whether these editnotices can be added to pages by any editor if the enforcing administrator has not done so, or whether they may only be added by the administrator who has applied the page restriction.
The edit notice can be added by editors with the page mover permission. Idk whether the idea of CT was to do away with this requirement but I don't think it did so in my usual area (AI/IP), the Arbpia edit notice (and talk page notice which can be added by any editor) is needed in general. Selfstudier ( talk) 08:43, 10 June 2024 (UTC)
Editnotices can be created by administrators, page movers, and template editors. If an editnotice exists, most editors can edit it, and I'd support non-admins rectifying clerical errors wherever possible. Speaking of which, if someone wants to collect some pages that need editnotices, I'm happy to cross a bunch of them off the list.
Arbs, I'd suggest that common practice has moved away from such editnotices being necessary. Between admins forgetting, banner blindness, and mobile editors not seeing them at all, I don't think the notices are meaningful in generating awareness of the restriction. Enforcement of restrictions these days tends to be dependent on both formal CTOP awareness and a request to self-revert being ignored or declined, meaning a few other checks are in place to avoid unwarranted sanctions. Would the committee consider changing this requirement to a recommendation? Firefangledfeathers ( talk / contribs) 18:43, 11 June 2024 (UTC)
Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.
An administrator who imposes a page restriction (other than page protection) must add an editnotice to restricted pages using the standard template ({{ Contentious topics/page restriction editnotice}} or a derived topic-specific template), and should generally add a notice to the talk page of restricted pages.(formatting removed). Barkeep49 ( talk) 22:06, 11 June 2024 (UTC)
{{Contentious topics/editnotice|XYZ}}
as an edit notice to pages clearly fully related to XYZ
would be helpful, even if no protection has happened yet.{{Contentious topics/editnotice|...|section=yes}}
as an edit notice to pages related to XYZ
closely enough to justify an existing CTOP page protection would also be helpful.{{Contentious topics/editnotice|blp}}
to BLPs, as being in
Category:Living people already causes {{
BLP editnotice}} to appear.
~ ToBeFree (
talk) 23:24, 11 June 2024 (UTC)Currently, there are no requests for arbitration.
Request name | Motions | Case | Posted |
---|---|---|---|
Amendment request: Article titles and capitalisation | none | ( orig. case) | 7 June 2024 |
Clarification request: mentioning the name of off-wiki threads | none | none | 4 June 2024 |
Amendment request: India-Pakistan | none | ( orig. case) | 7 June 2024 |
Clarification request: Contentious topics restrictions | none | none | 10 June 2024 |
No arbitrator motions are currently open.
Use this section to request clarification or amendment of a closed Arbitration Committee case or decision.
To file a clarification or amendment request: (you must use this format!)
{{subst:
Arbitration CA notice|SECTIONTITLE}}
to do this.This is not a discussion. Please do not submit your request until it is ready for consideration; this is not a space for drafts, and incremental additions to a submission are disruptive.
Arbitrators or Clerks may summarily remove or refactor discussion without comment.
Requests from blocked or banned users should be made by e-mail directly to the Arbitration Committee.
Only Arbitrators and Clerks may remove requests from this page. Do not remove a request or any statements or comments unless you are in either of these groups. There must be no threaded discussion, so please comment only in your own section. Archived clarification and amendment requests are logged at Wikipedia:Arbitration/Index/Clarification and Amendment requests. Numerous legacy and current shortcuts can be used to more quickly reach this page:
General consensus among participating Arbitrators is that nothing needs to be done at this point in time. Primefac ( talk) 20:01, 7 June 2024 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Initiated by HouseBlaster at 02:23, 13 May 2024 (UTC)
Statement by HouseBlasterThe
Manual of Style and
Article title policy are jointly authorized contentious topics. Speaking for myself, I have It seems that others are also unaware (in the conventional sense) that article titles are CTOPICs; at Wikipedia:Arbitration/Requests/Case#Persistent WP:IDONTLIKEIT behavior in WP:NCROY discussions it was about three days and 26KB of discussion before Guerrillero pointed out that article titles are already designated as a CTOP. The MOS and article titles are related, but distinct, issues. I think they should be split into seperate CTOPs to reflect the fact that they are distinct issues. House Blaster ( talk · he/him) 02:23, 13 May 2024 (UTC)
Statement by Extraordinary WritSplitting the remedy is probably more trouble than it's worth. But while we're here: there hasn't been a logged sanction under this case since 2020, and that's probably because its scope is so narrow that most title- or MOS-related disruption isn't covered. Honestly there's a strong argument for just repealing it altogether, although the timing may not be right for that. An alternative would be to expand it to include RMs and the like (certainly there have been plenty of issues there), but that would give administrators an awful lot of discretion. The status quo of having the CTOP cover just the policy/guideline pages (which are often less contentious than the RMs) doesn't really make sense to me, though, and the lack of use suggests it's not doing much of value. Extraordinary Writ ( talk) 03:13, 13 May 2024 (UTC) Statement by SarekOfVulcanI would oppose splitting them, because the application of the MOS guidelines to the article titles policy was a large part of the controversy that caused me to file the case in the first place. See also Comet Hale–Bopp. -- SarekOfVulcan (talk) 18:48, 20 May 2024 (UTC) Statement by {other-editor}Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the amendment request or provide additional information. Article titles and capitalisation: Clerk notes
Article titles and capitalisation: Arbitrator views and discussion
|
Initiated by Just Step Sideways at 22:38, 4 June 2024 (UTC)
List of any users involved or directly affected, and confirmation that all are aware of the request:
Two recent situations have revealed what appears to be some vagueness regarding when and if users should email private evidence to the committee, the utility of doing so when it concerns a curent on-wiki, but non-ArbCom discussion, and also if merely saying that a thread exists is not permitted.
(I seem to recall that there is a case somewhere where the committee discussed very similar issues, but I've been unable to locate it in the archives.)
I feel like this has the potantial to create a chilling effect where users will be afraid to post anything at all on off-wiki criticism sites, no matter how innocuous their posts are the topic being discussed may be, and that even mentioning the name of a thread on such a site is now forbidden, which seems a bit extreme to me.
I understand and agree that directly posting a link on-wiki to a specific post that contains outing is a clear violation of the outing policy. It is less clear to me that posting merely the name of an extremely long thread with no actual link to the thread at all is a violation. I would therefore ask that the committee clarify where the line is.
I've deliberately not named the individuals involved in these incidents as this is matter of interpretation of policy, specifically Wikipedia:Oversight. I can email more detailed information if needed but I imagine it should be fairly easy for you all to determine what I'm referring to. Just Step Sideways from this world ..... today 22:38, 4 June 2024 (UTC)
there is never a situation that calls for linking to or discussing a Wikipediocracy thread.seems a bit extreme to me. Do I agree with everything that is said and done over there? No, but I could say the same about here. There are several ongoing threads over there that contain valid and insightful criticism of Wikipedia content and policy. I have personally taken multiple actions here that have improved the project, that I likely wouldn't have done had I not read the criticism over there. I'd tell you which ones but right now it is unclear to me if I'm even allowed to say. Dispairaiging remarks like
No need to point people to WPO to hear ten blocked trolls give their opinions on it.aren't helpful. I seem to recall you saying at some point that you have never actually read anything over there, so it's hard to understand how you formed your opinions. Just Step Sideways from this world ..... today 17:56, 11 June 2024 (UTC)
I think it would be very interesting to hear ArbCom opinions on this question. In part, this issue comes up in the context of the 2024 RfA reform discussions heading in the direction of wanting accusations of wrongdoing against RfA candidates to be backed up with specific evidence, and the question comes up of how to provide specific evidence when it cannot be posted onsite. Does ArbCom want editors to submit such evidence about RfA candidates to ArbCom, and if so, can ArbCom respond to the evidence in a way that is sufficiently timely to be useful for RfA? -- Tryptofish ( talk) 22:56, 4 June 2024 (UTC)
I have lots of thoughts, but they boil down to: we will not link to (or obliquely mention) any thread with outing/doxxing; consider whether it is accessible to the public so it can be verified; and consider whether the WP user has linked themselves to the off-wiki account. If any of the 3 tests fail, then you can't bring it up at RFA (or anywhere else at WP). Sorry, the world is imperfect. Based on this, you would very often be able to discuss a Discord discussion, and very often not be able to discuss a WO discussion, but with exceptions in both cases. It seems like further details on this aren't useful until and unless I become God Emperor of WP, and can just implement it, but I can expand if someone wants. -- Floquenbeam ( talk) 23:28, 4 June 2024 (UTC)
I see this as a matter for the community, rather than ARBCOM. To me the heart of the matter is if, and how, we can discuss Wikipedia editors' off-wiki activities. ARBCOM has a role to play when off-wiki conduct impinges on on-wiki matters enough; typically, for harassment, collusion, or other disruption of our core purpose. The off-wiki conduct that has become a matter of discussion at RFA is very different: it isn't a violation of any of our PAGs, it is just behavior some editors find objectionable in an RFA candidate. We treat the off-wiki lives of our editors as private, and rightfully so. Discord and WPO are weird, in that they are strictly off-wiki fora populated by a large number of Wikipedians in good standing. I don't think it's an unreasonable position to take that behavior there shouldn't be immune to on-wiki scrutiny if it becomes relevant to on-wiki matters; I also don't think it's unreasonable to say that what happens off-wiki should stay there until and unless our PAGs are being violated, and then it needs to go to ARBCOM. But that's an area in which current policy seems to not cover all the contingencies, and the community needs to grapple with that. I don't see how a comment like this is useful to send to ARBCOM, or what ARBCOM could do if it was; but we're clearly unsettled as a community that it was posted, and we need to figure out guidelines for it. Vanamonde93 ( talk) 01:23, 5 June 2024 (UTC)
I agree that some clarification from the committee on these matters would be helpful. This isn't entirely up to them—for example, the ban on discussing Discord discussions is the result of a community RfC and it would be inappropriate to modify it either way here—but ArbCom has historically played a role in making editors feel generally uncomfortable about linking to things off-wiki. More specifically, a 2007 remedy pronouncing that quoting private correspondence is a copyright violation is still on the books and still cited in WP:EMAILPOST. Does the current committee agree with this interpretation?
In addition, ArbCom has a responsibility to regulate the oversight team, and I've had a feeling for a long time now that they been enforce an extremely broad understanding of what constitutes "outing" that is not necessarily reflective of broader community opinion. Some direction there could also be very helpful: OS is used as "tool of first resort", or so the mantra goes, but we shouldn't underestimate how chilling it is to have an edit suppressed. – Joe ( talk) 08:47, 5 June 2024 (UTC)
profiles on external sites, and by extension posts associated with those profiles, can reasonably be considered "personal information". For me it's the latter that is the problem here; the former is a good rule when applied to genuine personal information. Interestingly, it's also a relatively recent addition to the harassment policy, [1] [2] following this discussion in December 2020. The reason given for the addition was to bring the policy in line with the practice of oversighters, which rather speaks to my point of the OS team pushing things in a more conservative direction, not necessarily the community as a whole. – Joe ( talk) 06:36, 6 June 2024 (UTC)
I'd like an opinion on this as well, not necessarily just for RFA. Specific to WP:Discord, I !voted in the Discord RFC to restrict copying and linking Discord messages. I did so based on my reading of OUTING, HARASSMENT, and the community expectations of IRC logs, rather than strictly what I'd prefer. That consideration included what Joe references about the copyright concern of "private" messages, which seems to be part of the long standing rationale around IRC messages. I've also seen several times people suggest that OUTING goes as far as covering someone outing themselves on another Wikimedia project (i.e. a user page on eswiki), meaning that's not good enough to mention here on English Wikipedia. Prior to SUL, that may well have been, but SUL is long done. So what I'm really driving at is: Where is the line on identifying yourself sufficiently to be mentioned on site? Particular to the Discord, we have OAuth integration through an open source bot hosted on WMF resources. Is this enough to count as self-disclosure? Or does the connection to Discord have to be on-site (i.e. a userbox or otherwise)? Revisiting the Discord RFC is on the community, but some of these questions, such as EMAILPOST and how OS will act, are at least partially under Arbcom as Joe notes. -- ferret ( talk) 13:43, 5 June 2024 (UTC)
Regarding Ferret's comments regarding disclosures on other SUL wikis. I have a vague recollection that this was discussed previously, but I don't remember where. I don't think a single hard and fast rule can be applied to that, but it's a matter of how reasonable it is to expect en.wp editors to be aware of the disclosure. For example if you make a disclosure on another wiki and you prominently link to that page from your userpage here, that should count as disclosing it here. If you disclose something on your e.g. eswiki userpage and make it clear on your userpage here that you contribute to eswiki, then again it's reasonable to take that as having been disclosed to the English Wikipedia. However, if you state something on the e.g. Russian wikisource's equivalent of Wikipedia talk:Manual of Style, and don't link to that page here, then it has not been disclosed to the English Wikipedia. Obviously there will be many things in between the extremes that can only be decided on a case-by-case basis. However, unless you are sure it has been intentionally or obviously disclosed somewhere it is reasonable to expect English Wikipedia editors to be aware of, then assume it has not been disclosed. Thryduulf ( talk) 18:54, 5 June 2024 (UTC)
I think the community wants to have pretty firm protections against doxxing
I'd like the committee to make an explicit distinction between persons involved in the act of doxxing (or say vote canvassing or any other misconduct) on third-party sites, and persons who participate on those sites but are not abettors. It's futile to overreach and police what editors do and say outside wikipedia. Hypothetically speaking, I can say whatever I want on any third party site with a fictitious name, without any possibility of repercussion on my activity on wikipedia. Arbcom should act exclusively on cases where they find evidence of misconduct by an editor off-wiki without attaching any vicarious liability to other participants on that off-wiki platform. —
hako9 (
talk) 19:40, 5 June 2024 (UTC)
@
Levivich JSS/Beebs, you posted in that same thread over there six times since that post was made, and not a single word about this very open threat.
What is JSS supposed to do? Chide Vigilant aggressively so that they stop doxxing? As if that would work? The doxxing is going to happen whether editors here participate there or not. —
hako9 (
talk) 23:14, 11 June 2024 (UTC)
CaptainEek Statements like there is never a situation that calls for linking to or discussing a Wikipediocracy thread
are problematic. Are you suggesting that if I were to discuss my resignation of the tools in late 2013, a Wikipediocracy post--that persists to this day in somewhat redacted form--doxxing me and listing my employer's name and phone number and my home address and phone number (that were redacted so quickly by WPO leadership I couldn't confirm their accuracy) and several other identifying bits of information would be off limits for me to bring up to discuss the circumstances of my tools resignation? I'd like to think that, as the person doxxed, it is my prerogative to mention, discuss, or even link to such a thread, and the clear sense of
WP:OUTING is that such linkage would be permitted if done by me. (For the record, none of the information is particularly threatening to me 10 1/2 years later. Those overly interested can Google my current employer and discover why.)
Jclemens (
talk) 18:24, 11 June 2024 (UTC)
One of the first things I did after learning about it was searching my own name on there; boy was that a bad decision.CaptainEek, you highlight one of the ongoing negatives of Wikipediocracy: regulars there have a love/hate, but mostly hate, relationship with Wikipedia administrators that can have a demoralizing effect on Wikipedia editors. While I would also not recommend any admin or outspoken user search the site for their username, once having done so, it can be instructive to see how particular actions are discussed. In at least one case, only after being pointed to Wikipediocracy and reading the relevant thread did I understand the opposition to a stance I took. So while linking to criticism of another editor may well remain off limits, each mentioned editor should be made aware of the potential to review critics' unfiltered thoughts at the site. Jclemens ( talk) 23:11, 11 June 2024 (UTC)
A couple of days ago on WPO, Vigilant, the WPO user who most often doxes Wikipedia editors and openly threatens to continue doing so, wrote, in response to Eek's comments here, "Sounds like Eek needs an exposé" (link omitted). JSS/Beebs, you posted in that same thread over there six times since that post was made, and not a single word about this very open threat. Here, your third post is "Dispairaiging remarks like 'No need to point people to WPO to hear ten blocked trolls give their opinions on it.' aren't helpful." That's pretty bad: you take the time to criticize someone for criticizing WPO, but you don't criticize WPO for threatening to 'expose' editors.
(Also, Beebs, give up the "but they read it!" line of argument. Of course people who criticize WPO read it. Just like people on WPO read Wikipedia even though they criticize Wikipedia. This is not the "gotcha" that you seem to think it is: if people didn't criticize things they read, or didn't read the things they criticize, there would no criticism at all. Perhaps that's what you want?)
So w/r/t JSS's comment in the OP that "this has the potential to create a chilling effect where users will be afraid to post anything at all on off-wiki criticism sites," that chilling effect is good and we want that. Just like WPO is trying to create a chilling effect on Wikipedia by threatening to dox editors they disagree with, Wikipedia should create a chilling effect, or a taboo, about participating in off-wiki websites that dox editors, even if those websites refer to themselves as "criticism sites." There are other reasons not to have a blanket prohibition on linking or referring to another website (one of those reasons is so we can call people out for their wikipediocracy hypocrisy, as I am doing here), but "chilling effect" ain't it.
Levivich (
talk) 19:08, 11 June 2024 (UTC)
While I think the idea of prohibiting mention of the ignominious badsites and offsites was done with the best of intentions, it seems to very obviously and directly facilitate and enable any manner of bad behavior. In general, the way it ends up working in practice is something like:
Here is another example:
Another:
Whatever the reasoning was behind this omerta stuff, it seems in practice to have almost entirely bad implications -- it certainly doesn't stop people from going to WPO and doing whatever they want (trash-talking other editors, getting out the vote for RfCs/AfDs/etc, weird mafioso larping) -- the only thing it actually stops is us talking about it or doing something about it.
Contrariwise, this isn't even much of a benefit for WPO -- people onwiki are also completely free to just say stuff with no evidence because "well I can't link to it or tell anybody what it is". jp× g 🗯️ 03:27, 12 June 2024 (UTC)
Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.
Its not that you're forbidden from discussing the nonsense at WPO, but its not recommended and can in fact be avoided. CaptainEek Edits Ho Cap'n! ⚓ 18:57, 11 June 2024 (UTC)
we will not link to (or obliquely mention) any thread with outing/doxxing; consider whether it is accessible to the public so it can be verified; and consider whether the WP user has linked themselves to the off-wiki account. If any of the 3 tests fail, then you can't bring it up at RFA. However, I do agree with Joe and others that the Committee has some role to play, though I would prefer to share that role with the broader Oversight team. With OS, I find that 98% or so of the OS requests are clear yes or clear no under policy and require little thought on my part to action. It's the remaining 2% where the OS team should work to have consistency (I think ArbCom should set the expectation that there be less variation in OS response than in other admin areas, including CU). In the noticeboard example that JSS gives, this fell in that 2% which is why I consulted with someone else before taking action. Beyond this, there has been a lot of discussion about WPO of which I have a number of opinions about but is also not a unique use case when it comes to mentioning/linking to off-wiki threads/discussions which I see as the matter before us and thus doesn't need any special analysis beyond what I've written above. Barkeep49 ( talk) 21:57, 11 June 2024 (UTC)
Initiated by Jéské Couriano at 16:07, 7 June 2024 (UTC)
Over the past month or so we've been having members of the Indian Armed Forces either editing or attempting to create articles concerning military regiments in India. It's only recently come to light that this is a concerted effort by the Indian Army itself; practically all accounts involved have failed to disclose their connexions and very few have used their talk pages (and those that do tend to describe it as an order from higher up that they don't really have a choice but to obey). I'm not as concerned about the drafts, as they're G5-eligible. What I am concerned about are the pages already in mainspace that have been targeted by this campaign, such as 1889 Missile Regiment (India) and a host of others; see User:Jéské Couriano/2024 Indian Military Regiment Spam for a more complete list. I'm seeking to have the 500/30 rule apply specifically in the Indian military regiments topic area to stymie editing of this sort and to force these editors to the talk pages of the articles to make their case.
Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the amendment request or provide additional information.
there's no realistic way to predict which specific article the newest sock, either registered or IP, is going to editmeans that short of applying ECP to most or all of the articles in this topic area (which isn't reasonable) WP:ARBECR doesn't seem like it would address the issue. It would, however, create more barriers to other editors who would like to edit those articles. - Aoidh ( talk) 21:09, 7 June 2024 (UTC)
Initiated by EggRoll97 at 03:36, 10 June 2024 (UTC)
List of any users involved or directly affected, and confirmation that all are aware of the request:
Multiple pages protected under contentious topics procedures this year alone (see
WP:AEL#Armenia-Azerbaijan_(CT/A-A) for just a sample) have been protected under arbitration enforcement but have no editnotice or other restriction notice applied to the page. This is despite a line recurring in contentious topics procedures pages being, in part, When a page has active page restrictions, the following template must be used as an editnotice
, and the
contentious topics procedures page itself stating that an editnotice is required prior to blocking an editor for a violation, even if they are aware of contentious topics procedures, with the language of However, breaches of a page restriction may result in a block or editor restriction only if: The editor was aware that they were editing in a contentious topic, and The restricted page displayed an editnotice ({{Contentious topics/page restriction editnotice}} or a derived topic-specific template) specifying the page restriction.
Because of this, I ask for clarification as to whether these editnotices can be added to pages by any editor if the enforcing administrator has not done so, or whether they may only be added by the administrator who has applied the page restriction.
The edit notice can be added by editors with the page mover permission. Idk whether the idea of CT was to do away with this requirement but I don't think it did so in my usual area (AI/IP), the Arbpia edit notice (and talk page notice which can be added by any editor) is needed in general. Selfstudier ( talk) 08:43, 10 June 2024 (UTC)
Editnotices can be created by administrators, page movers, and template editors. If an editnotice exists, most editors can edit it, and I'd support non-admins rectifying clerical errors wherever possible. Speaking of which, if someone wants to collect some pages that need editnotices, I'm happy to cross a bunch of them off the list.
Arbs, I'd suggest that common practice has moved away from such editnotices being necessary. Between admins forgetting, banner blindness, and mobile editors not seeing them at all, I don't think the notices are meaningful in generating awareness of the restriction. Enforcement of restrictions these days tends to be dependent on both formal CTOP awareness and a request to self-revert being ignored or declined, meaning a few other checks are in place to avoid unwarranted sanctions. Would the committee consider changing this requirement to a recommendation? Firefangledfeathers ( talk / contribs) 18:43, 11 June 2024 (UTC)
Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.
An administrator who imposes a page restriction (other than page protection) must add an editnotice to restricted pages using the standard template ({{ Contentious topics/page restriction editnotice}} or a derived topic-specific template), and should generally add a notice to the talk page of restricted pages.(formatting removed). Barkeep49 ( talk) 22:06, 11 June 2024 (UTC)
{{Contentious topics/editnotice|XYZ}}
as an edit notice to pages clearly fully related to XYZ
would be helpful, even if no protection has happened yet.{{Contentious topics/editnotice|...|section=yes}}
as an edit notice to pages related to XYZ
closely enough to justify an existing CTOP page protection would also be helpful.{{Contentious topics/editnotice|blp}}
to BLPs, as being in
Category:Living people already causes {{
BLP editnotice}} to appear.
~ ToBeFree (
talk) 23:24, 11 June 2024 (UTC)