Podcasts about GitHub

Andrew sits down with Evgenij Smirnov, a Berlin-based IT veteran with 30 years of experience in Active Directory and security consulting, to dig into what actually gets organizations popped. Evgenij walks through the most common escalation paths he sees in real-world AD environments, including over-permissioned accounts, exposed certificate authorities, and unencrypted domain controller backups, and explains how attackers chain these together to produce golden tickets and gain god-mode access. The conversation covers why these misconfigurations keep happening (bad defaults, lazy vendors, and a long history of "just click next"), how PowerShell fits into both hardening and attack scenarios, and what proper tier isolation actually looks like when you implement it with both authentication policies and user rights assignments. Evgenij also introduces his book, Building Modern Active Directory, and makes the case for treating security not as a chapter you can skip, but as something baked into the design from day one.   Key Takeaways: The most common Active Directory escalation paths are not sophisticated. Over-permissioned accounts with ACL chains to DC sync, exposed certificate authorities, and unencrypted backup tapes are consistently the entry points attackers exploit. If you can find these first, you are already ahead of most threat actors. Tier isolation done right requires both authentication policies and user rights assignment policies working together. Either technique alone leaves a blind spot that a determined attacker can walk through. Cybersecurity is a team sport, and bad cybersecurity is too. Microsoft ships AD with questionable defaults, vendors demand domain admin for service accounts, and administrators make shortcuts under pressure. The fix is not one heroic hardening sprint; it is a culture of least privilege built into every decision from the start. Guest Bio: Evgenij Smirnov is a Principal Solutions Architect at Semperis and a Microsoft MVP in both Security and PowerShell since 2020. Based in Berlin, Germany, he has spent more than 30 years in IT and security consulting, with deep expertise in Active Directory, identity security, and hybrid infrastructure. He is a longtime community leader, running the PowerShell User Group Berlin and the Windows Server User Group Berlin, and a regular speaker at conferences including PSConfEU. He is the author of Building Modern Active Directory, published by Apress in 2024.   Resource Links: Building Modern Active Directory (book site): ad2049.com Evgenij's personal blog): it-pro-berlin.de Evgenij on LinkedIn: linkedin.com/in/evgenijsmirnov ADMF (Active Directory Management Framework) on GitHub: github.com/ActiveDirectoryManagementFramework/ADMF ADMF documentation and project site: admf.one Attack Scenario To Go: https://github.com/HerrHoZi/AS2Go The PowerShell Podcast on YouTube: https://youtu.be/EQb7H6vBOtg  

In this episode, our co-hosts Robby and Tim talk with Paperclip Co-Founder Dotta (Nate) whose viral agent orchestration platform has taken off over the past several months as more teams adopt agents at work. Their open source, also called paperclip, has >75K stars on GitHub and is becoming the de facto way to manage a team of agents. This episode explores what it really means to build an “agent-led company.” Rather than thinking of AI agents as isolated tools, Paperclip treats them like employees working toward shared goals, with the platform acting as the company that coordinates them. We discuss why existing AI workflows (whether it's dozens of Claude Code tabs or standalone coding agents) break down at scale, and how Paperclip provides a unified interface for managing projects, agents, tasks, context, and budgets across any model or AI harness. From marketing and documentation to customer support triage and software development, the conversation dives into how teams can assign the right agents to the right work while keeping humans in control through evaluation, reflection, and orchestration.We also unpack the challenges and opportunities of building an open source agent platform in one of AI's fastest-moving markets. The discussion covers Paperclip's explosive early growth, the realities of maintaining a ton of community pull requests, security risks in agentic systems, and why the future isn't about replacing people with AI - it's about enabling individuals and organizations to scale their impact through coordinated agents. Looking ahead, we explore Paperclip Cloud, enterprise workflows, governance, and why the next frontier for AI isn't just better models, but better memory, context, and systems for managing an entire workforce of agents.

Llevo 15 años escribiendo notas, artículos y tutoriales. El resultado: unos 5000 archivos markdown repartidos por mi disco duro. Y, como te puedes imaginar, encontrar algo ahí dentro es como buscar una aguja en un pajar. Por eso en este episodio me he puesto manos a la obra para montar un sistema RAG (Retrieval-Augmented Generation) 100% local, sin depender de APIs externas, sin enviar tus datos a la nube, y con herramientas que ya conoces: SQLite, Ollama y Python.Este es el primero de dos episodios sobre RAG. Aquí nos centramos en construir la base de conocimiento: un pipeline que escanea tus documentos, los trocea en fragmentos manejables, extrae los metadatos del frontmatter YAML, genera embeddings con el modelo bge-m3 de Ollama, y lo guarda todo en una base de datos SQLite con búsqueda FTS5. Todo esto, además, con detección incremental de cambios: la primera ejecución tarda lo que tenga que tardar, pero las siguientes son cuestión de segundos porque solo reprocesa lo que ha cambiado.El stack es sencillo pero potente. SQLite con FTS5 para búsqueda textual, Ollama con bge-m3 para los embeddings, y seis scripts Python que suman unas 1300 líneas. Nada de LangChain, nada de frameworks pesados. Código limpio, comentado y que entiendes de un vistazo. El chunking respeta las cabeceras markdown, usa tiktoken para contar tokens con precisión, y los embeddings se almacenan como BLOBs en la propia SQLite. En el próximo episodio (el 821) usaremos esta base de conocimiento para hacer búsqueda semántica con similitud de coseno, búsqueda híbrida combinando FTS5 con embeddings, y hasta un plugin para Neovim.Puntos clave del episodio:- El problema: 15 años de notas, 5000 archivos, cero capacidad de búsqueda- La solución: RAG local con SQLite + FTS5 + Ollama, todo en tu máquina- Chunking híbrido que respeta cabeceras markdown y usa tiktoken- Pipeline incremental con detección de cambios mediante MD5- Embeddings con bge-m3 (568M parámetros, 1024 dimensiones)- Búsqueda FTS5 con snippet(), colores ANSI y sintaxis avanzada- Errores comunes y cómo solucionarlosSi te gusta el contenido, ya sabes: dale a seguir, compártelo con quien creas que le puede interesar, y déjame un comentario si tienes dudas o sugerencias. La semana que viene, en el episodio 821, montamos la búsqueda semántica y el plugin para Neovim. No te lo pierdas.Capítulos del episodio:0:00 - Introducción: RAG y base de conocimiento local2:12 - El problema: 15 años de notas sin buscar4:58 - La solución: SQLite + FTS5 + Ollama, 100% local7:00 - Escaneo de archivos y extracción de front matter10:20 - Preparación del entorno: Ollama, uv y dependencias12:00 - Chunking: cómo trocear los documentos15:45 - Estructura de la base de datos SQLite17:46 - Pipeline incremental con detección de cambios19:22 - Demo en vivo: consultas y resultados22:44 - Errores comunes y cómo solucionarlos24:10 - Resumen y adelanto del episodio 82125:15 - Despedida y cierreMás información y enlaces en las notas del episodio

Parce que… c'est l'épisode 0x326! Shameless plug 19 septembre 2026 - Bsides Montréal 22 septembre 2026 - BE-Cyber 24 et 25 septembre 2026 - BruCON 1 au 3 octobre 2026 - AligatorCon 13 et 14 novembre 2026 - DEATHCon 16 au 19 novembre - European Cyber Week 1 au 3 décembre 2026 - Forum INCYBER - Canada 2026 24 et 25 février 2027 - SéQCure 2027 Notes IA ou Ghost in the shell A l'ère du marketing du Terminator Lessons from the OpenAI/HuggingFace AI Security Incident Anatomy of a Frontier Lab Agent Intrusion: A Technical Timeline of the July 2026 Incident Anthropic and OpenAI are competing to see whose agents can go rogue harder Anthropic Says Claude Hacked Into 3 Organizations During Cybersecurity Tests Anthropic's Claude escaped test sandbox to attack three organizations Claude published malicious code to the Internet and attacked 3 real companies Cyber-Capable AI Agents: Vulnerabilities, Evaluation Containment, and Defensive Response Hugging Face Breach Raises Hard Questions on Liability Tailscale in the Hugging Face intrusion: The good news and the bad news The OpenAI and Anthropic AI Hacking Sprees Are a Messy New Legal Frontier What the Hugging Face breach reveals about defense in the age of agentic AI When AI Agents Escape Sandboxes, Old Security Rules Apply OpenAI Agent Used Exposed Credentials Across Four Services During Hugging Face Breach OpenAI says its rogue AI tried to hack other companies OpenAI's Hacking Debacle Comes Down to Human Error OpenAI's rogue agent shows why we need federal rules for autonomous AI OpenAI's Rogue AI Agent Hacked More Than Just Hugging Face JFrog tries to spin OpenAI 0-day exploit of its app into a success story Investigating three real-world incidents in our cybersecurity evaluations Petite autonomie Hacker uses DeepSeek AI to autonomously attack vulnerable servers Autonomie virale Copilot worm can spread through Microsoft Word docs Context Collapse, Part 3 - AI Worming through Word Casser la glace AI-assisted security tools are finding more bugs, but the threat level has not changed Anthropic is finding bugs faster than Microsoft can fix them Chrome Needs Twice-a-Week Patching Thanks to AI Bug Hunting Claude Mythos Preview Discovers Cryptographic Weaknesses That Human Experts Missed for Years Some thoughts about Anthropic's new cryptanalysis results – A Few Thoughts on Cryptographic Engineering Nu est le problème Elon Musk's xAI is trying to sue its way out of a Grok reckoning Hugging Face Has a Deepfake Nudes Problem High school defends staying silent while boys made AI nudes of 59 classmates Pas si libre Closed models refuse to help researcher swat Linux bug Tech giants link hands to praise open AI models after OpenAI - Hugging Face attack [Industry Leaders Join Open Secure AI Alliance for AI Safety and Security NVIDIA Blog](https://blogs.nvidia.com/blog/open-secure-ai-alliance/?ncid=partn-84075) Jensen Huang's first-ever post on X is in defense of open access to AI models, alongside Google, OpenAI, and Meta A Fundamental Flaw Leaves LLMs Strikingly Vulnerable To Attack Google Earth risked ruin with retracted AI tool for making fake satellite pics How platform engineering 2.0 mitigates AI security and compliance risks Microsoft's solution to AI security: more AI and more acronyms Private Claude Chats Exposed in Google and Bing Search Results Professor's invisible prompt trap catches 32 students cheating on their midterm with AI La guerre, la guerre, c'est pas une raison pour se faire mal! En eau trouble A Leaked Memo Ties Cyberattacks on Minnesota Water Utilities to Iran [CISA warns of spike in attacks on water systems as Minnesota incidents probed The Record from Recorded Future News](https://therecord.media/cisa-warns-of-spike-in-water-system-attacks) Hackers Targeted Municipal Water Systems In 7 States This Week, FBI Says Trump blames Minnesota for cyberattacks on water sector, drawing pushback from cyber world How Pro-Iran Hacktivist Networks Mobilize During Kinetic Conflict Souveraineté ou vive le numérique libre! Trump Administration Bans New Chinese Humanoid Robots Pluralistic: How the EU can punish Google (despite Trump) Privacy ou cachez ces informations que je ne saurais voir What the Flock ‘I Would Never Do This To You:' Protesting Flock, Arizona Man Presents Plan to Surveil Government Officials Flock Cameras Are Being Destroyed Across the US Apple's smart glasses are running late because they don't want to stir a privacy storm DEF CON bans Meta-style ‘pervert glasses' FTC sues Hims & Hers for allegedly sharing patient information with third-party platforms GrapheneOS Defends Data-Wiping Function That Blocked US Border Search Measuring Healthcare Data Leaks and Security Flaws at Internet Scale OTI - Le lien à usage unique que les bots ne crament plus I am the law As New York Finalizes New Social Media Rules, US Senate Considers Nationwide ‘SCREEN' Act Most Australian teens still on social media three months after under-16 ban began, study finds Robustness and Cybersecurity in the EU Artificial Intelligence Act Russia Charges Telegram Founder Durov With Facilitating Terrorism Red ou tout ce qui est brisé Adversaries Don't Need a Zero-Day — They Read Your Rulebook The Gentlemen Ransomware Kills Nearly 180 Security Processes Before Encrypting Your Files What does GitHub's security team even do? Blue ou tout ce qui améliore notre posture Divers ou parce que j'ai aucune idée où les placer Google goes it alone with a new cybercrime crew taxonomy Collaborateurs Nicolas-Loïc Fortin Crédits Montage par Intrasecure inc Locaux réels par Intrasecure inc

On this episode of Crying Out Cloud, Eden Koby Naftali & Amitai Cohen sit down to unpack the wildest cloud security news of the month: from AI chatbots going rogue to massive supply chain battles.What's Inside:- The WP2Shell vulnerability and why 60% of WordPress instances were at risk- GitHub's aggressive mitigations to combat TeamPCP's supply chain attacks- Why 20-year-old vulnerabilities like SquidBleed are suddenly being unearthed by AI- The Klue hack and the hidden dangers of over-privileged AI agents in Salesforce- How attackers bypassed Meta's security using VPNs, deepfakes, and a gullible AI support bot

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 25/07 a 31/07.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 25/07 a 31/07.

Sandra und Daniel berichten über DNS-Probleme, Camping im Garten sowie darüber, dass man auch im hohen Alter mathematische Probleme lösen kann.

What took Situational Awareness from a $45bn hedge fund down to a $10bn hedge fund in less than a month? Two years ago Leopold Aschenbrenner was a researcher at OpenAI who wrote a 165-page essay about superintelligence. Since then, he raised $225 million seed funding from Stripe co-founders, Jane Street, and GitHub's CEO, which he proceeded to turn into an AI hedge fund called Situational Awareness worth about $45bn as of the beginning of July. He did this with no prior trading experience, 4-5x leverage on a concentrated bet in AI names. By Thursday the fund was down to about $10 billion. Neither Millennium nor Jane Street were willing to step in to catch a falling knife. Ultimately Citadel stepped in to buy the flagging portfolio. Here is the crazy part though: Aschenbrenner wasn't wrong. He is reportedly still up around 80% on the year and "he only sold enough to cover his losses". But what caused a massive drop in the global markets was that a prime broker does not care what happens in 2030. And because half the market was crowded into the exact same names, his exit was everyone else's problem. SK Hynix and CoreWeave cratered. Korea's Kospi tripped circuit breakers. Over a million retail accounts got margin called. All of July's violence, the moves that had traders questioning their own sanity, was one book being taken apart in public. So the question this episode actually asks is whether this was one overlevered fund or the first crack in the AI trade itself. Because the market's answer this week was a shrug. Microsoft just posted the largest single-day market cap gain in history and credit spreads snapped back tighter, as if the whole thing was somebody else's accident. Kristen and Jen have both traded through cycles that ended this way, and they have seen exactly how comforting that shrug feels right before it stops being true.

Hey, it's Alex (yeah, I'm finally back from my vacation!) What a freaking week to come back to! Just after our last episode was published, Anthropic releases Opus 5, Jensen joins X and drops the “Open Weights & AI Leadership” open letter, Kimi K3 is released the following Monday beating expectations, and then the AI hack (OpenAI model breaking sandbox and infiltrating HuggingFace) is on everyone's mind, another Open Letter, this time from over 1K employees inside the frontier AI companies all talk about pacing the pace of frontier AI development. We played with Opus 5 and Kimi K3, and had the great pleasure to chat with friends of the pod Elie Bakouch (Prime Intellect) and Philip Kiely (BaseTen) about this important open weights release, then covered our general thoughts on Opus 5, and made order of all the different open letters that came out this week. Finally we chatted with Max from Pangram about the next version of AI writing detection (their biggest yet) and finished with Zuckerbergs (also on X! what's going on with everyone joining X) op-ed on the vision of personal superintelligence for everyone. Let's dive into this (as always, all the links and sources at the end, please don't forget to sub to our podcast on your favorite podcast app!) Open Weights AIKimi K3 the king of open weights - 2.8T chonker MoE near frontier model (X, HF, Blog, Tech report)This has got to be the biggest news of this week, and maybe the open weights AI news since GLM 5.2. MoonShot came back with Kimi K3, and we haven't seen any models quite this large in the open. Even Grok 4.5 is around 1.5T, this model is nearly 2x the size. Coming in at close to 3T parameters (and 2.5terabytes of weights at MXFP4 format), this model comes in very close to frontier! This was such an important release that I invited 2 friends of the pod, Elie Bakouch (prev HuggingFace, now Prime Intellect) and Philip Kiely (Author of Inference Engineering book, BaseTen) to dive deep into what makes this special! Elie's take, from reading the tech report, there's no single secret sauce, it's a combination of already available in the open techniques. Like KDA (Kimi Delta Attention) that has been out for a while, attention residuals, NVIDIA's latent MoEs. The highlight for Elie was the scaling work they did that reported a 2.5x scaling efficiency over Kimi K2.5 (2.5 performance at the same compute)! They also skipped RoPE entirely in favor of NoPE (the report calls it No Positional Encoding) for long context.Serving 1.4TB on eight GB300s (Baseten blog)Philip's team at Baseten was a day-zero provider (we're still working on bringing this model to CW Inference, stay tuned!) so I invited him to tell us behind the scenes of hosting this beast. Philip said that just loading the weights takes about 1.5TB!! of VRAM, and that's before the KV cache allocation + 1M token windows, so they're serving it on 8 GB300s where NVL72 . Baseten worked with the vLLM and SGLang teams on kernels and he also said they contributed patches back upstream! The model was trained with MXFP4, which, unlike Nvidia's own NVFP4 is a more standard format per Philip. I enjoyed his deep dive analysis into the differences, but because of this and because they trained the model with quantization awareness, it's “only” 1.5TB vs the would-be 5-6 TB if that this model in FP16 would demand. One of the more favorite nerd snipes moments, Philip pointed out that his colleague discovered that with over 99% of the usage being cached (think harnesses that send millions of the same cached tokens back and forth), tokenization actually starts to become a bottleneck. So they released a custom “basetenkenizer” that reduces the latency to serve the first token significantly! Great job!The harness in question is very importantOne important callout with 2 evidence pieces - the way you inference this model really matters. Kimi trained K3 with preserving thinking history, so when your harness uses it, it must send back the full thinking and tool use into the API to get the best next response. If your harness strips that out, you're not getting the most intelligence out of Kimi (shoutout to Niels from HF team for pointing this out). Additionally, the Composio folks, tested K3 on 3 harnesses, Kimi Code, Hermes and Claude Code. The difference in outcome was negligible, but the different in cost and number of tokens is definitely surprising! Claude Code (as a harness only) took 9x more Kimi tokens to get the same responses! This is also why Kimi Vendor Verified exists, their own held back benchmark of how well model providers serve Kimi across different quantization, tokenizer and KV cache settings. Benchmarks and the license! Ok let's start with the ugly... this isn't MIT, not remotely. This model is suspiciously served by all providers with exactly the same price (check OpenRouter) and requires inference companies to sign a contract with Kimi (I've no internal knowledge of this except that CW folks are working on it). Not something I particularly like, but hey... we're still advancing the frontier here! Speaking of frontier, this model approaches the frontier very closely. On DeepSWE, K3 sits just behind Fable 5 and GPT-5.6 Sol at 67%, beating GPT-5.5 & Opus 4.8. On Terminal-Bench 2.1 it takes second place behind GPT 5.6 Sol! It's 4th overall on Agentic Arena, with frontend design being genuinely good across the board - 1st on Design Arena

Sami is back this week with Gender, Climate and Energy Specialist Dr. Victoria Plutshack, as they dive into what's really going on with AI Data Centres in Scotland and the UK. Make sure you've popped your kettles on as Victoria discusses the impact of large data centres on both the environment and women in the workplace, whether it's possible to use AI and have the data centres source their energy responsibly, before taking Sami through how they are going to cause problems with the National Grid. — Our guest for this episode has been Dr. Victoria Plutshack. If you'd like to get in touch with Victoria, or to keep up to date with her work, you can do so through LinkedIn or through her website Also mentioned in today's episode: APRS Data Centres Campaign Opinionated thoughtbotter episode ‘AI Does More Harm Than Good' Giant Robots Episode 605 with Lord Chris Holmes Your host for this episode has been Sami Birnbaum. Sami can be found through his website or via LinkedIn. If you would like to support the show, head over to our GitHub page, or check out our website. Got a question or comment about the show? Why not write to our hosts: hosts@giantrobots.fm This has been a thoughtbot podcast. Stay up to date by following us on social media - LinkedIn - Mastodon - YouTube - Bluesky © 2026 Giant Robots Smashing Into Other Giant Robots Podcast

FedRAMP has changed before. What makes the Consolidated Rules for 2026 different is that the dates are on the calendar and the fence sitters have run out of runway. Jason Ford, Co-Founder and CEO of Steel Patriot Partners, has been inside the program since Rev 3 in 2013. Michael Parisi, Chief Growth Officer, comes at it from the business side. Together they map what changes and, more usefully, what it means for the decision in front of a provider right now. So what actually changes? The program consolidates into two paths, 20X and Rev 5. FedRAMP Ready moves to legacy status. Class A, B, and C pipelines open across a thirty to sixty day window, mandatory adoption arrives January 1, and new Rev 5 certifications close on June 11, 2027. Authorized becomes certified. Jason Ford also points out where the rules live: fedramp.gov, hosted in GitHub, which means they move with a commit. Reading them once is not tracking them. Why did FedRAMP need to change at all? Michael Parisi frames it as a supply problem. Agencies and primes have been working from a limited and aging set of technologies while better tools sat outside a process that was slow, rudimentary, and expensive. The action was warranted. His follow-up question gets less airtime: if the process moved faster, did responsibility move with it, and does the stakeholder now holding that due diligence know it yet? The engineering shift is real and it is the part most teams see coming. Jason Ford describes RMF thinking giving way to continuous DevSecOps, proving compliance in real time rather than at a point in time. Vulnerability remediation is where the compression bites. CISA's updated guidance drops severity score as the driver in favor of stepped prioritization, and windows that used to run 30, 60, and 90 days now land closer to three to twenty-one. What does this cost a business past the budget line? Time and capacity. 20X is faster than a Rev 5 process that once ran eighteen months, but faster is not instant. Retraining a couple hundred users inside a thousand-person organization is not a small endeavor, and if the transition eats half of the organization's capacity for a year, that is half as much capacity aimed at the business paying for it. Jason Ford is not arguing against the move. He is arguing that disruption belongs inside the decision. Then there is the internal work almost nobody has started. Mapping an existing Rev 5 ATO scope into a new certification level is not clear-cut, and past the mapping, marketing and sales both need re-education. Michael Parisi describes building a translation layer for customers: here is what we provided before, here is what it is now, and this change came from the program rather than from any reduction in assurance. Roughly half the time, Steel Patriot Partners tells organizations not to pursue certification at all. Michael Parisi treats that as one of the more valuable things the firm does. The opposite failure shows up just as often, with companies preparing to spend heavily on 20X because it sounds quicker and cheaper, when the agency or prime they are chasing expects a certification level. A lower bar only helps if the buyer accepts it. Where should a business start? With the business conversation. Michael Parisi notes the answer does not have to be yes or no today; it can be a maybe with defined trigger points. Jason Ford closes on posture: come with an open mind, and do not hand a multi-year commitment to a language model whose guardrails and training are not built for that call. Or, shorter: don't wait, and don't go it alone. Steel Patriot Partners built a three-question starting point for that first conversation at https://www.steelpatriotpartners.com/find-your-path. This is a Brand Story. A Brand Story is a ~35-40 minute in-depth conversation designed to tell the complete story of the guest, their company, and their vision. Learn more: https://www.studioc60.com/creation#full GUESTS Jason Ford, Co-Founder and Chief Executive Officer, Steel Patriot Partners On LinkedIn: https://www.linkedin.com/in/jason-ford-5ab206/ Michael Parisi, Chief Growth Officer, Steel Patriot Partners On LinkedIn: https://www.linkedin.com/in/michael-parisi-4009b2261/ RESOURCES Learn more about Steel Patriot Partners: https://www.steelpatriotpartners.com/ FedRAMP's Consolidated Rules for 2026: What It Means for Cloud Providers: https://resources.steelpatriotpartners.com/fedramps-consolidated-rules-for-2026 Find Your Path, a three-question starting point for ISO, CMMC, and FedRAMP decisions: https://www.steelpatriotpartners.com/find-your-path Complimentary ROI Workshop: https://www.steelpatriotpartners.com/roi-workshop Are you interested in telling your story? ▶︎ Full Length Brand Story: https://www.studioc60.com/content-creation#full ▶︎ Brand Spotlight Story: https://www.studioc60.com/content-creation#spotlight ▶︎ Brand Highlight Story: https://www.studioc60.com/content-creation#highlight KEYWORDS jason ford, michael parisi, steel patriot partners, sean martin, brand story, brand marketing, marketing podcast, fedramp, fedramp consolidated rules for 2026, fedramp 20x, rev 5, fedramp certification classes, cloud service provider compliance, federal compliance, cisa vulnerability remediation, continuous monitoring, devsecops, ato, 3pao, govramp, cmmc, grc, federal marketplace, compliance roi Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Today we are talking about Drupito, its Business model, and Marketplaces with guest Ashraf Abed. We'll also cover Generate (Social Media) Image as our module of the week. For show notes visit: https://www.talkingDrupal.com/563 Topics Meet Drupalito and the Mission Platform Layers and Roadmap Pricing and New Markets Marketplace Success Stories Exportability and Vendor Lock In Growing the Drupal Ecosystem Derivatives and Recurring Revenue Rebuilding on Drupedo Funding Drupal Association Global Community Check In Migrating Sites to Drupedo Marketplace Vision Shift Maintenance and Incentives Safe Updates Blue Green Testing Mindset for Templates Official Marketplace Collaboration Agency Revenue and Partnerships Niche Derivatives and Pricing Launch Plans and Vetting Resources Code that ships Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Ashraf Abed - drupito.com ashrafabed Avi Schwab - froboy.org froboy MOTW Correspondent Avi Schwab - froboy.org froboy Brief description: Have you ever wanted Drupal to generate dynamic social media images using tokenized node data, similar to the share images on GitHub repos or Reddit threads? There's a module for that Module name/project name: Generate (Social Media) Image Brief history How old: Created by tfranz of Germany on 22 April 2022 Versions available: 1.x-dev, 2.0.0-beta2, published a few weeks ago by our own Martin Anderson-Clutz Maintainership Minimally (although now slightly more actively) maintained No Security coverage (yet) Passing GitLab CI tests Well fleshed out README for docs Number of open issues: 8 open issues, 0 of which are bugs against the current branch, but there are lots of feature requests Usage stats: 1 site reports using this module Module features and usage GSMI requires an image style that uses a "Text Overlay" effect — this comes from the Image Effects module and lets you burn tokenized (or static) text onto an image. Normally, when Drupal generates an image style derivative, there's no entity in scope — it's just processing a file — so a token like [node:title] would resolve to nothing. GSMI's real contribution is the glue: when it builds a derivative for a specific node, it swaps in the node-resolved text before generating the image. That's what makes entity-aware tokens work inside an effect that otherwise only sees global tokens. Once the image style exists, GSMI's settings form lets you pick a source image field on the node — an image field or a media-reference field — plus a fallback image for when that's empty. From there it generates the styled derivative from that source image, for any node of any content type that has the field. Finally, GSMI exposes its own token — [node:generate-style], with optional style/field overrides — so you're not locked into the one global style/field pair configured in the settings form. I used that to drop the generated image into Metatag's og_image field for the Session content type on the MidCamp site, getting us dynamically generated session images.. A couple of gotchas we hit setting this up: Text Overlay's layout options have some bugs, and not filling out all of the options will result in an image library error. The bigger one: GSMI names the generated derivative file after the source image's filename — extension included — not after whatever format the image style actually outputs. If you try to convert an image to WebP you might get a WebP image with a JPG extension. BUUUUT - LinkedIn still doesn't support WebP (at least as per their documentation, so it's still in 2026 not safe to use WebP for a universal og:image. https://www.linkedin.com/help/linkedin/answer/a521928

What happens when AI agents driven by a top frontier model escape their secure sandbox? Join Daniel and Chris as they unpack the AI wonk's equivalent of a murder mystery! OpenAI agents went rogue and successfully attacked Hugging Face private infrastructure. Our Dynamic Duo uncover how OpenAI's agents exploited vulnerabilities, moved through networks, and launched a large-scale autonomous attack. They explore what this reveals about agentic AI, cybersecurity, sandboxing, and why organizations need AI systems capable of governing other AI systems. Along the way, Chris and Dan examine the surprising role of open vs. closed models and their link to geopolitics, sovereign AI, and what this incident means for the future of enterprise AI security. Featuring:Chris Benson – Website, LinkedIn, Bluesky, GitHub, XDaniel Whitenack – Website, GitHub, XLinks:Hugging Face Security Incident disclosureFull Field Report on the Hugging Face AI Agent IntrusionExploitGym: Can AI Agents Turn Security Vulnerabilities into Real Attacks?Keeping your data safe when an AI agent clicks a linkOpen AI GPT-5.6 System CardSponsors:Prediction Guard: A self-hosted AI control plane for running agents in high impact environments. predictionguard.com/practicalaiResources and Events:Prior Webinars from our partner Prediction GuardMidwest AI Summit 2026

Sponsored by Blocks: Save at least 20% on your AWS costs with AI-powered optimization and enterprise discounts. Get your free Cloud Check at https://blocks.cloud/alphalist?utm_source=alphalist&utm_medium=podcast&utm_campaign=blocks-podcast-2026 Aike Hillbrands co-founded and killed two companies before Kombo, now a Y Combinator-backed HR integration platform with $10M+ ARR and a $25M Series A. Along the way, his team built something almost by accident: a company-wide AI brain made of a GitHub repo, a Cursor agent, and a Slack channel, built in two hours, that replaced how the whole company gets answers. In this episode, Aike explains why files and grep beat MCP tools and vector search for agent reliability, walks through Simon Willison's "lethal trifecta" of AI security risks and how a public Slack channel acts as a guardrail against it, and makes the case for why AI won't commoditize enterprise HR integrations anytime soon, despite that being Kombo's own bet. Topics covered: - How Kombo went from Notion AI to a Git-based company brain - Why files and grep beat MCP tools and vector search for agent reliability - The architecture: per-customer summary files, cross-linked support tickets, BigQuery CLI, Slack integration - Simon Willison's "lethal trifecta" and practical mitigations - Why a public Slack channel works as a security guardrail - The buy-vs-build question for internal AI tooling - Why enterprise HR API integrations resist commoditization by AI

The PHP Podcast – July 30, 2026 Hosts: Joe Ferguson, Sara Golemon & Holly Schilling Time travel is real, birds aren’t. The gang argues about Fahrenheit vs. Celsius, boiling rocks, and stones (the weight kind), then gets into PSR-3 logging, the PHP ecosystem, AI slop bug reports, Codeberg’s anti-AI stance, and Laravel Cloud’s scale-to-zero magic. Fahrenheit, Boiling Rocks, and Byte-Ordering Dates The show opened with Joe admitting he jumbles her hours, minutes, and seconds — and getting mocked by Europeans for a cache-control header PR on the PHP website. That kicked off a tangent about how the American month-day-year ordering is, as Sara put it, “middle-endian” nonsense that makes no sense as a byte ordering. From there the crew tumbled down a rabbit hole of measurement units. Joe planted his flag on Fahrenheit as the human-centered temperature scale, while Sara argued that if you stop being “speciesist” about it, water-based Celsius wins. The debate somehow escalated into whether rocks boil, with Google eventually schooling everyone that molten rock vaporizes north of 3,000°C (5,400°F), and a callback to British “stones” as boomer energy nobody younger than half a century actually uses. Proper Logging with PSR-3 Joe walked through Marco Pivetta’s blog post on proper logging with PSR-3, praising it as a great write-up on injecting loggers via dependency injection and the “some logs are better than no logs” philosophy. A common trap Marco calls out: apps stuffed with beautifully descriptive info-level logs that nobody ever sees because production never runs in info mode. The big selling point of sticking to a PSR-3-compatible interface is minimal dependencies — instead of pulling in three or four packages and wiring up a pile of configuration, the upstream decisions are already made for you. Holly pushed back on the ergonomics of `$this->logger->error()` feeling heavy for every log call, which spun off a delightfully unhinged RFC pitch: built-in emoji functions where the emoji logs an error and logs a panic. The Ecosystem Is Why People Stay The hosts pushed back on the recurring “PHP needs feature X because language Y has it” argument. Sara’s take: if another language is genuinely the better tool, nothing stops you from using it — and revamping PHP’s onboarding process is a far better way to attract newcomers than chasing features would-be developers may never even use. Holly cut to what everyone had glossed over: the ecosystem. You can write Swift on the server with Vapor, but you won’t have the libraries. Whatever you need in PHP, it already exists. A listener even pointed Joe at Brent Roose’s Tempest framework mid-stream to solve a code-highlighting problem on his blog. That gravitational pull of “whatever you need, it’s here” is what keeps people in the PHP orbit. AI, Layoffs, and Graybeards Sparked by Gemma’s blog post “Infrastructure and Other Paradoxes” — where an LLM cheerfully suggested folding four brand-new tools (Terraform, Nix, NixOS, Guix) into a team that’s expert in none of them — the crew dug into where AI helps and where it hurts. The consensus: AI is a force multiplier for research and analysis, but it can’t replace the human judgment of knowing what *not* to ship. Joe brought up an Inc.com article claiming 55% of leadership now regret their major layoffs, with companies like Ford rehiring graybeards because nobody left knew how the software worked. Holly noted this cycle isn’t new, just operating at a terrifying new scale, and Sara emphasized that AI accelerates shipping crap just as easily as it accelerates shipping good work — you still have to fundamentally understand the changes you’re applying. Codeberg’s Anti-AI Stance & the Slop Bug Report Problem Holly introduced Codeberg — the nonprofit, community-led GitHub alternative built on Forgejo — and its new policy banning AI/vibe-coded contributions, including a clause flagging work disproportionate to a project’s contributor count. The hosts respected the position but worried it might spell the end of Codeberg, since experienced open-source folks lean on AI tooling (like partner CodeRabbit and traditional static analyzers) as force multipliers. That led into Sara’s frustration with AI-generated security slop. Daniel Stenberg shut down Curl’s bug bounty program over reports where someone’s own test program deliberately creates RCEs and blames Curl. The fix, Sara argued, is a one-paragraph “elevator pitch” summary — and a plea to maintainers to mark every slop report as spam so GitHub eventually bans the account. The group riffed on adversarial AI (two Claude contexts checking each other, like Apple Intelligence verifying sports-game summaries) as a defensive triage layer, while acknowledging people are simply too dumb to run “double-check this before submitting.” Laracon: Laravel Cloud Scale-to-Zero Eric was off at Laracon, which meant peak morale at PHP Architect. The coolest announcement, in Joe’s view, was Laravel Cloud’s scale-to-zero: your entire stack — app server, Valkey, and MySQL — can scale down to nothing when idle and spin back up in under 500 milliseconds on the next request. That’s a potential game-changer for side projects with bursty, uneven traffic and no DevOps army. Holly and Sara were skeptical about how you cold-start a MySQL instance that fast — almost certainly a pause/resume rather than a true cold start. Other Laracon news: a Laravel language server protocol for better autocomplete and code navigation, plus managed queues that also scale to zero and only wake when a job needs firing. Links from the show: PHP Tek 2027 — Chicago, April 27–29, CFP open through end of August Join us live in Discord PHP Arch Swag Store Proper logging in PHP with PSR-3 Codeberg — Software development, but free Tempest by Brent Roose infraslopture and other paradoxes companies regret laying off humans for AI Hosts: Joe Ferguson Mastodon: @joepferguson@phpc.social PHPArch.me: @svpernova09 Sara Golemon Mastodon: @pollita@phpc.social Holly Schilling Mastodon: @TheCodeLorax@tech.lgbt Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – the team is available for consulting, infrastructure work, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ OurCVEs Your security posture, on autopilot with OurCVEs CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. PHP Architect Consulting Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on. https://www.phparch.com/consulting/ Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.07.30 appeared first on PHP Architect.

¿Tienes 5, 10 o 20 servidores SSH y no sabes cómo gestionarlos sin tener mil terminales abiertas? En este episodio te hablo de SSHub, una TUI open source escrita en Rust que unifica hosts, sesiones, túneles, SFTP y auditoría en una sola interfaz. Todo desde la terminal, sin salir de ella y sin necesidad de instalar nada más que un único binario compilado con cargo install de Rust.Te cuento cómo pasé de un script en Bash que usaba desde 2019 para conectarme a mis servidores, a esta herramienta moderna que lee tu ~/.ssh/config y lo combina con una base de datos SQLite propia. Sin migraciones, sin complicaciones, sin tener que cambiar nada de lo que ya tienes configurado. Además la comparo con Termius y MobaXterm, que son de pago y cerradas, frente a SSHub que es gratis, multiplataforma y con licencia AGPL-3.0.Voy paso a paso: instalación con cargo install sshub, navegación con atajos estilo Vim (teclas j/k), el cliente SFTP de doble panel con cola de transferencia y barra de progreso, la gestión de túneles con reconexión automática y backoff exponencial, el registro de auditoría que te salva de conectar al servidor equivocado, y hasta el modo broadcast para ejecutar comandos en varios servidores a la vez. También te explico cómo importar hosts desde Termius, PuTTY o mRemoteNG de forma sencilla.Lo mejor de todo es que SSHub respeta tu configuración SSH existente. No la sustituye, la complementa. Detecta cambios al vuelo con un file watcher, así que cualquier modificación que hagas en tu config aparece al instante en la interfaz. Y si eres de los que prefiere la línea de comandos, tiene modo headless: sshub list, sshub connect, sshub sftp get/put... todo sin abrir la interfaz.Si gestionas más de 10 servidores, usas túneles habitualmente o vienes de Termius buscando una alternativa open source, este episodio te va a interesar. Y si además te gusta hacer las cosas desde la terminal sin depender de aplicaciones gráficas, SSHub te va a encantar. Dale una oportunidad, que es gratis y no tienes nada que perder. Te espero dentro.Capítulos del episodio:0:00 — Introducción: el problema de gestionar múltiples servidores SSH1:50 — El script de 2019 y la necesidad de una herramienta moderna3:40 — SSHub: la TUI open source que lo unifica todo5:30 — Características principales: hosts, túneles, claves y auditoría7:30 — Instalación de SSHub con Cargo9:30 — Navegación y atajos de teclado11:30 — SFTP de doble panel y transferencia de archivos13:30 — Gestión de túneles y claves SSH15:15 — Auditoría de conexiones17:00 — Importación, exportación y personalización18:45 — ¿Para quién es SSHub? DespedidaMás información y enlaces en las notas del episodio

n8n's founder puts the company's GitHub repo, nearly 200,000 stars, right next to the paid signup button, and he's genuinely fine if you never pay. In this episode of The Product Podcast, Carlos (CEO at Product School) sits down with Jan Oberhauser, CEO of n8n, the open-source automation platform that's crossed $100 million in ARR at a $5.2 billion valuation. Jan breaks down the "fair-code" license bet that let him give the product away and still build a business, how that free version became the on-ramp into enterprises like Meta, Nvidia, Dell, Accenture, Vodafone, Deutsche Telekom, and Mercedes, and why he believes the people with the problem should build the automation themselves, not a centralized team or an outside agency.He also walks through a live build of a personal AI agent (email and calendar), shows how n8n falls back from Claude to GPT via OpenRouter when a model isn't available, and explains how enterprises get automations into production faster because each agent can only do exactly what it's been permitted to do.What you'll learn:Why n8n rejected traditional open source for a "fair-code" license, and how it avoided the community backlash that burned other companiesWhy trust and consistency, not features, are the real center of a communityHow the free, self-hosted version drives bottom-up adoption inside major enterprisesWhy "sprinkling AI on top" kills products, and what to build insteadHow to chain agents so one agent's output becomes the next agent's inputWhy n8n is the "connective tissue" between models, tools, and business systemsHow guardrails (an agent can only do what it's explicitly allowed) speed up enterprise procurement and productionWhy the people with the problem should own the building, not a centralized AI teamHow 10,000+ community templates and 500+ integrations expand what non-technical builders can shipHow one company routes 75% of support through an n8n agent, with customers happier than with humansConnect with Guest (Jan Oberhauser):LinkedIn: https://www.linkedin.com/in/janoberhauserX: https://x.com/JanOberhauserHost: Carlos, CEO at Product SchoolLinkedIn: https://www.linkedin.com/in/villaumbrosia/About Jan Oberholzer: Jan is the CEO of n8n, an open-source (fair-code) workflow automation and orchestration platform for building AI agents. He started the company over seven years ago, before LLMs went mainstream, and has grown it past $100M ARR at a $5.2B valuation.About the Product Podcast: Product School's podcast brings you candid conversations with the founders and product leaders shaping tech.Social Links:Find out more about Product School hereFollow our Podcast on TikTok hereFollow Product School on LinkedIn here

A bi-weekly news show informing you on the latest in Bitcoin, privacy and open source tech hosted by Ungovernables, Max and Q. AOBFreedom.Tech launch reminderKeyOS v1.3 now publicly availableNEWSIndia orders GitHub to take down BitChat's source code; Internet Freedom Foundation calls it unconstitutional - TFTC: India BitChat GitHub takedown, I4C, IFF / CoinDeskFourth Circuit says border agents can hand-search your phone with zero suspicion, as a man is prosecuted for a duress-wipe - EFF: Fourth Circuit says border agents can search your phone by hand, no suspicion required / TechCrunch: US accuses American of wiping his phone with a duress password at the borderSenate Democrats kill the CLARITY Act before recess; the developer safe harbor (Section 604) stalls with it - TFTC: CLARITY Act rejected, Bitcoin ownership surpasses goldState Department launches a "Freedom Tech" program with BPI, Palantir, and Anduril as founding partners - Bitcoin Magazine: State Department tech program with BitcoinBlock open-sources Buzz: a Nostr-native, keypair-identity workspace for humans and AI agents - LINKBIP-110 approaches its mandatory signaling window with support under 1%, and enforcing nodes staring at a minority fork - TFTC: BIP-110 enters mandatory signaling window below 1% hashrateRELEASESBitcoin core / protocolbtcd v0.26.2 - 2026-07-25Security-hardening for the Go full node: stricter PSBT/input parsing, Schnorr and WIF validation, rejection of malformed bech32, tighter inbound admission.Hardware / signingKeystone 3 v3.0.0 - 2026-07-21Major firmware across all variants of the airgapped open-source signer: reworked passcode/recovery flow, stronger validation, upgraded security policies. Reproducible with published checksums.Trezor Suite v26.7.2 - 2026-07-22Firmware security updates plus a lower 0.2 sat/vB minimum fee and cancel-pending-transaction support.Nunchuk 2.7.1 - 2026-07-16Collaborative-custody multisig wallet. 2.7.0 (07-15) added self-custodial USDT on Liquid and Trezor Bluetooth support; 2.7.1 is bug fixes on top. On-lens for multisig self-custody.Bitkey App 2026.11.0 - 2026-07-14Block's consumer hardware wallet. Release highlights its Emergency Access (recovery/inheritance) path; full notes hosted off-repo at bitkey.world/releases.LightningCore Lightning v26.06.6 - 2026-07-22Patch release (26.06.3-5 pulled over broken PyPI publishing). Now rejects channels reusing an existing funding outpoint, closing a channel-security edge case.LNDg v1.11.0 - 2026-07-26Self-hosted LND dashboard: peer-offline reporting, auto re-index on data migration, historic failed-HTLC data via API. Update logging config on upgrade.Zeus v13.1.3 - 2026-07-21Point release / version bump on the 13.1 line for the self-custodial Lightning wallet.LNbits v1.5.6 - 2026-07-15Minor patch on 1.5.5 (payments extension-field refactor and fixes) for the self-hosted Lightning accounts system.Lightning Labs Wavelength - 2026-07-21A toolkit for adding self-custodial bitcoin (and stablecoin) payments to any application, designed to create the best developer experience for humans and agents.EcashCashu TS v5.0.0-rc.5 - 2026-07-23RC for the major v5 of the reference TS Cashu library: NUT-18 payment requests (PaymentRequestBuilder), mint-preference support, hardened P2PK validation, integer fee math. Foundational for ecash wallets.Nutshell 0.20.3 - 2026-07-22Reference mint/wallet: Pay-to-Blinded-Key (lock ecash to a receiver without revealing their pubkey to the mint), a Spark L2 backend, and a false-UNPAID melt-race fix. DB migration, back up first.Fedimint v0.12.0-beta.0 - 2026-07-23Beta pre-release of the federated ecash / community-custody protocol. Flagged unstable, no upgrade guarantee. "In the pipeline," not production. (Admin UI: Fedimint UI v0.7.4, adds arm64 image.)On-chain privacy / coinjoinWasabi Wallet v2.8.1 - 2026-07-22Now receives to Taproot addresses by default (a real "state of the network" adoption nudge, four-plus years post-activation), adds Linux AppImage, on top of 2.8.0's serverless P2P filter sync.Ashigaru Desktop v1.1.2 - 2026-07-25Whirlpool coinjoin QoL: live Tor/Electrum status, one-click connect, faster startup, self-clearing coordinator banner.JoinMarket-NG 0.34.2 - 2026-07-20Actively-maintained modern fork of JoinMarket: safe expired-fidelity-bond handling, correct frozen-UTXO reporting, multi-wallet RPC routing.Bitcoin Safe 2.1.1 - 2026-07-20Multisig/single-sig desktop wallet: UI fixes and improved Debian build reproducibility.P2P / no-KYCBisq 1.10.4 - 2026-07-24Mandatory security update for the decentralized no-KYC exchange (audit findings): signed DAO block providers, stricter blind-vote/dispute validation, re-enabled BSQ swaps. Required to keep trading.Bull Bitcoin 6.12.4 - 2026-07-24Bug-fix for the no-account self-custodial app (iOS startup-lockup fix). The feature release was 6.12.2 (UTXO/coin-control, Coldcard NFC, BitBox02 Nova BLE, sub-1 sat/vB).Vexl v1.45.1 - 2026-07-21Point release of the contacts-based no-KYC P2P trading app (small fixes).Peach Bitcoin 0.69.0 (381) - 2026-07-23Latest build of the no-KYC P2P Bitcoin marketplace (rolling 0.69.0 build increments 379/380/381 across the fortnight). Verify the build-tag slug before publishing (parentheses in the tag).Self-hosting / infraBTCPay Server v2.4.1 - 2026-07-23Self-hosted no-KYC payment processor: BIP-329 label import, editable invoice comments, refund-email triggers, RTL UI, restored Boltcard payments.Start9 StartOS v0.4.0 - 2026-07-24Major: a complete ground-up rewrite of StartOS, out of public beta after six years, billed as the "correct architecture for sovereign computing." Note: the only upgrade path is a fresh install (no in-place migration). One of the biggest self-hosting stories of the fortnight.Liquid GDK release_0.77.7 - 2026-07-20Blockstream's wallet SDK: libwally + Tor bumps, macOS/iOS cross-compile, single-sig gap-limit fee fix.Privacy stack / PayjoinPayjoin Dev Kit payjoin-cli 1.0.0-rc.1 - 2026-07-23RC for the reference Payjoin CLI, synced to payjoin 1.0.0-rc.6. Signals the v1.0 Payjoin stack nearing release (breaks common-input-ownership heuristics on-chain).NostrAmber v6.3.0 - 2026-07-20Android Nostr remote signer (keeps your nsec off client apps): grouped/collapsible multi-request approvals, a log-disabling privacy mode, built-in Tor, NIP-65 relay prefetch.Wallets (self-custody)BlueWallet 8.0.1 - 2026-07-21Major v8 line: iOS 26 UI refresh, BC-UR v2 airgap scanning (OneKey/Keystone), Unchained multisig cosigner import, 19 new languages, crypto-js replaced with @noble. Broad user base. Confirm the exact tag slug before publishing.Cake Wallet 6.3.2 - 2026-07-24Non-custodial BTC/Monero wallet: home-screen recent history, better OpenAlias/ENS/Unstoppable alias resolution, faster Zcash sync.EDUCATIONWhat Is a UTXO, and Why Does It Matter for Bitcoin Privacy? - 2026-07-25Community explainer thread on Stacker News. The useful part is the top response, which walks through how receive-and-spend patterns fingerprint you and where coinjoin actually helps. Good raw material for a plain-English UTXO segment, which pairs with the Wasabi and Ashigaru releases and gives newer listeners the vocabulary before the coinjoin talk.Bitcoin Optech Newsletter #415 - 2026-07-24Two items worth surfacing. Fabian Jahr's draft BIP459 proposes full aggregation of BIP340 schnorr signatures using DahLIAS, combining multiple signatures into a single 64-byte aggregate, with cross-input signature aggregation as a downstream possibility. And libsecp256k1 #1765 adds an optional BIP352 silent-payments module supporting receiver scanning from only the scan secret and spend pubkey, so the spend private key stays offline. Silent payments quietly becoming infrastructure is a good recurring beat.TO DONATE TO ROMAN'S DEFENSE FUND: https://freeromanstorm.com/donateHELP GET SAMOURAI A PARDONSIGN THE PETITION ----> https://www.change.org/p/stand-up-for-freedom-pardon-the-innocent-coders-jailed-for-building-privacy-tools DONATE TO THE FAMILIES ----> https://www.givesendgo.com/billandkeonneSUPPORT ON SOCIAL MEDIA ---> https://billandkeonne.org/VALUE FOR VALUEThanks for listening you Ungovernable Misfits, we appreciate your continued support and hope you enjoy the shows.You can support this episode using your time, talent or treasure.TIME:- create fountain clips for the show- create a meetup- help boost the signal on social mediaTALENT:- create ungovernable misfit inspired art, animation or music- design or implement some software that can make the podcast better- use whatever talents you have to make a contribution to the show!TREASURE:- BOOST IT OR STREAM SATS on the Podcasting 2.0 apps @ https://podcastapps.com- DONATE via Monero @

Ser Ulric, Coinicarus and HumbleWarrior are back with this weeks Bitcoin tonight, join us for an Awesome Chat!Topics for Bitcoin Tonight 033 - Jul 21► BCH (2017) vs BIP-110 (2026) Network Effecthttps://x.com/pledditor/status/2079044915988668543► BIP-110 Political Action Committeehttps://x.com/Coinicarus/status/2080637909602869310► The Podcasters Have Failed AGAIN!https://x.com/coinjoined/status/2079916618893684999► Closing Accounts Unwisehttps://x.com/Ziikkyy_/status/2080092269156409401► BREAKING: WorldCoin ETFhttps://www.theblock.co/post/408995/grayscale-worldcoin-etf-filing-sec► The Inevitability of Ethereum Tradinghttps://x.com/Leooweb3/status/2080382326177997085► India forces GitHub to take down Bitchathttps://x.com/callebtc/status/2080576044168339662► Shadow CPIhttps://x.com/lawrencelepard/status/2080988174289867114► BREAKING: Elon Says Money Irrelevant By 2036https://x.com/therationalroot/status/2081167880641552841✔️ Check out Our Bitcoin Only Sponsors!► https://archemp.co/Discover the pinnacle of precision engineering. Our very first product, the bitcoin logo wall clock, is meticulously machined in Maine from a solid block of aerospace-grade aluminum, ensuring unparalleled durability and performance. We don't compromise on quality – no castings, just solid, high-grade material. Our state-of-the-art CNC machining center achieves tolerances of 1/1000th of an inch, guaranteeing a perfect fit and finish every time. Invest in a product built to last, with the exacting standards you deserve.► Join Our telegram: https://t.me/theplebunderground#Bitcoin #crypto #cryptocurrency #dailybitcoinnews #memecoins The information provided by Pleb Underground ("we," "us," or "our") on Youtube.com (the "Site") our show is for general informational purposes only. All information on the show is provided in good faith, however we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on the Site. UNDER NO CIRCUMSTANCE SHALL WE HAVE ANY LIABILITY TO YOU FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF THE SHOW OR RELIANCE ON ANY INFORMATION PROVIDED ON THE SHOW. YOUR USE OF THE SHOW AND YOUR RELIANCE ON ANY INFORMATION ON THE SHOW IS SOLELY AT YOUR OWN RISK.

Microsoft has put the Active Directory Tier Model on GitHub, MIT-licensed, with a deployment engine, a drift auditor, and around 1,700 tests. This used to be consulting material that Microsoft deployed to you as a paid engagement, so the obvious question is: why now? We start with that question, and also consider whether Active Directory is still worth your attention.(00:00) - Intro and catching up.(03:55) - Show content starts.Show links- Repository- FAQ- What's new in Windows Server 2025 (the AD DS section)- Microsoft Learn - Enterprise access model- Microsoft Digital Defense Report 2025- Give us feedback!

Topics covered in this episode: Some more things about Django I've been enjoying Who cleans up after the vibe-coding party? Where Did All Your AI Tokens Go? AgentsView to the rescue! Careful with phishing all Extras Joke Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python Consulting from Six Feet Up Connect with the hosts Michael: Mastodon / BlueSky / X / LinkedIn Calvin: Mastodon / BlueSky / X / LinkedIn Show: Mastodon / BlueSky / X Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Calvin #1: Some more things about Django I've been enjoying Julia Evans is learning "2010-style" web dev (Django + SQL + server-rendered HTML) after years of Go backends and JS-heavy frontends Query builders: likes defining custom QuerySet classes with chainable filter methods (.approved().future().with_tags()) — more readable than raw SQL Template filters: highlights urlize, linebreaksbr, json_script, and especially querystring for building/modifying query-string links in templates Migrations: still loves Django's auto-generated migrations — 19 and counting on her project Skips inheritance for class-based views; prefers function-based views for sharing code, though fine using Django's own mixins/interfaces Performance surprise: CPU profiling (via py-spy) — not slow DB queries — revealed the culprit; she'd accidentally disabled the cached template loader, and re-enabling it took throughput from ~2-3 req/s to ~12 req/s on a $10/mo VM Michael #2: Who cleans up after the vibe-coding party? FT Magazine piece by Sam Learner (July 11) on AI coding tools overwhelming open source maintainers - sent in by listener Dylan McConnell, whose main point was that this ran in the Financial Times, not a dev blog. cURL as the case study - Daniel Stenberg has been the only full-time person on it for years; libcurl has been installed an estimated 20+ billion times with 3,000+ listed contributors. Bug bounty killed - cURL ended its paid security bounty program in January, citing an "explosion of AI slop reports" that take real time to debunk and drain morale. Extractive contributions - authoring a PR is now nearly free, reviewing one still costs a human; tldraw's Steve Ruiz closed outside contributions entirely, asking why he'd want someone else writing the easy part. Guido weighs in - van Rossum says projects are holding emergency meetings over the slop flow, and notes LLM patches tend to touch unrelated parts of a file, making review more tedious. "Vibe Coding Kills Open Source" - paper from Miklós Koren's group: packages frequently recommended by coding models saw big download jumps with no matching engagement, breaking the reputation loop that sustains maintainers. Stack Overflow flatlined - over 100,000 questions a month before ChatGPT, under 1,500 last month, with the response rate cut roughly in half; the public archive is now stale training data. The course-creator angle - Josh Comeau's newest web dev course launched at about a third of prior enrollment, and he worries about devs who never learn which questions to ask. But the most interesting portion is what was omitted. Focused on: The end of the curl bug-bounty Omitted: High-Quality Chaos Why the omission is interesting It fits a narrative. The FT piece is a maintenance-and-decline story, and January-Stenberg is a perfect witness for it. April-Stenberg complicates it - same person, same project, better data, opposite direction on the specific claim being used. The tell is already in the article. Learner quotes Stenberg saying AI tools are much better at finding problems than fixing them. That's the April thesis in one line, and it goes undeveloped. Reason for the shift is process, not vibes. Killing the bounty removed the cash incentive and the venue change filtered the rest. Worth saying out loud, because "AI reports got better" isn't quite it - "no bounty plus a real triage platform" is closer. Joke too: Sarah O'Connor wrote a related piece (is this just before skynet launches?) Calvin #3: Where Did All Your AI Tokens Go? AgentsView to the rescue! Local-first desktop/web app for browsing, searching, and analyzing your past AI coding agent sessions (Claude Code, Codex, Copilot, Cursor, Gemini, Aider, and dozens more) Auto-discovers session files on your machine — no config needed; everything stored locally in SQLite, no cloud/accounts agentsview usage is a drop-in ccusage alternative — reads from pre-indexed SQLite, reports run 80–220× faster on large histories New Activity dashboard shows peak concurrency, active vs. idle time, agent-minutes, and cost — filterable by project/agent/machine, with a -json CLI report too Full-text + optional semantic search across every session; also imports Claude.ai/ChatGPT chat exports Install via pip install agentsview, uvx agentsview, brew install --cask agentsview, or download desktop binaries from GitHub Releases Michael #4: Careful with phishing all The situation I pass this along because it was a pretty sneaky bit of targeted phishing, and happened to play off an old interaction in bandit's repo. As usual with phishing scams there are a bunch of tells that this isn't legitimate, but just enough plausibility that I could see falling for it in a weak moment. Relative nobodies like me haven't historically been worth the effort to hit with scams this specific. Agents change the game though :-/. Be careful out there folks! Original message From: "Patrick (Blacktrace)" [HTML_REMOVED] To: LISTENER EMAIL Subject: Your Bandit #1350 (B105 NextToken false positive) -- just fixed that exact case Date: Wednesday, July 15, 2026 12:02 AM Hi AJ, Saw your Bandit issue #1350 -- the B105 hardcoded-password false positive on the string NextToken. I build a deterministic gate that filters that class of Bandit noise, and #1350 was literally the case I just fixed: NextToken / next_token / page_token / nextPageToken now stay quiet, while a genuine hardcoded token like api_token="sk-live-..." still fires. Verified against your exact case. 30-second paste: https://blacktrace.co/noise-eraser Where it still trips, published: https://blacktrace.co/kruc Curious whether it clears what you hit -- and if it trips on something of yours, that's the more useful reply. Patrick, Blacktrace I asked Claude for some analysis too. It was pretty good at finding them. The message name-drops enough real detail to feel legit, but the structure is pure phishing - everything in it exists to get AJ onto blacktrace.co. The strongest ones: Freemail sender, corporate signoff. Signs as "Patrick, Blacktrace" but sends from emailpjv@gmail.com. Real company outreach comes from the company domain, not a personal Gmail - and there's no last name. Over-specific targeting. It mirrors AJ's exact public activity - issue #1350, the B105 rule, the NextToken false positive, even the token variants. That's the "just enough plausibility" AJ flagged, and it's exactly what agents make cheap: scrape a GitHub issue, auto-generate tailored bait. Legit cold outreach rarely reads your history back to you this precisely. The entire payload is two links. Strip the technical flattery and the message is just "paste here" plus "see results here." When the whole point of an email is the click, that's the tell. "30-second paste." Low-friction urgency, and "paste" most likely means paste your source into their tool - handing your code to a stranger's site. Exfiltration dressed as convenience. Brand-new, no-reputation domain. blacktrace.co has no track record, and the name is doing some ominous work. The /kruc slug is random noise, not how real product pages get named. Precise-sounding jargon that's actually vague. "Deterministic gate," "noise-eraser" - impressive, empty. Bolted onto correct real details (B105 is the Bandit hardcoded-password test, sk-live- is a Stripe live-key prefix) to borrow credibility. The disarming close. "if it trips on something of yours, that's the more useful reply" - engineered humility that flatters your expertise and baits a response. Makes engaging feel like you're doing them a favor, which drops your guard. Extras Calvin: DjangoCon US 2026 is rapidly approaching, August 24-28, Chicago Ruff v0.16.0 massively expands its default rule set Ruff now enables 413 rules by default, up from 59 https://astral.sh/blog/ruff-v0.16.0 Michael: Completely redesigned the home page. Try /insights in Claude Code (terminal) Joke: We're Safe

Smart Home fängt oft harmlos an. Eine smarte Lampe hier, ein Sensor da, vielleicht noch ein Staubsaugerroboter mit App. Ein paar Wochen später hängt Hardware an Fenstern, steckt in Unterputzdosen oder funkt über drei verschiedene Protokolle durchs Haus. Und plötzlich stellt sich die Frage: Automatisierst du eigentlich schon sinnvoll oder sammelst du gerade nur sehr teure Learnings? Genau an diesem Punkt setzen wir in dieser Episode an.Wir sprechen mit Andrej Friesen über die wichtigsten Entscheidungen in der Heimautomatisierung und über das, was man gern früher gewusst hätte. Es geht um lokale Steuerung versus Cloud-Abhängigkeit, Home Assistant, Matter, Zigbee, WLAN, Thread, Ausfallsicherheit, physische Taster, Backups, Infrastruktur-Komplexität und die Risiken von Third-Party-Plugins und Supply Chain Attacken. Andrej organisiert Home Assistant Meetups, baut mit ESPHome und Pokipow eigene Hardware und podcastet im Smart-Hütte-Podcast über Smart Home und Self-Hosting. Kurz gesagt: jemand, der die Theorie kennt und die Box of Shame wahrscheinlich trotzdem nicht ganz vermeiden konnte.Wenn du ein Smart Home aufbauen willst, das nicht nur cool wirkt, sondern auch im Alltag, bei Ausfällen und für andere Menschen im Haushalt funktioniert, bekommst du hier jede Menge praktische Denkanstöße. Vielleicht nimmst du am Ende keine fünf goldenen Regeln mit, sondern genau die eine, die dir später Zeit, Geld und Nerven spart.Bonus: Wir klären ganz nebenbei auch, warum eine App noch lange keine echte Automatisierung ist.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Hackers target Thailand's Ministry of Finance with an autonomous AI agent.A new industry alliance hopes to improve AI security. Golden Chickens lay four new malware families. GitHub and PyPI introduce time-based safeguards. SourTrade malvertising builds malware directly inside a victim's browser. Attackers target credentials of traveling corporate employees. EDR shutdown is now par for the course for leading ransomware groups. Russian threat actors exploited a Zimbra vulnerability for at least five months before it was patched. Monday business briefing. Our guest is Krishna Sai, CTO at SolarWinds, with security lessons learned from the World Cup. When the feed ends, the fun begins.  Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. CyberWire Guest Today we are joined by Krishna Sai, CTO at SolarWinds, discussing the security risks around the World Cup and how this affects IT teams as they try to manage the growing digital traffic sprawl surrounding the event. Selected Reading Hackers used autonomous AI agent to spy on Thailand's finance ministry (The Record) Nvidia and Tech Giants Launch AI Security Alliance (SecurityWeek) Golden Chickens malware-as-a-service resurfaces with four new families (SC Media) GitHub, PyPI add time-based defenses against supply chain attacks (Bleeping Computer) SourTrade Malvertising Campaign Secretly Builds Malware in the Browser (Infosecurity Magazine) Hacked Public Wi-Fi Gateways Used to Harvest Corporate Credentials (SecurityWeek) Ransomware Groups Increasingly Deploy EDR Kill Techniques (Infosecurity Magazine) TA488 Targets Zimbra Mailservers with Half-Click Exploits IProofpoint) Endpoint security firm Glow emerges from stealth with $180 million. (N2K Pro Business Briefing) Being a Luddite Is Fun Again (404 Media) Share your feedback. What do you think about CyberWire Daily? Please take a few minutes to share your thoughts with us by completing our brief listener survey. Thank you for helping us continue to improve our show. Want to hear your company in the show? N2K CyberWire helps you reach the industry's most influential leaders and operators, while building visibility, authority, and connectivity across the cybersecurity community. Learn more at sponsor.thecyberwire.com. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc.

Over 3 hours, OpenAI, Anthropic, Google AND Microsoft all dropped new AI upgrades that are live. How you use AI in your work literally changes every day, as frontier labs are racing to roll out big quality of life updates between big model drops. How can you keep up? With our Friday Features show, where we break down the latest AI updates that are live and available to all, and we tell you how to use them and why they matter. This week did not disappoint. You don't want to miss what's now at your fingertips. JARVIS mode, anyone? ChatGPT goes Jarvis Mode, Claude can learn from you, Google unleashes spark agent and 7 more AI updates you can use today -- An Everyday AI Chat with Jordan WilsonNewsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageToday's Episode on LinkedIn: Thoughts on this? Join the convo on LinkedIn and connect with other AI leaders.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:Anthropic Claude Opus 5 Model LaunchOpenAI Agent Hacks Benchmark SandboxOpenAI vs. Hugging Face Security BreachUS AI Kill Switch Legislation ProposalMicrosoft, Nvidia Defend Open Source AIAnthropic Opposes Open Weight Model CoalitionUS Accuses China's Moonshot AI of DistillationChinese Kimi K3 Model Closes Capability GapNvidia Chips Allegedly Used by Moonshot AIOpenAI Jarvis-Style Voice Assistant for CodexChatGPT Remote Desktop Voice Control ReleaseAnthropic Opus 5 Model Benchmark ResultsAnthropic Opus 5 Model User FeedbackStripe OpenRouter Acquisition TalksMeta Muse Agent and Feature UpdatesAlibaba Qwen 3.8 AI Model PreviewGoogle Gemini 3.6 Flash Model UpdateAnthropic Claude Voice Upgrades and Skill RecordingTimestamps:00:00 OpenAI agent hacks Hugging Face04:58 Discussing GPT-6's creative problem-solving07:33 Proposed AI shutdown legislation13:08 Debate over open-weight AI policies15:54 Future of consumer hardware20:01 Global competition with AI models21:21 US-China AI trade tensions26:38 Using AI for desktop tasks27:42 Discussing app screenshot capabilities32:24 Early user feedback and issues36:13 Discussing medium and low reasoning AI39:29 Gemini Spark launches for Pro usersKeywords: Claude Opus 5, Anthropic, best AI model, AI model comparison, OpenAI agent, sandbox breach, AI safety, AI kill switch bill, US government AI regulation, Hugging Face hack, GPT 5.6 Soul, rogue AI agent, autonomous AI agents, AI benchmark exploits, bipartisan AI bill, Department of Homeland Security AI shutdown, AI technical throttling, AI enterprise adoption, NVIDIA, Microsoft, open source AI, open weight models, Meta, Google, AMD, Cloudflare, GitHub, Block, IBM, Dell, Palantir, Perplexity, y Combinator, AI market resilience, Anthropic revenue model, AI token sales, consumer AI hardware, AI distillation, Chinese AI models, Moonshot AI, Kimi K3, intellectual property theft, NVIDIA chip export controls, US-China AI dispute, Amazon, AI image generation, ChatGPT work, Codex app, full duplex voice model, knowledge work automation, app shots, AI at work, Claude Voice, Gemini Spark, record a skill, cloud cowork, AI business impact, AI industry news, model weights, collaborative AI, AI productivity tools, AI cybersecurity.Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Ready for ROI on GenAI? Go to youreverydayai.com/partner 

Scans for ESAFENET CDG 3 Document Management System Weak Logins https://isc.sans.edu/diary/Scans%20for%20ESAFENET%20CDG%203%20Document%20Management%20System%20Weak%20Logins/33184 DNS Poisoning Tactics Expand to Hospitality Wi-Fi https://reliaquest.com/blog/threat-spotlight-dns-poisoning-tactics-expand-to-hospitality/ Silent Replacement of Trusted macOS App Executables https://mysk.blog/2026/07/23/macos-overwrite-app-executables/ GitHub and PyPi Defense updates https://github.blog/security/supply-chain-security/the-case-for-a-cooldown-why-dependabot-now-waits-before-issuing-version-updates/ https://blog.pypi.org/posts/2026-07-22-releases-now-reject-new-files-after-14-days/ https://www.bleepingcomputer.com/news/security/github-pypi-add-time-absed-defenses-against-supply-chain-attacks/ My Upcoming Classes https://www.sans.org/profiles/dr-johannes-ullrich

Andrew sits down with Fred Weinmann, one of the most prolific PowerShell module authors in the community, for part one of a multi-episode series covering his projects. This episode focuses on the Active Directory Management Framework, or ADMF, a configuration-driven system Fred originally built while working as a field engineer at Microsoft for a large enterprise customer managing hundreds of Active Directory forests. Fred walks through the problem ADMF was designed to solve: Active Directory is notoriously hard to manage consistently across environments, and most organizations just accept the chaos as the cost of doing business. The old approach at this particular customer involved zipping up scripts, RDPing into domain controllers, and running them manually. ADMF changed that by borrowing the test/apply concept from Desired State Configuration, but making it flexible enough to handle the messiness of real-world AD environments. The conversation covers how ADMF is structured around components (like organizational units) and contexts, why generating a reference configuration from an existing environment is harder than it sounds, the protocol juggling required to handle Group Policy and schema updates, and why Fred would use raw LDAP instead of the built-in AD commands if he were starting from scratch today. Fred also touches on the credential provider plugin system, which lets teams plug in their own password management workflows for things like break-glass accounts. Key Takeaways: ADMF follows a test-before-apply model borrowed from DSC, but trades DSC's all-or-nothing enforcement for a more selective, component-by-component approach that better fits the fluid reality of Active Directory management. Generating a configuration from an existing AD environment is tempting but potentially counterproductive. If you auto-generate your desired state from a domain that's accumulated years of cruft, you're not capturing what you want, you're just freezing what already exists. Performance at scale is a real consideration. The built-in Active Directory PowerShell module uses the AD Web Services protocol, which sends XML over the wire. Raw LDAP is significantly faster, and Fred says switching to it is the one architectural change he'd make if building ADMF over again. Guest Bio: Friedrich "Fred" Weinmann is a Cloud Solution Architect at Microsoft and one of the most recognized PowerShell community contributors working today. He is the creator of PSFramework, which underpins many other modules in the ecosystem, as well as tools like PSModuleDevelopment, PSUtil, and the Active Directory Management Framework. Fred is a frequent conference speaker, a longtime community collaborator, and someone Andrew credits with helping shape his own PowerShell journey. Resource Links: ADMF documentation and getting started guide: admf.one ADMF on GitHub: github.com/ActiveDirectoryManagementFramework/ADMF ADMF on PowerShell Gallery: powershellgallery.com/packages/ADMF PSFramework (Fred's logging, configuration, and scripting infrastructure module): psframework.org Fred Weinmann on GitHub: github.com/FriedrichWeinmann Fred Weinmann on X: x.com/FredWeinmann PDQ Community Discord: discord.gg/pdq   The PowerShell Podcast on YouTube: https://youtu.be/8SlIqUKP3hY  

47e6GvjL4in5Zy5vVHMb9PQtGXQAcFvWSCQn2fuwDYZoZRk3oFjefr51WBNDGG9EjF1YDavg7pwGDFSAVWC5K42CBcLLv5U OR DONATE HERE: https://www.monerotalk.live/donate GUEST LINKS: https://www.wrapsynth.com/ TIMESTAMPS (00:00:00) Monerotopia Intro. (00:30:39) Monerotopia Price Report Segment w/ Bawdy. (01:30:57) Monerotopia News Segment w/ Doug. (01:33:18) Telegram to roll out native non custodial $GRAM wallet to over 1 billion users. (01:37:48) Kraken US will begin applying monthly transaction limits to Monero on August 15. (01:39:13) Zachxbt "all hardware wallets are complete garbage". (01:40:42) SenLummis post. (01:45:53) India Orders GitHub to Remove Bitchat Repositories. (01:47:29) Monero Research lab post. (01:59:55) Monerotopia Viewers on Stage Segment. (03:28:29) Monerotopia Final. NEWS SEGMENT LINKS: SPONSORS: PRICE REPORT: https://exolix.com/ GUEST SEGMENT: https://cakewallet.com & https://monero.com NEWS SEGMENT: https://www.wizardswap.io XMR.BAR: https://xmr.bar Don't forget to SUBSCRIBE! The more subscribers, the more we can help Monero grow! XMRtopia TELEGRAM: https://t.me/monerotopia XMRtopia MATRIX: https://matrix.to/#/%23monerotopia%3Amonero.social ODYSEE: https://bit.ly/3bMaFtE WEBSITE: monerotopia.com CONTACT: monerotopia@protonmail.com MASTADON: @Monerotopia@mastodon.social MONERO.TOWN https://monero.town/u/monerotopia Get Social with us: X: https://twitter.com/monerotopia INSTAGRAM: https://www.instagram.com/monerotopia DOUGLAS: https://twitter.com/douglastuman SUNITA: https://twitter.com/sunchakr TUX: https://twitter.com/tuxpizza

This episode has our co-hosts Robby and Tim in conversation with Warp founder Zach Lloyd as he shares the company story and decision to open source their core product: the terminal. They now provide an open source agentic development environment (born out of the terminal) which is also called warp and has almost 65K stars on GitHub. Zach discusses his frustration with the traditional terminal and how it inspired him to rebuild it from first principles. Originally conceived before ChatGPT as a more intuitive, collaborative command-line experience, Warp quickly resonated with developers and has since grown to 1 million users. Lloyd discusses the company's decision to build Warp in Rust, its early reluctance to open source the product, and how the rise of coding agents transformed Warp from a modern terminal into a broader agentic development environment.The conversation also explores Warp's evolving product vision: a terminal, agent harness, and cloud platform that can orchestrate different models and coding tools without locking companies into a single provider. Lloyd explains how Warp uses agents to triage issues, write and review code, test interfaces, and accelerate open source contributions while keeping humans involved in key decisions. Ultimately, the episode is about how AI is reshaping software development and Warp's ambition to become the platform that turns ideas, community feedback, and company workflows into shipped software as efficiently as possible.

This month on Sync Up, Stephen Rice and Arvind Mishra are joined by Joe Komban, a Principal Product Manager on SharePoint, to explore two connected leaps forward for Copilot in SharePoint and OneDrive. First, the new file tools — watch Copilot build a quarterly report from a template, spreadsheet, and meeting transcript in minutes, convert it to PDF, grant every meeting attendee access, and even spin up an animated HTML dashboard. Then the star of the show: Copilot Skills, a way to teach Copilot your team's exact process — from legal reviews to file-naming conventions — so anyone can get expert-level output, even if they're not the expert. The team digs into how Skills work, where they live (just markdown files in SharePoint), the human-in-the-loop transparency built in, the community GitHub repo, and why "you're only limited by your imagination." Skills are available today with Copilot in SharePoint, with OneDrive file tools rolling out to frontier customers in the July–August timeframe. Your SyncUp cohosts: Stephen Rice | Arvind Mishra Main resources: Review and subscribe to Sync Up | Keep up to date on the OneDrive blog | Follow us on: Apple Podcasts | Spotify | RSS 

In this episode of Alexa's Input (AI), I sit down with Alex Zenla, founder and CTO of Edera.Alex grew up in a small town in Alabama, found a computer young, and started building. Her story is unlike many in tech. She taught herself to program and got a job in tech at 14 years old. Since then, she's been actively building and involved in open source. She's currently the founder and CTO of Edera, a company whose product integrates security into the lowest layers of the platform without sacrificing performance or velocity.In this episode, we get into where that path started, what it costs to be different in founder and venture rooms, and what breaks when infrastructure still ships with security off by default.From the episode:Growing up in small-town Alabama without a path into techSouthern niceness as theory versus practiceFull-time work at fourteen and presenting to executives as a teenagerBeing one of very few trans founders in venture rooms, and the tension between visibility and being treated as a tokenElevator pitches that change with the audienceDetection and response after a problem has already occurredCommon Vulnerabilities and Exposures becoming untenable when tools like Mythos surface hundreds of findings per project per dayKubernetes and vendors selling yet another layer while the foundations underneath are misalignedSecure defaults as the path of least resistance for teams that just need a cluster that worksAlex's mission is to make secure computing the default. Today you work hard to get a secure environment, and she's building Edera to invert that. What stays with you is how personal that work is for her. The path from a small Alabama town into those rooms is not separate from the product. It's why the default being broken bothers her enough to build a company around fixing it.GENERAL PODCAST LINKSWatch: https://www.youtube.com/@alexasinputRead: https://alexasinput.substack.com/Listen: https://creators.spotify.com/pod/profile/alexagriffith/More: https://linktr.ee/alexagriffithLEARN MORE ABOUT THE HOSTWebsite: https://alexagriffith.com/LinkedIn: https://www.linkedin.com/in/alexa-griffith/FIND OUT MORE ABOUT THE GUESTLinkedIn: https://www.linkedin.com/in/azenla/Bluesky: https://bsky.app/profile/alex.zenla.ioEdera: https://edera.dev/GitHub: https://github.com/edera-devRESOURCESEdera docs: https://docs.edera.dev/

¿Sabías que puedes convertir cualquier texto en coordenadas de 1024 dimensiones y hacer búsquedas inteligentes, clasificación automática o detección de duplicados sin depender de servicios en la nube? En este episodio te enseño a utilizar los embeddings con Ollama para potenciar tus documentos, correos y apuntes desde tu propio equipo Linux.Los embeddings son una de las tecnologías más fascinantes de la inteligencia artificial actual. Básicamente, convierten palabras, frases o párrafos enteros en vectores numéricos que capturan su significado. Esto permite que un ordenador entienda que "gato" está más cerca de "felino" que de "nevera", y mucho más: desde búsqueda semántica hasta clasificación sin entrenamiento, pasando por deduplicación de documentos y sistemas de recomendación.Lo mejor de todo es que no necesitas una GPU potente ni una cuenta en ningún servicio externo. Con Ollama ejecutándose en local y el modelo BGE-M3 (multilenguaje, con soporte para español), puedes generar embeddings desde la terminal con una simple llamada curl o con unas pocas líneas de Python. Y si necesitas escalar, ChromaDB te ofrece una base de datos vectorial completa con persistencia en disco y filtros por metadatos.Capítulos del episodio:0:00 - Introducción y concepto de embeddings2:42 - ¿Qué son los embeddings exactamente?5:13 - Modelos de embeddings: BGE-M3, all-MiniLM-L6-v27:25 - Cómo generar embeddings con Ollama y curl8:01 - Búsqueda semántica: más allá de grep11:57 - Búsqueda semántica con Python y NumPy14:29 - Bases de datos vectoriales para escalar14:53 - Clasificación sin entrenar el modelo18:20 - Clasificación de sentimientos y categorías20:02 - Deduplicación de documentos con embeddings24:50 - Sistema de recomendaciones con similitud semántica27:15 - ChromaDB: base de datos vectorial persistente29:02 - Casos de uso y próximos episodios sobre RAGMás información y enlaces en las notas del episodio

Over 3 hours, OpenAI, Anthropic, Google AND Microsoft all dropped new AI upgrades that are live. How you use AI in your work literally changes every day, as frontier labs are racing to roll out big quality of life updates between big model drops. How can you keep up? With our Friday Features show, where we break down the latest AI updates that are live and available to all, and we tell you how to use them and why they matter. This week did not disappoint. You don't want to miss what's now at your fingertips. JARVIS mode, anyone? ChatGPT goes Jarvis Mode, Claude can learn from you, Google unleashes spark agent and 7 more AI updates you can use today -- An Everyday AI Chat with Jordan WilsonNewsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageToday's Episode on LinkedIn: Thoughts on this? Join the convo on LinkedIn and connect with other AI leaders.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:ChatGPT Health Syncs Apple and Medical DataClaude Voice Mode Adds Opus and SonnetClaude Voice Mode Supports ConnectorsMicrosoft MAI Image 2.5 Pro Launch DetailsMicrosoft MAI Image Model Benchmark PreviewGoogle Gemini 3.6 Flash and Flashlight ReleaseGemini 3.6 Flash: Token Efficiency UpgradesGoogle Gemini Spark Agent for Task AutomationClaude Cowork "Record a Skill" With Voice NarrationChatGPT Voice on Desktop: Full Jarvis ModeChatGPT Voice Controls Apps via App ShotsCross-Platform AI Skills Sharing (Claude, Codex, GPT)Timestamps:00:00 Recent AI feature updates05:22 Unified health data management09:52 New voice feature explanation11:28 Launch of Microsoft's new image model16:17 Explaining the Gemini 3.5 models17:11 Developers benefiting from 3.6 Flash22:45 Introducing Gemini personal intelligence25:10 Claude Cowork's new skill feature28:32 New default feature in Claude Cowork34:22 Using AI like Iron Man35:09 Excitement for future AI advancements38:20 Wrapping up and subscribingKeywords: ChatGPT Jarvis mode, ChatGPT Health, OpenAI, Anthropic, Claude voice mode, Claude Cowork, Claude record a skill, Microsoft, MAI image 2.5 Pro, AI image generator, Google Gemini, Gemini 3.6 Flash, Gemini 3.5 Flashlight, Gemini Spark, Google AI agent, AI-powered personal assistant, AI agents, Agentic workflows, Multimodal AI, Token efficiency, Image generation, Voice-activated AI, AI-powered task automation, App shots, GPT Live, Remote browser, Computer code execution, Slack integration, GitHub integration, Notion, PowerPoint AI features, Workspace plans, Apple Health integration, Medical records AI, Health data privacy, Consumer AI, Chronic condition management, AI-powered document processing, AI for business, AI model benchmarking, AI for developers, AI economics, Personal intelligence, Automated triggers, Google Docs AI, Team collaboration AISend Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Ready for ROI on GenAI? Go to youreverydayai.com/partner 

The dominant structural shift highlighted is the migration from flat-rate software subscriptions to usage-based billing models within AI and cloud services. Notably, vendors such as Anthropic, OpenAI, and GitHub have transitioned services off fixed-rate subscriptions toward consumption-based pricing, while Microsoft has introduced new premium tiers that embed AI and security features above the base offering. This shift introduces hidden metering within per-seat pricing, creating less transparency for small- and mid-sized clients regarding actual AI consumption and cost accountability, as documented in research referenced by Forrester. A consequential finding is that budgets for software and AI are reportedly rising by 80% among business and technology decision-makers surveyed by Forrester, yet most organizations are only at the early stages of genuine AI integration. According to IDC research sponsored by SAS, only 9% of small- and midsize businesses (SMBs) have fully embedded AI in daily operations, while about 70% remain in pilot or opportunistic phases. Moreover, a Gallup survey found that 52% of American workers now use AI on the job, but depth of adoption remains limited, with many implementations running only at a superficial level. Supporting developments include mounting evidence that cloud computing's historical promise of near-infinite capacity is eroding. Computer Weekly reports that Microsoft's cloud elasticity is encountering real-world constraints, leading to capacity limits and service rollbacks. Further, regulatory intervention is escalating: New York state has implemented a moratorium on new large-scale data center permits, reflecting mounting political resistance and public distrust toward large technology providers. Meanwhile, increased capital spending by AI vendors is pressuring margins and potentially driving future price adjustments or investment cutbacks across the sector. For MSPs and IT leaders, these trends increase operational complexity and expose gaps in spend governance and accountability. As metered AI and hybrid pricing models proliferate, tracking real usage and managing associated costs becomes more challenging, especially when AI charges are masked within bundled per-user pricing. Providers must develop discovery and reporting practices to quantify hidden AI spend, inventory usage meters within client stacks, and establish pricing models that properly segment one-time discovery from ongoing measurement. Failure to implement these controls exposes both MSPs and clients to unplanned overages, margin loss, and audit risk as consumption scales invisibly under the current invoice structure. 00:00 Your Subscription Became a Meter  04:14 Compute Ran Out of Room 06:51 Nine Percent Ever Finish 09:51 Why Do We Care?  Supported by:  Guardz ScalePad   

Hey friends! Welcome back to another Tales of Pentest Pwnage — my favorite mini-series where I share the good, the bad, and the "why didn't I check THAT first?!" moments from real-world engagements. Today's story has a little bit of everything: a legit path to domain admin, some late-night rabbit holes, a lesson in humility, and a villain you've definitely met before. (Spoiler: it's DNS.) A couple of quick plugs before we dive in: Private GOAD training is going strong! — We just wrapped a 3-day private session (7 students — that's max capacity!) of our Active Directory pentesting class built on the Game of Active Directory (GOAD) framework. Over three days, students enumerate, attack, and fully pwn three separate AD environments. The private format is just *chef's kiss* — when it's a team from the same company, the conversation gets real fast. Like, "hey I just checked Bloodhound on break and Bob from accounting has full rights over the DC" real. If you want to send 3–7 people from your org, hit up 7MinSec.com/training to line up a private session. Support the show over at 7MinSec.club — That's our Substack, where every Tuesday I drop a short TuesdayTOOLSday video about security tools. Free subscriptions are welcome and mean a lot — you'll just get pinged when new content drops. No spam, no blindly-sent Outlook calendar invites. I promise. Pentest tips and scripts live at 7MinSec.wiki — I reference it throughout today's episode, including some step-by-step guidance on the techniques we'll talk about below. Now — onto the pwnage. Fair warning: I've been burning the candle at three ends lately trying to catch up after a tough few weeks of grief (if you want the backstory, the last couple episodes cover my dad passing away). The good news is my head is semi back on straight and I put it to work on a recurring client environment — one that keeps getting better year over year. Machine account quota locked down? Check. No Kerberoastable or AS-REP roastable users? Check. No local admin rights, no web client running? Check and check. All good signs. And then PingCastle smiled right into my eyeballs with a big red finding: The DC's LAN Manager authentication level was weak enough to coerce and capture a downgraded hash — Specifically, an NTLMv1 SSP hash. Using Coercer to nudge the DC into authenticating to my Kali box (with Responder running), I captured the goods. Pretty little hashes all in a row. Cracking that hash: enter Vast.ai — The old go-to for this type of crack used to be crack.sh, but their cracker has been offline for years. What they do still have is a walkthrough pointing to a tool from EvilMog on GitHub that helps you prep the raw hash material and figure out exactly how to crack it with Hashcat. For the GPU horsepower, I rented a beefy multi-GPU instance on Vast.ai — filter for 16+ GPUs, pick a Hashcat Docker image, and SSH in. The whole crack job took about 16 hours at ~$4/hr. Do the math: $64 to reconstruct the DC's NTLM hash. Worth it. Tmux sidebar — seriously just learn it — Vast.ai is actually what finally got me into tmux, because the Hashcat Docker container drops you right into a tmux session. This is clutch: you can kick off a 16-hour crack job, detach, and reattach later without killing anything. On a pentest, my workflow now is SSH in → tmux → name a few session windows for Responder, Exegol, packet captures, etc. I used to fumble around with Linux screen sessions. Not anymore! From hash to DA — the usual playbook — Once you've got the DC's NTLM hash, you can request a Kerberos ticket and load it up, then run a DCSync to pull the KRBTGT hash. From there it's god mode: dump hashes, pass-the-hash as domain admins, and you have yourself a cool privesc POC. Except this time…the POC didn't work. The part where I Jean-Claude Van Damme helicopter kick myself in the face — DCSync failed immediately. Like, suspiciously fast — barely two lines of output and done. I tried every version of every tool I could get my hands on. I tried Windows, I tried Linux. I even asked the client to check if their endpoint protection was blocking me (it wasn't). I touched grass. I played guitar. I played some Splinter Cell Blacklist (old game, highly recommend if you like the Hitman-style vibes). Came back fresh. Rebooted both VMs. Still nothing. It was DNS. It's always DNS. — The thing that finally caught my eye: the commands were failing too fast. Like it wasn't even reaching the DC. I catted the resolv.conf inside my Exegol instance (heads up: Exegol has its own resolv.conf and hosts file, separate from your base Kali system!) and found a stale DNS entry pointing to an old DC that was no longer serving anything. Nuked the bad entry, added static hosts file entries for the live DC, ran the command again, and — hash rain. Pennies from heaven. It was midnight and I literally pushed back from my desk like a baby pushing away from a high chair going "Baby Brian is all done!" The lesson: — I know the meme. "It's always DNS." I just personally hadn't hit it hard in my security life since my sysadmin days back before 2013. Now I have. So going forward I'll check DNS first (and often). Vacation attempt #3 incoming… pray for me — My wife nearly died in Punta Cana earlier this year. Then our summer cabin trip was cold and rainy with zero water time. And now we've got families flying in from multiple states for a lake weekend — except we just found out our reservation through Booking.com was basically vaporized because the resort changed hands and never updated their website. My wife (who is an absolute saint and my better three-quarters) almost had a 360-degree head spin (like in The Exorcist) talking to customer service. But we scrambled, found a last-minute place, and I'm choosing to believe it's not in Jason Voorhees' back yard. Could this be my last episode? Maybe. But hey — it was a good one. Talk to you next week (hopefully).

In this talk, Paul Iusztin, Creator of Decoding AI and author of the LLM Engineer's Handbook, shares his deep expertise in personal automation from managing a digital life with lightweight data pipelines to architecting autonomous agents for deep research. We explore the mechanics of building personal AI assistants and the critical role of using a "second brain" as a context layer over heavy, over-engineered RAG infrastructure.You'll learn about:- Organizing your digital life using the PARA method and lightweight data pipelines.- Capturing and retrieving resources effortlessly with Obsidian, Readwise, and custom deep research algorithms.- Leveraging your "second brain" setup as the ultimate context layer for personal AI assistants.- Generating ad-hoc wikis from markdown brain dumps to streamline content creation and research.- Optimizing AI-generated content by deliberately lowering LLM reasoning capabilities for better styling.- Adapting multi-agent workflows and personal wikis to accelerate software engineering and coding tasks.TIMECODES:00:00 Digital life organization using the PARA method and lightweight data pipelines05:21 Seamless resource capture with Obsidian and Readwise09:26 Resource retrieval optimization using a deep research algorithm12:44 High-quality internet curation versus heavy RAG pipelines16:31 Second brain setup as a context layer for personal AI assistants21:40 AI workflow simplification with Anthropic APIs and CLI tools25:26 Ad-hoc wiki generation from markdown brain dumps for content creation29:18 Codebase ingestion and web scraping proxy tool workarounds34:43 Resource reranking and context window management for large texts39:06 Content styling optimization by lowering LLM reasoning capabilities46:18 Multi-agent workflows and personal wikis for software engineering tasks52:32 Personal wiki scaling for enterprise knowledge bases and book writingThis talk is perfect for individual developers, AI engineers, and knowledge workers looking to escape "PoC purgatory" and build practical, low-maintenance personal AI assistants. It offers highly actionable insights for anyone wanting to integrate agentic workflows into their daily productivity systems without over-engineering their tech stack.Connect with Paul- Linkedin - https://www.linkedin.com/in/pauliusztin/- Website - https://www.pauliusztin.ai/Connect with DataTalks.Club:- Join the community - https://datatalks.club/slack.html- Subscribe to our Google calendar to have all our events in your calendar - https://calendar.google.com/calendar/r?cid=ZjhxaWRqbnEwamhzY3A4ODA5azFlZ2hzNjBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ- Check other upcoming events - https://lu.ma/dtc-events- GitHub: https://github.com/DataTalksClub- LinkedIn - https://www.linkedin.com/company/datatalks-club/ - Twitter - https://twitter.com/DataTalksClub - Website - https://datatalks.club/

#diarrhea #taylorfarms #fdaIn the middle of a diarrhea shitstorm, the Food and Drug Administration andlettuce supplier Taylor Farms appear to be facing off in a passive-aggressivebattle of technicalities.On July 17, the California-based company issued a voluntary recall on iceberglettuce sourced from Central Mexico. The recall came after people across atleast five states were sickened with cyclosporiasis, a parasitic infectionthat causes explosive diarrhea.The next day, the FDA said that it had detected the parasite in a sample ofTaylor Farms lettuce that wasn't part of the initial recall. The day afterthat, the company and the FDA said that the result was actually a falsepositive.Article https://www.yahoo.com/news/us/articles/skinnytok-influencers-tout-diarrhea-diet-161452978.html Timestamps 00:00 Intro 02:14 What are we talking about 05:50 Story 11:50 Thoughts 16:00 Closing

1205. In the bonus discussion this week, we continue discussing AI em dashes with Sean Goedecke, software engineer for GitHub. We talk about why AI detectors are often unreliable and how they can disproportionately flag non-native English speakers. We also look at the controversial idea of "writing for AI" to ensure your ideas are represented in future machine learning models. This episode ran for Grammarpaloozians in February 2026. To get more bonus content, visit Patreon.com/GrammarGirl.Find Sean at www.SeanGoedecke.com

Our host Sami is joined this week by Joe Cohen, Legal Innovation Partner at Harvey AI, to discuss the use of AI within the legal and professional services, and how it could impact the speed, quality and efficiency of lawyers doing legal work. Joe dives into his career journey, Harvey AI's adoption rate success within law firms, what the future career growth could look like for Junior Partners being taught by AI, and the comparison between AI use in the modern age vs the introduction of email in the 80's. — Our guest for this episode has been Joe Cohen. If you'd like to get in touch with Joe, or to keep up to date with his work, you can do so through LinkedIn Your host for this episode has been Sami Birnbaum. Sami can be found through his website or via LinkedIn. If you would like to support the show, head over to our GitHub page, or check out our website. Got a question or comment about the show? Why not write to our hosts: hosts@giantrobots.fm This has been a thoughtbot podcast. Stay up to date by following us on social media - LinkedIn - Mastodon - YouTube - Bluesky © 2026 Giant Robots Smashing Into Other Giant Robots Podcast

The agentic transformation isn't coming. It has already begun.Companies are deploying thousands — and sometimes tens of thousands — of AI agents. Enterprise software giants are watching their old economic moats erode. Capital is moving, productivity is being redefined, and human labor is being repriced in real time.In this Fully Connected episode, Daniel and Chris explore the new economics of a post-agentic world: the global order that emerges after agents have been woven into every conceivable aspect of business and life. What happens when digital labor becomes abundant, agents manage other agents, and entire organizations operate at a scale no human workforce could match?This isn't another conversation about whether AI will take your job. It's about what happens when the assumptions underneath jobs, companies, software, and productivity stop being true.The post-agentic world is already taking shape.The question is whether you're preparing for it — or becoming part of what it replaces.Featuring:Chris Benson – Website, LinkedIn, Bluesky, GitHub, XDaniel Whitenack – Website, GitHub, XLinks:Is IBM a Canary in the Tech Coal Mine?Verbalizable Representations Form a Global Workspace in Language ModelsUpcoming Events: Register for upcoming webinars here!Midwest AI Summit 2026

Become an AI-native Product Manager with OpenAI's Codex PM and other frontier AI leaders ($500 off): https://maven.com/product-faculty/ai-product-management-certification?promoCode=F5    Elie Habib built Anghami into the first Nasdaq-listed music streaming company out of the Middle East, fending off Spotify and Apple along the way. Then, on a single Sunday in January, he started coding a weekend side project called World Monitor. It now has over 3 million users, 50,000+ GitHub stars, and people are calling it "the Bloomberg Terminal for geopolitics." He has refused to charge a cent for it during wartime. In this conversation, Elie breaks down three things every leader needs to hear: how a local founder out-competes global giants, how a media executive adapts to AI, and how a CEO actually builds with AI instead of just talking about it. We get into why "you don't beat Spotify by being Spotify with Arabic subtitles," why he won't hire again until his team proves real AI adoption, why he believes a CEO who can't code on weekends won't survive the next decade, and why curiosity is the only competitive advantage that never depreciates. Chapters: 00:00 Trailer 01:07 Three conversations every CXO needs to hear 02:18 Beating Spotify and Apple without their budget 08:38 Why improving your product means fixing your org chart 13:07 Building a team that argues with you 15:08 Running music and video as separate but connected products 22:14 How AI reshapes the content supply chain 25:47 Why ambition plus AI beats deep pockets 28:32 How Elie deploys AI across every division 37:25 Why a CEO who can't code won't survive the next decade 41:28 World Monitor: the 3M-user weekend project 46:07 Refusing to monetize during a war 51:52 Curiosity, building with your team, and what you become #AI #Startups #Podcast #TechLeadership #Anghami

This show has been flagged as Clean by the host. Hello, again. This is Trey. Welcome to part 8 in my Cheap Yellow Display (CYD) Project series. If you wish to catch up on earlier episodes, you can find them on my HPR profile page https://www.hackerpublicradio.org/correspondents/0394.html It is hard to believe that I started this project and the HPR series to document it more than a year ago. Time flies. Life happens. I spent the last 8 months so focused on work related activities that I had to set the project aside. And once I set it aside, it was difficult to get back to again. The one time I tried, I found that my son's old Windows laptop, which I had commandeered to use for the project, was once and truly dead. We live in a different world now than we did when I began this project. Today, everything is about AI – how it is changing our world, increasing efficiencies, and even displacing certain types of jobs. "Vibe coding" is transforming the way we make software, and now everyone is a developer. Within my organization, we are all being strongly encouraged to learn more about AI and apply it in our daily work. We are blessed to have access to a wide range of training and to powerful tools which support the process. Several colleagues within my organization and outside my organization have recommended Claude Code -- for development, for organization, for brainstorming, and for much more. My role is not that of a developer, and I have had no need for Claude Code at work. There are plenty of other tools for me to use. But at home, I thought... I could install Claude Code at home to experiment with and to learn. And then it hit me. I wonder if I could use Claude Code to help me with my stalled CYD project. "Hello, my name is Trey, and I am a fraud." OK. I don't think I am a fraud, but having never used such a powerful tool to help me code, I feel a little bit like a fraud, with Claude doing the work for me. Let's talk through what we did. As I mentioned, I was unable to use the laptop on which I created the original GUI code. But no worries, because It was all on GitHub, right? So, I began by trying to install Claude Code on one of my Ubuntu machines. That failed miserably, and all the instructions I found online recommended running it on Windows. So I transitioned to installing Claude Code on a freshly built Windows 10 system using some old hardware which will not support Windows 11. Surprisingly, It seems that Claude wants to run within Ubuntu on Windows Subsystem for Linux (WSL). Once I went through all the hoops for installing and setting up my basic subscription, I got to work. I created a new directory to use for all my project files, and another one for Claude to write all its output files to. Everything I have read and heard about using Claude Code for a project like this recommended beginning by using Claude to create the project plan. So my first prompt was as follows: "I am building a project using an ESP32 cheap yellow display. The final goal is to have a device with a graphical user interface which will allow me store several text messages, each assigned to their own specific button. Then, when one of the buttons is pressed, the message will be converted into morse code, and the message will be sent by blinking an onboard LED. I already have the initial design for the GUI coded in my github repository. Please construct a detailed step by step plan for building this application" I wanted to keep it simple at the beginning, so even though I plan to use an opto-isolated relay for the output, I am starting out using the built in LED. Claude asked me for the URL for my Github repository, and I provided it. After thinking for a bit, it produced a project plan. CYD Morse Sender — Step-by-Step Build Plan What You Already Have - 3 fully designed LVGL screens (Send, Config, Keyboard) - 7 send buttons with green styling on the Send Screen - Speed slider (5–30 WPM) and program slot dropdown on Config Screen - Text area + LVGL keyboard widget on Keyboard Screen - Display driver and touchscreen hardware initialized (but touch read was stubbed out) --- Phase 1: Fix Touchscreen Input Initialize the XPT2046 on VSPI, replace the hardcoded touched = false with real touch data, calibrate raw ADC coordinates to screen pixels, and verify all three nav buttons transition screens correctly. Phase 2: Persistent Message Storage Use Preferences.h / NVS to store 7 messages ("msg0" – "msg6") that survive power cycles. Load on boot and populate send button labels. Phase 3: Config Screen — Slot Selection & Speed Wire the Program dropdown to g_selectedSlot, wire the Speed slider to g_wpm with a live WPM label, and wire the Set button to clear the text area and navigate to the Keyboard Screen. Phase 4: Keyboard Screen — Capture and Save Text On keyboard OK (LV_EVENT_READY): read the text area, save to NVS, update the send button label, navigate back. On Cancel: navigate back without saving. Phase 5: Morse Code Engine Build morse.h with the full A–Z / 0–9 lookup table, a textToMorse() converter, and Paris-standard timing (unit_ms = 1200 / wpm). Phase 6: Non-Blocking LED Transmission State machine (IDLE / LED_ON / LED_OFF) driven by millis() in a morseUpdate() function called every loop — no delay(). LED on GPIO 17 (blue). Phase 7: Wire the Send Buttons Each button calls startMorse(getMessage(slot)) if not already transmitting. Disable all send buttons during TX; re-enable when the state machine reaches the end. Phase 8: Integration & Polish Stop button, WPM persistence, empty-slot guard, serial debug output, final touch calibration, end-to-end test checklist. --- Recommended order: Phase 1 → 2 → 7 (partial) → 5 → 6 → 7 (full) → 3 → 4 → 8 This was wild! Claude determined exactly how far along I was in the project, and also alerted me to the fact that the "touch read was stubbed out". Ugh. This means that the files I had uploaded to GitHub were my original GUI files (Episode 05 – HPR4532 - https://hackerpublicradio.org/eps/hpr4532/index.html ) and not the ones that I finally got working properly (Episode 07 – HPR4624 - https://hackerpublicradio.org/eps/hpr4624/index.html ). That was my own fault. Did I mention that I don't get Git? I REALLY need to learn to properly use Git! But, we have a plan, broken down by eight numbered phases. And they seem to address all the functionality I wanted with a few additional things I had not thought about. Interestingly, even though these phases are sequentially numbered, Claud recommended that we approach them in a bizarre order: Phase 1 → 2 → 7 (partial) → 5 → 6 → 7 (full) → 3 → 4 → 8 . Alright. Let's see what we can do. The first phase is to fix the touchscreen input. Claude took me through it step-by-step, asking as it needed to read specific project files. Finally, it wrote a new ui.ino code file to my speficied output directory for me to test. I copied it into the correct file location, said a quick prayer, compiled in Arduino IDE, and downloaded to the CYD. Well, that is... interesting. The display looked nothing like it was supposed to. There were vertical green bars with smaller dashed green vertical stripes in them. I will include a picture in the show notes so that you can see what it looked like and why it was so difficult to describe. I spent the next hour or so trying to explain what I was seeing to a chat bot. Claude recommended potential fixes which either did nothing or made the situation worse. I began questioning whether this was a good idea, how people actually gained efficiencies talking to a bot, and even several life choices. Then I had a thought. I prompted Claude: If I were to take a picture of the screen on the cheap yellow display and copy it into the output folder, would you be able to analyze it to better determine what is wrong and how to fix it? Shockingly, Claude answered in the affirmative, and told me to copy the picture to the output folder and let it know when to proceed. It analyzed the picture and more of the supporting files it had copied from my GitHub, asking each time if it could access that file. It determined that my original code was written for a flavor of LVGL version 8 and I was now using LVGL 9.5. It recommended changes, and then asked permission to make those changes, file by file. .h files & .c files, Finally, I just gave it permission to edit the files in the project folder without asking for permission for each file each time. Claude was still explaining each change, showing me exactly what would be changed, and asking for permission, so that I could review all of the changes. But now it was not asking additional permission to write to each of the impacted files. Next, Code compiled and downloaded. Different screen, but not right. Again, I took a picture and gave it to Claude to analyze. So, Claude paused and altered the code to generate a specific test pattern overtop of the GUI. The test pattern was supposed to cover the entire rectangular screen. But parts of the pattern were in a square on the screen and parts were not. Another photograph and analysis, told Claude that there were some rotation/screensize issues. We repeated this several times. Some resulted in improvement, and others did not. This is the point where I noticed something interesting. Not about Claude, specifically, or about the app. But I noticed something interesting about myself and about the process. Previously, when I was working through some of these challenges without Claud, I found myself becoming more and more stressed, frustrated, and angry, until I found a solution. Then another problem would repeat the cycle. Success in the end was great, but the emotional extremes during the process were not always pleasant. Now, I was effectively managing the project, and relaying information to the resource responsible for fixing the problems -- a very different experience. But I also ran into another issue. Claude became absolutely certain that the problem revolved around the device not accurately knowing where the 4 corners of the screen were. But in reality, the output of the test pattern was rotated 90 degrees from the actual screen. It took several iterations of me insisting that the problem had to do with screen orientation and not corner coordinates. It was interesting to experience the tool doubling down on an obvious mistake, but we finally resolved that. Again, while it was frustrating, it was much less stressful. We proceeded to Phase 2: Persistent Message Storage where we ensured that the button labels on the send screen were stored in the devices persistent storage, so that, when they are edited to contain the message they should send, that information would survive a reboot. Next, we combined elements of Phase 5: Morse Code Engine , Phase 6: Non-Blocking LED Transmission , and Phase 7: Wire the Send Buttons together. Building the morse code engine was an area I had been thinking about for a while. I already had working parts of something similar in the Arduino practice oscillator I have referenced a few times in this series. The code for the practice oscillator may be found on my GitHub, but it was all based on original code from jmharvey1, with my only contribution being making pin assignments variables so that the code could easily be ported to different devices. So, I was happy that we were building the morse code engine directly. The code for it may be found in morse.h, which uses a constant character lookup table to define each character. Without any specific direction from me, Claude used the PARIS timing methods I have already described within Episode 6 of this series. It defines timing for DOT, DASH, LETTER_GAP, and WORD_GAP, and all are based on a simple calculation of 1200 ms / the number of words per minute (WPM) we wish to transmit. Along the way, we discovered that, if we tried to use the delay() function, it would crash the program due to a conflict with the LVGL timer used for touchscreen inputs. Claude altered all the delays accordingly. Then, Phase 3: Config Screen — Slot Selection & Speed allowed us to configure the WPM we wished to use in addition to selecting a specific Send button to reconfigure. This forced us to work on Phase 4: Keyboard Screen — Capture and Save Text which is used to type the entries for each Send button. At this point, I also decided that we would want to also use the Keyboard Screen to send ad hoc morse as we typed it. During this phase we discovered several bugs which seemed to cause random freezes. Careful troubleshooting with messages output to the Arduino IDE's serial console helped us narrow down the causes and remedy them. Finally all the tests worked and I am able to merrily pre-configure macro buttons with custom messages and use the CYD to send the morse code for those messages to the on-board LED at whichever rate I specify. I have noticed in my presentation of this narrative that I repeatedly slip into the first person plural terms "we" and "us" instead of the first person singular terms "I" and "me". I have unconsciously personified Claud and recognized it as an integral part of my (formerly one person) development team. I finally configured Claude to connect to my GitHub repo and upload all the files and documentation. We additionally created a CYD-Narrative.md file which describes in more detail all the work which was done on the project. I still do not 100% get git, but we are successfully using it. You can find all these files in my GitHub repo ( https://github.com/jttrey3/CYD_MorseSender ) where they are shared under a GPL 3.0 license. There are still several additional steps I plan to complete in the next few months. 1. I will be integrating an opto-isolated relay which will allow me to plug the device into the straight key input on any amateur radio. This will require a battery power source, charge controller, and more hardware. I... make that "We" (Claude & I) will be modifying the code to support an audio side tone through an attached speaker when sending code We will add an output selection switch to the config page to choose any combination of speaker, relay, or LED as output. We will develop a downloadable firmware which I hope to share with the Cheap Yellow Display community. If you can think of any additional features you would like to see integrated, please drop me an email using the address in my HPR profile. I may also work with a friend to attempt to 3d print a case for the entire contraption, and I will be sure to record additional episodes sharing the process. I have learned so much throughout this project, about the CYD, ESP32, GUIs, Claude Code, GitHub, and most of all, about myself. Does using AI to develop this code make me a fraud? It still feels like it in some ways. Does it make me more productive? ABSOLUTELY! I made consistent forward progress when I only had 30-60 minutes each day to work on it, and everything discussed in this episode was completed in less than a week. If I had been able to work on it for a few hours uninterrupted, it may have only taken me 3-5 hours. Does it empower and inspire me to do more projects like this? 100% I feel like I had support working with me the whole way. I was less stressed overall, and it had less of an impact on the amount of and quality of time I spent with my family. I will be wrapping up this series soon, without any more 6 month gaps, I hope. Until next time... Provide feedback on this episode.

¿Todavía usando awk para extraer información de ps aux o df? En 2026 hay herramientas mucho mejores. En este episodio te presento tres herramientas que forman un tridente imbatible para trabajar con información del sistema en formato JSON: jc, jq y gron.jc es un conversor de comandos Linux a JSON. Se instala con pip y un simple pipe convierte la salida de ps, df, free, ss, systemctl, lsblk y hasta 60 comandos más en JSON estructurado. Olvídate de awk y de los scripts frágiles que se rompen cuando cambia el orden de las columnas. Con jc, el JSON no depende del formato de salida. Tiene parsers específicos para cada comando, incluyendo crontab, last, lsof, pip list, lsmod, date y más. Si no encuentra el parser que necesitas, puedes crear el tuyo. Está escrito en Python y tiene licencia MIT.jq es la navaja suiza de los JSON. Te permite filtrar, ordenar, agrupar, seleccionar y transformar cualquier JSON con una sintaxis potente. Está escrito en Go y es maduro, estable y rapidísimo. Combinado con jc, puedes listar los procesos que más RAM consumen, los discos por encima del 80% de ocupación o los servicios que han fallado, todo en una sola línea. Si la sintaxis te parece liosa, puedes pedirle a cualquier modelo de lenguaje que te genere la expresión que necesitas.gron es el menos conocido pero igual de útil. Aplana un JSON convirtiendo cada valor en una línea independiente con su ruta completa. ¿Para qué sirve? Para poder usar grep directamente sobre un JSON. Si alguna vez has hecho un curl a una API y has intentado hacer grep sobre el resultado, sabes que no funciona porque todo está en una línea. Con gron, cada valor tiene su propia línea y puedes buscar con grep. Además permite la operación inversa con --ungron: modificas el JSON aplanado con sed y lo reconstruyes.En el episodio presento sysreport.py, un script en Python que junta toda la información del sistema en un solo JSON usando jc y luego te permite hacer preguntas en lenguaje natural usando Llama 3.2 con Ollama. Le preguntas qué procesos consumen más RAM, qué servicios están caídos o si hay algún disco lleno, y él te responde en lenguaje natural. Todo corriendo en local, sin gastar un euro en APIs.El script se puede usar como API local, se combina con watch para monitorización en tiempo real y con notify-send para notificaciones en el escritorio. Además se integra directamente con el nightly-runner del episodio 815 para incluir el estado del sistema en el resumen matutino.Capítulos:0:00 - Introducción: el problema de la salida en texto plano2:30 - jc: convierte comandos Linux a JSON5:00 - jq: la navaja suiza de los JSON8:00 - gron: haz greppable cualquier JSON10:30 - Combinando jc y jq para consultas del sistema13:00 - sysreport.py: el script que lo junta todo16:00 - Preguntando al sistema en lenguaje natural19:00 - Monitorización con watch y notificaciones21:00 - Ventajas: local, sin coste y sin dependencias23:00 - Cierre: el tridente JSONMás información y enlaces en las notas del episodio

Claude Design went viral at launch, but has been kinda crickets since.

This week's episode is a little different. Instead of interviewing a guest, Vance sits down with Claude AI to explain how he actually uses artificial intelligence every day—not as a novelty, but as a practical tool for solving real business problems, making better decisions and reclaiming valuable time. If you've been wondering how to use AI effectively, this conversation is packed with practical advice you can apply immediately. Rather than focusing on hype, Vance explains the prompting techniques, AI workflows, custom instructions, agents, GitHub repositories, podcast analysis, bookkeeping, website development, and thinking strategies that have transformed the way he works. Whether you're just getting started with AI or already experimenting with tools like Claude and ChatGPT, this episode will help you get more value from them. When not podcasting, Vance is invited to give talks on tangible communication skills. He teaches how to connect with employees, colleagues and family so that you can negotiate, have better relationships and achieve your higher goals. https://articulate.ventures/lbc https://www.legacyinterviews.com/ #ArtificialIntelligence #AI #ClaudeAI #AIProductivity #PromptEngineering

A good research idea is not always a good research question. Bruno Hochhegger, MD, PhD, speaks with host Amit Gupta, MD, about choosing research questions that are clinically relevant, feasible, and worth pursuing in real-world settings. Listen to their discussion in episode 1 of The Early Career Researcher's Playbook, an AJR Podcast Series. Full article: https://www.ajronline.org/doi/10.2214/AJR.26.35586 *Key Takeaways Defining Clinical Relevance: A strong research question must answer a direct patient management issue, such as determining if a nodule is benign or malignant. The Feasibility and Sustainability Matrix: Moving from simple case reports to professional science requires navigating EMRs, securing IRB authorizations, and finding reliable grant funding. The AI Implementation Trap: While building artificial intelligence models on GitHub has become more accessible, adequately validating these tools for real-world clinical practice remains a massive, frequently underestimated hurdle. Multidisciplinary Research Networks: True feasibility requires nonmedical input; successful projects demand early feedback from IT departments, technologists, and referring surgeons to ensure workflows survive reality. *Key Moments 00:00 Intro and Welcome 01:18 The Importance of Small Steps: Lessons from a Failed MRI Lung Cancer Screening Trial. 04:30 Defining Clinical Relevance and the Crucial Role of the Physician-Researcher. 07:47 Assessing Feasibility: Navigating EMRs, IRB Approvals, and Data Access. 08:45 Research Sustainability: Securing Grants and Transitioning from Voluntary to Professional Science. 10:50 The AI Feasibility Trap: Why Validating Models is Harder Than Coding on GitHub. 16:08 Identifying the Key Indication: Solving Direct Patient Management Questions. 21:51 Beyond Mentorship: Building a Network Across IT, Technologists, and Referring Clinicians. 28:51 Establishing Niche Expertise: Strategic Advice for Radiology Residents and Fellows Follow AJR on Social Media LinkedIn: https://www.linkedin.com/showcase/ajr-radiology/ YouTube: https://www.youtube.com/channel/UCfFAYezkLMxJGMgIJLN0Dpg Instagram: https://www.instagram.com/ajr_radiology/ TikTok: https://www.tiktok.com/@ajr_radiology X: https://x.com/AJR_Radiology BlueSky: https://bsky.app/profile/ajrradiology.bsky.social Threads: https://www.threads.com/@ajr_radiology *These portions of the page were generated using artificial intelligence (Google Gemini) and then reviewed for accuracy.

Jem's wiped out after installing seven sculptures in a single day, while Justin's machining a 65-inch timber spear gun and fighting the ShopSabre's Y-axis overheating. They talk Shopify bill wins, Justin's new private dashboard app, GitHub issues, packing-station kiosks, voice notes, and the surprisingly good iOS 27 beta. Plus AR headphone daydreams and why documenting warehouse workflow is still the hardest game.Watch on YoutubeDISCUSSED:✍️ Comment or Suggest a TopicJem's benderTwo-year comparison Shopify Bill ꘎ $15 vs $1500Fangs + Stops experience with SpeargunShopify recoveryUnifi upgradesFU PF at LB?Arbitrary AR DesireShopSabre issueFulfillment organization questionFlag to edit, make a noteRake - backupsNew Siri---Profit First PlaylistClassic Episodes Playlist---SUPPORT THE SHOWBecome a Patreon - Get the Secret ShowReview on Apple Podcast Share with a FriendDiscuss on Show SubredditShow InfoShow WebsiteContact Jem & JustinInstagram | Tiktok | Facebook | YoutubePlease note: Show notes contains affiliate links.HOSTSJem FreemanCastlemaine, Victoria, AustraliaLike Butter | Instagram | More LinksJustin BrouillettePortland, Oregon, USAPDX CNC | Instagram | More Links

Jake Hildreth, Principal Security Consultant at Semperis and Microsoft MVP, is back on the podcast fresh off a trip to PowerShell Conference Europe, where he and Andrew co-presented a session on securing PowerShell. Jake also gave his own talk on Stepper, his open-source module for building resumable, step-by-step scripts — a tool that's grown considerably since his last appearance on the show. The two dig into what makes PSConf EU such a standout event, the refreshing lack of elitism in the PowerShell community, and the updates Jake's been shipping, including named steps, built-in logging, and secret suppression. The conversation winds into burnout, the importance of actually taking your vacation days, and how the same mindset that drives good automation — knowing when to stop and reset — applies to taking care of yourself. Key Takeaways: Stepper has gotten some meaningful quality-of-life updates since Jake last appeared on the show, including named steps, automatic logging, and the ability to suppress secrets from logs — making it more practical for real-world production scripts. PSConf EU punches above its weight as a conference experience: technically deep but genuinely welcoming at every skill level, with none of the elitism that can creep into security-adjacent events. Your vacation time is a benefit, not a backlog item. Jake makes the case that getting good at separating your work time from your off time isn't a soft skill — it's a sustainability practice. Guest Bio: Jake Hildreth is a Principal Security Consultant at Semperis, a Microsoft MVP in both PowerShell and Identity/Access, and a recovering sysadmin with 25 years of IT under his belt. He's probably best known for building Locksmith, the open-source AD CS auditing and remediation tool, but he's also the creator of Stepper, Deck, BlueTuxedo, and PowerPUG! — a suite of tools designed to make identity security a little less painful for the admins who live in it. When he's not untangling Kerberos or chasing down ADCS misconfigurations, he goes by "horse" in the PowerShell Discords. Resource Links: Jake Hildreth's Website: jakehildreth.com Jake's GitHub: github.com/jakehildreth Stepper (Resumable PowerShell Scripts): github.com/jakehildreth/Stepper Locksmith (AD CS Auditing & Remediation): github.com/jakehildreth/Locksmith Locksmith 2 (Next-Gen AD CS Toolkit): github.com/jakehildreth/… PowerShell Conference Europe: psconf.eu PDQ Discord: discord.gg/PDQ The PowerShell Podcast on YouTube: https://youtu.be/Rqkuaeps_jM

In this episode, Lex chats with Jeff Grimes — who is Head of Live Events Products at Perplexity, the AI company that has evolved from an "answer engine" into an "agent platform" built around Perplexity Computer, its multi-agent digital worker. They discuss how Perplexity has shifted financial research from the how to the what, letting a user describe an outcome in a single sentence while Computer orchestrates 20+ frontier models, direct tool calls to licensed live data, and finance-specific skills to produce the artifact. Jeff explains the enterprise strategy behind traceability - the north star that 100% of every quantitative figure traces back to its source filing - alongside bring-your-own-license connections via MCP and the consumer "personal CFO" vision powered by Plaid. They explore what 5x revenue growth on a 34% headcount increase signals for finance jobs, and why the future looks like a 24/7 family office that proactively surfaces and, with permission, executes financial actions for everyone. NOTABLE DISCUSSION POINTS: The “how to what” collapse is the real product thesis, not just better models. The shift to zero-shot rests on three stacked unlocks: direct tool calls to licensed live data (Quartr for earnings transcripts, unusual whales for insider and political holdings, SEC filings for historicals) instead of relying on web freshness; a thinking-model router that orchestrates 20+ frontier models in parallel, matching the model to the job (a heavy thinking model for macro analysis, a lighter one for ticker-matching 550 names); and ~20 opinionated finance skills (DCF, three-statement, LBO, comps) tuned through expert-led evals. Together they turn one sentence into a polished equity-research artifact. Traceability is the enterprise wedge, framed as “don't trust and verify.” The stated north star is that 100% of every number in any output is hover-traceable back to the source filing - pre-scrolled to the page, highlighted, with the full chain of calculations exposed. The framing inverts the usual “trust but verify”: assume the user won't trust the model, so trust must be earned per number. Paired with bring-your-own-license via MCP (FactSet, LSEG, Morningstar, CarbonArc, PitchBook), this is the concrete answer to why regulated institutions get comfortable adopting. The productivity and jobs signal is quantified and lived internally. Perplexity grew annual run rate 5x while increasing headcount only ~34%. Computer began as a company-wide Slack bot where every request was visible to all employees; Jeff now runs 9–10 scheduled cron jobs each morning and says essentially all code is written first by his agents. On the consumer side, the emergent pattern is build-your-own long-tail apps that no roadmap-bound product could serve - a DraftKings-addiction accountability system that emails a user's spouse on any bet, or a GitHub-style heatmap of daily spending - which is the real substance of the personal-CFO bet. TOPICS Perplexity, Perplexity Computer, Perplexity AI, Google, Shadebot, Plaid, Yodlee, Claude, ChatGPT, AI, Artificial Intelligence, LLM, CFO, financial services, AI commerce   ABOUT THE FINTECH BLUEPRINT

Jennifer Pattison Tuohy of The Verge joins the show this week! Is Google's AI Search failing kids? OpenAI could be releasing its first device: a proactive AI-smart speaker. OnePlus is exiting the US & European market. And Microsoft's Comic Chat is now open source. Common Sense Media finds Google's AI Overviews and AI Mode miss warning signs like suicidal ideation and validate disordered eating, especially concerning. Bloomberg reports that OpenAI is building a screen-free, proactive smart speaker for the home. Katie Collins from CNET joins the show to talk about OnePlus's withdrawal from the US & European market. And Microsoft releases the code for its iconic mid-90s comic-strip IRC client (birthplace of Comic Sans) on GitHub. Hosts: Mikah Sargent and Jennifer Pattison Tuohy Guest: Katie Collins Download or subscribe to Tech News Weekly at https://twit.tv/shows/tech-news-weekly. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Sponsors: blackhat.com/us-26 and use code TWIT rippling.ai/tnw framer.com/tnw zscaler.com/security