Ctrl-Alt-Speech: Is This The Real Life? Is This Just Fakery?
from the ctrl-alt-speech dept
Ctrl-Alt-Speech is a weekly podcast about the latest news in online speech, from Mike Masnick and Everything in Moderation‘s Ben Whitelaw.
Subscribe now on Apple Podcasts, Overcast, Spotify, Pocket Casts, YouTube, or your podcast app of choice — or go straight to the RSS feed.
In this week’s round-up of the latest news in online speech, content moderation and internet regulation, Ben is joined by guest host Cathryn Weems, who has held T&S roles at Yahoo, Google, Dropbox, Twitter and Epic Games. They cover:
- Google outlines plans to help you sort real images from fake (The Verge)
- Fake AI “podcasters” are reviewing my book and it’s freaking me out (Ars Technica)
- We Don’t Need Google to Help “Reimagine” Election Misinformation (Tech Policy Press)
- Social media owners top global survey of misinformation concerns (The Guardian)
- Expert Survey on the Global Information Environment (IPIE)
- X’s First Transparency Report Since Elon Musk’s Takeover Is Finally Here (Wired)
- Telegram will now provide some user data to authorities (BBC)
This episode is brought to you with financial support from the Future of Online Trust & Safety Fund, and by our sponsor Concentrix, the technology and services leader driving trust, safety, and content moderation globally. In our Bonus Chat at the end of the episode, clinical psychologist Dr Serra Pitts, who leads the psychological health team for Trust & Safety at Concentrix, talks to Ben about how to keep moderators healthy and safe at work and the innovative use of heart rate variability technology to monitor their physical response to harmful content.
Filed Under: ai, artificial intelligence, content moderation, disinformation, elon musk, misinformation
Companies: google, telegram, twitter, x


Comments on “Ctrl-Alt-Speech: Is This The Real Life? Is This Just Fakery?”
Not related, but here's an AI liability article I found interesting
Eugene Volokh put out an article about what liability the First Amendment does and doesn’t protect AI companies from. I was wondering what Mike Masnick would think about it. But I have some half-baked opinions (mostly disagreements) to share about it.
Regarding defamation occuring when e.g. a user shares a false statement of fact generated by an LLM:
…
I feel as if Volokh’s interpretation would allow the following kind of site to be liable for defamation: Keep in mind that people can detect lies about as reliably as a coin flip can.
Regarding Section 230:
…
Volokh thinks that courts should regard an LLM’s output as being created in part by the AI company because the AI company made the LLM and that therefore the AI company can be held at least partially liable of a user shares the LLM’s output with other people. Volokh doesn’t claim that an AI company categorically loses Section 230 protection due to training or adjust an LLM, but I feel as Volokh should’ve written a specific example about when being the party to train/adjust an LLM would be sufficient, rather than necessary but not sufficient, to take on liability for otherwise unprotected LLM outputs that a user chose to share with other people.
Regarding prevention of generation of unprotected speech:
And regarding prevention of generation of pornographic deepfakes:
I’m hoping that courts will be cautious about finding “failure to act to prevent repeated spread”. Preventing an LLM from repeating a bad output means dealing with the general impossibility of content moderation. If an LLM generates millions of outputs a day and 100 outputs get reported for defamation or deepfakes every day, what will courts and legislators expect the AI company to do to handle the large volume? And what will courts think when AI companies encounter the same problems that YouTube does with Content ID, especially the impossibility of detecting slight variations of previous bad outputs? I don’t want a repeat of the DMCA safe harbor, which is implemented in a way to incentive websites hosting user-generated content to treat the content referred to in an infringement notification as presumptive infringement.