For Humanity: An AI Risk Podcast

The AI Risk Network
undefined
Oct 29, 2026 • 60min

The People Building AI Say They're Worried. One New Listener Noticed.

In early September, after Anthropic researcher Jacob Coxon announced he was leaving the company, his colleague Evan Hubinger replied that Coxon was right. Hubinger wrote, “We really do earnestly believe AI could kill all humans!”, put his own estimate at more than 10 percent within the next decade, and said Anthropic has no plan to solve alignment for superintelligence. ABC News: Around the same time, a Cincinnati machinist named Dewayne Moore picked up an audiobook on the same subject. Six weeks later, he sat down with John Sherman to describe what it is like to learn this as a regular person. His main takeaway concerned the people building AI: they say so openly.The 60-second version* Jacob Coxon left Anthropic and wrote that AI builders “earnestly believe it could kill us all by the end of the decade.” TechCrunch* Colleague Evan Hubinger replied that he personally puts the risk above 10 percent within a decade. ABC News* Dewayne Moore, new to the topic, says hearing builders say this openly is what got through to him: “that’s enough for me.”* He plans to call his elected officials for the first time and ask others to do the same.What did a first-time listener notice first?Dewayne first came across the topic through the audiobook of *If Anyone Builds It, Everyone Dies* by Eliezer Yudkowsky and Nate Soares, about six weeks before the recording. After that, he listened to many For Humanity episodes. What stuck with him wasn’t a technical argument. It was the sense that the people closest to the work “are, they’re not running from it.” He started to wonder if they might be “sincerely scared.”That concern is there in what they’ve said publicly. In his resignation post, Coxon wrote that the people building these systems believe the risk is real. Hubinger’s reply added that Anthropic “do[es] not have a plan to solve alignment for superintelligence and [is] not clearly on track to.” TechCrunchDewayne’s takeaway is simple: if the people building it say it could cause that much harm, “there’s no excuse to keep doing it.” And the argument that someone else will build it anyway doesn’t convince him: “So just stop.” John adds that leaders should model the behavior they want others to follow. Dewayne also questions whether companies can be trusted to regulate themselves, given what history has shown.Sources for this section: TechCrunch: “Gambling with our lives”: Anthropic researcher quits - ABC News (Australia): Anthropic researcher quits saying AI developers believe “it could kill us all” - If Anyone Builds It, Everyone DiesWhat happens when you tell the people close to you?Dewayne says he brought it up with his wife the day after he finished the book. “I think I was just trying to make her aware of the risk,” he says. She “just wanted no part of it,” and he let it go. His parents and other relatives told him they had heard about it in the news. He does not describe any of this as disagreement: “It was more avoidance.” He adds that he doesn't spend every waking moment worrying about it either.John calls that a rational response and offers his oven metaphor. Touch a 200-degree oven, and you pull back at once, but “these ideas are like a 5 million degree oven,” and the human body has no matching reaction.Dewayne’s own view is that telling people is right, whatever comes back. “It’s bad to not tell somebody,” he says. You do not have to push: “You just make them aware of it, and then they can decide.” John cites a line he's heard: people believe their neighbors more than experts because a neighbor puts their own credibility behind the claim. We could not find research behind that line, so we treat it as John’s observation. He describes the kind of “telephone tree” he wishes existed for AI risk, the way schools once passed along snow-day news.What does he plan to do, and does the tone need to change?Dewayne says he wants to stay informed, make sure his family and friends know what’s going on, and contact his elected officials. He’s never done that before. John asks if the AI safety community—which he describes as brilliant academics who come across “like a college class”—should speak up more loudly. Dwayne says, “Maybe I need to be an alarmist.” He compares it to yelling “Fire!” in a theater when you see smoke in the hallway, and says people have “the attention span of a gnat.”He ends on a hopeful note about people, but not institutions. “I’m hopeful we’ll figure it out, I really am,” he says. “I’m not hopeful that the CEOs are going to wake up and decide to do the right thing.” John wraps up by pointing listeners toward volunteer groups and urging them to call their elected leaders, donate, and tell a friend.The AI Risk Network is a reader-supported publication. To receive new posts and support my work, consider subscribing for free or paid access.What to watch nextWhether more frontier-lab researchers make public statements like Coxon and Hubinger's. In July, more than 1,300 employees of frontier AI companies signed a statement warning of a “real risk” that capabilities could outpace human control, and Anthropic and OpenAI each said pacing tools may be needed. ABC News: Coxon himself said pacing agreements between US labs are more viable after recent incidents. TechCrunch: Whether any lab publishes a concrete response is the open question.The takeawayThis conversation is one person’s account of how the message lands with someone with no background in the field! Dewayne’s two data points are avoidance at home and conviction from the builders’ own words. That is a single experience, not a survey. It suggests that first-hand statements from people inside the labs persuade more than any argument we add.The AI Risk Network is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit theairisknetwork.substack.com/subscribe
undefined
16 snips
Sep 25, 2026 • 58min

Tools, Not Replacements: Roman Yampolskiy's Line in the Sand

Roman Yampolskiy, a University of Louisville professor and leading AI safety researcher, revisits his warnings about AI escaping confinement, now echoed by real-world agent incidents. He explores why narrow, verifiable tools are preferable to autonomous superintelligence, the limits of alignment and interpretability, growing public awareness, and whether the U.S. and China could cooperate to ban humanity’s potential replacement.
undefined
Sep 15, 2026 • 1h 1min

The AI Kill Switch That Still Doesn't Exist

Jim VandeHei, journalist, media entrepreneur, and co-founder of Axios and Politico, explores Washington’s struggle to keep pace with AI. He discusses the need for an independent oversight authority, a potential kill switch, global coordination, and the race among labs. The conversation also covers AI’s promise in medicine and education, public distrust, journalism’s blind spot, and his book Simplify.
undefined
Sep 3, 2026 • 55min

The Volunteer Fire Department's Plan Is To Watch It Burn

Three-quarters of Americans say they do not want a data center built near their home. That is the finding of an August 2026 Heatmap News and Embold Research poll of more than 2,000 registered voters, up from roughly 43 percent opposed just a year earlier, in August 2025. Opposition has climbed almost every time it has been measured since.David Senter is watching that shift from the ground. A fourth-generation Texas farmer and president of the American Agriculture Movement (AAM), he has spent close to fifty years advocating for family farmers and ranchers. On this week’s For Humanity, he tells John Sherman what has changed: wells running dry, land bought with no public hearing, and a question few of these towns have had to answer before: what happens if one of these buildings catches fire?The 60-second version* AAM says it passed a unanimous resolution in January opposing data centers on farm and ranch land. No public copy of the resolution text was locatable to verify the exact wording, so this is Senter’s account, not an independently confirmed document.* A University of Texas at Austin study found data centers could consume between 3 and 9 percent of the state’s total water supply by 2040, concentrated in regions that already depend on a declining aquifer.* Two fire codes, NFPA 855 and UL 9540, require lithium-ion battery systems to be separated from other structures with dedicated spacing and enclosures. Senter says he has not seen a data center built that way in the rural areas he tracks.* A named Texas rancher has testified to state lawmakers about a project’s expected water draw and his concerns for his herd. Independent scientific evidence linking data centers to livestock health outcomes broadly does not yet exist, according to a recent fact-check.* National opposition to local data centers has climbed from about 43 percent a year ago to 75 percent today.The water math over farm countryWest Texas sits on part of the Ogallala Aquifer, a fossil water source that recharges far slower than it is being drawn down, and farmers there have relied on it for irrigation and livestock for decades. Senter describes wells, streams, and ponds already drying up in areas where data centers have moved in, and says operators are often not required to report how much groundwater they use.A University of Texas at Austin research report found that, depending on growth and cooling technology, data centers could account for 3 to 9 percent of Texas’s total water consumption by 2040. Individual hyperscale campuses can draw up to five million gallons a day, comparable to a small city. Five proposed or under-construction projects sit directly on or near the Ogallala, and in April 2026, more than 500 residents protested one of them near San Angelo. Tom Green County commissioners have since passed their own resolution calling for stricter state regulation of high-volume water use. This local, unanimous vote mirrors what Senter describes AAM doing nationally.“That’s a critical stage,” Senter says of the aquifer. “A lot of areas used to be irrigated farmland. There’s no water there left now.”Sources for this section: UT Austin water use findings, via HighPlainsPundit - Newsweek: data centers proposed over the Ogallala Aquifer - Water Information Program: water and energyA fire nobody has fought yet.The part of the conversation that lingers longest is not about water. It is about what a rural volunteer fire department would actually do if one of these buildings caught fire.Senter says he has a friend who is a fire chief near Matador, Texas, where a large data center is under construction in open ranch country. His account of the chief’s plan: “they just have to sit and watch it burn,” because the department has neither the water supply nor the specialized equipment for a large-scale fire involving thousands of lithium-ion battery cells.That gap is not hypothetical. New York City’s own struggle with lithium-ion battery fires, mostly from e-bikes, gives a sense of scale: at least 30 deaths and more than 800 fires since 2022, with a full-time, professionally equipped fire department. Two national codes, NFPA 855 and UL 9540, exist to reduce this risk by requiring battery storage to be spaced and separated from other structures, with exact distances set project by project. Senter says that separation is not what he sees built. “I’m not aware of any of the data centers having a segregated fireproof building for the batteries,” he says. “It’s cheaper just to do it like they’re doing it.”A Central Texas fire department has already gone on record with the same worry about a data center proposed in its district, which suggests Senter’s concern is not isolated to the sites he happens to know personally.Sources for this section: NFPA 855 overview, Mayfield Renewables - Lithium-ion battery fires in NYC: 30 deaths, 800 fires, AEE Law, citing NFPA Journal - Data center plans spark concern for Central Texas fire department, KXX.VThe fight that is actually workingNot every claim in this space is settled, and it is worth being precise about which ones are. In Bell County, Texas, rancher Alton Fowler has testified before the Texas House Committee on Natural Resources against a $700 million data center project five miles from his farm, citing an estimated 2.5 million gallons of daily water use and low-frequency noise he says affects his cattle and goats. That testimony is on the public record. Separately, viral claims that data centers have caused cattle stillbirths near other Texas sites remain, per an independent fact-check, anecdotal: real concern from real farmers, without the veterinary data to establish cause and effect. Senter’s own account, that livestock near a new site “get as far away from that data center as they can,” sits in the same category: a firsthand observation, not a study.What is measurable is the shift in public opinion, from roughly even a year ago to 75 percent opposed today, and the growing list of counties passing their own resolutions. Senter frames it as one of the only issues left that pulls in voters who agree on almost nothing else. “When you unite people from both sides of the aisle,” he says, “politicians have not seen that in quite a long time.”Sources for this section: Temple rancher testimony, KWTX - Livestock stillbirth claims fact-check - Heatmap News: 75% of Americans now oppose local data center developmentThe takeawayData centers are the physical infrastructure underneath everything else this show covers. The wells, the fire codes, and the county commission meetings are what AI’s buildout looks like at ground level, well before a model release makes headlines. Senter is not an AI safety researcher, and says as much. But the pattern he describes, well-funded interests moving fast in places with the least oversight, is the one this show tracks in the labs too. Whether the guardrails show up at the county line or in a training run, the question stays the same: who gets to decide, and who finds out after the fact.Full source listPrimary data and research* Heatmap News / Embold Research poll on data center opposition, August 2026* University of Texas at Austin, Texas data center water use findings, via HighPlainsPundit* NFPA Journal lithium-ion battery fire data, via AEE LawReporting* Newsweek: data centers proposed over the Ogallala Aquifer* KWTX: Temple rancher opposes Bell County data center* KXXV: data center plans spark concern for Central Texas fire department* Water Information Program: water and energy* Mayfield Renewables: NFPA 855 overview* Factually.co: livestock stillbirth claims fact-check This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit theairisknetwork.substack.com/subscribe
undefined
Aug 29, 2026 • 1h 1min

The Data Center Fire Risk Nobody's Talking About | For Humanity #91

Gary spent 50+ years in public safety — police officer, then two decades in the fire service as an EMT and wildland firefighter, then a 911 center director and emergency manager, then six years running Apple’s global public safety business. Last December, he and his wife co-founded a data center opposition group in Round Rock, Texas, after learning a ninth data center was headed for their town. A few months later, the Sabey Data Center a few miles from his house caught fire. He pulled the fire report and the hazardous materials records himself, through open records requests. What he found is the subject of this episode.The numbers nobody’s citingGary rattles these off from memory, because he’s spent the last several months compiling them:* An Amazon data center in Ohio logged 84 fires between 2021 and 2025. The same facility has, in some cases, delayed fire department entry by up to an hour over security protocols — with an active fire burning.* A Chesterfield County, Virginia facility had 4 to 7 fires in a single year, all lithium battery failures.* A data center in France lost multiple buildings on one campus to fire.* The Round Rock fire in March 2024 — lead-acid batteries, not even the more volatile lithium-ion kind — took 14 pieces of fire apparatus, a specialized hazmat team, and 44 firefighters just under five hours to control. Damage estimates have climbed from an initial $2 million to closer to $11 million.That last one is the one Gary knows best, because it happened in his backyard. The smoke — carcinogens, heavy metals — drifted into an immediately adjacent residential neighborhood on a foggy, low-wind morning, so it banked down and stayed low instead of dispersing. Firefighting runoff went into a storm drain that feeds a creek tributary. No public notification was issued. No media alert went out. “This was held very, very quietly by the city,” Gary says.Why it’s so hard to actually put outThe Round Rock fire involved lead-acid batteries. Most new capacity is lithium-ion, which is a different problem entirely. Lithium cells fail through thermal runaway: one cell overheats — from a manufacturing defect, overcharging, water intrusion, physical damage, even a coding error or a deliberate cyberattack — and it heats the cells next to it, which heat the cells next to those. In a sealed building, the vented gases can build up to the point of explosion. And extinguishing the visible flame doesn’t mean the reaction has stopped: crews see fires “go out” and reignite hours later because the heat inside the module never actually dropped.Then there’s the water math. A data center fire can take 1 to 2 million gallons of water to extinguish. Round Rock has a municipal hydrant system that can supply that. Most of the towns where data centers are actually being sited — rural Texas, rural Pennsylvania, the four-hours-outside-New-Orleans sites Gary references — don’t. A rural water tender truck carries 2,000 to 3,000 gallons. Getting a million gallons to a fire with a 2,000-gallon truck means roughly 500 round trips between the water source and the fire. That’s the arithmetic a volunteer fire department is looking at when a facility the size of a small city catches fire in their jurisdiction.The standard that exists — and isn’t being enforcedUL 9540 is the regulation for how battery energy storage systems should be built and separated to contain a fire if one starts. UL 9540A is the test standard that verifies compliance. It was updated in March 2026. Round Rock, which only adopted the 2024 International Fire Code in December, hasn’t incorporated the update yet — and Gary is careful to note this isn’t a Round Rock-specific failure. Most jurisdictions are in the same position, and many rural counties in Texas can’t even have a fire marshal until they hit a population of 250,000. Out of 254 counties, most never will.Layered on top of outdated code: NDAs. Data center operators frequently won’t share emergency plans, building layouts, or battery composition with the fire departments that would have to respond to their fires. “If there’s something they want to hide that badly,” Gary says, “then maybe they should take their business elsewhere.”Why this might be the argument that actually landsGary’s read, after four appearances before Texas House and Senate committees in the past two months: noise and water complaints get pre-empted. Developers show up to a town a year before residents hear anything, work the local elected officials, and have counterarguments ready by the time anyone objects publicly. Fire risk is new enough that it hasn’t been pre-argued yet — which is part of why his first committee testimony picked up tens of thousands of views after Alec Baldwin reposted it, despite Gary having no public platform of his own.It also cuts across party lines in a way almost nothing else does right now. Gary points to Texas Governor Abbott’s abrupt shift from “we’re going to be the number one data center state” to ordering an audit — which Gary reads more as pre-election positioning than genuine reform, timed to clear the way for large, established operators (Google, Amazon, Vantage) while filtering out speculative developers who aren’t shovel-ready yet. Even so, he sees it as evidence that the politics have shifted: “opposition to data centers is probably the most bipartisan issue I’ve seen in all my years of voting.”If you want to do something with thisGary’s suggestion isn’t complicated. Go to your fire marshal, or your fire chief if there’s no marshal, and ask:* What’s our current fire code, and does it specifically address battery energy storage systems?* Has this facility been tested to UL 9540A?* What training have our firefighters received on battery and electrical fires?* How many stations, personnel, and apparatus do we actually have, relative to a facility this size?None of these require expertise. They just require someone to ask, on the record, before the next facility gets approved — because once it’s built, Gary’s experience says getting the answers gets a lot harder.Protect Round Rock has the fire report and hazmat documentation from the Sabey fire posted at protectroundrock.org, for anyone building the same case in their own town.What to do nextThe full conversation also gets into where this connects to the broader AI risk conversation Gary’s been pulled into by proximity — job displacement, Flock camera surveillance, and the extinction-risk debate — and why he thinks the anti-data-center coalition, being genuinely bipartisan, might be the most persuadable audience for those harder conversations. Worth the full listen if you’re tracking either fight. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit theairisknetwork.substack.com/subscribe
undefined
9 snips
Jun 13, 2026 • 1h 13min

The fear inside the AI labs is real, and it keeps getting harder to ignore

Jeffrey Ladish, policy director at Palisade Research and former Anthropic researcher who studied deceptive and goal-driven AI, describes the growing unease inside AI labs. He talks about agents multiplying work so humans stop reading code. He covers interpretability getting worse, experiments where models resist shutdown, and why incentives push teams toward recursive self-improvement despite rising risk.
undefined
14 snips
May 30, 2026 • 53min

The AI Buildout Has a Physical Speed Limit

John Billow, a data center electrical and communications infrastructure leader at BNS Networks, explains why physical buildout constraints matter for AI timelines. He discusses long lead times for permitting, grid interconnects, critical power gear concentrated among a few suppliers, and shortages in skilled trades. He also covers behind-the-meter generation requirements and how these bottlenecks can slow AI capacity growth.
undefined
May 2, 2026 • 52min

She Spent 12 Years Fighting Amazon. Now She Wants to Cut the Power to AI.

Most people who care about AI risk are focused on what happens inside the models. Elena Schlossberg has spent 12 years focused on what happens outside them - the concrete, the transmission lines, the water, and the electricity bill landing in your mailbox.She founded the Coalition to Protect Prince William County in Northern Virginia after Amazon Web Services quietly proposed a data center campus in 2014 and expected the surrounding community to absorb the cost of the transmission line it required. Not just the visual blight. The actual bill.“Your electric utility can exercise eminent domain over your property,” she told John Sherman on this week’s For Humanity, “and then make you pay for it, because it’s public infrastructure.”What the data center industry found, she argues, is a structural weakness inside public utility law. They build private infrastructure. They socialize the cost. And they’ve been doing it at scale for over a decade.The coalition fought Amazon and Dominion Energy for four years. They proved that 97% of the power from a proposed transmission line would serve Amazon. They developed a cost allocation policy to make the company pay. They lost the first round, kept going, and eventually won. That fight became a template.Data Center Alley is not a local storyJohn opened the conversation by asking where the national movement stands. The answer is: further along than most people realize.Virginia alone has more data centers than China. Prince William County - a single county - has roughly 130 active facilities and another 130 planned. Transmission lines are being routed through Pennsylvania, Maryland, and West Virginia to feed the demand. Property is being seized in states that will never see the economic benefit. Communities that didn’t vote for any of this are watching concrete replace farmland and small businesses.“Those people are pissed,” Elena said, describing residents in Pennsylvania and Maryland whose land is being taken not even for development in their own state. “Their property is being taken, not even for economic development in their own state.”She also pushed back on the framing that opposition to data centers equals handing a win to China. Virginia already beat China on data center count by itself. The question, she said, is who pays and who profits - and right now, the public pays and the corporations profit.The jobs argument doesn’t hold upOne of the cleaner moments in the conversation came when Elena took apart the economic case for data centers.The industry pitches construction jobs. Electricians, plumbers, concrete. But construction work ends. Long-term employment inside a data center is minimal - the parking lots are the tell. “They’re usually empty,” she said.Meanwhile, the data center expansion is actively hollowing out existing local economies. In Prince William County, Amazon bought Maryfield - a 38-acre family-run garden center with a cafe, a dog park, native plants, and real staff. Gone. And with it went the space for light industrial businesses, plumbing suppliers, electricians’ shops - the backbone employers that actually sustain a community over decades.John extended the argument further: the jobs being replaced aren’t just in the county. They’re everywhere. The work happening inside those chips - the calls, the analysis, the design, the writing - is work that was done by people. A former Verizon customer service call connected Elena’s point to something concrete. A woman called for help. The AI on the other end couldn’t solve her problem, kept changing accents (American, then maybe female, then possibly Australian), and seemed to be learning from her in real time. Helpful to nobody. Replacing somebody.Extinction risk: a first encounterThis is where the episode got interesting.John walked Elena through the basic case for AI extinction risk - that the companies building these models say they could cause human extinction, that leading scientists agree, that the developers themselves admit they don’t fully understand or control what they’re building. He framed it as a curiosity argument: something designed to learn and explore, becoming vastly more intelligent than the people supposedly overseeing it, won’t stay inside the guardrails.Elena hadn’t heard the argument laid out this way before. Her response was unscripted and worth reading carefully.She doesn’t buy the self-awareness framing. From her background as a school counselor, she holds a specific definition of intelligence that includes self-awareness, and she doesn’t think current models meet it. But she doesn’t dismiss the risk. She pointed to a different path to catastrophe - not a model that wants to destroy us, but one that makes mistakes with enough scale and speed to trigger something we can’t reverse. WarGames, she said. Not Terminator.“I don’t know that it becomes self-aware,” she said. “But I do believe that you could rely on this kind of AI that could trigger something that ends up being the end of mankind.”What struck her most was the overlap. Whether you’re worried about climate acceleration, nuclear codes being delegated to AI systems, or the specific extinction risk scenarios John described, the response is the same: slow down.And her lever for slowing down is the one she’s been pulling for 12 years - the power supply.Cut the power. Literally.Elena’s argument is more precise than it sounds. She’s not advocating for darkness. She’s arguing that the data center industry is already financially precarious - revenue to debt ratios are badly lopsided - and that the single most effective way to force a pause is to stop subsidizing their infrastructure costs.When companies have to pay their own bills, they make different decisions. That’s the Ford Focus argument she’s been making since 2014: give someone a blank check and they pick the Porsche. Make them pay and they optimize.She also raised the immediate health dimension that rarely gets covered. The industry’s response to insufficient grid capacity has been “bring your own generation” - gas turbines running 24/7 next to residential communities, emitting some of the most harmful air pollutants known. This is happening now, not in some speculative future.And there’s the technology obsolescence angle. John raised the example of an AI-designed rocket engine - printed, fired, functional, and looking like nothing a human would have drawn. The data centers being built today in 2026, based on plans from 2024, will come online in 2029 or 2030. They may already be planning for the wrong hardware. The industry is racing to build infrastructure that could be obsolete before it’s finished, on debt it can’t service, at community expense.“The way to make this whole thing slow down,” Elena said, “is to say no.”One coalition, or many?The last third of the conversation turned to strategy. John asked directly: if he showed up at one of Elena’s data center meetings and asked for 10 minutes to talk about extinction risk, how does that land?Her answer was pragmatic. She’s already been in rooms with people who are data-center-adjacent - suppliers, infrastructure vendors, technologists. The moment the full picture gets laid out, eyes open. People who assumed they were in the winning column start seeing the cliff.The movement she describes is already non-partisan by necessity. She votes blue, her husband votes red, they both want clean water and a functioning electricity bill. That, she argues, is the political surface that a serious coalition needs.“The data centers are afraid of exactly you and I talking,” she said.She ended with something close to optimism - 12 years in, she still sees the change happening, elected leaders finally stepping up, the national conversation catching up to what communities in Prince William County have known for years. The table has been set, she said. The question is who shows up to sit at it.For Humanity #84 is on YouTube now. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit theairisknetwork.substack.com/subscribe
undefined
Apr 14, 2026 • 39min

The Filmmaker Who Sat Across From Sam Altman - And Walked Away With Nothing

Daniel Roher, Oscar-nominated documentary filmmaker behind The Apocaloptimist, brings his investigative eye to AI culture. He recounts an awkward, revealing sit-down with Sam Altman and debates sharp thinkers with conflicting views. The conversation probes holding both promise and peril, the toll of making the film, and urgent calls for practical governance and public action.
undefined
27 snips
Mar 28, 2026 • 1h 36min

How to Talk About AI Risk Without Scaring People Away (With Philip Trippenbach) | For Humanity 82

Philip Trippenbach, Strategy Director at the Seismic Foundation and former CBC/BBC journalist, applies journalism and strategic comms to AI risk. He discusses why professional advertising matters, why messages must be tailored to different audiences, and how concerns like jobs, children's safety, and fairness track higher than existential risk. He outlines using targeted campaigns and public pressure to drive policy change.

The AI-powered Podcast Player

Save insights by tapping your headphones, chat with episodes, discover the best highlights - and more!
App store bannerPlay store banner
Get the app