This episode explores what the “open web” truly means amid shifting standards, AI automation, and evolving economic pressures. Drawing on discussions from IETF 124 and W3C TPAC, it highlights how browser architects, policy experts, and researchers are reexamining long-held assumptions about access, interoperability, and the role of automated agents. Learn why openness isn’t a binary state but a multidimensional spectrum shaped by values such as attribution, consent, and continuity. The conversation offers a grounded look at how technical governance and community norms must adapt to keep the web both usable and sustainable.

Digital identity wallets are becoming a central focus in global identity conversations, driven by regulatory pressure, rapid technical evolution, and growing expectations around interoperability. This episode examines how layered architectures, protocol choices, and platform behaviors shape the user experience in ways that are often misunderstood. Listeners will learn why the Digital Credentials API (DCAPI) is frequently blamed for issues it cannot control, how differing operating system and browser implementations create fragmentation, and why meaningful governance and clear technical boundaries are essential for secure, privacy-respecting digital identity ecosystems.

This episode explores the regulator’s dilemma at the heart of digital infrastructure, where accountability, compliance, and governance reshape the systems they aim to protect. Heather Flanagan examines how modern identity, critical infrastructure, and risk management challenges emerge as digital environments outgrow traditional oversight models. Listeners will learn why compliance-era controls no longer match today’s API-driven reality, how sovereignty contributes to Internet fragmentation, and why resilience now depends on coordination and shared accountability. The discussion offers a clear, thoughtful perspective on evolving digital identity governance.

Last month’s AWS outage did more than interrupt chats and scramble payment systems. It reignited a political argument that has been simmering for years: whether cloud platforms have become too essential to be left in private hands. In the U.K., calls for digital sovereignty resurfaced almost immediately.

A friend sent over an interesting article by Ross Haleluik that opened with "Why it’s not just power grid and water, but also tools like Stripe and Twilio that should be defined as critical infrastructure." The point being made is there there are some services (as demonstrated by the recent AWS outage) that cause significant harm if they become unavailable. The definition of critical infrastructure needs to go beyond power, water, or even core ICT networking.

For decades, standards development has been anchored in the idea that the Internet is (and should be) one global network. If we could just get everyone in the room—vendors, governments, engineers, and civil society—we could hash out common rules that worked for all.

These anti-facial recognition glasses technically work, but won’t save you from our surveillance dystopia.

I've been having an intellectually fascinating time diving into Internet fragmentation and how it is shaped by supply chains more than protocols. There’s another bottleneck ahead, though, one that’s even harder to reroute: people. Innovation doesn’t happen in a vacuum. It requires human talent that builds systems and sets standards.

I had one of those chance airplane conversations recently—the kind that sticks in your mind longer than the flight itself. My seatmate was reading a book about artificial intelligence, and at one point they described the idea of an “infinitely growing AI.” I couldn’t help but giggle a bit.