Polish court enjoins Facebook 'private censorship': just one sign of new norms in digital rights

Much worry about censorship today focuses on the private sector, specifically and especially the large tech companies--Google, Facebook, Twitter--who have so much power over what we read, hear, and see.  When I was in journalism school, in ethics class in the early 1990s, a student once mentioned the possibility of a news organization withholding a sensitive story and worried that that would be "censorship."  Professor Lou Hodges--a great teacher, great person, since deceased--vigorously corrected the student, saying that censorship by definition must be governmental action. 

Louis Hodges, W&L

Well denotational niceties aside, and with the great respect due to Professor Hodges, I'm not sure the distinction remains salient.  I've been worried about the private sector in the free speech realm for a long while.  I've already posited in print that the greatest looming threat to the freedom of information around the world today is not government, but private corporations, and I've started writing about what can be done (what already is being done in Africa, relative to: the United States, India, and Europe, forthcoming).  Indeed, even the classical distinction between freedom of expression and the freedom of information has lost much salience in the information age.

In the United States, for good historical reasons, our constitutional law draws a sharp line between the freedom of speech and the freedom of information, and also between state action, "censorship," and private action, so-called "private censorship."  Both of those lines have eroded in the real world, while our law stubbornly insists on them.

Foreign constitutional systems, such as the European and African human rights regimes, do not come with the historical baggage that carved these lines in U.S. constitutional law.  These younger systems are proving more adept at navigating the problem of private action that would suppress speech and information.  That flexibility has meant full employment for lawyers in the counsel offices of Big Tech.

It also means that the law of the internet and the law of digital rights is no longer being authored in the United States.

In Poland, a digital rights organization called the Panoptykon Foundation--I assume named for the legendary imaginings of English philosopher Jeremy Bentham--is litigating without shame against Big Tech, Google and Facebook included.  In a suit against Facebook, Panoptykon has taken up for "SIN," an (acronymed appropriately if coincidentally?) anti-drug NGO in Poland.  SIN apparently suffered content-based take-downs and blocks on Facebook.  It's not clear why Facebook (algorithms? censors?) targeted SIN, though TechCrunch speculated that it might have to do with SIN's strategy on drug counseling: more of a "use responsibly" approach than an abstention-only approach.

The action is based on Polish statute, which guarantees freedom of speech and does not get hung up on any American-style state-action limitation.  In June, a Warsaw court ex parte ordered (in Polish, via Panoptykon) Facebook to stop blocking or removing any online SIN content, pending litigation.  Technically the respondent in the case is Facebook Ireland.  But one can imagine that American Facebook execs are on alert, as foreign courts fuss ever less over the public-private distinction.

Professor Hodges might roll over in his grave to hear me say it, but I am confident that "private censorship" will be the free speech story of the 21st century.  America will be dragged into a new world of legal norms in digital rights, willingly or not.  I would rather see us embrace this new world order and confront the problem of a runaway private sector than see our civil rights law relegated to legal anachronism.

Read about SIN v. Facebook at Panoptykon.  Hat tip @ Observacom.

Ethics problems in law, education inform message on Christian ethics in biblical story of widow's offering

Last Sunday, it was my privilege to deliver a message on "Christian ethics," arising from Mark 12:41-44, at my local church in Barrington, R.I.

The service is posted on the church website. The message begins at about 31 minutes and runs about 24 minutes in duration.

I used two problems in conventional ethics as jumping off points: one, from legal ethics, a lawyer's unintentional acquisition of privileged records produced mistakenly in discovery; and two, from higher education, a student's unintended acquisition of an unfair academic advantage.

I used the term "doing ethics," which I borrow from, though it is not unique to, the work of Bob Steele (no relation), Jay Black, and Ralph Barney, with a powerful assist by Lou Hodges, in journalism ethics in the 1990s. I was privileged to have a front-row seat when they worked out the revised code of ethics for the Society of Professional Journalists at that time, especially the game-changing "Minimize Harm" principle.

In crafting the church message, I am indebted especially to mentors Eric D'Agostino and Scotty Neasbitt, who helped me navigate the research; and to my church leadership, including Dan Harrington, who writes thought provokingly for the ProJo; and, always, to my wife, an unflinching editor.

I note that, as always, this blog is personal and not affiliated with nor controlled by my employer. Sometimes content on this blog serves both to inform the public and to educate my students about the law. This posting, however, concerns religious belief and is exclusively personal in nature. No public resources nor on-the-job time was used in the work of the above-described message, nor in the production of this blog post. At the same time, of course, readers of any and every religious tradition and belief system are welcome on this page and at The Savory Tort, just as all students are welcome and encouraged in my classroom.

Google censors opinion condemning private censors

On December 31, Google blocked access to a Savory Tort post from 2019 on free speech and censorship in New Zealand.

I received this message from Google on New Year's Eve:

As you may know, our Community Guidelines (https://blogger.com/go/contentpolicy) describe the boundaries for what we allow--and don't allow--on Blogger. Your post titled "NZ prosecutions for sharing Christchurch vid would suppress news, free speech, but worse is empowerment of private censors" [my boldface] was flagged to us for review. This post was put behind a warning for readers because it contains sensitive content; the post is visible at http://www.thesavorytort.com/2019/03/nz-prosecutions-for-vid-sharing-would.html. Your blog readers must acknowledge the warning before being able to read the post/blog.

Why was your blog post put behind a warning for readers?

Your content has been evaluated according to our Adult Content policy. Please visit our Community Guidelines page linked in this email to learn more [link below]. We apply warning messages to posts that contain sensitive content. If you are interested in having the status reviewed, please update the content to adhere to Blogger's Community Guidelines. Once the content is updated, you may republish it at [URL omitted]. This will trigger a review of the post.

For more information, please review the following resources:
Terms of Service: https://www.blogger.com/go/terms
Blogger Community Guidelines: https://blogger.com/go/contentpolicy 

Sincerely,
The Blogger Team

Setting aside for a moment the irony of private censorship of a post about private censorship,* I wanted to understand what triggered the block. As the headline indicates, I fretted in the post about New Zealand criminal law being turned against online re-publishers of the horrifying video of mass shooting at a Christchurch mosque in 2019. I wrote that the lack of newsworthiness exception in New Zealand law would be problematic in U.S. First Amendment law, and the prosecution could not withstand analysis under Brandenburg v. Ohio (1969). And I wrote some about how the modern internet has posed a challenge to the dated First Amendment doctrine.

Willow Brugh via Wikimedia Commons and Flickr CC BY-SA 2.0

At first, I thought maybe I linked to the objectionable video itself; I had not. I did mention by "dot com" name a problematic website from earlier internet days that was infamous in freedom-of-information circles for hosting gruesome content. But I didn't hyperlink it, and the site no longer exists at that address anyway.

The message from Google referred to the "Adult Content policy."  Here's what the policy disallows:

We do allow adult content on Blogger, including images or videos that contain nudity or sexual activity. If your blog contains adult content, please mark it as 'adult' in your Blogger settings. We may also mark blogs with adult content where the owners have not. All blogs marked as 'adult' will be placed behind an 'adult content' warning interstitial. If your blog has a warning interstitial, please do not attempt to circumvent or disable the interstitial - it is for everyone’s protection.

There are some exceptions to our adult content policy:

• Do not use Blogger as a way to make money on adult content. For example, don't create blogs that contain ads for or links to commercial porn sites.
• We do not allow illegal sexual content, including image, video or textual content that depicts or encourages rape, incest, bestiality, or necrophilia.
• Do not post or distribute private nude, sexually explicit, or non-explicit intimate and sexual images or videos without the subject’s consent. If someone has posted a private nude, sexually explicit, or non-explicit intimate and sexual image or video of you, please report it to us here [hyperlink omitted].

There's nothing remotely sexual about the 2019 post. Nor is there any depiction or description of violence, other than a reference to the mere occurrence of the tragedy, which was well reported in news media with plenty more detail.

Links to The Savory Tort were once banned from Facebook, too, for more than a year. When I inquired, Facebook sent me a form message saying that The Savory Tort violated Facebook terms of service for content. I sent further inquiries, made appeals, etc., but Facebook never clarified how the terms were violated. Indeed, Facebook never responded with other than form messages confirming the ban. For all the hoopla about a "Facebook supreme court" and thoughtful, human review of content, those avenues apparently are not open to the little people such as me.

Ultimately, a former student and labor attorney complained about the ban to Facebook, after he was denied permission to share a link to my blog. He kindly let me know. Subsequently, consequently?, and suddenly, links could be posted. The ban vanished as mysteriously as it had appeared. Not a word from Facebook, then or since.

The Facebook ban came about upon a complaint from someone who didn't like something I wrote, I suspected. That happens. For example, I wrote once about a family law case in the Massachusetts Supreme Judicial Court, and I was threatened with legal action by the disappointed party. 

It's easy for someone to complain to Facebook or Google Blogger about online content. The complaint is not necessarily reviewed by a real person, or it is and the person is incompetent or indifferent. It's easier to block or take down content than arbitrate a dispute. That's why trolls and publishers have been able to abuse the notice-and-takedown system that has debilitated fair use of intellectual property.

Here, Google said that the post "was flagged to us for review" (my italics) and "has been evaluated." The choice of words, muddling passive voice notwithstanding, suggests that a third party triggered the review. How anyone, even a bot, at Google then could have found adult content, or anything in violation of the content terms, is a mystery to me. I can conclude only that the block was imposed automatically upon the complaint, with no review at all.

I would seek further explanation or ask for a human review, but that, it seems, is not an option. Google offers me the opportunity to have the block reviewed only after I "update the content to adhere to Blogger's Community Guidelines." I see no violation of the guidelines now, so I don't know what to update.

Now let's come back around to that irony, which might not be coincidental.  (Irony and coincidence are not necessarily the same thing, whatever Alanis Morissette would have you believe.)  The dangers of private online censorship was the theme of my post in 2019. The block on my post occurred in December 2022 only weeks after Elon Musk began to censor his critics on Twitter. Musk is still at it, by the way, seemingly having acceded this week to Indian government demands that Twitter censor critics of Prime Minister Narendra Modi. 

At the same time in December that Musk was making headlines with Twitter censorship, the Supreme Court scheduled (for Feb. 21) the oral argument in Gonzalez v. Google LLC (track at SCOTUSblog). The case asks whether internet service providers such as Google enjoy section 230 immunity from liability in the provision of targeted content, such as search results, apart from the conduct of traditional editorial functions, akin to newspaper editors choosing letters to the editor. David McGarry explained for Reason two weeks ago, "The plaintiff is Reynaldo Gonzalez, whose daughter was murdered in a 2015 terrorist attack. [He] argues that YouTube, a Google subsidiary, should face liability because its algorithms recommended terrorist content posted on the platform that Gonzalez says aided the Islamic State."

That's a potential liability exposure that might incline Google to censor first and review later.

Perhaps someone triggered the automatic censorship of a great many online articles about private censorship, hoping to make the very point that private censorship is dangerous. If that's what happened here, I would offer a grudging salute. But I would like to see the point actually made, not just fruitlessly attempted.

At the end of the day, I'm not so broken up about the block, as opposed to a ban like Facebook's, which frustrated me no end, as I could not share content at all with family and friends. A reader who encounters a sensitive content warning wall might be only more interested to know what lies beyond. And my target audience isn't children anyway. 

I figure there's a reasonably good chance that this post will wind up behind a warning wall for having referred to a warning wall. So be it. Anyone interested enough to be investigating a four-year old story of censorship probably will get the ironist's point, and mine.

* My journalism ethics professor at Washington and Lee University in the early 1990s, the late great Lou Hodges, railed against the word "censorship" to describe private action, so would have regarded the term "private censorship" as outrageously oxymoronic. Professor Hodges was steeped in classical learning and recognized that the word "censor" comes from the Ancient Roman word referring to a public magistrate whose responsibilities, on behalf of the state, included counting people and property—thus, "census"—and the enforcement of public morals through what we now call "censorship." To honor Professor Hodges, I long insisted on the same distinction. But in recent years, I have given in to the modern trend to employ the term regardless of the private or public nature of the actor. Professor Hodges could not then have anticipated that we would soon have an "Internet" that looks very much like a public commons, thus reviving the seemingly antiquated First Amendment problem of the company town. The term "censorship" seems to me apt for a world in which transnational corporations such as Google and Meta might as well be governments from the perspective of ordinary people.