Jess Miers 🦝 Profile picture
May 18 31 tweets 9 min read Twitter logo Read on Twitter
Hello and welcome to my live reading of the recent SCOTUS #Section230 cases. Since Gonzalez was rightfully vacated, this thread will focus on the Twitter v. Taamneh opinion. Let's dig in:

Gonzalez: supremecourt.gov/opinions/22pdf…
Taamneh: supremecourt.gov/opinions/22pdf…
And if you're new here / just tuning in, you can start with my primer on the cases here: jessmiers.medium.com/what-to-expect…
Strong start: content moderation at scale is HARD Image
I greatly appreciate the Court's framing of recommendations as a tool for online publishers to organize and curate information, no different from the choices an offline newspaper makes as to content it displays on its front page. This is the crux of the 1A issue. Image
Setting the stage a bit for those that are new. The overarching Q in this case is whether Twitter "aided and abetted" the ISIS terrorists that carried out their attack in Turkey. Here is the framework we're working off of (from Halberstam): Image
And importantly, the Court notes that the offline issues present in Halberstam are imprecise when applied to online publishers. The Court will rightfully adjust the framework: Image
Court notes the consequences of broad interpretation, here. Any bystander at a crime scene could be charged with aiding and abetting the crime itself.

This will be crucial for Twitter. Remember: we're similarly talking about Twitter's inaction (failure to remove). Image
See also: Image
And again we see the Court reject a rigid analysis of Halberstam as applied to these facts, suggesting that this was the 9th's fatal error. Image
Here is the test for aid/abet that the Court will rely on going forward: Image
KEY POINT: Taamneh argued that JASTA applies when a defendant generally aids/abets terrorism (i.e. it's enough to show that Twitter generally permits some ISIS content on the service).

Twitter argues that the claim must be tied to a specific act of terrorism. The Court agrees. Image
See also (Taamneh's fatal error was contending that Twitter could be generally liable for any and all bad acts stemming from ISIS....):

um...Prodigy / Compuserve redux? Image
But note, there are indeed limits: Image
Okay, so we understand the rules. Let's dig into the application: Image
Important note: Taamneh never alleged that the specific Turkey attacks were actually coordinated on any of the social media services at issue in the case: Image
All good points, but just a note that even if Twitter did pre-screen content, #Section230 would still apply as to civil liability for that content: Image
wow Image
WIN FOR ALGORITHMIC CURATION ***

***though I will note this graf makes me a little nervous when it comes to the implications -- is the Court suggesting algo curation is fine if done neutrally? This could get wonky as applied to gen AI... Image
(reminder, I'm live tweeting so ya'll are just getting my stream of consciousness atm. Actual analysis to follow later).
bingo: Image
Right -- again, think of what Twitter stands to lose in aligning with ISIS. Image
SUPER IMPORTANT

Plaintiffs have been trying to end run 1A / 230 by arguing that Internet services owe a duty to their users to act. The Court decisively shuts that argument down.

That's a huge win against these looming frivolous failure to warn cases... Image
wow Image
Court outlines examples of where services could be in trouble. I'm worried about the liability for conscious selection / promotion. This could get tricky when it comes to promoting terrorist content from human rights orgs for example. For 230, conscious selection doesn't matter. Image
hello i'm back sorry -- reporter calls......
crucial: Image
9th really screwed up. As I've said, these cases had no business being in front of SCOTUS.

We have decades of precedence that affirm 230 protects algo curation. And here, SCOTUS unanimously determines that Taamneh failed to even state a claim. Kinda embarrassing for the 9th. Image
Again -- come on Ninth Cir... Image
Good point though I do remain slightly concerned about the implications for future tort based claims against Internet services. Plaintiffs are really going to hone in on the neutrality args (imo). Image
If we must go to discovery just to figure out how attenuated the relationship is between the service and the tort, then 230 is pretty much moot.

So, this is all to say that the lower courts need to remember that none of this is new. Nothing changes wrt intermediary liability.
TY for following my live read!

To sum:
-- this was a pretty clean win overall for online publishers like G and Twitter;
-- no problematic 230 dicta;
-- some concerns WRT neutrality and common carriage and how that will affect Gen AI and TX/FL cases;
-- victory lap well earned

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jess Miers 🦝

Jess Miers 🦝 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jess_miers

May 18
Alright, now that I've had more than a minute to think about all of this, some additional thoughts:

This was the *best case scenario* for these cases today. The Taamneh opinion only reinforces the status quo (a major win for websites AND users). #SCOTUS
I have to say, it was surprising to see such a clean win authored by Justice Thomas no less. I think many of us assumed he would have been eager to undermine existing precedence around 1A and even 230 as applied to online publishers.

That's not at all what occurred here.
Keep in mind of course, this was a very narrow issue for SCOTUS (aiding and abetting law). So, it doesn't really come as a surprise that we got such a clean decision here.

The bigger concern really was how the Court would approach Gonzalez. They got it exactly right.
Read 8 tweets
May 16
There are several issues with this response. First, in the U.S., there is no legal distinction between age estimation, assurance, and verification. Under a constructive knowledge requirement, they're synonymous.
Companies can't just "estimate" age when the penalties are immense for getting it wrong.

So, under a constructive knowledge scheme, the only way a U.S. company can be 100% sure they're compliant is if they implement age verification. That's how our litigation system works.
With that, it is utterly disingenuous to state that facial recognition is not part of the age verification conversation. Companies in the UK are already relying on facial recognition products like @getyoti to comply with the AADC. Nothing stops U.S. companies from doing the same.
Read 4 tweets
May 15
Major apologies to my boss today for spending most of the work day on Twitter.

Here's a thread of cases rejecting the "indisputable fact" that websites are state actors. 🧵
But first HUGE S/O to @ericgoldman who continues to meticulously report on these cases.

You can also find the 60+ cases we rounded up, many of which invoke state actor claims, in our paper here: papers.ssrn.com/sol3/papers.cf…
Hart v. Facebook Inc., 2023

Held: A President’s one-time statement about an industry does not convert into state action all later decisions by actors in that industry that are vaguely in line with the President’s preferences.

blog.ericgoldman.org/archives/2022/…
Read 22 tweets
May 15
Same tired response from the same tired pro-censorship playbook: if you can't beat them on substance, try personal attacks.

Look, if you don't have the expertise to debate 1A jurisprudence, it's okay. You can just say that.
BTW the whole incident with Candeub started when he decisively stated that it's an "indisputable fact" that websites are state actors.

As soon as I began saying that no court has ever held this in the history of these jawboning suits, he cut me off and wouldn't let me continue.
and because he wouldn't let me get a word in on this point and because the moderator had to step in to shut him down, I dropped the point and proceeded with my next points.
Read 5 tweets
May 14
Let's talk about this.

I won't name / shame the co-panelist here, but I'll note that he's notorious for this kind of behavior, especially towards women.

I was super anxious about this panel, which is not the norm for me these day, b/c of this individual.
Here's the thing.

Women on the conference beat are held to higher standards than everyone else. If we raise our voices, we're aggressive. If our tone is a little too sharp, we're bitchy. If we stumble over our words or don't have quick enough responses, we're out of our depth.
We are constantly under scrutiny, from the way we look to the way we speak to the tiniest of expressions we may make.

Not only that but depending on the makeup of the panel (i.e. majority male), we have to fight just to get a word in...but not too much so as to appear rude.
Read 13 tweets
May 12
I had the wonderful opportunity to join @UNL_NGTC and @GusHurwitz for a discussion on content regulation.

I focused primarily on the recent state efforts to curb the First Amendment rights of online publishers and users. The following was my opening statement:
Good morning and thank you for hosting us today to discuss the state of technology law and policy. I'm Jess Miers, legal advocacy counsel at Chamber of Progress, a left-of-center trade association that approaches technology policy from a progressive lens.
Today, I'm here to discuss the Age Appropriate Design Code (AADC), a law that originated in the UK, was successfully enacted in California last year, and has now spread like a plague throughout the US.
Read 33 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(