IndieWeb post types

This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:

 Listen

Listened to How to Secure the Software Supply Chain by The Tech Trek
Post details
In this episode of The Tech Trek, Amir sits down with Matt Moore, CTO and co-founder of Chainguard, to explore the escalating importance of software supply chain security. From Chainguard’s origin story at Google to the systemic risks enterprises face when consuming open source, Matt shares the lessons, best practices, and technical innovations that help make open source software safer and more reliable. The conversation also touches on AI’s impact on the attack surface, mitigating threats with engineering rigor, and why avoiding long-lived credentials could be your best defense.🔑 Key Takeaways:Security Starts with Engineering: Doing engineering right makes security (and even compliance) much easier.Control the Full Chain: Building from source and applying best practices at every build stage significantly reduces exposure to CVEs.Attackers Exploit the Edges: Most attacks start small—with a leaked credential or compromised dependency—and cascade through the ecosystem.AI Introduces New Vectors: As AI tools integrate deeper into dev workflows, they bring both value and new risks that require thoughtful containment.You Can’t Leak What You Don’t Have: Eliminating long-lived credentials is one of the simplest and most effective ways to reduce breach risk.⏱ Timestamped Highlights:00:45 – What Chainguard does: securing open source consumption and curating safe containers.02:56 – Chainguard’s origin story and co-founders’ experience at Google.06:50 – Building minimal, hardened container images from source to mitigate CVEs.09:40 – Real-world example: how compiler hardening flags protected Chainguard from a high-severity CVE.10:59 – The invisible sprawl of open source in enterprise stacks—from Kubernetes to AWS SDKs.15:45 – How leaked credentials power cascading supply chain attacks.22:30 – “You can't leak what you don't have”: Chainguard's credential-less auth approach.24:30 – Most breaches come from known vulnerabilities—not zero-days.25:38 – AI and security: new use cases, new threats, and the need for explainability.30:41 – AI adoption in enterprises: security best practices still apply, just to new tools and risks.34:43 – Learn more at chainguard.dev and explore hardened images at images.chainguard.dev.💼 Career Tips (from the episode):Don’t wait for zero-days: Most real-world breaches stem from unpatched, well-known vulnerabilities. Ship secure, stay patched.Build from source: If you're in a security or DevOps role, aim to build and control your stack from the source code up—this provides auditability and trust.Engineering rigor is a differentiator: Whether you're launching a startup or working in enterprise tech, applying fundamental engineering principles helps you scale securely.📚 Resources Mentioned:🛡️ OpenSSF Projects – e.g., SIGstore, Scorecards, SLSA.🛠 Projects Mentioned: Kubernetes, Istio, Flux, Tekton, Cert-Manager, Cloud Code.💬 Quote of the Episode:“If you do engineering right, security becomes easier. And if you do security right, compliance becomes easier.” — Matt Moore

by Jamie Tanna's profile image Jamie Tanna .

 Listen

Listened to Demystifying Cyber Resilience and the Tools That Help | Open at Intel by PodBean Development 
Post details
In this episode, Michael Lieberman, Co-founder and CTO of Kusari, walks us through the intersection of open source software and security. We discuss Mike's extensive involvement in OpenSSF projects like SLSA and GUAC, which provide essential frameworks for securing the software development life cycle (SDLC) and managing software supply chains. He explains how these tools help verify software provenance and manage vulnerabilities. Additionally, we explore regulatory concerns such as the Cyber Resilience Act (CRA) and the vital role of the recently released Open SSF Security Baseline (OSPS Baseline) in helping organizations comply with such regulations. Mike also shares insights into the evolution of open source security practices, the importance of reducing complexity for developers, and the potential benefits of orchestrating security similarly to Kubernetes. We conclude with a look at upcoming projects and current pilots aiming to simplify and enhance open source security.   00:00 Introduction and Guest Welcome 00:19 Mike's Background and Role in Open Source 01:35 Exploring SLSA and GUAC Projects 04:57 Cyber Resiliency Act Overview 06:54 OpenSSF Security Baseline 11:29 Encouraging Community Involvement 18:39 Final Thoughts   Resources: OpenSSF's OSPS Baseline GUAC SLSA KubeCon Keynote: Cutting Through the Fog: Clarifying CRA Compliance in C... Eddie Knight & Michael Lieberman   Guest: Michael Lieberman is co-founder and CTO of Kusari where he helps build transparency and security in the software supply chain. Michael is an active member of the open-source community, co-creating the GUAC and FRSCA projects and co-leading the CNCF’s Secure Software Factory Reference Architecture whitepaper. He is an elected member of the OpenSSF Governing Board and Technical Advisory Council along with CNCF TAG Security Lead and an SLSA steering committee member.  

by Jamie Tanna's profile image Jamie Tanna .

 Listen

Listened to Open Source Security: Hobbyist Maintainers with Thomas DePierre
Post details
Thomas DePierre joins Open Source Security to discuss the central idea from his blog post, "You are all on the hobbyist maintainers turf now," exploring the massive disconnect between the corporate world that consumes open source and the hobbyist community that actually produces it. The conversation reveals this isn't a new problem, but a long-standing reality whose consequences for security, stability, and the future of software we are only now beginning to truly confront. The show notes and blog post for this episode can be found at

by Jamie Tanna's profile image Jamie Tanna .

 Like

Liked The New Stack (@thenewstack.io)
Post details
✨ Author Spotlight: Jennifer Riggins ✨ She’s never written a line of code — and that’s her superpower. With a background in journalism and a career shaped by dev storytelling, @jkriggins.bsky.social helps bridge the gaps between developers, business leaders, and everyday users.

by Jamie Tanna's profile image Jamie Tanna .

 Like

Liked The Nuanced Writer (@skriptble.me)
Post details
Just finished mastering episode 24 of @fallthrough.fm, which is actually our 25th episode since our first was episode 0. For one, I’m amazed that we’ve been able to not only ship 25 episodes, but also do so every week (on the same weekday with a couple exceptions).

by Jamie Tanna's profile image Jamie Tanna .

 Listen

Listened to Kent Beck by Gergely Orosz 
Post details
Kent Beck—creator of Extreme Programming and co-author of the Agile Manifesto—reflects on decades of coding, from the birth of TDD to his experiments with AI tools shaping software’s future.

by Jamie Tanna's profile image Jamie Tanna .

 Listen

Listened to Scott & Mark Learn To... How Not to Ship the Org Chart | Scott & Mark Learn To...
Post details
Listen to Scott & Mark Learn To... How Not to Ship the Org Chart from Scott & Mark Learn To.... In this episode of Scott & Mark Learn To, Scott Hanselman and Mark Russinovich discuss the concept of shipping the org chart, a term used to describe when different teams' outputs are inconsistently integrated, reflecting the organizational structure rather than a cohesive product. Scott recounts his experience test-driving an electric vehicle with a disjointed interface, which made him question the internal coordination within the automaker. Mark explains how Microsoft addresses this issue through standardization and tooling, emphasizing the need for consistent APIs and user experiences. They also debate the balance between maintaining consistency and fostering innovation, and how large tech companies like Microsoft and Apple manage these challenges.   Takeaways:    Establishing UX design standards helps maintain a consistent user experience across features Inconsistent design or functionality can impact user perception and trust in a product Integrating quality checks early (shift left) helps prevent issues and reduces later fixes    Who are they?     View Scott Hanselman on LinkedIn  View Mark Russinovich on LinkedIn          Listen to other episodes at scottandmarklearn.to  Watch Scott and Mark Learn on YouTube         Discover and follow other Microsoft podcasts at microsoft.com/podcasts   Download the Transcript  

by Jamie Tanna's profile image Jamie Tanna .