Building safety tools no one can take away with ROOST’s Camille François

Camille François, founding president of ROOST, joins Reid Hoffman and Aria Finger to discuss building online safety as shared infrastructure rather than proprietary tools controlled by individual companies. The core argument is that safety shouldn't be hostage to corporate decisions—when Twitter acquired and shut down Smyte, a safety tool, it left platforms vulnerable. ROOST's mission is to create safety commons that startups and platforms can access independently. The episode explores several concrete examples: Discord's experience after the Smyte acquisition, a fandom app run by two people that identified 19 child exploitation cases in two weeks (demonstrating how safety tools enable detection), and a daycare's decision to change their Alexa wake word to 'computer'—used as a metaphor for how the next generation should relate to AI and technology more critically. Key themes include why social media represented an anomaly in tech development (centralized, proprietary safety rather than shared infrastructure), the gap between policy and enforcement (policy without tools is ineffective), and how a shared safety commons could level the playing field for startups competing against tech giants. The discussion frames safety infrastructure as analogous to encryption—something that should be invisible, universal, and not dependent on any single company's goodwill or business model. The episode positions safety as a public good problem: individual companies optimizing for engagement or profit often deprioritize safety, but if safety tools were shared infrastructure (like DNS or HTTPS), they'd be more robust, affordable, and available to everyone from large platforms to small creators.

Verdict: A thoughtful exploration of safety as infrastructure with concrete examples and forward-looking analysis, though the show notes alone don't fully confirm whether the 84-minute runtime is tight or padded.

Technology rubric

• Technical accuracy 3/5 20%

  References real cases (Smyte acquisition, Discord, fandom app detection) and draws reasonable analogies (encryption as model), but show notes don't provide enough detail to verify technical claims about safety infrastructure design.

• Insight beyond the headlines 4/5 20%

  Reframes safety as infrastructure problem rather than corporate responsibility issue; the Smyte case and commons model offer forward-looking analysis beyond typical 'companies should do better' takes.

• Clarity for non-experts 4/5 15%

  Uses accessible analogies (encryption, daycare Alexa example) and frames complex infrastructure concepts in relatable terms; likely avoids heavy jargon based on show notes framing.

• Substance 3/5 15%

  Multiple concrete examples (Smyte, Discord, fandom app, Alexa) and thematic coherence suggest solid content, but show notes alone don't confirm depth of discussion or whether conversations stay focused or drift.

• Delivers on its title 4/5 15%

  Title promises 'safety tools no one can take away'; episode directly addresses this through ROOST's infrastructure model and critiques of proprietary tool acquisition, though depth of delivery unclear from notes alone.

• Value for time 3/5 15%

  84 minutes is substantial; show notes suggest thematic coherence and multiple examples, but without hearing the episode, pacing and whether it justifies full length cannot be confirmed.

How we score Technology

Worth it if you care about online safety policy, platform governance, or how tech infrastructure should be designed to serve public good rather than corporate interests.

Based on the episode description. AI-generated; it can be wrong.