Wikipedia:APLRS

Wikipedia:Arbitration/Requests/Case/Antisemitism in Poland

Wikipedia:Arbitration/Requests/Case/Antisemitism in Poland


Case opened on 14:40, 9 June 2019 (UTC)

Main case page (Talk) Evidence (Talk) Workshop (Talk) Proposed decision (Talk)

Case clerks: SQL (Talk) & Bradv (Talk) & L235 (Talk) Drafting arbitrators: AGK (Talk) & Opabinia regalis (Talk)

Case closed on 17:54, 22 September 2019 (UTC)

Case amended by motion on 02:39, 1 December 2019 (UTC)

Case amended by motion on 19:54, 30 May 2020 (UTC)

Case amended by motion on 02:34, 18 December 2020 (UTC)

Case amended by motion on 18:48, 9 May 2021 (UTC)

Case amended by motion on 10:15, 20 September 2021 (UTC)

Case amended by motion on 21:36, 14 December 2022 (UTC)
(implemented on 18:24, 23 September 2023 (UTC))

Case amended by remedy on 16:30, 20 May 2023 (UTC)

Case amended by motion on 21:15, 4 January 2024 (UTC)

Watchlist all case (and talk) pages: Front, Ev., Wshp., PD.

Case information

Involved parties

Prior dispute resolution


Preliminary statements

Statement by Icewhiz

Starting after this perplexing AfD, I have been cleaning dubious sources, notably Mark Paul ("ignoble ungrateful Jew" myth[1] ,RSN, RfC) which were used in hundreds of articles. I have also fixed:

  1. Loosmark sock (+Poeticbent), IcewhizFix - Describing a Polish pogrom against Jews,[2][3] as Jewish oppression of Poles followed by Germans killing Jews - see AE determining this was a hoax. Note VM loudly asserted restoring this was non-actionable. Also see: Dr. Morris S. Whitcup on Wikipedia's articles
  2. Poeticbent+Loosmark sock, IceWhizFix - Local poles burn 600-2000 Jews alive in barn,[2][4] described as Jewish oppression of Poles followed by Germans killing Jews.
  3. Poeticbent,Loosmark sock,Poeticbent,IceWhizFix: related to 1+2, obfuscation of local killings+explusion+Jedwabne.[2][5]
  4. Poeticbent,IceWhizFix - extermination camp for Jews,[6] described as "intended to kill Jews and Poles from all nearby towns and villages" (Polish citation in article: "Jews".[7])
  5. PoeticbentBiałystok,PoeticbentHistoryOfTheJews,PoeticbentCommons - IceWhizFixBiałystok,IceWhizFixHistoryOfTheJews,IceWhizFixCommons - "Jewish welcoming banner" in 1939 image captions (extended discussion, caption offwiki) - actually election notice to the People's Council of Western Belarus in 1941
  6. Loosmark sock,IceWhizFix - describes the "Polish operation" (one of multiple NKVD national sweeps) as "the genocide of Poles in the Soviet Union", misstating named historians[8] and using a dubious source. Contrast academic sources:[9][10][11].

The wide scope and nature indicate these aren't innocent mistakes, but deliberate distortion/denial rising to WP:HOAX. The small editor pool involved prior to 2018 did not remove such content, and tolerated widespread use of sources that clearly fail WP:RS policy.

Volunteer Marek (VM), adds little new content (see last article 1.5K, single bareurl primary source), has been reverting and stonewalling corrections.

VM's conduct: (see also referred AE)

  1. Despite repeated requests to stop, VM has hounded me. Between 15 and 30 May he has followed me to some 38 articles - 4 new articles I authored, ~20 articles VM never edited previously, and ~14 articles he had edited previously.(interactiontool 15-30May)
  1. VM has restored/inserted material on Jews/communists not supported by citations: "Soviet-armed Jewish militiamen helped NKVD agents send Polish families into exile" (not in source) or against MOS:ETHNICITY(lead) "was a Polish communist official of Jewish background trained...
  2. (below)
  3. WP:NPA/WP:ASPERSIONS:
  4. considers sourced on-topic descriptions of antisemitism in Poland as: "It's a COATRACK for the whole disgusting and racist "Poles are anti-semities" POV into this article.".
  5. WP:PROXYING Loosmark, fails verification:
  6. WP:PROFRINGE/WP:UNDUE - op-eds in right-wing media/blog by far-right activist/historian:[12][13][14][15]
  7. WP:BLPSPS: .

Editors restoring content challenged as failing verification (doubly so from socks(WP:PROXYING)), are expected to verify. However -

  1. VM has restored content contradicted by the cited sources. If a source says "white" an editor shouldn't be saying "black". This is not a "content dispute", but rather WP:CIR. e.g. , describing this as "excuse to remove well sourced text" - besides most of the content not being in the source (+being bullshit: refugees sought USA for standards of living), some of it is refuted in page 72 in citation.
  2. It seems he spent all of 1 minute - 07:00,06:59 different article in examining content challenged on being from a banned sock, failing V (+SYNTH, NPOV, and MOS).
  3. VM has openly admitted he restored newly introduced content challenged as V/NOR without verifying - (Kopciowski, is missing "thousands").
  4. See this discussion - VM seems to be arguing for the sake of arguing (or as a bargaining chip?) for content (WP:BLP scholar attributed) clearly failing V.
  • Clarification (though said all along) - this request is first and foremost about Poeticbent/Loosmark. Examples 1-5 are egregious, show a pattern, can't be explained away as a mistake, well beyond POV pushing. A ban would make WP:REVERTBAN apply, and allow for methodical treatment of vast amount of content by Poeticbent in mainspace. Icewhiz (talk) 08:42, 3 June 2019 (UTC)

@SilkTork:,@Robert McClenon: AE referred this here not since it was not actionable, but since it was too complex and time-consuming (Sandstein,Seraphimblade). In retrospect, I should've filed AE with the worst, and easiest to evaluate diffs - which would've been: allegations of racism: , extremism: , WP:ASPERSIONS: . These are all actionable under DS, and easy to evaluate.Icewhiz (talk) 05:00, 4 June 2019 (UTC)

@Opabinia regalis: - User:Loosmark was banned on 29 November 2010. WP:REVERTBAN would seem to apply to edits afterwards. I am not saying VM is communicating with Loosmark, but that the provision in WP:PROXYING - "Editors who reinstate edits made by a banned or blocked editor take complete responsibility for the content." - applies.Icewhiz (talk) 09:35, 4 June 2019 (UTC)
@AGK: - Jew with a coin (which I authored, and did not expect to turn into a battleground - I saw this a light-weight topic that would be DYKable) is a good example. Despite sourcing, certain editors have been objecting to this being common/widespread/popular (see , tag clarify on popular). Very limited outside input at: Wikipedia:Reliable sources/Noticeboard/Archive 266# Jew with a coin. And now we have the following unresolved dispute: first introduced, taggedFailedV, tagRemoved: spurious tag based on personal OR, attempt to Match source, reverted: "original text was fine". Discussion: Talk:Jew with a coin/Archive 1#Dobrosielski - popularity (VM absent from the discussion). The Polish language source (a preliminary research report) contradicts the text being pushed here (heck - the text itself - "However the practice is very limited in Poland and doesn't have wide popularity with only 19% of Poles surveyed possessing such item and 16% confirming its use." - is a self contradiction - "only 19%"?!?!). Besides being clear in the Polish, We have an academic summarizing the Polish source in this English translation of an article by Ewa Tartakowsky. Which says:

This image is not only widespread: one in two respondents associated it with the superstition according to which it brings prosperity. But it does not automatically follow that people use it. According to Paweł Dobrosielski, “only” 24% of respondents knew that one must place a grosz behind the frame..."

"Another survey" also wrong. After the last revert, I walked away. At RSN/NORN - I'll probably get walls of text and little outside input. At AE - I'll probably get "no action, content dispute". And this misuse of sources (either very poor quality, or misrepresentation) is rampant - particularly in non-English sources that few editors are willing to verify themselves. Introducing content clearly contradicted by the very source you are citing is a conduct issue. Jew with a coin is light subject matter, but this occurs throughout the topic area.Icewhiz (talk) 05:17, 5 June 2019 (UTC)
In terms of WP:AGENDA - I'll readily admit I've performed hundreds of edits challenging use of self-published material by Mark Paul("ignoble ungrateful Jew" myth[1],RSN, RfC), Ewa Kurek (see recent TPM, as well as - referring to her as a revisionist/distorter), op-eds in far-right media (e.g. Nasz Dziennik), etc. - removing content, placing cn tags, or replacing with mainstream academic sources - I happily admit to this per WP:RS/WP:NPOV.
Shockingly - 22 May diff by Piotrus sources such as Kurek are still being brought up despite being "somewhat controversial" (per Piotrus) and self-published by iUniverse. See Piotrus here (or the whole discussion) where Piotrus contrasts Kurek to Jan T. Gross and Jan Grabowski (historian) on the basis of "Polish far-right media".Icewhiz (talk) 06:33, 5 June 2019 (UTC)
  • Additional parties - This was originally opened as an AE referral here. In light of the committee's comments, and since there is indeed an issue throughout the topic area, I intend to bring in the case, should it be accepted, evidence against Piotrus (advocating fringe sources (e.g. above), tag teaming - e.g. diff Piotrus, diff VM (prior to this being on any public fora), and misrepresenting source (and failing to provide quotations per WP:NOENG) - while admitting he did not actually check the sources himself (+a few other cases)), Tatzref (in relation to aforementioned incident + a few other ones), and Xx236 (BLPTALK/personal attacks - e.g. ,,"Icewhiz symhatises with German Nazis"). There is probably merit for additional parties here as well.Icewhiz (talk) 14:17, 8 June 2019 (UTC)
More information references ...

Statement by Poeticbent

Statement by Volunteer Marek

The first 6 diffs from Icewhiz have nothing to do with me, they concern users which have long ceased editing Wikipedia. Putting aside the question of whether Icewhiz is presenting these honestly, I am not going to respond to them, except to note that it’s strange for Icewhiz to try and bring a case against an editor from eight years ago.

In regard to the diffs against me, I tried to respond. And quickly ran out of the word limit. However, all these are content disputes. I do want to say that they misrepresent and falsify the nature of these disputes. Icewhiz accuses me of “UNDUE” or “OR” etc, and it's all false, but at the end of the day, these are run-of-the-mill accusations that Wikipedians often throw at each other. To the extent that it's not the ArbCom’s job to adjudicate content disputes (that’s a matter for likes WP:RSN etc) I would advise the committee to take this case ONLY IF they are willing to look into sources, check what’s actually in them, delve into who’s misrepresenting what.

Regarding the portions of Icewhiz’s statement I do wish to respond to

First is his initial presentation of the problem, which included an odious and utterly false insinuation that I was engaged in “Holocaust denial/distortion”. This is absolute nonsense. Icewhiz did NOT provide a single diff which would even come close to supporting such a contention. He did finally remove that part although apparently only to shorten his statement. However, he reintroduced another repellent accusation even as he “trimmed”. In response to my description of his edits as “shitting on Poland” (yes, I know, I should have worded that better), he responded with:

"Referring to a <diff of my comment>- are Holocaust victims killed by Poles "shit"?

This is messed up. I very clearly was criticizing the fact that overwhelming majority of Icewhiz’s edits in this topic area attempt to portray Poland in a negative light (WP:AGENDA). Icewhiz dishonestly tries to turn that into a claim that I referred to Holocaust victims as “shit”.

This is simply lying and smearing. Obviously I said no such thing nor did I imply it. It’s an abhorrent thing to say and for personal reasons, I am disgusted that someone would accuse someone of such a thing. With both the original insinuation and the odious claim about Holocaust victims Icewhiz did NOT provide a single diff or supporting piece of evidence. This goes beyond WP:ASPERSIONS, it’s simply a smear. And for what? To get an upper hand in an ArbCom case request?

It is one thing to be falsely accused of violating Wikipedia policies like WP:UNDUE or WP:OR. Par for the course. I don’t take it personally. But these two accusations go far beyond that. They are personal, hence my initial strong reaction. I would hope that any normal person in the same position would react the same way. These accusations are not just your usual Wikipedia bickering about POV and sources. They betray a cynical, dishonest, willingness to say anything, accuse a fellow editor of anything, misrepresent anything. Just to win a dispute.

Its exactly this kind of behavior which has led to quick indef blocks in the past. Recently one of Icewhiz’s partners in edit warring, Yanniv was indefinitely banned by User:TonyBallioni for exactly this behavior. Why should Icewhiz get away with what others regularly get indef blocks for?

User:Aquillion below says that this has to do with collapse of WP:AGF. That ship has sailed friend. When someone falsely accuses you of “Holocaust denial/distortion” and falsely claims you referred to Holocaust victims as “shit”, WP:AGF is simply no longer an option.

And that concerns a bigger question. If Icewhiz has no shame in showing up here and lying about other editors, then how do you think he approaches Wikipedia editing in general? He misrepresents what editors said. He misrepresents sources. He misrepresents Wikipedia policies. Etc.

I don’t know what could be done at this point to restore the good faith. I think with some of the others involved in the conflict, like Francois Robere, yeah… good faith can still be assumed, despite everything. But with Icewhiz, the guy needs to seriously rethink and redo how he approaches Wikipedia editing. An indef block or at least a topic ban will give him the time to reconsider.

Regarding User:Alanscottwalker's suggestion of mediation - that is indeed what is needed here. AFAIC it has been suggested before but "some" participants weren't keen on it. Maybe give it another try.Volunteer Marek (talk) 13:23, 5 June 2019 (UTC)

@DeltaQuad: since there are exemptions being granted left and right to the word limit I have no idea what I'm at. Also, if I go over, then you remove, then an exemption is granted, then... removing it in the first place was kind of pointless no? Anyway, since Icewhiz wants to add other people to the case, an obvious person to add is User:François Robere who's been involved in this disputes, consistently and reliably supporting Icewhiz.

Also, Icewhiz says: "I'll readily admit I've performed hundreds of edits challenging use of self-published material by Mark Paul (...), Ewa Kurek (...) op-eds in far-right media (e.g. Nasz Dziennik)" - yeah, except nobody has a problem with THOSE edits. Icewhiz is acting like he's some kind of martyr, battling others to remove these sources, but in reality nobody gives a fudge if he removes them (or even support these removals). The problem is that Icewhiz is removing OTHER well sourced material. Indeed, he'll often use the mere existence of unreliable sources - which are not being used - as an excuse to remove OTHER, reliable, sources. "Oh look, there is this unreliable source Nasz Dziennik out there that nobody here actually wants to use, that means I get to remove all the DIFFERENT reliable sources WP:IJUSTDONTLIKEIT". It's a dishonest switcharoo tactic and part of the reason why talk page discussions go nowhere.Volunteer Marek (talk) 22:46, 8 June 2019 (UTC)

Indeed, come to think of it, the only person here to use far-right sources in an article (a BLP no less) is ... Icewhiz himself. So Icewhiz himself has no qualms using far right sources (fronda.pl, tysol.p, prawy.pl), which he pretends to oppose, when these happen to match his POV. This is gaslighting.Volunteer Marek (talk) 22:51, 8 June 2019 (UTC)

More information Preliminary statements by uninvolved editors. ...

Preliminary decision

Clerk notes

This area is used for notes by the clerks (including clerk recusals).
  • Icewhiz has requested a word limit extension, which is granted to 750 words. For the Arbitration Committee, Kevin (aka L235 · t · c) 23:53, 1 June 2019 (UTC)
    • The increased word count has been extended to all participants. --Cameron11598 (Talk) 19:06, 2 June 2019 (UTC)
  • @Volunteer Marek: you are currently over 2,000 words in your statement please reduce your statement to 750 words or less.--Cameron11598 (Talk) 19:06, 2 June 2019 (UTC)
  • @Piotrus: you are currently over 1,500 words in your statement please reduce your statement to 750 words or less.--Cameron11598 (Talk) 19:06, 2 June 2019 (UTC)
  • I've removed the image in Icewhiz's statement per clerks-l --Cameron11598 (Talk) 19:08, 2 June 2019 (UTC)
  • @Icewhiz: you are over 1700 words please trim your statement to 750 words. --Cameron11598 (Talk) 21:55, 2 June 2019 (UTC)
  • @Risker: Obviously I'm no longer an Arb, but what has been told to us is all people have 750 words on this case request only. I collapsed the sections because they are excessively over (mostly double) the limit. -- Amanda (aka DQ) 04:47, 3 June 2019 (UTC)
  • User:Piotrus has requested a further extension here. It has been passed to the committee. -- Amanda (aka DQ) 04:52, 3 June 2019 (UTC)
  • @Paul Siebert: Please be aware you are at 760 words and have no further room for additional statements. -- Amanda (aka DQ) 14:44, 3 June 2019 (UTC)
  • @Icewhiz: Links to statements or evidence outside of this venue are not permitted. You need to present what you have here. -- Amanda (aka DQ) 15:12, 3 June 2019 (UTC)
  • @Piotrus: You have been extended to a total of 1250 words by Arbitrators. -- Amanda (aka DQ) 17:43, 3 June 2019 (UTC)
  • Recuse having made a statement and been involved in prior dispute resolution. GoldenRing (talk) 12:52, 4 June 2019 (UTC)
  • Several notes:
  • SilkTork's vote is being counted as an oppose at this time per them indicating when commenting.
  • @Icewhiz: We are currently waiting to hear back from Arbitrators on your new extension request. Please be aware even if you are looking for 1250, you are already over that at 1335. I would recommend trimming.
  • @Volunteer Marek: You are still over the permitted 750 words at 813. Please trim or request an extension.
-- Amanda (aka DQ) 09:12, 5 June 2019 (UTC)
  • In regards to VM, I have forced a word removal so that they are at an appropriate length. -- Amanda (aka DQ) 18:28, 6 June 2019 (UTC)
  • @François Robere: So you are aware, you are at the limit and have no further room for replies. -- Amanda (aka DQ) 09:14, 5 June 2019 (UTC)
  • @Volunteer Marek:, Linking to previous statements effectively sidesteps the word limit. Please decide on one statement to make here, and present it. SQLQuery me! 02:51, 6 June 2019 (UTC)
  • I've gone ahead and removed the link. -- Amanda (aka DQ) 18:23, 6 June 2019 (UTC)
  • @Piotrus:, Please do not link to statements, analysis, or evidence elsewhere, including in hidden comments. You'll need to make your statement within the allotted word limit. SQLQuery me! 17:43, 6 June 2019 (UTC)
  • I've gone ahead and removed the link. -- Amanda (aka DQ) 18:23, 6 June 2019 (UTC)
  • @Paul Siebert: You have been granted an additional 250 words by the committee. This brings your total word limit to 1,000 words (750+250 =1000). --Cameron11598 (Talk) 06:48, 8 June 2019 (UTC)

Arbitrators' opinions on hearing this matter (6/0/0)

Vote key: (Accept/decline/recuse)

As there appear to be only two people involved in this - Icewhiz and Volunteer Marek, I think this could be sorted quicker and easier on ANI, perhaps by an interaction ban and/or topic ban. Only if the community are unable to solve this problem should ArbCom get involved, and as there doesn't appear to have been that community discussion yet, I am inclining toward a decline. Meanwhile, I shall give Volunteer Marek a warning for the personal attack on Icewhiz. SilkTork (talk) 16:33, 2 June 2019 (UTC)
  • Folks, please stop arguing the case here. The Committee are not interested at this stage in looking at every single diff, and arguments back and forth on the implications of such diffs. Such detail is for the evidence page if a case is opened. There is no need for extravagant length statements. What we do here is look to see if this is the sort of situation that ArbCom can and should deal with. For that we simply need a summary of the concern, links to where previous dispute resolution has been tried and failed, and a few representative examples of the conduct that is causing concern. Please read Wikipedia:Arbitration/Guide_to_arbitration#Case_request_statements - I'll copy it out here:
In a request for Arbitration, a User tries to show the Arbitrators that there is a dispute requiring their intervention, as well as preliminary evidence of wrongdoing. A short and factual statement of 500 words or fewer should be written, including diffs where appropriate, to illustrate specific instances of the problem. The filing user is also expected to show that prior dispute resolution has already been attempted. Exceptions apply to situations where the Arbitration committee is the only possible venue of dispute resolution, e.g. those involving sensitive real-life evidence, or administrator misconduct. The Request is intended to be a summary of the available evidence including enough information to show why Arbitration is needed. You are not trying to prove your case at this time: if your case is accepted for Arbitration, an evidence page will be created that you can use to provide more detail.
For me, as the filer hasn't shown that appropriate dispute resolution has been tried I'm a decline. Icewhiz and Volunteer Marek please read Wikipedia:Dispute resolution; there are several options there for you to explore, though given the heat generated here, my recommendation is that you take this to ANI, where the community can decide if an interaction ban is sufficient, or if topic bans also need handing out. SilkTork (talk) 16:19, 3 June 2019 (UTC)
I'm seeing that people are saying we should accept this case, but the case as presented before us is of one editor accusing another editor of hounding him and inappropriate edits, and the accused editor saying the fault goes the other way. So - as presented - this is a behaviour dispute between two editors on the same topic. The sort of dispute that normally goes to ANI not AE. That the dispute has failed at AE indicates to me that possibly the dispute keeps going to the wrong venue. I'm also seeing that people are saying the case is complex. Is that because the dispute is unclear, and/or is being presented in the wrong places? If someone can explain from what Icewhiz has presented what would be the scope of this case, that would be a help. For me, what I see is a clash between two editors that could be resolved by an IBan, and a discussion regarding a possible Topic ban for one or either or both which could be appealed after six months. If those who monitor and edit articles relating to Jews in Poland find that topic area is more stable and productive after the outcome of whatever ANI decide, then the matter has been resolved. If problems continue in that area, then the matter can again be brought to the community and sanctions stepped up. Only at the point where the community cannot agree on sanctions, or the community have run out of options should it come to ArbCom. So, again, as presented, this appears to be a dispute between two editors, and so I feel it would be quicker and easier to resolve at ANI; however, if someone can put forward a case request, naming the parties that should be in the case and why, then I will look again, and if appropriate vote to accept. SilkTork (talk) 16:06, 4 June 2019 (UTC)
I've been thinking on this, but I'm still of the (now sole) view that this is a POV Battle/Conduct Dispute that should and can be resolved by the community. The origins of the dispute are common on Wikipedia - a disagreement on POV in articles that relate to religion/ethnicity/nationality. I mentioned my concerns regarding POV Battles a number of times during replies to questions during the ArbCom Elections. I do feel that POV Battles should be of greater concern to the community, and that the community should be looking for better ways to prevent them happening in the first place. Pushing this to ArbCom or AE is not the way that the community should be dealing with such disputes, and is certainly not the long term solution to POV Battles.
Discussion on POV can be really helpful to the strength and neutrality of an article. If people are not questioning POV then bias can creep in. So it is important to have such discussions, and it is helpful to have two editors (or groups of editors) who are approaching a topic from different angles. But when editors go beyond discussing how to improve the article and resort to personal attacks and bad faith accusations, then the community needs to step in and issue sanctions. If the community feels that the current systems in place for dealing with POV Battles is not appropriate, then the community should be actively looking for such a system (and some have been mentioned on this request page). I have faith in this community. In the inventiveness of this community. But the community will not be able to resolve this and future such issues if they keep directing ArbCom to sort it out.
ArbCom will not be able to sort this out, nor will AE, as both forums have the wrong sort of structure, and the wrong remit. Discussions related to this dispute need to be freer and looser than the rigid forms of AE and ArbCom allow. There needs to be greater interchange between the people involved. The forum should not be simply geared up to looking at wrong-doing and assigning sanctions or not. It should be looking at solutions. And allowing cross talk that sparks imaginative ideas. Looking at the conduct between IW and VM we have them often reverting each other. VM will sometimes remove several paragraphs , sometimes a single word . IW will then put the text back: , . That's a content dispute - ArbCom doesn't settle those. And it is difficult to settle this dispute without looking at the content.
And, as I keep saying, the community have not yet had the opportunity to look into this. It has only come to either ArbCom and AE, which, as I keep saying, are not the appropriate forums for dealing with this sort of dispute.
Where I am shifting in thinking is that this should be shoved to ANI just to hand out bans. GoldenRing says Topic bans have been tried, and that's not worked. And a user in this topic area has been issued a Topic ban, and has since given up all editing of Wikipedia. I'm not ruling out issuing such bans if appropriate, but if the edit warring, personal attacks, and casting aspersions is on investigation less than it appears at first glance at this request, then a better solution could be found, and such a better solution is unlikely to come from AE or ArbCom.
Could the community try a Holocaust in Poland Editing Panel? Both would be banned from reverting each other. So if IW or VM find an edit in the topic area that they dislike, they could refer the matter to the Holocaust in Poland Editing Panel who would adjudicate. SilkTork (talk) 11:00, 7 June 2019 (UTC)
  • Oooookay. Yes, I know arbcom makes everyone a little frazzled, but the sweary stompy back-and-forthery is not helping, please rein it in, guys. (Edit summaries included.) @Icewhiz:, I agree with the confusion expressed by some other commenters about focus - your requests starts with a number of diffs dating back to 2011, the latest 2017, by a blocked editor and an inactive one (Note for readers who are spacey like me: Poeticbent's last edits were in May 2018, not 2019.) with the comment that these were issues "until 2018-9". Could you please be specific (but brief!) about what aspects of this are current or ongoing? (Separately, unless you have specific evidence of relevant interactions, I'd drop the "proxying" stuff for now and focus on issues that are current and actionable. But then, this is my personal preference; I don't generally consider claims of "proxying". People can get their editing ideas from wherever they like.) Opabinia regalis (talk) 09:15, 2 June 2019 (UTC)
    • I'm usually first to call for an end to word-limit fussiness, but there's way too much stuff here and I still can't quite make out what the request is. Given that, I'm hesitant to sent it all back to ANI where the mudslinging problem is worse. (Edited to add: to be clear, I'm not asking for anyone to post still more stuff. I would like to see 2-3 sentences about what value arbcom could add here, preferably 0 of which refer to blocked or inactive editors.) Icewhiz, I don't think "proxying" is really what you mean - the letter of WP:PROXYING says that editors should not make edits at the direction of a banned or blocked editor (emphasis original) unless they have an independent reason to do so. If you do have such evidence, please pass it along, but I expect you do not in fact have any evidence that anyone is making edits at the "direction" of an editor blocked eight years ago, and you're really trying to make a different point about retaining material contributed by a blocked editor, somewhere along the lines of the rationale underlying WP:G4. Relatedly, it is fine to argue that you think someone is POV-pushing, but implications of Holocaust denialism are very serious and hurtful and should not be made without extremely compelling evidence. Opabinia regalis (talk) 08:50, 4 June 2019 (UTC)
    • Accept, reluctantly. I find these source-heavy cases difficult when I don't know anything about the topic, and it's not an area where arbcom overall has a strong record of success (in part because you really have to consciously stop yourself from making judgments about personalities and self-presentation if the meat of the material is difficult to wrap your mind around). But I think it's clear from the comments from AE admins and others not involved in the dispute that there's something here that would benefit from a careful structured inquiry. Of course, accepting a case request does not mean accepting its original framing and I think it's worth emphasizing that cases examine the conduct of all parties. Given the way the request stage has proceeded, I also would strongly encourage anyone who thinks that another party has posted insulting or offensive comments should contact the clerks or arbcom as a whole, and should definitely not take matters into their own hands and fire back. Opabinia regalis (talk) 08:06, 7 June 2019 (UTC)
  • Leaning decline, because this appears to be between Icewhiz and Volunteer Marek. If so, I think ANI should have a shot at it first. And I endorse SilkTork's warning, Marek – dial it back. Katietalk 18:35, 2 June 2019 (UTC)
* Decline in favor of other forms of dispute resolution. Piotrus, that was helpful, and I'd like ANI to get a crack at topic bans and/or IBANs first. Katietalk 12:48, 4 June 2019 (UTC)
Okay, I'm convinced. Accept to examine behavior but not to evaluate sourcing. We tried that once and it just doesn't work. Katietalk 17:06, 5 June 2019 (UTC)

* I've read a lot of the discussion here and for one, there is WAY too much bickering going on. This mater should be handled at ANI for the community as a whole to discuss. Decline. RickinBaltimore (talk) 16:32, 3 June 2019 (UTC)

The more I see of this, the more I realized I was incorrect at first. The behavior here is definitely in need of ArbCom's review and a case I now feel is justified. Accept RickinBaltimore (talk) 12:42, 6 June 2019 (UTC)
  • Placeholder: I intend to review this request and vote as soon as possible. AGK  13:17, 4 June 2019 (UTC)
    Accept. We are setting the bar too high here. If even we are not sure yet what the dispute entails, what hope does the community have of defining the problem, let alone sorting it? The community designed arbitration for this kind of dispute. Many encyclopedia articles are being damaged by this dispute. Volunteer Marek (MK) is a prolific participant in the dispute, but seems to be right enough that administrators at AE recognise there is more to the matter than first appearances. That is where the process breaks down. We designed AE to sanction misconduct, not to act as a miniature ArbCom. The best method of working out what is causing these problems is arbitration. AGK  21:20, 4 June 2019 (UTC)
  • On the surface as framed, this appears to be an upset between two editors, but I'm glad I held off on posting. I'm persuaded by GoldenRing's links especially, this has been going on for a while, and it doesn't look like it's going to get any better. I can't say it's a case I relish taking on, but you can mark me as Accept. WormTT (talk) 20:48, 6 June 2019 (UTC)
  • Accept. I'm reasonably convinced that this is intractable as is, and will require the kind of back-breaking that ArbCom was set up for. We're not qualified to establish the reliability of the sources, but I think we can examine whether the sources presented are being quoted correctly (misrepresenting what a source says is a conduct issue, IMO) and whether or not that's being done systematically/intentionally. PMC (talk) 23:49, 6 June 2019 (UTC)

Temporary injunctions

Interaction ban

2) Volunteer Marek (talk · contribs) and Icewhiz (talk · contribs) are prohibited from interacting with or commenting about one another, except that they may submit (directly to the committee) responses to a proposed decision in these proceedings. Arbitrators supporting will desire immediate implementation under net 4 rules.

Enacted --Cameron11598 (Talk) 17:11, 19 August 2019 (UTC)
Passed 4 to 0 under net 4 rules for immediate implementation at 17:14, 19 August 2019 (UTC)

Final decision

Principles

Purpose of Wikipedia

1) The purpose of Wikipedia is to create a high-quality, free-content encyclopedia in an atmosphere of camaraderie and mutual respect among contributors. Contributors whose actions are detrimental to that goal may be asked to refrain from them, even when these actions are undertaken in good faith; and good faith actions, where disruptive, may still be sanctioned. Use of the site for other purposes is prohibited.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Verifiability

2) On Wikipedia, the reliability and accuracy of content is paramount. Wikipedia:Verifiability, a policy, requires that article content that is challenged or likely to be challenged – within reason – must be attributed to a published reliable source supporting the information presented.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Preexisting disputes

3) Issues that are contentious in real life are likely to be so on Wikipedia. However, Wikipedia does not permit disputed issues to be imported into its encyclopedia articles or to affect the pursuit of its purpose. Conduct that furthers a preexisting dispute on Wikipedia should receive special attention from the community, up to and including sanctions. It is perfectly possible to present a balanced, accurate, and verifiable encyclopedia article about contentious issues or preexisting disputes.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Neutral point of view

4) All Wikipedia articles must be written from a neutral point of view, with all relevant points of view represented in reasonable proportion to their importance and relevance to the subject-matter of the article. Undue weight should not be given to aspects that are peripheral to the topic. Original research and synthesized claims are prohibited. A neutral point of view requires fair representation of all significant historical interpretations. This refers to legitimate differences in interpretation of the historical record, as opposed to views considered fringe, outdated, or significantly biased or inaccurate by the substantial consensus of reliable sources.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Non-English language sources

5) Wherever possible, English-language sources are preferable to sources in other languages so that English-speaking readers can readily verify the content of the article and, if desired, can consult the source for more information. However, sources in other languages are acceptable where an English equivalent is not available. Where editors translate a direct quote, they should quote the relevant portion of the original text in a footnote or in the article. There is no requirement for a translation of the source in other circumstances, although courtesy and good practice suggest that if a genuine concern arises concerning the content or reliability of the foreign-language source, providing a translation or paraphrase of the relevant portion of its content will help address the concern.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Talk pages

6) The purpose of a Wikipedia talk page is to provide space for editors to discuss changes to its associated article or project page. Article talk pages should not be used by editors as platforms for their personal views. Users should approach article talk page discussions as a place to advance arguments, listen to other users, and try to move the group towards a consensus.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Findings of fact

Locus of the dispute

1) This complex dispute centers on reliable sourcing, non-neutral point of view, and battleground behavior over a range of articles related to anti-Semitism and Jewish history in Poland, specifically in relation to World War II and The Holocaust, and including a number of BLPs of scholars studying these topics.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Editing environment in the topic area

2) It is immediately evident that the editing environment in the topic area is highly strained, featuring assumptions of bad faith, personal attacks, incivility, and battleground behavior.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

History at dispute-resolution venues

3) The topic area at issue is covered by discretionary sanctions originally authorized in 2011 in the Eastern Europe case. The current dispute has seen numerous arbitration enforcement filings, including:

More information Link, Filer ...

In addition, a request for amendment of the Eastern Europe case was filed by Icewhiz on 16 April 2019, and was declined by the committee. Aspects of the dispute have also been covered at the reliable sources noticeboard (e.g. 1, 2, 3, 4) and the biographies of living persons noticeboard (e.g. 1, 2, 3).

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Incivility and inflammatory rhetoric

4) A background of abrasive and uncivil commentary features in many conversations related to this dispute, including conversations in dispute-resolution venues:

  • Volunteer Marek engaged in name-calling (), made unhelpfully sarcastic talk-page comments (, ), and personalized disputes (, )
  • Icewhiz made unnecessarily inflammatory comments (), made negative insinuations about Poland (), and made inappropriate ethnically derogatory comments (, )
Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Assuming bad faith

5) Both parties regularly assume the worst of others' editing, including interpreting errors, misunderstandings, and disagreements about sources as hoaxing and lying.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Battleground behavior

6) Participants in this topic area have demonstrated significant battleground behavior, often apparently reflecting efforts to "win" content disputes via conduct-review mechanisms. Icewhiz has been involved in an unusually large number of AE requests as filer, subject, or commenter. Both Icewhiz and Volunteer Marek were topic-banned for three months in July 2018 for battleground behavior.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Hounding

7) On 10 occasions in a one-month period, Volunteer Marek appeared to edit an article because Icewhiz did so (see Evidence § Volunteer Marek's harrassment of Icewhiz: Hounding).

Passed 5 to 1 at 19:01, 22 September 2019 (UTC)

Accusations of sockpuppetry and proxying

8) Poeticbent was blocked in 2011 for sockpuppetry and subsequently unblocked after an appeal to the Arbitration Committee in March 2012. He last contributed to Wikipedia in May 2018. No evidence has been supplied that he has engaged in sockpuppetry or proxying since his departure.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Insinuations of Holocaust denial

9) Icewhiz inappropriately and falsely linked Volunteer Marek to Holocaust denial ()

Passed 5 to 1 at 19:01, 22 September 2019 (UTC)

BLP violations

10) Significant aspects of this dispute center on sourcing in BLPs and on commentary about BLP subjects, generally scholars of the topic at issue.

  • Icewhiz has used inappropriate sources in BLPs (), made negative edits to BLPs () including editorializing in Wikipedia's voice (, ), and made arguably BLP-violating edits on talk pages by posting negative claims or speculations about living scholars (, )
Passed 4 to 1 at 19:01, 22 September 2019 (UTC)

Sourcing disputes

11) Large volumes of evidence in this case center on disputed sourcing, including allegations of bias, POV-pushing, use of low-quality sources. Editors involved in these disputes are not limited to the named case parties.

Passed 5 to 0 at 19:01, 22 September 2019 (UTC)

Challenges in evaluating evidence

12) Many of the issues in this dispute center on subtleties of source interpretation – for example, whether a particular source is reliable, whether a particular author is qualified, and whether a source is being misunderstood or misrepresented. RSN and talk page RfCs have often failed to settle these questions, in part because the sources are largely written in Polish and there are few uninvolved editors able to read them. This fact has also hampered arbitrators' ability to efficiently investigate claims related to source interpretation and representation.

Passed 5 to 0 at 19:01, 22 September 2019 (UTC)

Specific-article sourcing restrictions

13) In June 2018, as part of an arbitration enforcement action, NeilN (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) enacted sourcing restrictions on the article Collaboration in German-occupied Poland, stating Only high quality sources may be used, specifically peer-reviewed scholarly journals and academically focused books by reputable publishers. English-language sources are preferred over non-English ones when available and of equal quality and relevance. and Anyone found to be misrepresenting a source, either in the article or on the talk page, will be subject to escalating topic bans. The effect of this restriction has been positively received.

Passed 5 to 0 at 19:01, 22 September 2019 (UTC)

Events since the close of the workshop

14) Since the close of the workshop:

Passed 5 to 0 at 19:01, 22 September 2019 (UTC)

Remedies

Poeticbent removed as a party

1) Poeticbent is removed as a party to this case.

Passed 5 to 0 at 19:01, 22 September 2019 (UTC)

Icewhiz banned from interacting with Volunteer Marek

More information Amended by motion at 02:39, 1 December 2019 (UTC) ...

2) Icewhiz (talk · contribs) is indefinitely banned from interacting with or commenting on Volunteer Marek (talk · contribs) anywhere on Wikipedia (subject to the ordinary exceptions).

Passed 5 to 0 at 19:01, 22 September 2019 (UTC)
Amended by motion 8 to 0 at 02:39, 1 December 2019 (UTC)

Icewhiz topic-banned

3b) Icewhiz (talk · contribs) is topic-banned from the history of Poland during World War II, including the Holocaust in Poland. This topic ban may be appealed after one year has elapsed.

Passed 5 to 0 at 19:01, 22 September 2019 (UTC)

Volunteer Marek topic-banned

More information Rescinded remedy. ...

Article sourcing expectations

More information Superseded versions, Superseded version (until May 2021) ...

5) All articles and edits in the topic area of Polish history during World War II (1933-1945) and the history of Jews in Poland are subject to a "reliable source consensus-required restriction."

Passed 4 to 1 at 19:01, 22 September 2019 (UTC)
Amended by motion at 18:48, 9 May 2021 (UTC)
Amended by remedy at 16:30, 20 May 2023 (UTC)
Amended by motion at 21:15, 4 January 2024 (UTC)

Acknowledgment of delay

6) The committee acknowledges the lengthy delay in preparing the proposed decision for this case. We apologize to the case participants and to other editors interested in the topic area, and thank them for their patience.

Passed 6 to 0 at 19:01, 22 September 2019 (UTC)

Extended confirmed restriction

More information Superseded version (until September 2021) ...
More information Superseded version (until December 2022) ...

7) The extended confirmed restriction is imposed on edits and pages related to the history of Jews and antisemitism in Poland during World War II (1933–45), including the Holocaust in Poland, broadly construed. As designated by the Eastern Europe arbitration case, the area also remains a contentious topic.

Passed 6 to 0 by motion at 19:57, 30 May 2020 (UTC)

Amended by motion at 10:15, 20 September 2021 (UTC)
Amended by motion at 21:36, 14 December 2022 (UTC), implemented at 18:24, 23 September 2023 (UTC)

Enforcement

Enforcement of restrictions

0) Should any user subject to a restriction in this case violate that restriction, that user may be blocked, initially for up to one month, and then with blocks increasing in duration to a maximum of one year.

In accordance with the procedure for the standard enforcement provision adopted 3 May 2014, this provision did not require a vote.

Appeals and modifications

More information 0) Appeals and modifications ...
In accordance with the procedure for the standard appeals and modifications provision adopted 3 May 2014, this provision did not require a vote.
Comments:

Amendments

Antisemitism in Poland: Motion (December 2019)

Remedy 2 of Antisemitism in Poland ("Icewhiz and Volunteer Marek interaction-banned") is renamed Icewhiz banned from interacting with Volunteer Marek and amended to read:

Icewhiz (talk · contribs) is indefinitely banned from interacting with or commenting on Volunteer Marek (talk · contribs) anywhere on Wikipedia (subject to the ordinary exceptions).
Passed 8 to 0 by motion at 02:39, 1 December 2019 (UTC)

Antisemitism in Poland: Motion (May 2020)

The following is added as a remedy to the Antisemitism in Poland arbitration case: 7) 500/30 restriction: All IP editors, users with fewer than 500 edits, and users with less than 30 days' tenure are prohibited from editing articles related to the history of Jews and antisemitism in Poland during World War II (1933–45), including the Holocaust in Poland. This prohibition may be enforced preemptively by use of extended confirmed protection (ECP), or by other methods such as reverts, pending changes protection, and appropriate edit filters. Reverts made solely to enforce the 500/30 rule are not considered edit warring.

    • Editors who are not eligible to be extended-confirmed may use the Talk: namespace to post constructive comments and make edit requests related to articles within the topic area, provided they are not disruptive. Talk pages where disruption occurs may be managed by the methods mentioned above.
    • Standard discretionary sanctions as authorized by the Eastern Europe arbitration case remain in effect for this topic area.

Passed 6 to 0 by motion at 19:57, 30 May 2020 (UTC)

Antisemitism in Poland: Motion (December 2020)

Remedy 4b of Antisemitism in Poland ("Volunteer Marek topic-banned") is rescinded.

Passed 7 to 1 by motion at 02:34, 18 December 2020 (UTC)

Amendment (May 2021)

Remedy 5 of the Antisemitism in Poland case ("Article sourcing expectations") is amended to read as follows: The Arbitration Committee advises that administrators may impose "reliable-source consensus required" as a discretionary sanction on all articles on the topic of Polish history during World War II (1933-45), including the Holocaust in Poland. On articles where "reliable-source consensus required" is in effect, when a source that is not a high quality source (an article in a peer-reviewed scholarly journal, an academically focused book by a reputable publisher, and/or an article published by a reputable institution) is added and subsequently challenged by reversion, no editor may reinstate the source without first obtaining consensus on the talk page of the article in question or consensus about the reliability of the source in a discussion at the Reliable Sources Noticeboard.

Passed 10 to 0 with 1 abstention by motion at 18:48, 9 May 2021 (UTC)

Amendment (September 2021)

Remedy 7 of the Antisemitism in Poland case ("500/30 restriction") is retitled "Extended confirmed restriction" and amended to read as follows:

Extended confirmed restriction

7) The extended confirmed restriction is imposed on edits and pages related to the history of Jews and antisemitism in Poland during World War II (1933–45), including the Holocaust in Poland, broadly construed. Standard discretionary sanctions as authorized by the Eastern Europe arbitration case remain in effect for this topic area.

Passed 8 to 0 by motion at 10:15, 20 September 2021 (UTC)

Motion: contentious topic designation (December 2022)

21) Each reference to the prior discretionary sanctions procedure shall be treated as a reference to the contentious topics procedure. The arbitration clerks are directed to amend all existing remedies authorizing discretionary sanctions to instead designate contentious topics.

Passed 10 to 0 with 1 abstention by motion at 21:36, 14 December 2022 (UTC)

Amendment (May 2023)

2) Remedy 5 of Antisemitism in Poland is superseded by the following restriction:

All articles and edits in the topic area of Polish history during World War II (1933-1945) and the history of Jews in Poland are subject to a "reliable source consensus-required" contentious topic restriction. When a source that is not an article in a peer-reviewed scholarly journal, an academically focused book by a reputable publisher, and/or an article published by a reputable institution is removed from an article, no editor may reinstate the source without first obtaining consensus on the talk page of the article in question or consensus about the reliability of the source in a discussion at the Reliable Sources Noticeboard. Administrators may enforce this restriction with page protections, topic bans, or blocks; enforcement decisions should consider not merely the severity of the violation but the general disciplinary record of the editor in violation.

Passed 7 to 2 with 3 abstentions by remedy at 16:30, 20 May 2023 (UTC)

Amendment (January 2024)

Clerks are instructed to add a new section, entitled "Reliable source consensus-required restriction" to the Enforcement section of the Arbitration Procedures with the following text:

The Committee may apply the "Reliable source consensus-required restriction" to specified topic areas. For topic areas with this restriction, when a source that is not an article in a peer-reviewed scholarly journal, an academically focused book by a reputable publisher, and/or an article published by a reputable institution is removed from an article, no editor may reinstate the source without first obtaining consensus on the talk page of the article in question or consensus about the reliability of the source in a discussion at the Reliable Sources Noticeboard. Administrators may enforce this restriction with page protections, topic bans, or blocks; enforcement decisions should consider not merely the severity of the violation but the general disciplinary record of the editor in violation.

Remedy 5 of Antisemitism in Poland is superseded by the following restriction:

All articles and edits in the topic area of Polish history during World War II (1933-1945) and the history of Jews in Poland are subject to a "reliable source consensus-required restriction".

Wikipedia:Requests for arbitration/Eastern Europe is amended to include the following restriction:

All articles and edits in the topic area of Lithuania history during World War II (1933-1945) and the history of Jews in Lithuania are subject to a "reliable source consensus-required restriction."

Clerks are instructed to link to the Arbitration Procedures in the two restrictions above and are empowered to make other changes necessary to implement this new enforcement procedure.

Passed 8 to 0 with 2 abstentions by motion at 21:15, 4 January 2024 (UTC)

Enforcement log

Any block, restriction, ban, or sanction performed under the authorisation of a remedy for this case must be logged at Wikipedia:Arbitration enforcement log, not here.


Share this article:

This article uses material from the Wikipedia article Wikipedia:APLRS, and is written by contributors. Text is available under a CC BY-SA 4.0 International License; additional terms may apply. Images, videos and audio are available under their respective licenses.