When a D.C. Circuit judge causally cites your and @rachelbovard’s articles on a @FedSoc panel to share skepticism that gov’t jawboning is the reason #BigTech censors certain political views. 🙌
TL/DR: Congress should not engage in Big Tech’s self-created crisis regarding government compulsion. Instead, it should put forward real reforms that can address their herculean grip on our digital markets and public squares.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
In light of the Gonzalez v. Google oral argument, I thought I'd re-up some of my views on the ways the Court could go. Put simply, the Court is evaluating what does the text of Section 230(c)(1) actually say and do? Pretty loaded question, indeed.
Let's start with the basics. Section 230 (c)(1) says that "[n]o provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider."
Notice that there is no mention of the word "immunity" in the text. All the statute says is that we cannot treat an "interactive computer service" provider, in this case Google's YouTube, as the publisher or speaker of a third-party post, such as a YouTube video. That's it.
In Gonzalez v. Google, SCOTUS has a chance to clarify #Section230's meaning. Courts interpret Section 230 as shielding #BigTech from practically all civil liability when 3rd party content is at issue. I argue that nothing in the text supports that reading. newsweek.com/gonzalez-v-goo…
One option to rectify this is that tech companies should only be protected from causes of action that target a speaker or publisher, such as defamation suits—as opposed to protecting them from enforcement actions via federal civil statutes.
Another option would be to shield companies from liability for hosting and displaying content, but hold them responsible when they take actions beyond those of a traditional publisher, such as when they algorithmically push certain content to users.