Connect with us
The Residences advertisement

Uncategorized

Wikipedia’s ‘Supreme Court’ tackles alleged conspiracy to distort articles on Holocaust

(JTA) — When a pair of professors earlier this month published a paper accusing a group of Wikipedia editors from Poland of revising articles to distort the history of the Holocaust, their research went viral.

Most academic articles are seen by dozens or hundreds of people at best. This one, published in The Journal of Holocaust Research, hit more than 27,000 pageviews within weeks.

The paper’s reach was fueled by its analysis, unprecedented in the academic literature on Wikipedia, and its finding that a dedicated group has for some 15 years manipulated a source of information used by millions in ways that lay blame for the Holocaust on Jews and absolve Poland of almost any responsibility for its record of antisemitism.

The paper caught the eye of not just scholars and journalists but of the people in charge of resolving disputes over editing on crowd-sourced Wikipedia, the seventh-most popular website on the internet and one that is seen as the last bastion of shared truth in an ever-fracturing online environment.

Typically, disputes among Wikipedia editors are resolved through community consensus mechanisms, but occasionally those mechanisms fail and allegations are brought to Wikipedia’s Arbitration Committee, a panel of elected editors known as Wikipedia’s Supreme Court. 

“Wikipedia is not exactly democratic but anarchistic in a way that actively discourages any sort of an authority coming to solve a dispute,” said Joe Roe, a veteran Wikipedia editor who served on the committee in 2019 and 2020. “The Arbitration Committee is a very limited exception.”

In this case, something especially unusual happened. The Arbitration Committee, or ArbCom, decided to look into the allegations without receiving a formal request to do so. No one could recall the committee taking such a step in its nearly two decades of existence. 

“A myopic decision here could result in untold numbers of people being fed a distorted view of Jewish/WWII history, which could have very real consequences given the recent amplification of violently antisemitic rhetoric by mainstream public figures,” wrote a user named SamX in a public post about the case. “ArbCom needs to get this right.”

The article that triggered the opening of the case was published under the title, “Wikipedia’s Intentional Distortion of the History of the Holocaust.” It accused 11 current and former editors of intentional distortions to numerous articles relating to the Holocaust in Poland. The paper referred to the editors by their usernames but also provided their real names if they had publicly identified themselves on Wikipedia message boards. 

“Due to this group’s zealous handiwork, Wikipedia’s articles on the Holocaust in Poland minimize Polish antisemitism, exaggerate the Poles’ role in saving Jews, insinuate that most Jews supported Communism and conspired with Communists to betray Poles, blame Jews for their own persecution, and inflate Jewish collaboration with the Nazis,” wrote co-authors Jan Grabowski, a historian at the University of Ottawa, and Shira Klein of the history department at Chapman University in Orange, California. 

Normally, mistakes on Wikipedia, whether intentional or not, can be quickly fixed by experienced editors who deploy a set of rules regarding sourcing and style. But in this case, the alleged distortionists know Wikipedia’s mechanisms well enough to at least appear to follow the rules and are willing to spend time arguing with other editors who step in to intervene. It becomes harder to get to the truth because they work to discredit established historians and prop up fringe voices to create the semblance of a real-world debate over historical events, according to the article. 

In one of the dozens of examples documented in the study, the alleged distortionists have tried to pass the self-published work of an antisemitic Polish writer named Ewa Kurek as a reliable source. Kurek has said that COVID-19 is a cover for an attempt by Jews to take over Europe and that Jews enjoyed life in Nazi ghettos. An editor named Volunteer Marek argued in a backstage conversation among editors that Kurek should be cited as any “mainstream scholar” would be. And another editor, working on an article about a 1941 massacre of Jews in Poland, added Kurek’s claim that minimized the number of Jewish victims and exonerated Polish perpetrators. 

Jewish school children pose for a portrait in the 1930s in Wizna, near Jedwabne, Poland. New research revealed that members of the Polish community killed their Jewish neighbors on July 10, 1941 during World War ll despite previous claims that Nazi Germans were entirely responsible. Polish President Aleksander Kwasniewski apologized for the massacre of hundreds of Jews by their neighbors during ceremonies marking the 60th anniversary of the murders. (Laski Diffusion/Getty Images)

One thing the research didn’t discuss is what motivates these editors to invest so much time and effort into distorting Wikipedia. Klein said the omission was deliberate. 

“We’ve been very careful not to make any assumptions on what drives them or what their politics are,” Klein said. “Instead, we’ve tried to focus just on what they’ve done, which is in the written record. And as we say in the article, we don’t see any evidence of them being tied to a government or being in the service of anyone else.”

Klein’s disclaimer obliquely points to a larger challenge around the historical record of the Holocaust in Poland. A central tenet of the country’s ruling Law and Justice party is defending the image of ethnic Poles and imposing nationalist narratives on the past, especially the period of World War II. While history shows that many Poles participated in the persecution of Jews, Poland’s nationalist right insists on portraying Poles only as victims or heroes. 

In 2018, the Polish government passed what’s known as the Polish Holocaust Law, which makes it illegal to slander the Polish nation or blame the country for Nazi crimes. In practice, the law has served to censor scholars and chill debate. 

Grabowski, Klein’s co-author on the paper, has for years sparred with the nationalist right over Poland’s historical memory. He sued a Polish group that accused him of publishing lies about Polish history in 2018, and in 2021 was ordered by a Polish court to apologize for his research before an appeals court ultimately overturned the order. 

Domestically, Poland’s ultranationalists have largely won the war over the public discourse, which has freed them to focus on the global scene, where English-language Wikipedia is regarded as a major battlefront. 

In this atmosphere, even something as basic as the background of Yiddish novelist and Nobel prize laureate Isaac Bashevis Singer can become fodder for debate. For years, Singer was at the center of a fight between two editors over whether Singer was best described in the first line of his Wikipedia article as a Jewish or Polish author. The eventual compromise — “Polish-born Jewish American” — lasted for almost two years until Feb. 23 when someone again dropped the “Jewish.”

The Wikipedia editors now being accused of distorting articles to further nationalist narratives have rejected the allegations against them. 

“I have not engaged in any ‘Holocaust distortion,’ on Wikipedia or anywhere else. I am not a ‘right-wing Polish nationalist,’” said Volunteer Marek in a public comment on a Wikipedia message board that was endorsed by at least one other alleged distortionist. “I am not part of some nefarious ‘Polish conspiracy’ on Wikipedia which seeks to manipulate content. All of these accusations are ridiculous and absurd. They are particularly disgusting and vile since they go against everything I believe in.”

In the debate about how to handle the case, dozens of arbitrators and ordinary Wikipedia editors — all volunteers — spoke of the situation on a Wikipedia message board as something close to an existential crisis for Wikipedia. Not only was the website accused of being used to spread antisemitic propaganda, but it was also alleged to be vulnerable to large-scale manipulation by a small group of bad-faith actors. 

There is little confidence in the community that a solution is within reach. By its own rules, the committee isn’t supposed to decide on disputed information. It’s more of a disciplinary body that evaluates the behavior of Wikipedia editors and can ultimately decide whether to restrict their editing privileges or ban them outright. 

But figuring out if the accused editors have indeed evaded safeguards and undermined Wikipedia’s integrity would seem to require that the arbitrators become experts on the history of the Holocaust in Poland. 

The decision to take up the case serves to acknowledge that the committee failed to solve the problem when it last considered complaints about editing related to the Holocaust in Poland about two years ago. That was during Roe’s tenure and he says the committee was distracted by another dispute at the time. 

“It can’t be escalated further than it already has in our mechanisms,” Roe said. “The best we can do is what’s currently happening now — just put it through those mechanisms again, and hope that something better will come out on the other side.”

In explaining why the committee must nevertheless take on the case, an arbitrator who goes by Wugapodes commented that the only other choice is to kick the can down the road. 

“This will not be an easy issue to resolve, but the committee was not convened to solve easy issues,” Wugapodes wrote, pointing out that the timing is right given the attention and involvement of outside experts and editors. “We can leverage these resources now or wait for this decade-long problem to get still worse.”

By a vote of nine to one on Feb. 13, the committee decided to open the case. The proceedings, which start with an evidence-gathering phase, are expected to last up to six weeks, after which they can decide to ban and restrict offending editors. 

Beyond that, an unorthodox last resort option is also available. Wikipedia’s so-called Supreme Court could ask for help from an even higher authority: the Wikimedia Foundation, a nonprofit that owns the encyclopedia. The foundation intervened in 2021 in what some see as a similar scenario of a far-right takeover on the Croatian-language Wikipedia, hiring an outside expert to disentangle the web of obfuscation and banning a set of editors. 

Roe said that his tenure on the committee in 2019 and 2020, which featured related complaints about the editing of articles on the Holocaust in Poland, helped lead him to believe that Wikipedia should embrace change, at least when it comes to controversial political topics. 

“I would like to see these difficult and politically charged content problems be referred to a new body made up of external experts, and that we don’t insist on doing everything internally among the community volunteers,” Roe said.

But he acknowledged that such a scenario is unlikely to result from the Poland dispute. 

“It’s not a popular view and it kind of goes against the general idea of Wikipedia,” he said. 

—
The post Wikipedia’s ‘Supreme Court’ tackles alleged conspiracy to distort articles on Holocaust appeared first on Jewish Telegraphic Agency.

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Uncategorized

Is it a tornado or bomb warning? No, it’s the Shabbat siren!

One Friday, shortly after I moved to New York City, I was walking through Bedford-Stuyvesant when an air raid siren went off. As it wailed, a group of older Black men playing chess in the park stood up, shook hands and clapped each other on the back. “Shabbat Shalom!” they said to each other. “Gut shabbes!”

I have no idea if any of these men were Jewish. But they knew what the siren was for. After all, they go off every week in the very Jewish neighborhoods of Crown Heights, Borough Park, Midwood and Williamsburg, to mark the arrival of Shabbat. Twice, actually: Once 18 minutes before Shabbat, as a warning, and then moments before Shabbat begins. They also blare before holidays such as Passover, Rosh Hashanah and Yom Kippur.

Not everyone feels so positively about the Shabbat sirens, however — or, as one Redditor called them, “shalarms.” They’ve startled and panicked plenty of newer, unfamiliar residents. On Reddit, transplants near the Jewish neighborhoods often ask their fellow residents if there is some sort of bomb or tornado warning. A friend of mine told me she had to Google it when she first moved to the area, confused by the weekly wailing.

But why air raid sirens? Who runs them? Why aren’t there similar alarms in most Jewish neighborhoods, or other cities with many Jews? (A siren briefly made an appearance in London, and was quickly removed.) And how on earth did this custom develop in the first place? The mystery is surprisingly difficult to solve.

Of sirens and shofars

According to the Talmud, in the tractate Shabbat, Jews are supposed to announce the approach of the Sabbath with six blasts of a shofar, each of which corresponds to an act of preparation for the evening:

“The first blast is in order to stop the people from work in the fields. The second blast is to stop those who are working in the city, and to inform the proprietors to close the stores. The third is to inform them to light the Shabbat light.”

The Talmud instructs there be a pause after the third blast that lasts “the length of time it takes to fry a small fish or to stick bread to the sides of the oven” so that anyone who forgot to cook “and needs those foods for Shabbat may do so then.”

As Jews were ousted from Jerusalem in the early second century, this practice fell out of favor — it drew too much attention to an already-persecuted group. But some version of the practice was kept alive in many Jewish communities around the world. Some places, including Krakow in Poland, had a town crier who would go through the Jewish neighborhoods to remind people of the incoming Sabbath. In Jerusalem in the 1930s, someone would walk through Mahane Yehuda market to warn shopkeepers that it was time to shutter their stores. And in Djerba, Tunisia, someone still blows a shofar on a roof in the Jewish neighborhood.

Perhaps this is what inspired the sirens — though the air raid sirens heard in Brooklyn do not give blasts in the sound of a shofar, nor are there six of them. They do seem to operate by a similar logic, however; a gap of 15 minutes between the two sirens allows people to rush home, take a quick shower or finish frying a small fish, apparently. In today’s New York City, no one needs time to trudge back from a field, but a warning call is still relevant.

And sirens announce Shabbat in religious cities across Israel, including in Jerusalem, differentiated from the sirens that warn of missile fire only by cadence — a steady tone for Shabbat, an oscillating pitch for rockets. (During times of war, to reduce confusion and blood pressure, Jerusalem has sometimes broadcast religious melodies instead of a siren.)

Battles over noise

The Brooklyn sirens are independently operated and they don’t come from one central authority in any given neighborhood; there are multiple in the Orthodox area of Midwood in Brooklyn, on top of various yeshivas, and several throughout the Satmar areas of Williamsburg and the edges of Bed-Stuy. Crown Heights seems to have only a single horn, on top of the synagogue Chevra Shas — but it’s powerful enough to reach my apartment, more than half a mile away.

They are not universally beloved; neighbors have complained about the noise level and disruption, filing complaints with the city for sirens that have reached as high as 106 decibels — about the same as a jackhammer —  sometimes resulting in tickets from the city’s Environmental Protection Agency issued to the yeshivas or synagogues housing each alarm. There have been Change.org petitions to ban them, and people have regularly called the police on their local sirens.

But the synagogues operating the alarms have resisted, pointing out that noise limits have exemptions for religious institutions, and citing nearby churches bells and mosque calls to prayer that reach similar decibel levels.

A similar interfaith alliance has been forged in Israel. In 2016, Orthodox political parties in Israel, which usually stand in opposition to Arab parties, blocked a bill requiring mosques to lower their volume for the call to prayer. Their fear was that any ruling about religious noise ordinances would limit the Shabbos siren too.

Some cities, often more religious ones like Jerusalem or Bnei Barak, run Shabbat sirens municipally, but in others, they are installed and distributed by an organization called Noam Kedushat — which specializes in speakers that play melodies instead of a loud tone — or are even operated by individuals off of their own roofs. There have been feuds over the sirens, particularly in religiously divided cities; progressive party Meretz tried to block the sirens in Tel Aviv, categorizing them as noise disturbances, and there have been lawsuits in Beer Sheva over a Shabbat speaker one woman installed on her house.

As religion increasingly splits Israeli politics, the sirens have become increasingly contentious; secular residents regard them as an annoyance or impediment akin to the fact that Israel’s public transit does not run on Shabbat. This year, a group of activists claimed the sirens amounted to “religious coercion.”

In Brooklyn, however, even after Oct. 7 when antisemitism has risen, public feeling toward the sirens is generally warm. Every few months, a Reddit post pops up asking about the siren. And every time, commenters reliably identify the noise as “our Jewish friends,” “your Jewish neighbors” or something similarly friendly; some celebrate it as an announcement of the weekend.

At most, they find it slightly annoying, but not particularly bothersome. A woman at a bus stop on the same block as one of the sirens told me that it shocked her at first — “It was like a tsunami of sound,” she said. “But you get used to it. It’s annoying but it’s only on Fridays.”

As my friend Phil put it, they are part of the “delightful (noisy) fabric of the city.”  He likes to imagine “it’s two old siren nerds going up on the roof to crank the war surplus siren they lovingly maintain.”

But is that what’s happening?

A loud mystery

It’s not clear how long the sirens have been marking Shabbat in New York City; a 1991 New York Times article on the Crown Heights riots noted the sirens. In a 2014 article on a Chabad news site, a rabbi named Mendel Goldstein claimed to have invented the Crown Heights siren and said at the time of publication that he’d been running it for 30 years, placing that siren’s birth in the mid-1980s.

There is shockingly little information about the sirens publicly available — not who owns them, or how they run, or whether they’ve been updated over the decades. A 2014 article in Gothamist, ostensibly about the sirens, is in fact largely about the city’s history with actual air raid sirens, during World War II. No synagogue or yeshiva has ever commented to a mainstream news outlet about the noise complaints, and no one has gone on record explaining how they run in NYC. Somehow, the Shabbos versions remain elusive, even though they’re a hard-to-miss part of life in Brooklyn.

And despite the warm feelings many Brooklynites seem to hold toward the sirens, people are oddly close-lipped and even hostile about their origin story or their owners.

The air raid siren in Crown Heights, on the roof of a synagogue on Kingston Ave. Photo by Mira Fox

I went to find the source of the sound nearest me one Friday afternoon, and was standing there, staring up at it and waiting when it went off, as dozens of Chabad families streamed by me. One man, perhaps seeing an opportunity to bring me into the Chabad fold, stopped and smiled and asked me if I knew what the tall pole with flared air horn speakers on top was, I said I knew what it was, but nothing else about it, and that I was a journalist trying to discover its history; he speed-walked away.

I got a bit more of information from an elderly white-bearded man, who stopped to ask me if I was looking for a synagogue. He told me that the siren goes off automatically, programmed once a year — disappointing information for Phil’s romantic vision of old nerds maintaining their analog siren. But my most knowledgeable source yet peeled off to greet a friend when I tried to learn more.

After reaching out to a Chabad-run neighborhood news site for Crown Heights, I got a number for Mendel Goldstein. When he didn’t answer numerous calls or messages, I asked around and got the number for his nephew Levi. He answered, but while he was jovial, he was also openly suspicious of my intentions. He wanted to know who gave out his phone number, and asked what the piece was about.

“I want to make sure, you know, you’re depicting the siren in a positive light!” he told me. I related my story about the chess players, and he seemed pacified; he said he’d get back to me with his uncle on the phone. He did not.

I had a similar exchange with another Chabad representative, Motti Seligson; he was excited about the idea, and told me he loved the siren and grew up with it. When I told him about my experience trying to reach Goldstein, he opined that that the inventor, whoever it might truly be — he notably did not confirm Goldstein’s claim to invention — didn’t want to talk about it and just wanted to humbly serve his community without any fanfare, or no more fanfare than an air raid siren that can be heard for blocks already provided.

Still, Seligson promised me he’d find somebody who would chat about the siren. He also promised to find me the perfect Shabbos dinner that would connect me to the perfect Chabad shul. He never got back to me either, even after I followed up about dinner. I tried a Chabad-run library; no answer.

I may never know the true history of my Friday sirens. But for me, they symbolize everything I love about New York — its diversity, its quirks, the way Judaism is woven into the city in a way everyone, Jewish or not, knows about and appreciates. Judaism is part of being a New Yorker, whether it’s the people graciously explaining to concerned Redditors that the sirens announce the weekend instead of an incoming hurricane, or it’s the men playing chess in the park and pausing to wish each other a gut shabbes.

I think of it every Friday as the siren sings faintly through my own Crown Heights apartment windows. Though these days the Shabbat siren also serves as a disheartening reminder of how early the sun sets.

The post Is it a tornado or bomb warning? No, it’s the Shabbat siren! appeared first on The Forward.

Continue Reading

Uncategorized

I’ve been chanting my bar mitzvah Torah portion annually for 40 years. It keeps me grounded in a polarized world.

The Phantom of the Opera had a run of 13,981 Broadway shows across 35 years. Baltimore Orioles legend Cal Ripken Jr., played in 2,632 consecutive baseball games over 17 seasons. The District of Columbia has voted for a Democratic candidate for president in 15 consecutive presidential elections. And this Thanksgiving weekend, I will chant my bar mitzvah Torah parsha (the weekly Torah portion), Vayishlach, for the 40th straight year.

As streaks go, mine certainly will not make a list of history’s greatest. Yet for four decades, I have leined (chanted) it in Israel, the Czech Republic, Vermont, California, Tennessee, Illinois, New York, D.C., and many other international and domestic cities. Whether home or away, every synagogue and Jewish community where I read Torah welcomed me as a fellow Jew as I chanted the ancient words: “וַיִּשְׁלַ֨ח יַֽעֲקֹ֤ב מַלְאָכִים֙ לְפָנָ֔יו אֶל־עֵשָׂ֖ו אָחִ֑יו אַ֥רְצָה שֵׂעִ֖יר שְׂדֵ֥ה אֱדֽוֹם – Jacob sent messengers ahead to his brother Esau in the land of Seir, the country of Edom.”

This 40th year will be particularly memorable because I will return to the place my streak started – Kesher Israel in Washington, D.C. – where I will read Vayishlach as my 94 year-old father sits in the front row of the synagogue and corrects any mistakes I make.  After 40 years, I do not make many, but he still catches every one.

Vayishlach recounts the reunion of estranged brothers Jacob and Esau, as well as the failed unification of the children of Jacob and Hamor after a son of Hamor raped a daughter of Jacob. The parsha’s themes resonate strongly today.  The first lesson is that brothers, no matter the distance between them, should never forget the family ties that bind them.  The second lesson is that when one community commits an act of extreme violence against another, it is extraordinarily difficult to forget and make peace.  These stories teach us that we Jews must always welcome our brothers and also protect ourselves from others who would do us harm.

Three chantings in my streak best reflect Vayishlach’s lesson of brotherly love: my second anniversary when I was living in Northern Israel on a kibbutz; my eighth anniversary when I was a college senior in rural Vermont; and my approximately twentieth anniversary when I was traveling with my father in the Czech Republic.

When I was 15 years old, I lived for a year on Kfar Blum in Israel’s Hula Valley.  There was a small non-denominational synagogue on the kibbutz which struggled to get a minyan.  I approached the lay leader of the synagogue – there was no rabbi – and asked if I might be permitted to chant my bar mitzvah portion on Shabbat.  He seemed skeptical – after all, what American Jew knew enough Hebrew and the Torah “trope” (the musical melody used when chanting Torah) to read an entire parsha?  Fortunately, my on-the-spot practice for him proved my credentials, and he permitted this young American to lead their Shabbat minyan.  While I cannot say that I became a regular attendee, whenever I saw the older synagogue members around the kibbutz, they always had a smile and a nod for the young American Jew who could chant Torah.

Six years later, as a student at Middlebury College in Vermont, there was no Shabbat minyan on campus or in the nearby towns.  So I called the historic Ohavi Zedek Synagogue (“OZ”) in Burlington, Vermont.  OZ was founded in 1885 and is one of Vermont’s oldest and largest Jewish congregations.  Again, after convincing the synagogue chazan (prayer leader) that I could read Torah, I drove an hour from Middlebury to Burlington to chant Vayishlach before a much larger congregation than I was used to.  When I finished and briefly joined the kiddush after services, I awkwardly accepted Mazel Tovs from my Jewish elders.  They expressed pride in my chanting and their hope that I would read Torah again in their shul.

About a decade later, I traveled with my father to the Czech Republic.  It was a business trip for him and a vacation for me.  Early on a Thursday morning, we went to the Old-New Synagogue in Prague’s Jewish Quarter for morning minyan.  I knew this might be my only chance to keep my bar mitzvah streak alive, so before the Torah service, my father and I approached one of the leaders to ask if I might lein.  In the spirit of detente, we negotiated an agreement: They would let me chant as long as one of their members stood next to me in case I could not, in fact, read Torah.  I surprised them again, reading smoothly and earning an invitation to another post-service kiddush and a l’chaim.

Today, when Jews neither feel safe in our communities nor welcome in others, my 40-year bar mitzvah Torah reading streak motivates me to build bridges across our Jewish faith and with others.  After all, our survival throughout history depended on maintaining our Jewish traditions while also being thoroughly engaged in contemporary society.  When I chant this verse – “וַיָּ֨רׇץ עֵשָׂ֤ו לִקְרָאתוֹ֙ וַֽיְחַבְּקֵ֔הוּ וַיִּפֹּ֥ל עַל־צַוָּארָ֖ו וַׄיִּׄשָּׁׄקֵ֑ׄהׄוּׄ וַיִּבְכּֽוּ; Esau ran to greet Jacob, embraced him, fell on his neck, kissed him, and they wept” – I choose the uplifting interpretation that the two brothers reunited in love.  I will continue to be inspired by the lessons of Vayishlach that have never been more important to our Jewish communities, in cities and countries, large and small.

The post I’ve been chanting my bar mitzvah Torah portion annually for 40 years. It keeps me grounded in a polarized world. appeared first on The Forward.

Continue Reading

Uncategorized

NFL suspends star wide receiver Puka Nacua following allegations of antisemitism, assault

(JTA) — The NFL suspended Los Angeles Rams star wide receiver Puka Nacua for three games on Thursday, months after he faced a lawsuit from a woman who alleged that he had made an “unprovoked antisemitic statement.”

But Nacua — who led the league in receptions last season — won’t miss any additional games, as the league is allowing him to serve the suspension while he recovers from an injury.

Madison Atiabi, who is Jewish, alleged that Nacua, 25, said “f— all the Jews” at a dinner in L.A. last New Year’s Eve. According to the lawsuit, Atiabi said she “immediately felt uncomfortable and emotionally distressed.”

Atiabi also alleged that Nacua “forcibly” bit her on the left shoulder, “leaving a circular imprint of his teeth on her body,” and that he bit her friend’s thumb “with such force that her companion screamed in acute pain.”

Nacua’s attorney, Levi McCathern, said in a statement at the time that Nacua denied the antisemitism allegations “in the strongest possible terms.” McCathern characterized the biting as “horseplay.”  No charges were filed, and the civil case is ongoing.

The NFL allows players to serve suspensions while on the injured list. But the timing of the suspension for Nacua — who previously got in trouble for making an antisemitic gesture on a livestream — raised questions about whether the NFL intended for one of its brightest young stars to miss any game time.

After Nacua sustained a knee injury Nov. 8, the Rams placed him on injured reserve, stipulating that he would miss at least four games but leaving open the possibility of a return before the playoffs. He underwent surgery to repair a sprained MCL on Tuesday, ruling him out until next season.

By waiting until Nacua returned from injury to announce its decision, the NFL could have ensured that Nacua missed games he would otherwise have played. The league also could have levied a more significant fine.

Nacua, who is still on his rookie contract, will reportedly lose $950,000 in lost game checks. He is expected to sign a lucrative free-agent contract after the season, meaning that he would have been in line to forfeit a much heftier sum — potentially several million dollars — had the league levied the suspension upon his return.

The NFL also reportedly told Nacua that future violations of the league’s personal conduct policy could lead to significant discipline, including a permanent ban.

The March lawsuit came a few months after another high-profile antisemitism scandal involving Nacua.

Last December — roughly two weeks before the alleged New Year’s Eve incident — Nacua appeared on Jewish influencer Adin Ross’ livestream show, where he was encouraged by Ross to perform an antisemitic touchdown dance during his next game. The dance recreates an infamous gesture known as “The Happy Merchant” that depicts Jews as greedy. Nacua performed the dance on the livestream, but never during a game.

After facing backlash — including calls for the Rams to cut Nacua — the wide receiver apologized in an Instagram post that featured the branding of the “Stand Up To Jewish Hate” campaign, the advocacy group founded by New England Patriots owner Robert Kraft. That post is no longer visible.

“When I appeared the other day on a social media livestream, it was suggested to me to perform a specific movement as part of my next touchdown celebration,” Nacua wrote in the now-removed post. “At the time, I had no idea this act was antisemitic in nature and perpetuated harmful stereotypes against Jewish people.

“I deeply apologize to anyone who was offended by my actions as I do not stand for any form of racism, bigotry or hate of another group of people.”

The NFL and the Rams also released statements at the time, neither of which named Nacua.

This article originally appeared on JTA.org.

The post NFL suspends star wide receiver Puka Nacua following allegations of antisemitism, assault appeared first on The Forward.

Continue Reading

Copyright © 2017 - 2023 Jewish Post & News