Thursday, March 7, 2024

UK anti-SLAPP bill takes fire

The United Kingdom has an anti-SLAPP bill on the table, and lawyer Gideon Benaim has cataloged objections.

In broad strokes, the bill follows the usual pattern of anti-SLAPP, looking for free speech and public interests on the part of the defendant, which then burdens the plaintiff with proving probable success on the merits out of the gate.

Benaim published his objections on the INFORRM blog, part 1 and part 2. Some of his objections track those that I articulated in 2021 as to American anti-SLAPP statutes. I lamented the unfairness of expecting a plaintiff to meet an extraordinary proof standard such as actual malice as to falsity without the benefit of discovery. The equivalent UK approach expects a plaintiff to overcome a bare public interest defense without the opportunity to probe the publisher's process or motives.

Benaim also points out, as I have, that anti-SLAPP is as likely to be invoked by the powerful against the weak as vice versa; Goliath media giant against aggrieved individual; or, as happened, President Trump against sexual assault complainant Stormy Daniels.

Benaim is a rarity, a plaintiff's lawyer in media torts. Not that everyday aggrieved individuals will be able to score a place on his client list, which includes JK Rowling, Naomi Campbell, Roman Polanski, and Gordon Ramsay.

At least in the United States, at least, the already daunting odds of prevailing in a media tort case against a publisher with expert defense counsel on retainer causes most would-be plaintiffs not to sue at all, no matter how just their causes. They can't find counsel and certainly can't navigate complex media torts pro se. And that's before anti-SLAPP comes into play, threatening a losing plaintiff with having to pay the attorney fees of the media giant's high-dollar representation.

As I've written before, anti-SLAPP works well when it works well. Statutes just aren't drafted to ensure that that's always the case. It looks like the UK is struggling with the same problem.

No comments:

Post a Comment