How can digital identity be used to build better trust and systems in our daily transactions? There are really significant challenges and consequences to having a national guaranteed identity – a single identity provider.
Knowing who you’re interacting with, in every form, in every situation is not as simple as you might think. There’s a lot of analogues to physical identity that are worth considering.
What would it mean for us to not have privacy? Does identity mean we don’t have privacy in our interactions? Who can we trust and what authority do they have?
Distributed ID is a web three concept of being able to use zero trust and identify users without having a central authority.
In this conversation, we talk about critical concepts like Open ID trust government actions, and how this could be influential and important in a web three and IoT context.
We really drill into how the system works, and I know you will enjoy the conversation
How do we handle distributing identity? DID stands for distributed identifiers, and today we talk about Web3 as well as distributing identity.
Distributing identity is not just about people and personal identity, but also about things and how we identify and track different things in a distributed way without a centralized infrastructure. That’s fundamental to what Web3 is talking about.
How do we break down the centralization that we have been building over the last 15 years of what Web3 people call Web2, and look at ways to do it in a decentralized way where the trust is between the parties involved? Where it’s set up in a way that you don’t have to have a centralized trust authority.
We spend a lot of time talking about this, what the spec is, what it means, and looking at it in a broader context.
In the July 21st episode, Rob Hirschfeld explores the world of decentralized identifiers (DIDs), a crucial technology emerging from W3C specifications for web three. The conversation underscores the significance of laying the groundwork for web3 protocols and establishing bridges between current and future technologies. While the disruptive impact of web3 remains uncertain, the episode emphasizes the importance of widely adopting, testing, and integrating these new specifications into present-day technologies to shape the next generation of digital frameworks. For a deeper dive into the discussion on decentralized identifiers, tune in to the full podcast at the2030.cloud.
Our discussion about governance as code today is one of a series that we’re going to be starting. In today’s episode, we started out discussing what is Governance as Code. Then we dug into identity and how important it is to know who is doing what in a governance process.
Along the way, we touch on topics such as Infrastructure as Code, trust, logging, and audit – all essential components for governance.
If this is your first time hearing about Governance as Code, you will learn a lot here. Even if you already know the topic, the back half of today’s podcast poses some fantastic conversations and questions.
In the May 9th Cloud 2030 discussion on “Governance as Code,” Rob Hirschfeld emphasizes the significance of building automation as code for creating resilient infrastructure. The conversation focuses on the challenge of tracking identity in automated systems to understand who initiated specific changes. Recognizing the importance of untangling transitions and identifying contributors becomes a foundational component of governance as code efforts. Join the insightful discussions at the2030.cloud and explore the in-depth May 9th episode of DevOps Lunch and Learn with Cloud 2030.
